The gap between a good workshop and a changed practice is usually about two weeks. Here is how to close it.

This week

Run your one micro-habit on real work. Just the one you chose in Studio 5. Do not add the other four.

Put your Explorer Workbook somewhere you will actually see it — the field artifacts are short by design, meant to be used in the middle of a working day rather than studied afterward.

This month

Run the loop three or four times: do the work, read the trace, name the pattern, choose the next practice. That is enough repetitions to tell whether the habit is holding, and to notice which capability you reach for most.

Then add a second one. Not before.

Your five artifacts

• Four Conversations Field Log — when you catch yourself, or your AI, jumping straight to implementation.
• Discovery Conversation Transcript — when a conversation changes a design and you want to remember why.
• Testability Review Card — before you ask AI for an implementation.
• Collaboration Protocol — before AI acts, on team or solo work.
• Personal Learning Loop — the ten minutes after, that most people skip.

If you want to bring this to your team

Do not present the Collab. Run one thing and let people notice.

• Bring one AI transcript to a retro and review it together with the Studio 5 labels. Twenty minutes.
• Try the four mob roles for a single work session — Navigator, Shepherd, Verifier, Driver — with AI assigned a role too.
• Ask one question in your next planning conversation: what behavior here has to be independently verifiable?

Teams adopt practices they have felt work. They rarely adopt practices they have been told about.

A realistic warning

The pull back toward speed is strong, and it does not feel like a decision. It feels like a busy week. When you notice you have stopped looking at traces, that is not failure — it is the signal to run the loop once, deliberately, and start again.