How Do I Hold People Accountable Without Micromanaging Them?

Start with a real commitment

One of my most repeated mantras is: Do what you said you were going to do, by when you said you would do it, because it matters. It sounds almost ridiculously simple. But after more than twenty years of coaching businesses, I'm still surprised by how often that basic discipline is missing.

Deadlines become wished-for dates. Actions get rolled over. People say: "I'll try." "I'll give it a go." "I'll get around to it." "When things calm down." "When I get a chance." None of those is a proper commitment.

A commitment needs some basic ingredients: What will be done? Who owns it? What does completed actually mean? By when? If those things are unclear, you don't have accountability yet. You have an intention. And intentions are terribly difficult to manage.

An honest no is better than a dishonest yes

Accountability starts before the person agrees to do anything. If somebody cannot genuinely deliver something by Friday, I would much rather hear: "I can't do Friday." Good. Now we can have a proper conversation. Why not? What would have to move? What is realistic?

What can you actually commit to? Perhaps the answer is Wednesday. Fine. Now everybody can plan around Wednesday. What isn't useful is somebody saying: "Friday's fine." when they already suspect it isn't. Friday arrives. Nothing. Monday arrives. Somebody has to chase them.

And only then do we hear about everything that got in the way. That's not accountability. That's often conflict avoidance dressed up as agreement. People do not have to say yes to everything.

In fact, one mark of a trustworthy employee or manager is that they're willing to push back before making a commitment they cannot reasonably keep. A truthful conversation at the beginning protects trust. A false agreement damages it later.

Put a date on it

Two of the most important words in my accountability mantra are: By when. A commitment without a date is really just a good intention. "I'll do it." When? "Soon." When? "When I get a chance." And when will that be? If something matters, put a date on it.

Not because you're trying to control every movement somebody makes. Because other people need to know what they can rely upon. If your work is due Friday, somebody else's work may begin after yours. They may then have promised something to somebody else. And that person may be depending on them.

Think of a row of dominoes. One doesn't fall and the entire sequence stops. Three people further along may have no idea why the thing they were expecting hasn't arrived. Reliability isn't just a nice personal characteristic. It's part of the operating system of a business.

Be clear about what "done" means

Another source of accountability trouble is that two people can apparently agree to the same action while holding completely different pictures of what completion means. If somebody agrees to read a book before the next coaching session: "I started it." isn't the same as:

"I read it." If somebody agrees that a process will be completed, approved and communicated by Friday, a half-written draft sitting on their laptop isn't what was promised. It may be progress. But progress and completion are not the same thing.

That doesn't mean we need to become brutal or pedantic. It means we need to be clear. What exactly are we agreeing will exist when this action is finished? Clarity prevents a surprising amount of unnecessary friction later.

Record the commitment

This is where accountability starts to become a system rather than a memory test. If something matters, record it. What is the action? Who owns it? What is the due date? Then come back to it. That isn't micromanagement. It's management. Imagine five people sitting in a leadership meeting.

Everybody agrees that three important things need to happen. People nod. Somebody says: "Yep, I'll take care of that." Everyone leaves. Nothing is written down. A week later somebody vaguely remembers that Sarah said she'd do something. Sarah remembers the conversation rather differently.

Someone else thought Michael owned it. Nobody can remember whether it was supposed to be completed this week or merely started. That's not accountability. That's a conversation and a hope. If an agreement matters enough to make, it matters enough to record.

Accountability is not constant checking

Once somebody has made a clear commitment and it has been recorded, you do not necessarily need to hover over them. You shouldn't need to ask every morning: "Have you done it yet?" "How's it going?" "Did you start?" "Where are you up to?"

"When are you going to finish?" If you have to supervise every step, you may have a different issue: capability, clarity, confidence, authority or perhaps whether the person should own that responsibility at all. Normal accountability can be much simpler. We agreed what you would do.

We agreed by when. You have the authority and resources you need. Now go and do it. And at the appropriate point, we'll come back to the commitment. That is quite different from following somebody around with a clipboard.

When the date arrives, come back to it

This is the part organisations often miss. They are reasonably good at making commitments. They're much less good at returning to them. If I said I would have something finished by Friday, then at some point after Friday there needs to be a very simple question: What happened?

Did I do what I said I would do? Yes? Good. Close the action. No? Then let's understand why. Not because we're trying to catch somebody out. Because otherwise dates become decorative.

And once everybody learns that dates don't really mean anything, you've lost one of the fundamental building blocks of accountability.

Don't endlessly roll actions over

One habit I would love businesses to stop is allowing the same action to sit on an Action Register week after week while somebody simply changes the date. Monday becomes Friday. Friday becomes next Wednesday. Wednesday becomes the end of the month.

