Most organizations try to deliver first and figure out the human conditions later. I’ve run it the other way for fifteen years, across engineering and leadership, and I’ve measured the trade more than once: it holds.
Care to Deliver isn’t a process. It’s a sequence of conditions, and the order matters — skip a link and the chain breaks somewhere downstream, usually where you can’t see it yet.
Sharing is the hinge
Everything upstream of trust is cheap to say and hard to do. Sharing is where it gets real, because sharing isn’t only information — it’s context, uncertainty, mistakes, credit, and responsibility. That requires vulnerability, and sustained vulnerability is what becomes trust.
So a team that hoards knowledge, moves hard conversations into private channels, or stops asking questions in the open isn’t failing at communication. It’s protecting itself. The behavior is the symptom; the missing condition is safety.
Safety sits next to accountability, not instead of it
Psychological safety is a felt condition, not a policy. You can’t announce it. You can only produce the conditions where people ask questions, admit mistakes and challenge ideas without calculating the cost first.
But safety alone isn’t the goal:
Safety without accountability turns into complacency. Accountability without safety turns into fear.
Strong teams hold both at once. That’s the harder thing, and it’s the part most teams get wrong in one direction or the other.
Teams don’t fail suddenly — they stagnate
They slow down. Blockers stay unresolved, channels go quiet, meetings turn into reporting rituals, experimentation stops. From the inside it still looks functional.
The fix is movement, deliberately introduced. Fishermen used to put a shark in the tank during transport: without it the fish stop moving and arrive unhealthy. On a team, the shark is a person who asks the uncomfortable question, challenges the assumption, pushes for clarity. Not conflict for its own sake — the tank doesn’t need to be bigger, it needs something in it that keeps things moving.
Tension only works inside safety. Outside of it, it’s just pressure.
Key tensions
- Trust is earned and verified, not assumed. Delegate and verify — those are one move, not two.
- Disagree, then commit. After open discussion a leader may still choose a direction; the team commits and learns together.
- Activity is not outcomes. Shift the focus to what was achieved, not what was done.
What it produced
Outcomes that look improbable from the outside usually weren’t forced directly. They came from a system healthy enough to produce them.
That’s not a metaphor for me. As COO of a ~70-person consultancy it took client NPS from negative to 99, and employee eNPS from 10 to 95, in six months — no new metrics, no mandates, trust rebuilt first and delivery allowed to follow (full case study →). A year later leadership asked me to treat people as cost lines instead of the mechanism that was working. I left. That was a decision to protect the method, not to abandon it.