Double Diamond
One committed problem statement and one committed solution concept, each chosen against recorded alternatives, handed to Concept-to-Launch for delivery
Inputs
- Problem area or opportunity statement (symptom-level, solution-free)
- Customer access or existing research corpus
- Available resources (budget, team, timeline)
- Constraints that any solution must respect
What BOB Does
- continuous-discovery → gather problem-space signal from customers; capture symptoms and unmet needs without proposing solutions
- jtbd-building → map customer jobs, push/pull/anxiety/habit forces, and current workarounds across the gathered signal
- Commit ONE problem statement. Record every framing considered and why each rejected one lost
- ask-boardroom → convene the board to generate and debate at least three genuinely distinct solution concepts for the committed problem
- prioritization-craft → score the competing concepts against a single framework and produce a ranked list
- Commit ONE solution concept. Record the runners-up and the reason each lost
- ship-decisions → classify the committed concept's reversibility and set explicit go/no-go criteria
- [[Concept-to-Launch]] → execute build, positioning, launch, and measurement for the committed concept
Outputs
- Discovery Signal.md
- JTBD Map.md
- Problem Statement.md (with rejected framings)
- Solution Concepts.md (three or more, with the board's debate)
- Concept Ranking.md
- Ship Decision.md
- Everything produced by [[Concept-to-Launch]]
Time Savings ~1-3 weeks for the two diamonds, before delivery begins manual → automated with agent assistance
Try It "A problem or opportunity needs deliberate exploration before a solution is committed — the team is at risk of building the first idea that surfaced"
Compounding Each run refines templates and context — 6 automated steps improve with accumulated data