Why your people behave the way they do.
Thirteen things leaders say about their people, and where each one actually came from.
Here are thirteen things leaders say. Most people will recognise several, and nobody recognises none.
Pick yours. Then hold it in mind, because the rest of this is about where it actually came from.
Now the useful part. Every one of those is a behaviour, and behaviour is not a personality trait held by four hundred people simultaneously. It is a response. It was learned here, from something, and the something is usually still running.
The reflex, and why it fails
The instinct with any of the thirteen is to treat it as a people problem. Talk about mindset. Ask for more ownership. Book the workshop. Wonder about hiring differently.
It rarely works, and there is a reason it rarely works. You are trying to talk people out of a conclusion they reached by watching. That is an unfair fight, and the watching wins.
So try the other direction.
Run it backwards
Take the first one, because it is the one I hear most: my team are not ambitious enough.
Do not ask why they are like that. Ask what someone would have to be feeling to write a careful goal on purpose. Probably something like this: reaching and missing costs me more than comfortably delivering.
Then ask where they would have learned that. Not from a values slide. From watching.
From the review where the team that missed an ambitious goal had a harder time than the team that hit a small one. From the stretch goal that arrived with no extra resource, which quietly told everyone it was decoration. From the colleague who flagged a risk early and got treated as the problem rather than the person doing their job.
Nobody announced any of that. It was all just visible.
What they saw, what they feel, what they do. That is the whole chain, and it runs in both directions, which is the part that matters most. Because what one person does becomes what the next person saw. The disengagement that follows an unexplained promotion is not the end of the story. It is the next lesson, delivered to everyone watching.
This is why culture spreads without anyone teaching it. It is being taught constantly, by events.
Truths, half-truths and lies
Now the part that surprises leaders most, and the reason this cannot be fixed by saying the right thing more loudly.
What people know is a mix of three things: what actually happened, what they inferred, and what they were told by someone else who inferred it. All three behave identically. All three get acted on as fact.
So somebody was not punished for missing an ambitious goal. But it looked that way to one person, who mentioned it to two others, and within a quarter it is simply understood that ambition is dangerous here. Nobody is lying. Nobody is even wrong exactly. An event with no explanation attached got given one, because a gap in a story does not stay a gap.
Half of what your organisation believes about you is inference, and you have never seen the list.
That is not a criticism of anyone's people. It is what minds do with incomplete information, and it is the strongest argument I know for saying the true thing early. Silence is not neutral. It gets filled, usually with the least generous available explanation, and then that explanation starts teaching too.
Two more, quickly, so you can see the pattern
Nobody tells me bad news early. What would you have to feel? That the messenger carries the cost. Where would you learn it? From the check-in that opens with “are we on track?”, which is a question with a preferred answer. From the project that went amber and got scrutiny instead of help. Nobody instructed anyone to hide anything. The first question did the teaching, fifty times a year.
They do not take ownership. What would you have to feel? That judgement is not really wanted, and being wrong is more expensive than being slow. Where would you learn it? From a decision made at your level and overturned without explanation. From three approvals for something small. From a goal that arrived fully formed, which taught you your job was delivery, not thinking.
Notice what happens to the leader in these. In each case the behaviour they are frustrated by is a rational response to something they built, usually years ago, for a sensible reason they have since forgotten. That is not a comfortable thought, but it is a hopeful one. A design can be changed. A personality cannot.
Why a framework will not do this
This is where I have to be direct about what our work is, because it is easy to mistake it for things it is not.
A framework is a good thing. So is a template, and so is a well-run ideation session. They all share a property though: they are general. They arrive the same way at every company, which is exactly what makes them scalable, and exactly what makes them insufficient here.
Because none of the thirteen live in the general. They live in the specifics of your place.
- They live in the cracks: the handover nobody owns, the decision that gets made in two rooms, the thing everyone knows and nobody has written down.
- They live in the shadows: what happened to a person two years ago that is still setting the ceiling on what people will risk today.
- They live in legacy decisions: the approval threshold from when the company was forty people and cash was tight, still running at four hundred people, still teaching distrust to people nobody distrusts.
- And they live in experiences, which is the least tractable and most powerful of the four. The quarter that went badly. The reorganisation nobody explained. The manager who was tough on one person in front of others, once, three years ago.
You cannot hand a company a template for that. There is no worksheet for a shadow. The work is to go and find what is actually teaching, in this specific place, and that is why it looks less like a methodology rollout and more like an investigation.
How we actually work, then
Three disciplines, and they are what make this defensible rather than speculative.
We read what is happening, not what people say about it. Nobody says they do not trust their teams. They say they want more rigour around approvals. So we do not ask what the culture is.
We read it in how goals get set today. How people get noticed. What actually gets rewarded. What it means here to fail, and what it costs to ask for help. Then a set of reads we have built up over the years across a hundred organisations, combining the artefacts, the goals, the reviews, the last ten promotions, the initiatives that quietly stopped, with anonymous conversations with the people living inside it.
Both halves are necessary. The artefacts tell you what was decided. The conversations tell you what it taught, which is frequently not the same thing and is never written down anywhere. And the anonymity is not a courtesy. It is the thing that makes the second half true.
We do not put a belief in scope unless we can point at the thing it built. This matters. Without that rule this becomes an opinion about your leadership, which is a different conversation and a worse one. With it, everything we say back to you is anchored to something you can look at and check.
And nothing in it is about anyone being wrong. No belief on the list is wrong. “People need boundaries” is right in some contexts, and so is “trust people and get out of the way.” The problem is never the belief. It is a belief applied everywhere when it should apply somewhere, encoded into a process, and then forgotten while the process kept teaching. So the work is to make it explicit, decide where it genuinely applies, and check that how you run matches the decision you just made.
That is a design conversation, not a re-education programme. Which is the only version a serious leadership team will tolerate, and rightly.
By design, rather than by accident
Almost nobody designed how their company runs. It accreted. A threshold here, a ritual there, a reporting format someone inherited, a recognition habit that formed because one leader happened to praise one thing in one meeting. None of it was chosen as a system, and all of it is teaching as if it were.
That is not a failure. It is just what happens when a company grows faster than anyone can document it. But it does mean the answer to “why do our people behave like this” is nearly always sitting in the accretion, waiting to be read.
And when you do read it, the thirteen stop looking like thirteen problems. They start looking like a handful of decisions, most of them old, some of them no longer serving anyone, each teaching something you would not choose to teach if you were choosing today.
You get to choose today.
The one thing to take
If you only keep one sentence from this, keep this one.
You cannot out-message the evidence. Your people are gathering it every week, from your approvals, your promotions, your first question in the check-in, and what happens to the person who says something uncomfortable. That evidence will beat any announcement, every time, and it is the most changeable thing you own.
So the question is not how to get better people. It is a much better question than that.
What has your company been teaching, and did you mean to?
The Advantage Plan Ops Diagnostic is ten questions and three minutes, scored in your browser, and nobody sees your answers but you. It reads the environment you have built, not the people in it, and it is a compass rather than a verdict.
This is the part of our work that never fits on a slide: reading what your company is actually teaching, then redesigning the handful of decisions doing the teaching. If one of the thirteen is yours, that is a good and honest conversation to have.
Talk it through with Matt →
A UK-based strategy and OKR consultant and two-time SaaS founder with a venture-backed exit, Matt turns strategy into execution for teams scaling from tens to thousands. He co-founded ZOKRI in 2018, having previously co-founded Linkdex, a venture-backed enterprise SaaS platform he led to a trade sale. He writes the methodology behind these notes.