Understand what is really happening before deciding what to change.
Discovery creates a shared evidence base before organisations commit to solutions.
We investigate users, staff, existing services, processes, technology and organisational constraints to understand what is actually happening.
The result is a clearer view of the problem, the people affected and the opportunities worth pursuing.
Explore Discovery ↓Goals · Behaviour · Experience
Workarounds · Knowledge · Friction
Workflow · Decisions · Hand-offs
Platforms · Data · Constraints
Ownership · Policy · Priorities
Measures · Feedback · Evidence
Start with evidence rather than assumptions about the solution.
Understand the problem before designing the response.
Organisations often begin transformation with a proposed answer.
A new platform, redesigned interface or process change may appear obvious before the underlying causes of the problem have been understood.
Discovery creates space to understand the current service, the people using and delivering it, the constraints shaping it and the evidence already available.
That evidence creates a stronger foundation for prioritisation, service design and investment decisions.
Replace assumptions with a clearer picture of reality.
What do people actually need?
Understand goals, behaviours, expectations, difficulties and the outcomes people are trying to achieve.
How does the current service really work?
Explore the customer-facing service alongside the people, processes, systems and decisions supporting it.
Where are the real problems?
Separate symptoms from underlying causes and understand where friction is being introduced.
What should we address first?
Use evidence to identify meaningful opportunities rather than attempting to change everything at once.
Build the evidence from more than one perspective.
The exact mix depends on the service, the questions being explored and the evidence already available.
User interviews
Understand needs, behaviours, experiences and expectations directly from the people using the service.
Stakeholder interviews
Gather organisational knowledge from service owners, subject-matter experts, operational teams and decision makers.
Service observation
Understand what teams actually do, including workarounds and dependencies that may not appear in documented processes.
Existing service analysis
Review journeys, processes, systems, documentation, policies and current service artefacts.
Evidence review
Bring together existing customer feedback, analytics, service measures and operational evidence.
Evidence synthesis
Connect qualitative and quantitative findings to identify patterns, themes, risks and opportunities.
Research becomes useful when the evidence connects.
Interviews alone are not the final output.
Discovery brings different evidence together to create a shared view of the service, the problem and the organisational context.
Patterns across customer evidence, operational experience, processes, systems and data help distinguish isolated complaints from structural service issues.
Research, data and existing knowledge.
Find relationships across the service.
Understand what the evidence means.
Define the issues worth solving.
Decide where change can create value.
Evidence people can understand and use.
Outputs are designed to help teams move from fragmented knowledge to shared understanding and better decisions.
Research findings
Clear synthesis of user, stakeholder and operational evidence.
Current-state view
A clearer picture of how the existing service operates today.
Needs & pain points
Evidence-based understanding of the people affected by the service.
Problem statements
Clearly framed service problems grounded in research rather than assumptions.
Opportunity areas
Prioritised opportunities for redesign, improvement or deeper investigation.
Recommended next steps
A practical evidence-based direction for the next stage of work.
Discovery should reduce uncertainty, not create more documentation.
Agree what needs to be understood.
Define the key questions, boundaries, stakeholders and evidence already available.
Gather evidence from the service.
Speak to users and staff, observe service delivery and review existing information.
Connect the evidence.
Identify patterns, contradictions, dependencies and root causes.
Turn insight into direction.
Frame priority problems and identify the most useful next stage of work.
Useful when the answer feels obvious but the evidence is not.
Discovery is particularly valuable before major design, technology or transformation decisions become difficult to reverse.
Different stakeholders have different explanations for the same service problem.
Customers are experiencing friction but the root cause has not been established.
A transformation programme is about to begin and needs a clearer evidence base.
A new system or platform is being considered before service needs have been fully understood.
Teams know individual parts of the service but lack a shared end-to-end view.
Existing data, feedback and organisational knowledge are fragmented across different teams.
Need to understand what is really happening?
Tell us what is unclear, where the service is struggling or what your organisation needs to understand before making a decision.
Start a conversation ↗