A Better Way

Collective Punishment: Because Management Haven't Got the Balls to Deal With the Actual Fucking Problem

There are many ways to identify an incompetent manager.

Some can't make decisions.

Some can't communicate.

Some have the emotional intelligence of a parking meter and the leadership qualities of a damp fucking tea towel.

But there's one particular species of management incompetence that deserves its own special place in the corporate hall of shame.

The manager who discovers that three people are taking the piss and decides to punish an entire department.

It's a remarkable approach.

Imagine running a school where three children are misbehaving, so the headteacher announces that all 400 pupils are banned from going home.

Or discovering that somebody has been stealing sandwiches from the office fridge, so management introduces compulsory bag searches, CCTV monitoring and a formal authorisation process for purchasing fucking bread.

Ridiculous?

Of course.

But dress it up in corporate language, call it an operational improvement initiative, and suddenly everybody's supposed to applaud.

And this particular example is magnificent.

Because it involves school runs, annual leave, sickness, departmental meetings, management cowardice and, ultimately, a formal conversation about the apparent dangers of telling the fucking truth.

The Crime of the Century

Let's establish what happened.

A handful of younger employees had been taking the piss.

Not all younger employees.

Not an entire generation.

A handful.

People who weren't meeting expectations.

People who were taking liberties.

People whose approach to the working day apparently involved seeing how little work could be completed before somebody noticed.

Now, I'm not defending that.

If somebody is being paid to work and they're deliberately bunking off, deal with it.

Investigate.

Establish the facts.

Have a conversation.

Set expectations.

Manage performance.

And if necessary, take disciplinary action.

It's not fucking complicated.

That's literally what managers are employed to do.

But apparently, confronting the individuals responsible was considered far too difficult.

So management developed an alternative strategy.

Punish everybody.

The experienced employees.

The reliable employees.

The parents.

The people who consistently delivered.

The people who had spent years demonstrating that they could be trusted.

All of them.

Because somewhere in the department, Tyler had discovered that nobody was checking whether he was actually working on a Friday afternoon.

And rather than have a difficult conversation with Tyler, management decided to redesign everybody else's fucking life.

Brilliant.

Absolutely fucking brilliant.

School Runs: An Unacceptable Threat to Operational Excellence

The first proposed rule concerned working hours.

Specifically, parents who needed flexibility to take their children to school or collect them afterwards.

Apparently, this was becoming a problem.

Not because these employees were necessarily failing to deliver.

Not because their work wasn't getting done.

But because management had decided that the department needed greater consistency.

Consistency.

Wonderful word.

Very corporate.

Sounds reassuring.

Sounds strategic.

Sounds considerably better than:

"We don't trust you anymore because a few people have been taking the piss."

Under the new arrangements, parents could potentially find themselves unable to do the school run without consequences.

Including the possibility of having their pay docked.

Let that sink in.

A responsible adult who has been performing their job perfectly well could suddenly face financial consequences for collecting their fucking children from school.

Why?

Because Tyler hasn't been doing his job.

What an extraordinary piece of management logic.

Imagine explaining that to your children.

"Sorry, kids. Daddy can't collect you today."

"Why not?"

"Because somebody called Tyler in another part of the department hasn't been doing enough work."

"Who's Tyler?"

"Nobody fucking knows, but apparently he's now in charge of our family arrangements."

And here's what makes it particularly insulting.

Many of these employees have probably spent years working flexibly.

Managing their responsibilities.

Attending meetings.

Meeting deadlines.

Supporting customers.

Delivering work.

And now, suddenly, they're being treated as though collecting their children represents some elaborate scheme to defraud the company of twenty-seven minutes.

Perhaps management would prefer the children to remain at school indefinitely.

Just leave them there.

Monday to Friday.

Collect them at Christmas.

Think of the operational efficiencies.

Annual Leave: Please Don't Make Plans for Your Actual Life

Then came the holiday restrictions.

Under the proposed arrangements, employees would no longer be able to book annual leave far in advance.

Now, this is particularly fucking stupid.

Because normal people plan holidays.

Especially families.

They save money.

They compare prices.

They book flights.

They arrange accommodation.

They spread payments over several months.

Sometimes they book six months ahead.

Sometimes twelve.

