Understand the context.
Map the people, tasks, business constraints, and existing systems around the opportunity. Bring research, stakeholder knowledge, and current evidence into one working picture.
When it helps
Start with what matters.
Before choosing features or technology, establish who the product is for, what it needs to change, and which questions could alter the plan. Discovery gives the next investment a reason.
- 01An idea needs a first useful version.
- 02An existing product has competing priorities.
- 03A complex brief needs a feasible path.
What we take on
The work behind the progress.
Test the assumptions.
Use interviews, focused prototypes, and technical exploration to examine the questions with the greatest consequence. Choose the method to match the uncertainty.
Shape the scope.
Separate the essential journey from later possibilities. Define the behaviors, dependencies, and constraints a first release needs to handle.
Plan the next move.
Make priorities, sequencing, and tradeoffs visible. Connect the intended experience to a staged plan for design, engineering, and validation.
Decisions & detail
Depth where
it makes a difference.
Specific questions, deliberate tradeoffs, and useful artifacts that make the work understandable.
Choose the right way to reach people.
A responsive web application, installable web experience, and native or cross-platform mobile app solve different needs. Consider how people arrive, which device capabilities matter, offline behavior, distribution, accessibility, and the cost of maintaining each surface.
The decision: one shared experience, separate platform experiences, or a staged approach—with a reason for each.
Make business constraints part of the plan.
Budget, time, procurement, existing platforms, and internal ownership shape what can be delivered responsibly. Define the critical journey first, then use experiments or a smaller release to reduce the unknowns before expanding.
The decision: what the first release must prove, what can wait, and what evidence would change the plan.
What you take forward
Something you can work with.
The exact scope is agreed around your product. These are the kinds of outputs that turn the work into a useful next step.
- A shared product brief and definition of success
- A map of assumptions, risks, and dependencies
- Key journeys or a focused prototype
- A prioritized scope and staged delivery plan
You leave with a direction to evaluate, the reasoning behind it, and a clearer basis for the next decision. The answer may be to build, test something smaller, or change the plan.
Feasibility belongs in the conversation early. Accessibility needs, sensitive data, integration constraints, and operational ownership can all change what a sensible first release looks like.
How we build in careA practical question