Managers do not need more slogans about trust or more exhortations to "be vulnerable", they need a method. The practical steps that shape how a team behaves when stakes rise, stakeholders conflict, and the schedule will not slow.
This is where Part 2 lives of this two-part series on psychological safety—in the domain of execution. The moves below are simple, but not easy. They demand management that is precise, transparent, and comfortable with discomfort—good luck with that I hear some sceptics say. But that is the price of candour and the precondition for clarity. It is also something that can provide value even when managers are far from great.
And in that world, guardrails matter.
For while a simple framework doesn't create great management, it can at least stop the worst habits from compounding. It gives teams something to hold onto when the person in the chair isn't up to the task. To reject structure because a small subset might abuse it is to mistake an edge case for the norm.
Good managers won't need this kind of scaffolding; bad ones won't use it well. But for the large population in the middle—the competent-but-stretched, the developing, the overwhelmed—structure is not Orwellian. It's oxygen.
Below are the six moves I have found to be most useful with management teams. They require no internal taskforce, no three-day retreat with matching ropes course, and no culture consultants. They require only thought and consistency.
1. Call Failures by Their Proper Names
In part one, I distinguished between intelligent failures and basic mistakes. Part two now puts that distinction to work.
Dr Robert N. Winter
If you haven't already, read part one.
Teams spiral into fear when all failures are treated the same. They spiral into complacency when none are scrutinised. Managers can break those cycles by creating a shared language that classifies failure at the point of review:
