Scoping the thing worth building first
Turning a broad ambition into a first release that can be built, shipped and measured.
What you get
- Scope definition and MVP cut
- User and job-to-be-done mapping
- Success metrics
- Phased delivery plan
- Estimate with assumptions stated
What changes
- A first release small enough to actually ship
- Agreement on what success looks like before building
- Cut features recorded as phase two rather than argued twice
When teams call us
- A brief that has grown to sixty features
- A team unsure which half to build first
- A launch with no definition of whether it worked
Process
How the work runs
The same four phases whichever engagement model you pick, each ending in something you can read.
Brief
What decision you are trying to make, and what would change your mind. An audit without a decision behind it is a document nobody reads.
- Decision stated
- Constraints named
- Access arranged
Review
Code, architecture, infrastructure and process, weighted toward the parts that cost money when they fail.
- Code read
- Architecture mapped
- Team interviews
Findings
Written up and prioritised by impact against effort, with the reasoning included so you can disagree with it.
- Prioritised list
- Effort estimates
- Reasoning shown
Handover
A working session with your team. The output is theirs to act on, with or without us.
- Walkthrough
- Q&A
- No lock-in
Not sure which service your project needs?
Most useful projects cross two or three of them. Describe the outcome and we will map it.