Discover
Understand the field, users, constraints and risks.
- Our role
- Listen, review existing tools and identify constraints.
- Your role
- Share your workflows, goals and key contacts.
A shared understanding of the need
A clear project, from scoping to handover.
We define the priority journey, deliverables and acceptance criteria, then work through testable versions. The schedule accounts for required content, access and approvals.
From need to handover
Frame
Turn the need into scope, priorities and success criteria.
- Our role
- Define priorities, dependencies and the proposal.
- Your role
- Decide on scope and confirm priorities.
An agreed scope and proposal
Design
Prototype journeys, architecture and visual language.
- Our role
- Design the journeys and prepare a prototype.
- Your role
- Review screens and confirm essential workflows.
A prototype to explore
Build
Develop in verifiable increments with regular demos.
- Our role
- Develop, test and present progress.
- Your role
- Try each version and bring feedback together.
A testable solution, ready for delivery
Deploy
Prepare data, security, documentation and production.
- Our role
- Prepare the launch and check agreed user journeys.
- Your role
- Approve content, access and release.
A launch prepared together
Support
Measure, improve and transfer knowledge.
- Our role
- Document, train and clarify ongoing support.
- Your role
- Learn the tool and assign its owners.
The keys to move forward
After launch.
Your organisation should ideally own the domain and service accounts. The proposal sets out access, code and documentation to hand over, acceptance and training. New features are quoted separately; maintenance and support require an agreement on scope and working arrangements.
- clear steps
- 6
- continuous accountability
- 1
A concrete problem to solve?
A website to launch, an application to imagine, a process to simplify. Tell us about your business and what you want to change.