You don’t adopt the method all at once. You swap in one piece at a time, lowest-risk first, and let the rest follow. Each step is a substitution for something you already do, so there’s nothing new to fund and nobody new to convince. Each also stands on its own — you can stop after any one of them and still be better off than you were.
The adoption path
Run these in order. Each swap earns the credibility for the next, and each lets the team feel the benefit before you ask anything more of them.
1. Replace your stand-up with a Daily Check-in
Start with the format; the discipline follows. Keep the same slot in the calendar. Change the question from “what did you do yesterday” to one Things to Figure OutThings to Figure OutEach person's one thing to figure out today, framed as a Why/How/What/When question that resolves into a Lesson Learned. (TFO) per person — exactly one thing each person commits to figure out today, phrased as a Why / How / What / When question. Add a line for the day’s lesson and a line for anything blocking. Every resolved TFO produces a Lesson Learned. That’s the learning loop, running from day one — and the Check-inDaily Check-inA 15-minute daily ritual where the team surfaces reality and unknowns rather than reporting status. becomes a written log of the day, not a status round-robin people forget by lunch.
2. Replace your demo with the Board Meeting agenda
Standardise the weekly close. Keep whatever demo slot you have, but adopt the structure: what was the problem, how we solved it, and the data that proves or disproves it — shown live in production or as concluded research, never as a mock-up. Split the hour evenly between the team presenting and the room discussing. You don’t need a formal Product BoardProduct BoardTwo or more stakeholders who see the team's weekly demo and coach it — the human in the loop, with no single lead. in the room yet; you need the agenda. The discipline of showing real outcomes against the original problem is the point — it forces #REALITY into a meeting that usually trades in optimism.
3. Rewrite one “epic” or project as an Initiative Document
Pick one piece of work already in flight and write it up against the template: the customer and their single shared problem, the solution, the ApproachThe ApproachThe multi-week narrative roadmap — titled weekly outcomes ("The one where…"), each with a demo, planned backwards from success. and its weeks, the team, the business case, and how you’ll measure success. Don’t roll it out everywhere — write one. Then hand it to someone who wasn’t in the room and watch how fast they get up to speed. That speed-of-onboarding is the test; a good Initiative DocumentInitiative DocumentThe PR/FAQ-shaped document where an initiative's context lives — customer, solution, plan, business case, and success metrics. is one a new hire can read in about half an hour and understand the whole bet.
4. Try five iterations of the Product Meetup
Five minutes per team, actuals only — what actually shipped or got learned, not what’s planned. Run it five times, because one or two won’t tell you anything; the value is in the rhythm and in the cross-team context it builds. The Product Meetup is a company-wide ritual, separate from the team’s weekly demo — treat it as the org’s window into running initiatives, not another status meeting.
What melts away
Most of the early pushback — “isn’t this writing overhead?”, “do we really need a board?” — dissolves after the first full cycle. Not because anyone wins the argument, but because the team watches the work it no longer needs disappear:
- The status updates the Daily Check-in absorbed.
- The alignment calls and re-explanations the Initiative Document made redundant.
- The scattered reporting the Board Meeting replaced with one standard close.
Nobody misses them. The time doesn’t vanish — it moves out of one-off meetings, chat threads, and ticket comments and into two documents the whole team can read. That redistribution is the method’s first dividend, and it’s the one that buys you permission for everything else.