From the request to the underlying need
A request suggests a solution. Research identifies the outcome customers need and the context in which it matters.
Which feature will keep consuming maintenance capacity and adding complexity after release?
A feature with limited relevance may consume capacity long after launch. We help examine the decision, considering not just delivery but also maintenance, complexity and the cost of delaying other priorities.
For CPOs, Product Managers, CTOs and SaaS companies.

Companies served by George Eich
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
Customer requests, sales and internal teams compete for roadmap capacity. A feature may look small during development but keep requiring support, infrastructure, testing and maintenance with every release.
“It's just one feature to close the deal.”
“How many customers really need this?”
“We will have to maintain it in future releases, too.”
“Does the return justify the ongoing commitment?”
As these obligations accumulate, the team spends more time supporting past decisions while postponing improvements that could benefit more customers.
Da decisão à geração e captura de valor
A need may exist without justifying strategic priority. Research tests relevance, while leadership also considers capacity, feasibility and economic returns.
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 Value Matrix guides decisions across three horizons: strengthen Core Business, expand through Expansion and create through Innovation. The Study supplies evidence, while value creation, capture and ROI also depend on economic conditions and execution.
In The Need Gap 2026, median reach was 16.67%. Before turning a request into a feature, it is worth understanding its reach within the customer base supporting the product.
The study analyzed 1,423 needs across 59 companies. These figures describe need reach; the study did not measure feature costs.
Fonte: The Need Gap 2026, estudo de George Eich.
I want to review prioritiesAccumulating features for small groups can increase complexity without creating a proportional increase in product value.
Every new release must coexist with everything delivered before it.
Support and infrastructure can consume part of the expected returns.
Development capacity is divided between new work and maintaining what exists.
An executive interpretation that connects evidence to the decision your leadership needs to make. The deliverables reflect the agreed business context and scope.
A request suggests a solution. Research identifies the outcome customers need and the context in which it matters.
Quantitative selection reveals who shares the priority; ICAN measures perceived need fulfillment.
An updateable evidence base guides the roadmap. Feasibility, complexity and opportunities for value capture complete the choice.
Tell us what your company needs to decide.
Executive guidance on what moves forward, what waits and which existing commitments need reconsideration.
Which opportunities deserve the next cycle and which require more evidence.
Shared evidence for discussing relevance, reach and returns across teams.
Recommendations for evaluating choices that consume capacity with limited shared benefits.
As entregas específicas são definidas conforme a decisão e o escopo contratado.
When a contract or request pressures the next release.
When support and recurring adjustments compete with product evolution.
When the feature list grows and the value proposition loses clarity.
When you need to assess whether building more is the right decision.
The engagement identifies relevant customer needs and connects them with product decisions. We assess reach, expected benefits, delivery capacity and economic potential to guide what advances, waits or requires reconsideration.
Beyond development, consider support, infrastructure, testing, maintenance and the time the team cannot devote to other improvements. Prioritization brings these consequences into view before taking on new commitments.
Priority guidance is built around business context. Estimates, dependencies and schedules are reviewed with the responsible team to turn direction into a feasible plan.
Executive analysis of priorities, the reasoning behind choices and recommendations for the development agenda. Specific deliverables depend on the decision and agreed scope.
The typical reference is three to six weeks for structured research and executive analysis, depending on scope, information access and participant availability.
You describe the product, decision and competing deliverables. The conversation helps us understand the context and define how the Institute can contribute and what scope makes sense.
Bring the competing deliverables. We will discuss roadmap priorities in light of relevance, sustainability and returns.
I want to review prioritiesRequest a conversation with the George Eich Institute.
NEXT DECISION
Briefly describe the decision, investment or challenge you need to assess. We will follow up to understand your needs and agree on an appropriate scope.
Preview mode. No data will be sent.
We will contact you to discuss your decision and next steps.