06
Six controlled stages
Every stage ends with a usable approved output.
Discovery, analysis, requirements, prototype, architecture, and development handover.
Engagement Process
Move forward through approved decisions—not accumulated assumptions.
Each stage produces a usable output and a clear approval point before the next layer of product or technical detail begins.
06
Approval at every stage
Discovery, analysis, requirements, prototype, architecture, and development handover.
Stage Gates
Every phase has an input, output, and approval point.
This prevents detailed work from continuing on top of an unresolved assumption.
Discovery
Understand the business opportunity and establish a shared starting point.
Inputs
- Idea or client request
- Existing notes or documents
- Known constraints
Activities
- Stakeholder questions
- Goal and user analysis
- Scope exploration
Outputs
- Discovery findings
- Initial scope
- Open-question register
Approval Gate
Business direction confirmed
Analysis
Turn raw information into a coherent product and requirement structure.
Inputs
- Discovery findings
- Stakeholder feedback
- Existing workflows
Activities
- Gap analysis
- Business-rule mapping
- Risk and dependency review
Outputs
- Requirement map
- Scope recommendation
- Risk register
Approval Gate
Scope boundaries accepted
Requirements
Create the level of documentation required for approval and implementation.
Inputs
- Approved scope
- Business rules
- Priority decisions
Activities
- BRD or SRS writing
- User stories
- Acceptance criteria
Outputs
- Requirement baseline
- Prioritised backlog
- Traceable decisions
Approval Gate
Requirements signed off
Prototype
Validate how users will move through the product before engineering begins.
Inputs
- User flows
- Screen requirements
- Brand direction
Activities
- Wireframes
- Responsive interface
- Interaction review
Outputs
- Interactive prototype
- Screen inventory
- UX decisions
Approval Gate
Experience direction approved
Architecture
Define a practical technical direction aligned with scope and quality needs.
Inputs
- Functional scope
- Quality attributes
- Integration needs
Activities
- Technology evaluation
- Threat modelling and control mapping
- Data, API, privacy, and security design
Outputs
- Architecture blueprint
- Security and compliance control map
- Deployment direction and technical risks
Approval Gate
Technical direction approved
Development Handover
Package the approved product so a team can estimate and execute with confidence.
Inputs
- Approved requirements
- Prototype
- Architecture
Activities
- Roadmap planning
- Vendor briefing
- Team and milestone guidance
Outputs
- Handover package
- Delivery roadmap
- Evaluation checklist
Approval Gate
Ready for development
Start at the Correct Stage
Existing work is reviewed before anything is repeated.
An engagement can begin with discovery or start later when reliable requirements, prototypes, or architecture already exist.