More scrutiny doesn't create accountability. It creates compliance.

A team misses its targets. Leadership tightens up.

More KPIs. Weekly check-ins. A new dashboard. Updates in writing, every Friday.

And something does improve. The reports.

The results usually don't.

What scrutiny teaches

When people know they're being watched more closely, they don't just work harder. They change what they're working on.

They start managing how things look.

Risks don't get flagged, because a flagged risk turns the dashboard red. Targets get set where they're safe to hit. Everyone says yes in the meeting, because a no looks like resistance. Problems get fixed quietly, or hidden until they can't be.

From the outside, it looks like a team under control. From the inside, it's a team protecting itself.

Accountability isn't the same as being watched

Accountability means "I own this outcome, including telling you when it's going wrong."

Scrutiny means "I'm watching to see whether you get it wrong."

The first needs people to bring you bad news early. The second teaches them not to.

That's why accountability without safety turns into compliance. People do exactly what's measured, report exactly what's safe, and own nothing that isn't written down.

What to do instead

When something goes wrong, ask "When did you first know this was at risk?" before "Why didn't you hit the target?" The first question gets you information. The second gets you a defence.

Make expectations a conversation, not a broadcast. People own targets they helped shape. They comply with targets that were handed to them.

Fewer measures, owned by the people doing the work. If trust is low, more dashboards won't help.

Make it safe to report a problem. Separate the news from the person who brings it. If flagging a risk costs someone, the next risk won't be flagged.

And when it really is underperformance, deal with it directly. Safety doesn't mean lower standards. It means the hard conversation happens early and honestly, not through a dashboard.

The dashboard that made everything look better

I worked with a team whose performance had started slipping, so leadership responded the way leaders often do: they added visibility.

New KPIs. Weekly reporting. More frequent one-to-ones. Every Friday, each person had to explain what they'd delivered, what was behind and what they were doing about it.

Within a month, the dashboard looked better.

The problem was that the work didn't.

People had become very good at managing the numbers. Risks were raised later. Targets were broken into smaller pieces that were easier to report as progress. Anything that might make a metric look bad was dealt with quietly before it reached the weekly meeting. The reports were increasingly detailed, and increasingly reassuring.

Then one of the biggest projects missed a critical milestone.

The leader was surprised. According to the previous six weeks of reporting, everything had been under control.

It hadn't.

The team had learned that being the person who reported a problem made you responsible for the problem. So people had stopped bringing problems early. Leadership had responded to falling performance by making honesty more expensive.

They changed the system. Fewer KPIs. Clear owners. Less reporting for the sake of reporting. And, most importantly, the first question when something went wrong became "When did you first know this was at risk?" rather than "Why didn't you hit the target?"

The dashboard became simpler. The conversations became harder.

And over time, the team started surfacing problems earlier again, which gave leadership something the old system never had: enough time to actually do something about them.

Clear, or just compliant?

Next time you're tempted to tighten things up, ask one question.

Are your people clear, or just compliant?