Because, unlike senior management, most people don't have an unlimited supply of disposable income and the ability to book a luxury holiday on a fucking whim.

But apparently, advance holiday planning was now an operational concern.

So employees were expected to organise their lives around management's inability to forecast departmental capacity.

"Can I book two weeks off next August?"

"Unfortunately, we're unable to approve leave that far in advance."

"Why?"

"Because we need to ensure appropriate resource availability."

Right.

So you can't tell me whether I can take a holiday in nine months because you don't know what the workload will look like.

But you can apparently predict the department's strategic direction for the next three fucking years.

Interesting.

Perhaps we should cancel the transformation roadmap.

Clearly forecasting isn't one of our strengths.

And what happens when employees can't book holidays early?

They pay more.

They lose availability.

They can't spread the cost.

Their families can't make plans.

But don't worry.

Management has improved operational efficiency.

By making everybody's personal life considerably more fucking difficult.

Outstanding leadership.

Sick? Please Present Yourself for Inspection

And then we arrive at my personal favourite.

Sickness.

Under the proposed arrangements, employees who were unwell would have to telephone their manager and attend a Teams call.

Not simply report that they were sick.

Not follow a normal absence notification process.

No.

They'd have to appear on camera.

So the manager could assess whether they were genuinely unwell.

WHAT THE ACTUAL FUCK?

Who came up with this?

Who sat in a management meeting and said:

"I've got an idea. Why don't we make sick employees appear on video so we can inspect them?"

And who, in the name of all that is fucking holy, agreed?

Imagine the conversation.

"Morning, Martin. I'm really unwell today."

"Sorry to hear that. Could you switch your camera on?"

"Why?"

"I just need to assess whether you're genuinely sick."

Assess?

Are you a doctor now, Martin?

Have you secretly completed a medical degree between your resource planning meetings and your annual performance reviews?

Are you going to inspect my tonsils through a webcam?

Ask me to cough?

Request a stool sample?

Perhaps I should hold a thermometer up to the camera while you consult the company's absence management policy.

And what exactly constitutes sufficient visual evidence?

If I've got a migraine, do I have to demonstrate sensitivity to light?

If I've got food poisoning, should I provide a live broadcast from the fucking toilet?

If I'm suffering from anxiety, do I need to perform a convincing breakdown for your professional assessment?

And what happens if I look reasonably healthy?

"Sorry, you don't appear sufficiently ill."

Well, forgive me, Doctor Fucking Martin.

I didn't realise you could diagnose medical conditions using a £19 Logitech webcam and a qualification in middle management.

There are legitimate reasons for managers to contact employees who are off sick.

Welfare.

Support.

Absence reporting.

Understanding whether adjustments are needed.

But treating a Teams call as some kind of amateur medical lie detector?

That isn't supportive management.

That's a fucking audition for Casualty.

Introducing the New Departmental Efficiency Initiative

Of course, management couldn't simply announce that they no longer trusted the department.

That would sound terrible.

So the whole thing needed a title.

Something impressive.

Something strategic.

Something that suggested the company was making a bold, progressive improvement to its operating model.

Perhaps:

Departmental Delivery Effectiveness and Resource Optimisation Framework.

Beautiful.

Absolutely meaningless.

But beautiful.

The communication would explain that the new measures were designed to improve consistency, strengthen accountability and ensure the department continued delivering exceptional outcomes for its clients.

Oh, do fuck off.

Seriously.

SUCK MY FUCKING DICK.

Stop dressing up your inability to manage a handful of employees as some grand initiative to improve customer delivery.

If three people are taking the piss, deal with those three people.

Don't tell a department full of experienced professionals that their family arrangements, holiday plans and medical absences are suddenly threats to operational excellence.

That's not transformation.

That's collective punishment wearing a fucking lanyard.

And the insulting part isn't just the rules.

It's the assumption that everybody is too stupid to recognise what's happening.

You haven't discovered a revolutionary new management strategy.

You've simply decided that confronting a few individuals is harder than inconveniencing everybody else.

The Brave Leader Who Couldn't Deliver Her Own Announcement

Now, you'd imagine that a manager introducing such significant changes would have the courage to explain them personally.

After all, these weren't minor administrative adjustments.

They affected people's families.

Their finances.

