Documentation Index
Fetch the complete documentation index at: https://docs.productbrain.com/llms.txt
Use this file to discover all available pages before exploring further.
ProductBrain’s core insight: a single dataset rendered two ways, with animated transitions between them.
The Boardroom and the Factory Floor
Strategic thinking and delivery execution are different cognitive modes. The risk is making strategic decisions from the factory floor — or doing factory work when you should be in the boardroom.
ProductBrain collapses this problem. The Planning Tree is the boardroom: what are we building and why? The Delivery Map is the factory floor: build the thing that was decided. But because they’re the same data, you’re never fully disconnected from one while working in the other. The strategic lens is applied during delivery, not instead of it.
Planning Tree (Strategy)
The tree shows why you’re building something.
Goal: Help shoppers save money
└── Need: Compare prices across stores
└── Approach: Barcode scan with live lookup
└── Job: Price comparison shows for scanned barcode
- Map out what you’re betting on
- Check that work connects to business value
- Explore approaches for a need
- See the full strategic landscape
Delivery Map (Execution)
The matrix shows what you’re shipping and when.
| Barcode Scan | Manual Entry | AI Prediction |
|---|
| MVP | Price shows for scan | Entry form works | — |
| Phase 2 | Multi-store comparison | Favorites list | Photo prediction |
- Plan what ships in the next iteration
- See the balance of work across approaches
- Check if an iteration is overloaded
- Track progress on delivery
The bridge: Approaches
Approaches are the node type that lives in both worlds. In the tree, an approach is a strategic bet hanging from a need. In the matrix, it’s a column header with jobs beneath it.
This is why approaches carry both strategic metadata (Kano classification, measure) and delivery metadata (their child jobs carry iterations and status). The approach is the handoff point between the person setting the agenda and the person (or agent) delivering the work.
Switching between views
Toggle between views at any time. The data doesn’t change — only the layout. Goals and needs are visible in the tree but not the matrix. Jobs are visible in both. Approaches are the column headers in the matrix and branch points in the tree.
Tasks and the Misc column
Tasks (standalone items outside the hierarchy) appear in a Misc column in the Delivery Map. They’re visible alongside your structured work but clearly separated — a reminder that not everything fits the tree, and that’s fine.
