Product strategy
Start with the audience and outcomes the product needs to address. Feature selection comes later.
Compare features by the customer problem they solve and their business impact.
Decide what to build now and what can wait.
For CPOs, heads of product, CEOs 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
Sales needs a feature to close a deal. A customer wants a customization. Leadership sees a new opportunity. Product teams keep delivering, but the backlog grows faster than the company can evaluate the value behind each request.
“This feature could close the deal.”
“We need this in the next release.”
“Which problem deserves our attention?”
“What should we stop building?”
Delivering more features can increase maintenance and complexity while leaving important customer problems unresolved. Product prioritization should determine where capacity deserves to go.
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.
Teams spend time on requests whose relevance was not compared with other opportunities.
New features, dependencies and exceptions increase the effort needed to maintain and explain the product.
Important needs lose space to the most visible request or the most influential stakeholder.
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.
Start with the audience and outcomes the product needs to address. Feature selection comes later.
Examine relevant customer needs and how well they are currently met. This helps distinguish value to preserve from hypotheses for creating more value.
Connect evidence to positioning, offering choices and economic assessment. The roadmap translates that direction into development choices.
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.
A clear view of the relevant opportunities that deserve product and technology capacity.
The reasons supporting each priority and the assumptions that still need to be tested.
What to preserve, investigate, develop, review or defer in upcoming decisions.
Specific deliverables are defined according to the decision and the agreed scope.
When the team has more development opportunities than available capacity.
When deal requirements and customer customizations keep changing the product direction.
When the product offers many capabilities but its value is becoming less clear.
When additional hiring or technology investment depends on clearer product priorities.
It is the decision about where to concentrate product, technology and development capacity. It connects relevant customer problems and business opportunities to choices about what to preserve, build, investigate or defer.
Product prioritization guides where product capacity should focus. Roadmap prioritization addresses what enters the delivery plan now, what waits and what should leave it. The two can be connected depending on the decision.
Yes. Existing features, customer commitments and new opportunities can be assessed together to guide what to preserve, improve, review or stop prioritizing.
An executive interpretation connecting the evidence to the decision your leadership needs to make. Direction for product priorities: A clear view of the relevant opportunities that deserve product and technology capacity. Evidence behind the choices: The reasons supporting each priority and the assumptions that still need to be tested. Guidance for the product agenda: What to preserve, investigate, develop, review or defer in upcoming decisions. 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 product and development capacity. We will assess how to help your leadership choose a clearer focus.
Help me prioritize our productRequest 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.