I've lost count of how many workshops started with someone asking for solutions.

The request changes slightly. Sometimes it's delivery, sometimes quality, sometimes ownership or communication. The proposed fixes change too. More automation. Better planning. Another review. A different process. After a while I stopped paying much attention to the proposed solutions. They're useful, but they tell you much more about where people currently are than where they need to go.

What interests me is the moment when the conversation shifts.

A team starts by talking about deployments. Twenty minutes later they're discussing trust. They begin with testing and end up talking about incentives. They complain about communication until someone casually mentions a decision nobody remembers making. Suddenly half the conversation makes more sense.

Those moments are difficult to engineer. They don't happen because someone asked the perfect question. I started writing down the things I kept reaching for during those workshops. Questions. Facilitation techniques. Ways of separating observations from interpretations. Small experiments that helped teams test their assumptions instead of arguing about them.

I originally wanted to post a list of questions. Cheat Sheet, if you will. Eventually they became something much larger than my original notes.

I've attached the first public version of that playbook below. It's released under CC BY 4.0 because I'd rather see it evolve than sit on my hard drive.

If you end up using it, changing it, or discovering places where it breaks down, I'd genuinely like to hear about it.

After all, that's usually where the conversation shifts.