Their annual leave.

Their health.

Their working arrangements.

Surely the person responsible would stand in front of the department, explain the rationale and answer questions.

Wouldn't she?

Of course she fucking wouldn't.

Because that would require a spine.

Instead, she delegated the announcement to her direct reports.

Magnificent.

Absolutely magnificent.

Here's a manager prepared to impose restrictions on an entire department but apparently unwilling to stand in front of the people affected and explain why.

That's leadership, apparently.

Make the decision.

Hide behind your management team.

Let somebody else deliver the bad news.

And remain safely removed from the consequences.

It's the corporate equivalent of throwing a brick through somebody's window and then sending your neighbour round to explain that the broken glass represents an exciting opportunity for improved ventilation.

And the poor direct reports?

They get to sit there delivering rules they may not even agree with.

Trying to answer questions they probably can't answer.

Defending decisions they didn't make.

While the person responsible remains safely tucked away behind another layer of management.

A gutless fucking masterclass.

Any Questions?

And then came the moment of genius.

The announcement had been delivered.

The new restrictions had been explained.

The department had been informed that its flexibility, holiday planning and sickness reporting were all about to become considerably more complicated.

And somebody made the single biggest mistake of the entire exercise.

They asked:

"Does anybody have any thoughts?"

Oh.

You magnificent fucking idiots.

You really shouldn't have done that.

Because somewhere in the meeting was an experienced employee who had spent years delivering work, managing responsibilities and behaving like a responsible adult.

An employee who hadn't been bunking off.

Hadn't been abusing flexibility.

Hadn't been taking the piss.

And who was now being told that his working arrangements were going to be restricted because management couldn't deal with the people who actually were.

And unlike Kevin, who would undoubtedly describe the announcement as a positive step towards greater operational alignment, this particular employee had absolutely no intention of pretending the proposal was sensible.

He unmuted.

And he told them.

Exactly.

What.

He.

Thought.

Not the sanitised version.

Not the carefully rehearsed corporate version.

Not the version beginning with "Firstly, I'd just like to thank the leadership team for their transparency."

No.

The actual fucking version.

Why were responsible employees being punished for other people's behaviour?

Why were parents being penalised?

Why were employees being prevented from planning holidays?

Why were managers apparently appointing themselves medical examiners?

And why wasn't management simply dealing with the individuals responsible?

All perfectly reasonable questions.

Unfortunately, reasonable questions become deeply inconvenient when the answers expose management incompetence.

And this particular employee wasn't interested in wrapping his objections in seventeen layers of diplomatic corporate bullshit.

He'd been asked what he thought.

So he told them.

And apparently, management wasn't quite prepared for the possibility that somebody might actually answer.

The Department Has Become Anxious

Now we reach the most spectacular part of the entire story.

The aftermath.

Because following this exchange, the employee was summoned to a meeting with his manager.

Not to discuss whether the new rules were fair.

Not to review the concerns raised.

Not to consider whether the department-wide restrictions were proportionate.

No.

To discuss his communication.

Apparently, his comments had caused some team members to become anxious.

Anxious.

ANXIOUS?

Let's examine that for a moment.

Management announces that parents may no longer be able to collect their children without risking financial consequences.

Management announces that employees may be unable to book family holidays sufficiently far in advance.

Management announces that sick employees may have to appear on camera for a manager to assess whether they're genuinely unwell.

An employee challenges these proposals.

And management concludes that the employee is responsible for making people anxious.

ARE YOU TAKING THE FUCKING PISS?

You've just introduced a collection of rules that potentially interfere with people's family lives, finances and personal wellbeing.

And you're surprised they're anxious?

Perhaps they're anxious because they don't know how they're going to collect their children.

Perhaps they're anxious because they've already started saving for next year's family holiday.

Perhaps they're anxious because the next time they're ill, they're going to have to perform a fucking medical pantomime for Martin on Teams.

But no.

Apparently, the source of the anxiety is the person who pointed out that the proposals were ridiculous.

That's extraordinary.

It's like setting fire to the office, then formally reprimanding the employee who shouts:

"THE FUCKING BUILDING'S ON FIRE!"

For creating unnecessary alarm.

No, Martin.

The fire created the alarm.

The person shouting merely drew attention to the fucking flames.

