Do you produce a strategy document?

We produce a recommendation with the evidence behind it and the trade-offs named, usually with a prototype or design artefact that makes the option concrete. Strategy that cannot be made tangible tends not to survive contact with delivery.

Can you help us execute afterwards?

Yes, and it is common, a strategy engagement frequently continues into product design work. It can equally be handed to your in-house team, and the recommendation is written to be actionable either way.

Expertise / Digital Product Consulting

Product decisions are business decisions that happen to have screens.

Where the product should go, what to stop investing in, whether to build or buy, and what kind of team the next two years need. These are the questions that determine whether any design work matters.

Start a conversationProduct Strategy in full

Who this page is for

For executives and product leaders making portfolio and capability decisions.

Related capability

Product strategy
Product discovery
User research
Market research
UX audits
Product audits
Customer journey mapping

The questions we are usually brought in for

Whether a product line is worth continuing. Whether to build, buy or partner for a capability. How to sequence a platform migration without stalling delivery. Whether to serve a new segment with the existing product or a separate one. Where design capability should sit and what it should own.

Each has a design-shaped component and none of them is a design question. Bringing a design partner into them early is unusual and tends to produce better answers, because the practical consequences surface before the strategy is committed.

Deciding what to stop

Most product portfolios carry features and product lines that survive because nobody has a mechanism for ending them. They consume engineering attention, complicate the interface for everyone and generate support cost out of proportion to usage.

We map usage against maintenance and support cost, then make the case for what to sunset. This is consistently harder to get agreed than building something new, and the value is usually larger.

The operating model behind the product

Team topology determines product coherence more reliably than any design process does. When one team owns provisioning, another billing and a third the admin console, users experience three products stitched together, and no amount of design system work fixes it.

Where we find that, we say so plainly. It is an organisational finding and it should be written as one rather than softened into a design recommendation nobody can act on.

Signals

When this work is worth doing

If two or more of these are true, the conversation is probably overdue.

The roadmap is a list of requestsThere is no thesis, only accumulated obligations.
A platform decision is being made on instinctExpensive, slow to reverse, and worth an evidenced view.
Nothing has been sunset in yearsComplexity is compounding and nobody owns the decision to stop.
Design sits too far downstreamBrought in to execute decisions it could have improved.

How we scope it

Three ways this usually runs

Durations are typical rather than fixed. We scope after the first conversation, not before.

Product strategy review
4 to 6 weeks
Portfolio, roadmap and market position assessed against usage evidence and cost.
You receive
- Portfolio assessment
- Strategic options
- Recommended direction
Build / buy / partner assessment
3 to 5 weeks
A specific capability decision, evidenced against cost, risk, time and experience implications.
You receive
- Options analysis
- Cost & risk view
- Recommendation
Design operating model
6 to 10 weeks
Where design capability should sit, what it owns, how it is governed and how it is measured.
You receive
- Operating model
- Team topology
- Governance & measurement

Digital Product Consulting

Questions we hear before we start

We work at a smaller scale, closer to the product, and we can prototype an answer rather than only model it. The trade-off is honest: we are not the right partner for a large organisational transformation programme, and we will say so.