Chapter 2 of 14
The home page
The home page reads in ten seconds: what the workspace holds, what waits on someone within fifteen days, where the bets stand, and what moved in the last thirty days.
The line of counts
Under the workspace's name, a line counts what it holds, and each count opens the matching page: initiatives, in progress, late (in red, only when an initiative not done is past its end date), scored, bets, committees, and the maturity out of 100 with its stage, or the diagnostic's progress.
The maturity stages: Exploration below 25, Foundation below 50, Acceleration below 75, Leadership from 75.
First steps
In a new workspace, the block Your first committee in five steps tracks what makes an empty workspace something a committee reads. Each step ticks itself off from the data, and opens where it is done: name your products, add at least three initiatives, write a bet and attach initiatives to it, prepare your first committee, invite the person who decides with you. The block disappears once a first session is closed. Hide folds it before that.
To handle
To handle gathers what waits on someone within fifteen days, in five groups named by a verb. Your own rows come first, then what is late, then by date. Six rows per group, then "n more". A group's counter turns red when something in it is late.
| Group | What it holds |
|---|---|
| Decide | The questions of a live session (or of a closed session left unanswered), and the bets that are due: target reached, or horizon passed. |
| Do | The decisions taken whose action is waiting. In red when the due date has passed. |
| Prepare | The sessions within fifteen days: "no decision asked yet" or "n decisions to prepare". A session whose date passed without being opened says so. |
| Record | The gains to record, the usage and metric readings due on validated business cases, and "nobody answers for it" when the owner is missing. |
| Replan | One line for the initiatives past their planned date, naming the oldest, and the drifts GitHub announces. |
The bets
The Bets table gives each bet with its State, its Last reading, its Initiatives and its Horizon. Active bets first, then confirmed ones. A sentence sums up: "Of n bets: 2 on track, 1 to watch…".
| State | Rule |
|---|---|
| Confirmed | The committee confirmed the bet. |
| Reached | The last reading reaches the target. |
| Horizon passed | The decision date has passed. |
| No metric | The bet has no start and no target. |
| No reading | No reading, or the last one is more than thirty days old. |
| On track | The share of the way covered is at least the share of the time elapsed. |
| To watch | Behind by up to twenty points on the time elapsed. |
| Late | Behind by more than twenty points. |
Last 30 days, and what remains to fill
Last 30 days lists up to eight dated events: a Decision taken, an action Done, an initiative Delivered, a bet Reading with the previous value, a Gain recorded.
Folded at the bottom, To fill says what the workspace cannot compute while it is empty: an unfinished diagnostic, no bet, initiatives not scored yet, in progress without a size, serving no bet, too many initiatives in progress at once, bets with no reading for more than thirty days.