Bring it to your team

1. Open this week's model and read the one-line versions for executives and engineers aloud.
2. Ask one person where they have seen it at work, for better or worse.
3. Put the first question to something the team is working on now.

Post the link in your team channel every Monday; the model of the week changes then.

1. Five minutes: show the diagram (download it as PNG for a slide) and explain the idea.
2. Ten minutes: read the example scenario together. Where would it have played out differently here?
3. Fifteen minutes: apply the three questions to one real system or decision.
4. Ten minutes: read "How it misleads you". Where could we misuse it?
5. Five minutes: agree one action or experiment, and who owns it.

One model per session. Depth beats breadth.

1. Pick the playbook that fits the moment and switch on worksheet mode.
2. Write the decision in a sentence at the top, so everyone answers the same question.
3. Work through the steps, about ten minutes each. A scribe types the answers into the worksheet.
4. Download the Markdown and turn it into an ADR or a decision paper.

Invite at least one person who disagrees with the leading option.

1. Everyone brings one problem they are seeing, in a sentence.
2. Match each to the symptoms page, or to the nearest one.
3. For the two most common, discuss the first model listed and what it suggests.
4. Each person leaves with one experiment to try before the next clinic.

Collect the problems that matched nothing. They are candidates for new models.

1. Choose three models from the "Reviewing a solution design" playbook that fit the design.
2. Copy their questions into the review invitation, so the author can prepare.
3. Open the review by agreeing which of the questions matter most.

Reviews go better when the author has seen the questions first.