Skip to main content
The Delivery Map is the execution side of ProductBrain. It shows the same data as the Planning Tree, reorganized for delivery.

​
Reading the map

  • Columns are your active bets
  • Rows are iterations, your delivery slices
  • Cells are jobs. The proof that each bet is being delivered
  • Misc column holds standalone tasks (outside the tree hierarchy)
Above each column, you’ll see the bet label and its parent need and goal. The strategic context for why this work exists.

​
Filtering by iteration

Select an iteration from the dropdown to focus on what’s shipping now. Only bets with jobs in that iteration appear as columns. This keeps the view clean. No empty columns cluttering the map.

​
Show All toggle

When an iteration is selected, toggle Show All to see ghosted jobs from other iterations. This shows what’s coming, future work queued under the same bets, without losing focus on the current delivery slice.

​
What to look for

  • Balance: Is the iteration pulling from multiple bets, or is everything under one? A healthy iteration progresses several bets by a small amount rather than one bet by a large amount.
  • Depth vs breadth: Are you going too deep on one bet when you should be getting a first version of another into the world? The advanced version can wait.
  • Size: Does the iteration have a reasonable number of jobs, or is it overloaded?
  • Progress: Which jobs are done? Which are still open? Is one bet blocking others?
  • Gaps: Are there bets with no jobs in any iteration? That’s a bet you’ve made but haven’t committed to delivering.
  • What’s coming: Toggle Show All to see future work queued under the same bets. This tells you how deep each bet goes. Whether you’re one iteration away from done or three iterations deep with more planned.

​
Planning an iteration in the map

The Delivery Map is where iteration planning becomes tangible. A few principles that help: Start with the theme. What’s this iteration about? “Onboarding”, “API access”, “Payment flow”. The theme tells you which bets should have jobs in this slice. If you can’t name the theme, the iteration is probably a grab bag. Rocks first, then sand. Pick 2-3 bet-level deliverables that define the theme. Add supporting jobs. Fill remaining capacity with small fixes and tasks. If the iteration is all small tasks and no strategic work, it’ll ship but won’t move the needle. Cross-cut the tree. The best iterations pull from multiple goals. An iteration scoped entirely under one goal might be too narrow. Check if there’s related work under other goals that belongs in the same theme. If it keeps growing, split it. An iteration that accumulates jobs session after session without shipping is a planning problem. Ask: what’s the minimum I could ship today? Split, ship the core, defer the rest.

​
Switching back to the tree

Click the view toggle to return to the Planning Tree. The data is the same. You’re just changing the lens from “what are we shipping” to “why are we shipping it.”