WORKSPACE / ALLOCATION
Decide the split first.
How the company spends its capacity, before a single topic is scored.
Planning horizon
| Period | Start date | End date | State | Candidate cut-off | Allocation |
|---|---|---|---|---|---|
| Jan 1, 2027 | Mar 31, 2027 | scoring | Confirmed | ||
| Oct 1, 2026 | Dec 31, 2026 | closed | Historical | ||
| Jul 1, 2026 | Sep 30, 2026 | closed | Historical | ||
| Apr 1, 2026 | Jun 30, 2026 | closed | Historical |
Teams and capacity
| Team | Capacity |
|---|---|
Dev days, not person days. Capacity can include AI. Set it first: the split and team distribution below build on it.
Overall split · Q1 2027
Keep the lights on: bug fixes and maintenance. Content owned by Engineering.
What engineering builds to reduce KTLO and speed up delivery. Content owned by Engineering.
Strategic product bets that move the strategy pillars forward. Owned by Product.
Customer topics, prioritized by modified WSJF and the cut line. Owned by Product.
Drag a divider to move capacity between its two neighbors, in 5% steps. The customer prioritization and cut line use only each team’s Customer dev days.
Team distribution
| Team | KTLO | Productivity | Strategic | Customer | Total | |
|---|---|---|---|---|---|---|
| Core Platform120 dev days | 120 / 120 | |||||
| Integrations90 dev days | 90 / 90 | |||||
| Mobile60 dev days | 60 / 60 | |||||
| Column totals | 54 of 54balanced | 27 of 27balanced | 95 of 94.5balanced | 94 of 94.5balanced | 270 |
Allocation decided.
Decided by Product · Dec 7, 2026
Restore the original Harbourline demo data and clear your confirmations.