Process

A navigation chart. Not a checklist.

The eight stages below are iterative, not linear. We return to earlier stages as we learn. Every stage has a purpose, deliverables, and questions it answers.

01

Observe

Understand the real problem without contaminating it with our assumptions. This is the most undervalued stage — and the most important.

Deliverables

  • ◆Field research synthesis
  • ◆Assumption inventory
  • ◆Stakeholder interview notes
  • ◆Observed behavior summary

Questions resolved

  • What are people actually doing (not saying)?
  • What problem are we really solving?
  • What assumptions are we making that need testing?
02

Understand

Synthesize raw observations into patterns, opportunities, and a clear problem statement worth solving.

Deliverables

  • ◆Mental model map
  • ◆Opportunity framework
  • ◆Clear problem statement
  • ◆Prioritized risk register

Questions resolved

  • Where is the real pain?
  • Which problems are worth solving?
  • What would success look like?
03

Design

Create the minimum coherent experience — the simplest thing that could work for a real user solving a real problem.

Deliverables

  • ◆Information architecture
  • ◆Interaction principles
  • ◆Visual language definition
  • ◆Design decision log

Questions resolved

  • What's the simplest thing that could work?
  • What must we include vs. defer?
  • Where will users struggle?
04

Prototype

Build the fastest thing that can be tested with real users. A prototype is an argument made tangible, not a deliverable.

Deliverables

  • ◆Functional prototype (Figma or code)
  • ◆Test script and evaluation criteria
  • ◆Usability session recordings
  • ◆Iteration recommendations

Questions resolved

  • Does this work for real users?
  • Where does it break down?
  • What assumptions were wrong?
05

Build

Engineer the real product — reliable, secure, and ready for real use at launch scale.

Deliverables

  • ◆Working production software
  • ◆Technical documentation
  • ◆Test coverage and CI pipeline
  • ◆Deployment and infrastructure

Questions resolved

  • Is it reliable and secure?
  • Does it scale with the first 1,000 users?
  • What breaks under load?
06

Launch

Ship to the real world, carefully. Launch is not the end — it's when real learning begins.

Deliverables

  • ◆Production deployment
  • ◆Monitoring and alerting setup
  • ◆Launch communication and messaging
  • ◆Success metrics definition

Questions resolved

  • What are our success metrics?
  • How do we know if it's working?
  • What's the plan if something goes wrong?
07

Refine

Learn from real use and improve. The first version is always wrong about something — the goal is to find out what, quickly.

Deliverables

  • ◆Usage analytics review
  • ◆User feedback synthesis
  • ◆Iteration backlog
  • ◆Issue triage and resolution

Questions resolved

  • What surprised us?
  • What do users actually use vs. what we thought?
  • What's the highest-leverage improvement?
08

Grow

Scale what works. Build the systems, team, and infrastructure that let the product grow beyond its initial scope.

Deliverables

  • ◆Growth framework and scaling plan
  • ◆Team handoff documentation
  • ◆Technical roadmap
  • ◆Operational runbooks

Questions resolved

  • What needs to change as we grow?
  • What should we build next?
  • When does the team need to expand?

Ready to walk through the process together? Start by telling us what you're trying to build.

Begin the process →