Services / Strategy
Product Definition
Define what the product actually is — core journeys, scope boundaries, and version one priorities.
Overview
What this involves
From validated insights, we define what the product actually is. Core user journeys, must-have versus nice-to-have, and where the boundaries of version one should sit. Product definition bridges the gap between strategy and execution, giving your team a clear, shared understanding of what they are building and why.
Deliverables
What you get
- Product requirements document
- Core user journey maps
- Feature prioritisation (MoSCoW or RICE)
- Version one scope definition
Questions
Frequently asked
- How detailed is the product definition?
- Detailed enough to start designing and building with confidence, but not so detailed that it becomes a waterfall specification. We define the what and why at a level that leaves room for the design and engineering team to figure out the best how.
- What if requirements change after definition?
- They will. Product definition gives you a framework for making good decisions as things evolve — it's not a rigid contract. We build in the decision-making principles, not just the decisions.