1. Diagnose
Examine the request, available evidence and the people affected. Clarify the problem before defining the solution.
Our approach
Logic Before Code
Don’t start with the solution.
Every business challenge has options. Before you build something new, we help you understand what really needs to change—and choose the right next step.
Before the investmentPut the decision on the table.
Improve what existsBuild something newSimplify how work happensValidate before investing
The useful next step depends on what we discover.
01
The problem behind the problem
The initial request is often a symptom, not the real issue. We dig deeper to understand what’s actually happening—across people, processes, data and customers.
Follow the causeThe request is visible. The cause may be elsewhere.
- Missing information
- The same data, requested twice.
- Unclear ownership
- Who takes the next step?
- Disconnected systems
- A handoff that never arrives.
Illustrative possibilities. Investigate before choosing a solution.
What we explore
- Are customers struggling to book?
- Is the sales team missing information?
- Do existing systems not talk to each other?
- Is the real issue a process or team capability?
- Would a simpler solution work better?
02
A five-stage way of working
We follow a structured but flexible process. Not every engagement needs all five stages—we use what’s relevant to your situation.
Explore the stages ↓A flexible processEach stage should move the decision forward.
- 01
Diagnose
Understand the real problem
From request to evidence. - 02
Prioritise
Focus on what matters most
Make the order explicit. - 03
Design
Develop and compare options
Make trade-offs visible. - 04
Execute
Support implementation
Put direction into practice. - 05
Improve
Measure and refine
Learn from what changes.
Use the stages your situation needs.
What happens at each stage?
2. Prioritise
Compare the opportunities against the goals, constraints and dependencies. Choose where attention matters most.
3. Design
Develop realistic alternatives and make the trade-offs explicit. Agree what is worth testing or pursuing.
4. Execute
Help translate the direction into priorities, responsibilities and delivery decisions. The support depends on the engagement.
5. Improve
Review what changes in practice, test the assumptions and refine the next step as new evidence appears.
03
We look at the whole business
Product, technology, people and commercial decisions don’t exist in isolation. We examine how different parts of your business influence each other.
One connected businessFollow one decision across the business.
- Customers
- Marketing & sales
- Operations & processes
- People & teams
- Product & technology
- Finance & commercial
- Customer need
- The promise made to the customer.
- Team handoff
- Who owns the work, and what happens next?
- Business impact
- What changes in the systems and economics?
A local change can create a consequence elsewhere.
04
How we make recommendations
We compare realistic options, consider trade-offs and recommend the approach that best fits your goals, constraints and context. There is no predetermined answer—it could be build, buy, improve or wait.
See an example ↓05
Human judgment, technology and AI
We use research, analytics, automation and AI where they add value. But understanding context, weighing trade-offs and making the final decision remains a human responsibility.
Human judgment stays in the loopTools can prepare the work. People must own the call.
Technology and AI
Faster analysis · Better insights · More options
Human judgment
Context and experience · Trade-off decisions · Accountability
Set the question · Context · Assisted analysis · Options · Review the work · Accountability
Context → assisted work → human review.
06
See our thinking in practice
Here’s a simplified example of how the same request can lead to different recommendations, depending on what we discover.
A founder says
“We need a new CRM.”
Select a finding to see how the recommendation changes.
What we discover
Teams cannot see a reliable customer history across tools.
Possible recommendation
Compare integrating existing systems, improving data ownership and replacing the CRM.
What we discover
The issue may sit in ownership, handoffs or follow-up routines.
Possible recommendation
Clarify responsibility, improve the follow-up process and test whether the current CRM can support it.
What we discover
Important needs remain unmet after checking the process and existing capabilities.
Possible recommendation
Define the gaps, compare suitable platforms and assess the cost and effort of migration.
Illustrative example. A finding changes the next step.
07
What you actually receive
The output follows the problem—not the other way around. Depending on the engagement, you may leave with one or more of the following:
What the work leaves you withUseful artefacts. Built around the problem.
Clear problem statement
The issue, the context and the questions.
Prioritised opportunities
A visible order for what matters.
Workflow map
Ownership and handoffs made explicit.
Decision brief
Options, trade-offs and the next step.
Product roadmap
The sequence, rather than a feature pile.
Go-to-market plan
Who to reach, and how to approach them.
Implementation support
Decisions that help work move forward.
Ongoing leadership
Product judgment within the team.
The output follows the problem, not the other way around.
08
What we believe—and what we don’t
Our working principlesAn examined decision beats an automatic answer.
We believe
- Understand the problem before proposing a solution
- Examine evidence, people and business context
- Compare alternatives and acknowledge trade-offs
- Make decisions that teams can act on
- Revisit decisions when new evidence appears
We don’t assume
- Every problem needs new software
- More features automatically mean more value
- The most sophisticated option is always best
- A strategy document alone creates results
- The first recommendation must always remain correct
Make the reasoning visible. Revisit it when the evidence changes.
You don’t need to arrive with a perfectly defined problem.
Sometimes you know exactly what isn’t working. Sometimes you only know that the next investment feels too important to get wrong.
We can start by understanding the situation together.
Discuss a Decision ↗A useful first conversationYou bring the context. We work through it together.
The next step can be small. It needs to make sense.