From request to need
A request suggests a solution. Research identifies the customer outcome and the context behind it.
Compare customer requests, internal ideas, and product improvements before committing your team.
Use evidence to choose what to build first and explain what can wait.
For CPOs, product managers, product leaders and CTOs.

Companies George Eich has worked with
Institutions and startup programs
While switching platforms, the team used customer needs to decide which features to include and which to defer.
The team used customer evidence to decide when to strengthen its core product and when to expand its offering.
“We gained a more strategic view of the product and were able to prioritize the roadmap and the company’s positioning.”Feedback shared with the Institute · English translation
A deal adds a feature. A customer escalates a request. Leadership introduces another initiative. The roadmap keeps growing, deadlines move and the team reorganizes its work. Being in the plan starts to mean being promised rather than being chosen.
“Can we promise this for next quarter?”
“What should enter now?”
“Which commitment can leave the plan?”
“Where does our request stand?”
A roadmap cannot protect focus if every new request becomes a commitment. Leadership needs to choose what deserves capacity now and make clear what should wait.
The risk is committing capital, people and technology to priorities that add effort and complexity without increasing the company's ability to create and capture value.
The team absorbs more commitments than it can sustain without displacing important work.
Competing initiatives keep changing the sequence and expectations around delivery.
Urgent requests enter the plan without a sufficiently clear connection to relevant product value.
The Study investigates the needs behind the options before priorities are ranked. The company and the Institute define the decision, customer groups and scope; findings inform resource allocation.
A request suggests a solution. Research identifies the customer outcome and the context behind it.
Quantitative selection shows who shares the priority; ICAN measures perceived fulfillment of the need.
An updateable evidence base informs the roadmap. Feasibility, complexity and value-capture possibilities complete the assessment.
Bring the decision your company needs to make.
An executive interpretation that connects evidence to the decision your leadership needs to make. The deliverables reflect the agreed business context and scope.
The opportunities and commitments that deserve the current delivery focus.
Reasons supporting what should enter now or wait, and the assumptions still unresolved.
What to preserve, review or remove before adding new work to the roadmap.
Specific deliverables are defined according to the decision and the agreed scope.
When the next quarter has more candidate initiatives than available capacity.
When sales commitments repeatedly alter the delivery plan.
When an overloaded roadmap raises questions about hiring or outsourcing.
When the roadmap has expanded but its connection to product priorities has weakened.
It is the decision about what should enter the delivery plan now, what should wait and what should leave it. It connects relevant opportunities to current capacity before more commitments are made.
No. The focus is the choice of priorities rather than the software used to display or manage the roadmap. The engagement can use the company's existing context and information.
Yes. Existing commitments can be reviewed alongside new opportunities to guide what to preserve, defer, revise or remove from the current plan.
An executive interpretation connecting the evidence to the decision your leadership needs to make. Direction for the next roadmap choices: The opportunities and commitments that deserve the current delivery focus. Evidence behind the sequence: Reasons supporting what should enter now or wait, and the assumptions still unresolved. Guidance for existing commitments: What to preserve, review or remove before adding new work to the roadmap. Specific deliverables are defined according to the decision and the agreed scope.
The reference is 3 to 6 weeks for structured research and executive analysis, depending on the scope. Timing depends on the decision, access to information and participant availability. The first conversation helps assess the appropriate format.
Tell us what is competing for your roadmap. We will assess how to help your leadership choose what enters now and what should wait.
Help me prioritize our roadmapRequest a conversation with the George Eich Institute.
We have received your request. Our team may contact you to discuss your decision and next steps.
Back to the pageShare your contact details and main decision. Role and revenue are optional.
Suas informações foram recebidas. A equipe entrará em contato para entender sua decisão e avaliar o próximo passo. O envio não representa um agendamento automático.
Voltar ao início ↑Preview mode. No data will be sent.
We will contact you to discuss your decision and next steps.