I asked the Lean Hospitals Coach to role-play as a manager bringing me a problem. Then it evaluated my coaching in real time. Within three exchanges, it caught a habit I teach others to avoid.
The Problem I Was Given
The scenario: a unit manager's daily huddle board has been empty for weeks. Staff are not speaking up. The manager has started writing problem cards themselves. They came to me and asked: “What should I do?”
I responded the way a lot of leaders respond. I thanked them for raising it and asked:
“Why do you think staff aren't speaking up?”
Where I Got Caught
The coach's evaluation was direct: “You opened with appreciation and a question, which signals support. But thanking someone for asking is a gesture, not coaching. It doesn't move the conversation forward.”
Then it went further: “‘Why' too early pushes for explanation, not observation. A stronger opening would cut directly to the behavior:
‘What happens during those huddles?'”
I have been telling leaders for years to ask about what they see before asking why. And the first thing I did when someone brought me a problem was ask why.
Knowing the right coaching move and making it under pressure are apparently two different skills.
The Broken Loop
My next question was better:
“What happens when people share a concern or idea?”
The manager told me: “Last week, a nurse mentioned we keep running out of IV pumps on the night shift. I said we'd look into it, but we never circled back. She didn't bring anything up the next day.”
There it was. People do not stop speaking up because they lack courage. They stop because the system taught them that speaking up goes nowhere. The nurse raised a problem, nothing visible happened afterward, and the silence in the next huddle was entirely predictable.
Related Post: Fear and Futility: Why People Don't Speak Up-and How Lean Leaders Can Remove Both
The Mistake I Teach Others to Avoid
I asked:
“What is taking up your time? How can you free up time for this improvement work?”
The coach: “You jumped ahead. The manager just told you the system for tracking problems does not exist. By pivoting to workload, you made this about personal prioritization instead of fixing the loop for the team.”
The manager had just described a missing process — no way to track issues, no visible follow-up, no closure. And I walked right past it to ask about time management.
I teach people to stay on the process. I skipped the process.
What the Coach Summarized
Three patterns to watch for:
1) Stay closer to the current process. Keep questions anchored in what is visible, trackable, and habitual for the team — not just the manager's intentions or schedule.
2) Surface the broken feedback loop before shifting to anything else. The reason people go silent is almost always that nothing visible happened the last time they spoke up.
3) Ask about observable behavior, not reasons. “What happens during the huddle?” before “Why aren't people speaking up?” — especially early, before you have earned the right to ask why.
Why This Is Worth Telling You
I could have published a post about how well the Lean Hospitals Coach handles complex scenarios. That would be the normal marketing move. Show the product working. Highlight the features. Maybe impress people.
Instead I am telling you it caught me making mistakes I teach others to avoid.
The number of people who can coach this way is small. And the ones who exist are not available at 11pm when you are replaying a difficult conversation in your head.
That is the gap this tool fills. A practice partner that holds the discipline when you cannot find a sensei.
An Unexpected Use
Here is one use case that surprised me: you can record yourself coaching someone — a real conversation with a staff member, a manager, a team — and upload the transcript to the Lean Hospitals Coach. Ask it to evaluate your approach. It will tell you where you asked too early, where you diagnosed before listening, where you skipped the process question.
Obviously, ask permission before recording — and frame it as your own development, not surveillance. “I am working on my coaching skills and would like to record this so I can review my approach afterward” is honest and respectful.
It is like having a coaching supervisor review your tape, except the supervisor is available any time and has infinite patience for replaying the same three minutes.
The Real Difference
Here is the thing about AI tools: most of them are built to make you feel good. They validate your thinking, organize your ideas, and produce tidy action plans. They are optimized for satisfaction.
This one is optimized for learning. Those are different things.
A good coach makes you uncomfortable. A good AI product makes you comfortable. I am building something that violates the second rule in service of the first. The frustration of being questioned — of having your assumptions challenged, your “why” returned with a “what do you actually see?” — that is not a flaw in the product. It is the product.
If you want to see what it catches in your coaching, the free demo is at leanhospitalsbook.com/start. Ask it to role-play a scenario with you. Bring a real situation. See what habits surface that you did not know you had.
You might find out, as I did, that the gap between what you know and what you do is wider than you thought.