Eventually nobody can remember when it was originally due. At some point, stop moving the date and have a different conversation. Ask: Is this action actually important? Does this person have the skill to do it? Do they have the authority? Do they have the capacity? Are they avoiding it?

Did they ever genuinely agree to it? Perhaps the action needs to be reassigned. Perhaps something else has to move. Perhaps it is no longer important and should be removed. Perhaps the person needs help. Perhaps there is a performance issue. All of those are legitimate possibilities. But endlessly rolling the date forward teaches everybody one thing: The dates aren't real.

If the commitment is at risk, speak early

Accountability does not mean pretending that nothing ever goes wrong. Real life happens. A customer crisis appears. Somebody becomes ill. New information reveals that a piece of work is much larger than anyone expected. Priorities genuinely change. Fine. The commitment may need to change.

But it should change through a conversation, not through silence. A reliable person doesn't disappear until the deadline has passed and somebody chases them. They come early and say:

"I committed to Friday. I'm not going to make it. Here's what's happened, here's what I've tried, and here's the new date I can genuinely commit to." Perhaps they also say: "And this is what I need, if anything, to make that happen." That conversation can preserve trust. Silence usually damages it.

Use evidence, not memory

Accountability also becomes much easier when you stop managing from anecdotes. Managers often say things such as: "I've spoken to them about this before." "This keeps happening." "They're always late." "They never meet deadlines."

"Everyone knows this is a problem." Perhaps they're right. But then I start asking questions. When did it happen? How many times? What was agreed? What was the due date? What actually happened? Was it discussed? What evidence do we have? Memory is a terrible management system.

Memory opens the door to arguments about recollection. Evidence changes the conversation. If attendance is becoming unreliable, track it. If deadlines keep slipping, record them. If the same mistake keeps happening, write it down. Something interesting happens when you stop relying on memory.

Patterns appear. Conversations become calmer. Instead of arguing about somebody's recollection of what happened six weeks ago, you can discuss the facts in front of you. Evidence beats memory every time.

Accountability shouldn't come as a surprise

If somebody is repeatedly failing to honour important commitments, eventually there may need to be a harder conversation. But that conversation shouldn't arrive out of nowhere. They should already know:

• what was expected;
• what they agreed to;
• when it was due;
• what actually happened;
• whether this is a one-off or a pattern;
• what conversations have already occurred.

That's another reason recording commitments matters. Good accountability reduces surprises. It gives people the opportunity to see their own performance clearly and respond to it.

Leaders don't get a special exemption

You can't ask your team to honour commitments while treating your own as optional. People watch leaders very carefully. They notice whether you keep cancelling their one-on-ones. They notice whether you promised to make a decision and never came back to it.

They notice whether something that was apparently very important last month has quietly disappeared this month. They notice whether you arrive at meetings prepared. They notice whether you do what you said you were going to do.

If you continually cancel somebody's one-on-one meeting, for example, don't be surprised if they eventually conclude that the meeting — or perhaps they themselves — aren't particularly important in your world. Leadership isn't only what you say in meetings. It is what happens afterwards.

Accountability also means noticing when people deliver

There should be consequences at both ends. If somebody repeatedly ignores important commitments, eventually that needs to be addressed. But when somebody consistently does what they said they would do, particularly when doing so was difficult, notice that too. The person who always prepares.

The person who follows through. The person who warns you early when something is at risk. The person who comes to the meeting with the evidence. The person whose word you can depend upon. Don't take those people for granted. They're the glue. Reliable people remove chasing. They remove uncertainty.

They remove workarounds. They allow everyone else to get on with their own job instead of constantly wondering whether somebody else is going to do theirs. Those people are worth their weight in gold. So where does micromanagement begin?

Micromanagement begins when the leader unnecessarily takes over how a capable person does their job. Accountability is different. Accountability says: Here's the outcome we agreed. You own it. Here's when we agreed it would be done. You have room to do your job.

And we will come back to what happened. One controls the person. The other makes the commitment visible. That is a very important distinction. You don't create autonomy by removing accountability.

You create autonomy by making the destination clear, giving somebody appropriate authority to get there, and then expecting them to own what they agreed.

A simple accountability rhythm

If you want to improve accountability without becoming a micromanager, start with this:

1. Agree the action

Be clear about what will actually happen.

2. Give it one owner

Not "the team." Not "we." Who is the person responsible for making sure it gets done?

3. Define completion

What will "done" look like?

4. Agree the date

By when?

5. Record it

Don't rely on memory.

6. Give the person room to execute

Don't hover unnecessarily.

7. Come back to the commitment

Did it happen?

8. If it didn't, understand why

Don't automatically roll the date.