The Official Conversation

But it gets better.

Because the manager apparently had to record an official conversation.

A formal discussion.

An educational intervention.

The employee needed to be instructed about when it was appropriate to communicate certain things to the wider team.

Let me translate.

"You've raised concerns that we'd rather you hadn't raised in front of everybody."

Now, to be fair, there are perfectly legitimate reasons for managers to discuss how employees communicate.

Personal abuse, intimidation and inappropriate conduct should be addressed.

But challenging a departmental policy?

Questioning management decisions?

Explaining why a proposal is unfair?

Those are not inherently inappropriate activities.

Especially when management has explicitly invited feedback.

You can't ask people what they think and then act astonished when somebody has the audacity to fucking think.

And if the substance of the concerns is valid, perhaps the first priority should be examining the concerns.

Not producing an official record of the person who raised them.

Because the moment employees see somebody formally challenged after speaking openly, something interesting happens.

They stop speaking openly.

They start nodding.

They start agreeing.

They start saying things like:

"Yes, I can see the rationale behind that."

Even when they think the proposal is absolute fucking bollocks.

And management interprets the resulting silence as evidence that everybody is aligned.

Congratulations.

You've successfully created a department where people are afraid to tell you the truth.

What an outstanding achievement.

Perhaps Kevin can nominate you for a leadership award.

The Great Corporate Anxiety Transfer

There's a fascinating trick in corporate management.

When leadership makes an unpopular decision, the resulting frustration is often treated as a communication problem.

Not a decision problem.

A communication problem.

Employees are unhappy?

Perhaps the messaging wasn't clear enough.

People are worried?

Perhaps we need to manage expectations.

Staff are angry?

Perhaps we need a more structured engagement approach.

Somebody openly challenges the decision?

Perhaps they need coaching on appropriate communication.

Notice what's missing?

The possibility that the original decision was fucking stupid.

That option apparently never makes it onto the agenda.

Instead, the organisation begins rearranging the furniture around the problem.

A communications plan.

An engagement workshop.

A manager briefing.

A frequently asked questions document.

An official conversation with the employee who dared to object.

Anything.

Absolutely anything.

Except admitting:

"Actually, perhaps imposing these rules on everybody was a terrible idea."

Because that would require somebody senior to accept responsibility.

And in some corporate organisations, accepting responsibility is treated as a more serious offence than making the original mistake.

What a Competent Manager Would Have Done

Let's imagine, just for a moment, that the department was managed by somebody with a functioning brain.

A handful of employees are suspected of abusing working arrangements.

What happens?

First, the manager establishes the facts.

Are they actually failing to work their contracted hours?

Are they missing deadlines?

Are they unavailable when required?

Is there evidence of misconduct?

Then the manager speaks to the individuals concerned.

Explains expectations.

Provides support if there's a genuine issue.

And takes appropriate action if the behaviour continues.

Meanwhile, the reliable employees carry on doing their jobs.

Parents continue managing school runs within agreed working arrangements.

People book holidays in advance, subject to sensible operational planning.

Sick employees follow a reasonable reporting process.

And the department continues functioning.

No enormous policy announcement.

No collective punishment.

No angry departmental meeting.

No official conversation about somebody making colleagues anxious.

Just straightforward, competent management.

But apparently, that would be far too fucking easy.

Much better to create an entirely new administrative process, inconvenience dozens of employees and then spend the next six months managing the fallout.

After all, how else would we demonstrate operational transformation?

The Real Cost of This Bullshit

Here's the part that incompetent managers consistently fail to understand.

The damage isn't limited to the immediate inconvenience.

It's what happens to trust.

Imagine being a reliable employee.

You've spent years delivering good work.

You've supported customers.

You've met deadlines.

You've helped colleagues.

You've managed your responsibilities.

You've demonstrated that you can be trusted.

Then one day, management announces that your freedom is being restricted because some other employees have been behaving badly.

What message does that send?

That your track record means nothing.

That your professionalism means nothing.

That your reliability means nothing.

Because the moment somebody else takes the piss, management treats you as though you're equally untrustworthy.

And that's when something changes.

You stop feeling valued.

You stop believing the company recognises your contribution.

You begin wondering why you've bothered being so conscientious.

And eventually, you start looking elsewhere.

Not because you're lazy.

Not because you're entitled.

Not because you don't want to work.

But because you're tired of being treated like a fucking child by people who are supposed to be managing adults.

And when you leave?

Management will probably describe it as another example of the challenges associated with employee retention.

Perhaps they'll organise a workshop.

And What Happened to the Actual Offenders?

This is the question I'd really like answered.

What happened to the handful of employees who were supposedly responsible for the problem?

Were they investigated?

Were expectations clarified?

Were their performance issues addressed?

Were managers held accountable for allowing the situation to develop?

Or did they simply carry on doing whatever they were doing while the rest of the department endured a collection of increasingly ridiculous restrictions?

Because that's the ultimate insult.

The people taking the piss create the problem.

The reliable employees suffer the consequences.

The managers avoid difficult conversations.

And the person who challenges the arrangement gets an official discussion about appropriate communication.

WHAT A FUCKING MASTERPIECE OF INCOMPETENCE.

You couldn't design a more backwards system if you tried.

The Lessons Learned

Of course, in a truly enlightened organisation, this entire episode would eventually become the subject of a lessons learned exercise.

The management team would gather.

Somebody would prepare a PowerPoint.

The first slide would be titled:

Improving Employee Engagement During Operational Change.

Martin would discuss stakeholder communication.

Sandra would explain the importance of psychological safety.

Kevin would praise the leadership team's commitment to continuous improvement.

And somebody would recommend additional training to help employees respond more constructively to change.

Because clearly, the biggest problem wasn't the collective punishment.

Or the restrictions on family life.

Or the inability to plan holidays.

Or the bizarre sickness inspection process.

Or the cowardly delegation of the announcement.

No.

The problem was that somebody had the audacity to object.

And the final action from the meeting would probably be:

Ensure future departmental communications are delivered in a way that minimises employee anxiety.

Excellent.

Here's an idea.

STOP INTRODUCING FUCKING STUPID RULES.

That should reduce anxiety considerably.

The Final Word

There's a fundamental difference between leadership and control.

Leadership means setting expectations, supporting people, making decisions and dealing with problems.

Control means imposing restrictions because you don't trust people to behave responsibly.

And when a manager responds to a handful of poorly performing employees by restricting an entire department, that's not evidence of strong leadership.

It's evidence that they've lost the ability, or the courage, to manage individuals.

What's particularly infuriating is the way these decisions are packaged.

They're never presented as punishment.

They're improvements.

Transformations.

Operational enhancements.

Measures designed to ensure exceptional service delivery.

All accompanied by carefully selected corporate language intended to make something deeply unreasonable sound strategically sophisticated.

But no amount of jargon can disguise a fundamentally stupid decision.

And no amount of management training can replace the courage required to deal with the actual people causing the problem.

As for the employee who spoke up?

Perhaps he could have expressed himself more diplomatically.

Perhaps his delivery was a little forceful.

Perhaps he didn't sufficiently appreciate the delicate emotional requirements of a management team accustomed to receiving enthusiastic agreement from Kevin.

But here's the thing.

HE WASN'T THE ONE WHO INTRODUCED THE FUCKING RULES.

He didn't prevent parents from collecting their children.

He didn't interfere with people's holiday planning.

He didn't propose inspecting sick employees over Microsoft Teams.

He didn't delegate the announcement because he couldn't face the department.

And he didn't ask for honest feedback only to become offended when somebody provided it.

Management did those things.

So if employees were anxious, perhaps management should examine the decisions that made them anxious.

Not simply the person who challenged those decisions.

And if the organisation genuinely wants to improve efficiency, employee engagement and customer delivery, perhaps it could begin with a radical new initiative.

MANAGERS ACTUALLY MANAGING THE PEOPLE WHO ARE CAUSING THE FUCKING PROBLEM.

No transformation programme required.

No external consultants.

No employee engagement workshop.

No seventeen-slide presentation.

Just a manager with enough competence to identify the problem and enough backbone to deal with it.

And if that's too much to ask?

Perhaps the manager should be the one attending a formal educational conversation.

Preferably conducted over Microsoft Teams.

With the camera switched on.

So somebody can assess whether they're genuinely fucking qualified to do the job.

#Corporate Fuckery