Skip to main content

Framework Overview

A systematic approach to building software products from idea to production.

The Pipeline​

Every software project follows this 9-phase pipeline:

Idea -> Capture -> Validate -> Design -> Spec -> Architect -> Build -> Test -> Ship -> Learn
                                                                                  |
                                                                                  v
                                                                            (iterate)

Phases​

1. Capture​

Identify the problem worth solving. Document the pain point, who experiences it, and initial solution ideas.

Key outputs:

  • Problem statement
  • Target user definition
  • Initial hypothesis

2. Validate​

Before building, verify the problem is real and the solution is viable.

Key outputs:

  • User research findings
  • Competitive analysis
  • Go/no-go decision

3. Design​

Define the user experience and product design.

Key outputs:

  • User flows
  • Wireframes/mockups
  • Interaction patterns

4. Spec​

Document detailed requirements for what to build.

Key outputs:

  • Product Requirements Document (PRD)
  • Feature specifications
  • Acceptance criteria

5. Architect​

Design the technical solution.

Key outputs:

  • System architecture diagram
  • Technology choices (with ADRs)
  • Data models
  • API contracts

6. Build​

Implement the solution.

Key outputs:

  • Working code
  • Unit tests
  • Documentation

7. Test​

Verify quality and functionality.

Key outputs:

  • Test results
  • Bug fixes
  • Performance benchmarks

8. Ship​

Deploy to production.

Key outputs:

  • Production deployment
  • Release notes
  • Monitoring setup

9. Learn​

Gather feedback and iterate.

Key outputs:

  • Usage analytics
  • User feedback
  • Next iteration plan

Using the Framework​

For New Projects​

Start at Phase 1 (Capture) and work through each phase sequentially. Don't skip phases - each builds on the previous.

For Features​

Existing products adding features can start at Phase 3 (Design) or Phase 4 (Spec), depending on how well-defined the feature is.

For Bug Fixes​

Jump directly to Phase 6 (Build), but ensure you have clear acceptance criteria.

Templates​

Use these templates to document each phase:

Next Steps​

Dive into each phase for detailed guidance: