Why your team lacks accountability (and how to fix it)
My 4-step accountability system
Hey there happy Tuesday team,
If you caught the sneaky teaser I posted yesterday… you’ve already had a tiny glimpse. But the team and I have been building something in secret for the last 5 months, something I wish existed when I was managing teams.
Tomorrow marks the start of a whole new era both for me personally, and for our business and team. I can’t wait for you to see what we’ve built.
11am sharp tomorrow morning, keep an eye on your inbox for the details.
But today we’re here to talk about the the a point in most management journeys where things start to feel so much heavier than they should.
This is the moment many managers describe in similar ways:
“My team won’t take ownership.”
“I feel like they don’t take accountability unless I micromanage the outcome”
“They only act when I tell them what to do.”
Was I the problem?
I remember a period early in my management career where I felt constantly interrupted. My team was engaged, communicative, and clearly comfortable coming to me, which I initially saw as a positive sign. I had worked hard to be approachable, supportive, and present and I wanted to be the kind of manager people could rely on.
But they reled on me for everything.
Small decisions were brought to me and work was paused until I gave input. People would message with “quick questions” that, if I am honest, they already knew the answer to. At first, I took this as trust. Over time, it became something else entirely.
The more I stepped in, the more they stepped back. And eventually, I reached a point where I realised something uncomfortable.
My team was failing to take ownership because I’d trained them not to.
Accountability is not a personality trait
One of the biggest misconceptions in management is that accountability is something individuals either have or do not have. That some people are naturally “owners” and others are not.
In reality, accountability is not a personality trait. It is a response to an environment.
If a team consistently defers decisions, avoids responsibility, or waits for direction, it is rarely because they lack capability or ambition. More likely it is because the system they operate within has taught them that this is the safest, or most efficient, way to work.
For example:
If decisions are always checked or overridden, why would people keep making them?
If managers regularly step in to “fix” things, why would the team try to solve them?
If ownership is unclear, it naturally will flow upward.
And so, without intending to, many managers create teams that are highly dependent on them, while simultaneously feeling frustrated by that very dependency.
The micromanagement line
Micromanagement does not usually begin with a desire to control. It begins with a desire to care.
You want things to go well. You want to support your team. You want to ensure standards are met and deadlines are hit. So when something feels uncertain or off-track, you step in. You offer guidance, provide clarity, or take something back to move it forward.
In isolation, these actions feel helpful. But over time, they create a pattern. And that pattern sends the clear message that: “The manager is ultimately responsible for making this work.”
Once that belief is embedded, behaviour follows. People escalate sooner, they seek reassurance more frequently and they hesitate to act independently because they have learned that they do not need to.
This is where many managers find themselves stuck. They are working harder than ever, trying to drive performance, while unintentionally reinforcing the very behaviours that are holding their team back.
My 4 step accountability system
After 10+ years managing teams myself, and training thousands of managers across different industries, I’ve seen the same pattern over and over again.
When a team lacks accountability, it’s rarely because the people are wrong.
It’s because the system is.
High-performing teams don’t rely on motivation, pressure, or “stepping up.”
They run on clear ownership and consistent behaviours that make accountability the default. And the good news is, this is something you can build.
Here are the four shifts I’ve seen work time and time again to move a team from dependency to real ownership:
Step1: Make the ownership explicit.
Every piece of work, every project, every outcome should have a clear owner. Not a group of people involved, not a shared responsibility, but one person who is accountable if it succeeds or fails. Without this clarity, accountability becomes diluted, and decisions are delayed.
Step 2: Change how you respond to your team.
When questions come your way, particularly those that do not require your expertise, resist the instinct to answer immediately. Instead, redirect the responsibility back. Asking “What do you think?” or “What would you do if I wasn’t here?” creates a moment of ownership.
It feels slow at first, but it builds capability far more quickly than providing answers ever will.
Step 3: Resist the urge to rescue
When something begins to slip, it is natural to want to step in and fix it. But each time you do, you reinforce the idea that accountability sits with you. Instead, hold your team within the problem. Ask them how they plan to resolve it. Support them, but do not take it away from them.
Step 4: Use questions, not answers
If you want your team to take ownership, you need to stop jumping in with answers and start leading with questions. The moment you tell someone exactly what to do, you take the thinking away from them, and over time they learn to rely on you instead of figuring things out themselves.
Questions do the opposite, they push responsibility back to the individual and force them to think, reflect, and come up with solutions.
For example, when something goes wrong, like missing a target, it’s easy to default to direction:
❌ “You’ve struggled to get responses, try emailing or posting next time.”
❌ “I don’t want to see the same results next month.”
But this keeps ownership with you.Instead, shift to questions:
✅ “Since we’ve struggled this month, what projects could you work on now to build better systems for next month or quarter?”
✅ “How can we make sure this doesn’t happen again?”
Instead of being told what to do, your team is thinking through the problem, owning the solution, and taking responsibility for the outcome.
A final reflection
If you recognise yourself in this, you are not alone. This is one of the most common challenges managers face, especially the ones who care the most about doing a good job. And the frustrating part is, it can feel like a people problem. Like your team just needs to step up.
But in reality, it’s almost always a system problem. And the good news is, that means it’s fixable.
That’s exactly what I’ve become a bit obsessed with solving over the last 6 months. And tomorrow, I’m going to show you what I’ve been building that solves this in a very scalable and fast way inside every team on the planet.
Something that gives you real visibility into ownership, accountability, and what’s actually happening inside your team, so you’re not guessing, reacting late, or carrying everything yourself.
But… More on that tomorrow 👀
H
There’s a warmth and groundedness to your writing that makes encouragement feel believable instead of cliché.
You write in a way that feels like someone gently reminding people they’re allowed to grow, rest, and become.
It’s fair to say that accountability is a system output, not a personality trait, and most managers do create the dependency that they’re frustrated by (especially new managers), and the story told here is a good way to introduce it.
Where it gets harder is the four steps. They’re all aimed at the manager in isolation, which both doesn’t scale and only works until the system above them pushes back and asserts its own expectations. When something slips because a manager held back and let their team own it, their boss (who is under their own pressure and incentive structure) notices the slip, not the development happening underneath it. That one moment resets everything. Not because the manager lacked discipline or the improvement they were trying to make was wrong, but because the incentive geometry above them just gave them a very clear answer about what’s actually expected and rewarded.
Considering that this is a systemic problem, any fix has to actually reach into that system rather than treat individual traits or the manager’s habits inside the system. One can only attenuate or improve so much before they run into the wall of what the system itself rewards, ignores, or punishes, and intention alone is not enough to push back against systemic forces.