No. The customer picks the page, not the number. John Cutler's November 5, 2026 post on engagement design as cooperative game design recommends prototyping a milestone-and-RAG version, a North Star framework, and a graded capability scorecard, then walking the client through them to see which they would play and which answers their boss. The version a client picks is the one that answers the boss, not the one that catches the slip, and a firm can lose that score without anyone noticing. In a forward deployed engagement the score exists before the game: the eval row set is the statement of work, done is the rows passing, the number is known at scoping (60 percent in Colin Jarvis's case, as reported on falkster.com), and the scorecard is four numbers, time to landing, reversal rate by day 60, generalization rate, and hours per deployment, each against the firm's own last quarter. The pull to extend the engagement is fixed by contract, hours falling over the term and the renewal price written before the pilot. Prototype the one screen the boss reads, in three shapes if you like; the number under all three is the same.
No. Let them pick the page their boss reads, in any shape they would open. The number underneath was fixed the day you signed, and it has to be able to turn red without anyone's permission.
Cutler's recommendation as published, the four scorecard numbers, and the contract lines are in Cutler Says Let the Customer Pick the Score. Kill the Scorecard Menu.. The numbers themselves are defined in The FDE Scorecard: Count What Stayed, Not Who Was Sent.
Last reviewed 2026-11-06 · 1 min read