Advise · Capability
Know what is worth building
before you build it.
We help teams turn an opportunity, problem or early product idea into something clear enough to invest in — defining who it is for, what it needs to achieve, what belongs in the first release and what should be tested before engineering begins.
When the idea needs evidence
Building is expensive. Uncertainty should be cheaper.
Product work often begins with enthusiasm rather than evidence. There may be a customer need, an internal opportunity or a promising idea — but important questions around the user, value, scope and commercial case are still unresolved.
We help answer those questions before they become expensive engineering decisions.
- 01The opportunity is clear, but the product is notThere is a recognised need or opportunity, but the proposition, users and product shape are still too broad.
- 02Too much is being treated as MVPEvery feature feels important and the first release is becoming indistinguishable from the long-term vision.
- 03There is no shared definition of successBusiness, product, customers and technology teams are working from different assumptions about what the product should achieve.
- 04Investment needs stronger evidenceLeadership needs confidence that the problem, proposition and path to value justify further spend.
The decisions
Before asking how to build it, decide what deserves to exist.
- 01Who is this for?Which users or customers matter first, and what meaningful problem are we solving for them?
- 02What outcome are we trying to create?What should change for the customer and for the business if the product succeeds?
- 03What belongs in the first release?What is essential to prove value, and what can wait until there is evidence to justify it?
- 04What must we learn before committing?Which assumptions carry enough risk to justify research, prototyping or technical validation?
- 05How should success be measured?What behaviour, adoption, commercial or operational signals would show that the product is working?
- 06What should happen after validation?Proceed, reshape, narrow, sequence differently — or stop before more capital is committed.
Specialist services
Shape the product — or test the riskiest assumption first.
What you leave with
Enough clarity to commit — or not.
The exact outputs depend on the opportunity, but a Product Strategy & Validation engagement should make the next investment decision substantially easier.
- 01A defined product opportunityA clear statement of the user, problem, business opportunity and intended outcome.
- 02A sharper propositionWhy the product should exist, what makes it useful and where it creates differentiated value.
- 03A prioritised first releaseA defensible distinction between what needs to ship first, what can follow and what should not be built yet.
- 04Validated assumptionsResearch, prototypes, feasibility work or other evidence around the areas carrying the most risk.
- 05Defined success measuresClear behavioural, operational or commercial indicators that can be instrumented once the product is live.
- 06A usable handoverEnough definition for Omniway Build, your internal team or another engineering partner to begin without restarting discovery.
Our approach
Reduce uncertainty before increasing investment.
- Understand the opportunityBusiness goals, users, existing behaviour, constraints and what triggered the idea.
- Frame the problemSeparate the real customer and business need from the features already being imagined.
- Shape the propositionDefine audience, value, journeys, capabilities and what would make the product worth using.
- Validate what mattersTest the assumptions carrying enough uncertainty to change the investment decision.
- Define the first moveTurn the evidence into scope, priorities, success measures and an executable next step.
Our perspective
Product strategy should remove choices, not create a bigger backlog.
A product strategy is useful when it makes investment decisions easier. We try to narrow uncertainty, establish priorities and create enough evidence for the team to move confidently.
- 01Problem-ledStart with the user and business problem, not the requested feature.
- 02Evidence-informedUse research where it can materially change the decision rather than validating what everyone already wants to believe.
- 03Ruthlessly prioritisedA useful first release is deliberately smaller than the complete product vision.
- 04Engineering-awareProduct choices consider feasibility, architecture, integrations, data and the cost of operating what gets built.
From direction to execution
Validate the product — then keep moving.
Product Strategy & Validation can stand alone, hand over to your teams or continue through Omniway without repeating the discovery already completed.
FAQ
Common questions about Product Strategy & Validation.
It defines what product should be built, for whom, why it matters, what should come first and which assumptions need evidence before significant engineering investment is committed.
Transformation & Technology Strategy considers broader organisational and technology change. Product Strategy & Validation focuses on a specific product, proposition, platform or customer opportunity.
No. We can start with a business problem, customer need, market opportunity or an existing product that needs to be rethought.
The smallest coherent release that delivers meaningful value and generates useful evidence — not simply the smallest possible list of features.
Yes, where a prototype is the right way to answer an important question around usability, proposition, workflow or feasibility.
Yes. The depth depends on the engagement and may include stakeholder interviews, customer research, workflow analysis, testing and behavioural evidence.
Yes. Product strategy work can begin with an existing roadmap, backlog or specification and assess whether priorities still reflect the user and business case.
Yes. The same work can continue through Product & Software Engineering, although the strategy can also be handed to your internal team or another engineering partner.
It depends on the uncertainty involved. A focused product strategy or validation sprint may take a few weeks, while a broader discovery involving multiple user groups, prototypes or technical feasibility work can run longer.
No. We also use Product Strategy & Validation to rethink existing products, prioritise major new capabilities, challenge an existing roadmap or decide whether a product should continue in its current direction.
