Unions have a weapon which costs them nothing in pay and gets nobody fired. It's called work to rule.

Staff do exactly what the rulebook says. No more. Every form filled in. Every check run. Every approval waited for. And the place grinds to a halt.

Wikipedia's entry on work-to-rule puts it plainly. Obeying the rules isn't grounds for discipline or lost pay. And the tactic exposes rules which are "technically in place but impractical" and would hamper the organisation if anyone followed them as written.

Read it again. Following your rules to the letter is a recognised form of strike.

So why does your engineering organisation reward it?

Three factory workers in overalls stand still reading a giant rulebook while cardboard parcels pile up on a stalled conveyor belt behind them

Your rulebook describes a world nobody works in

Every process doc I've ever written described a tidy world. Tickets arrive with clear requirements. Reviewers respond within a day. Staging looks like production. The on-call engineer has the access they need at 3am.

None of those things stay true for long. The work keeps moving because somebody, somewhere, bends a rule. They deploy the fix before the change board meets. They grant themselves temporary access and tell the security team afterwards. They skip the template and write the design doc in a Slack thread.

Gartner measured how common this is. In a survey of 1,310 employees in May and June 2022, 69% said they had bypassed their organisation's cybersecurity guidance in the previous 12 months. 74% said they would bypass it if it helped them or their team hit a business objective.

Three quarters. These aren't a handful of rebels. This is your workforce.

I'm not sure about this part: Gartner's numbers cover security guidance only. I couldn't find solid data on how often engineers work around other processes, like change approvals or ticket templates. My own experience says it's at least as common, but I have no number to back it up.

The rule-bending is already happening on your team. The only question is whether you hear about it.

The cricketer who had to hide his coaching

Debra and I had Roland Butcher on Corey-osity Unleashed. Roland was the first Black cricketer to play for England, in 1980. After he retired he went into coaching, and ran straight into a rulebook.

The English coaching manuals, he told us, said "this is how you do it. There are no exceptions." They tried to build every player to one ideal template. Big players, small players, different styles... one shape for all of them. Roland knew it was wrong. He'd learned the game as a kid in Barbados, where young players expressed themselves first and got coached around it.

So what did he do? He kept quiet. A young coach who rocked the boat, he said, "will find yourself easily ostracized from the system." For years he played it close to his chest, balancing what the manual demanded against what his players needed.

Debra calls the two of us rebels in our profession, and she offered Roland a spare rebel cape on the spot. He didn't turn it down. "I don't like people being put in a particular box," he said. Rules from 1970 don't get to tell you how to play in 2025... "you must still do it this way" was never an argument he accepted.

Here's the part which should worry every engineering leader. Roland was right, and the system punished people for being right in public. So he went quiet. The game lost years of what he knew.

Your engineers do the same thing. Every day.

A software engineer in a cream hoodie and a terracotta cape works at a standing desk while colleagues in identical grey cardigans sit at their desks

Hidden deviance kills. Visible deviance teaches.

I'm not arguing rules don't matter. I wrote a whole post on why rules don't kill creativity, bad rules do. Some deviations are dangerous.

Sociologist Diane Vaughan named the dangerous kind after studying the Challenger disaster. She called it normalization of deviance. A clearly unsafe practice comes to feel normal because it hasn't caused a catastrophe yet. The warning signs sit there for years, "misinterpreted, ignored or missed completely".

Look at what makes it deadly. Not the bending. The silence around the bending. The workaround becomes part of how things get done. Nobody writes it down. Nobody asks whether the rule or the workaround is wrong.

Now look at the other kind. In Vietnam in the 1990s, Jerry and Monique Sternin worked with Save the Children on child malnutrition. 64% of the children weighed in the pilot villages were malnourished. Instead of handing out a rulebook, the Sternins went looking for poor families whose kids were thriving anyway.

Those families broke the local norms. They fed their children shrimp, crabs and sweet potato greens, foods most people considered unsuitable for kids. They fed them three or four times a day instead of two. The program built on what these families did, and malnutrition fell by 85% over the two-year pilot.

Same behaviour. Breaking the norm. Opposite outcome.

The difference? Someone saw the deviation, asked why it worked, and fed it back into the system.

Split scene: on the left a developer secretly tapes a cracked pipe behind a curtain, on the right a developer points at the same cracked pipe on a whiteboard while teammates lean in

What your org rewards today

Look at who gets promoted in most engineering organisations:

  • the engineer who never leaves a ticket field blank
  • the team with a perfect score on the quarterly process audit
  • the lead who never escalates, because escalating looks like failure

Now look at who gets a quiet word from their manager:

  • the engineer who shipped the hotfix outside the change window and saved everyone's weekend
  • the person who keeps asking why a one-line config change needs three approvals
  • the one who wrote a script to skip the flaky integration test, and told the whole team about it

You've built a system where silent compliance is safe and open deviation is risky. So people do both. They comply on paper and bend in private. You pay the full cost of the rules, carry the full risk of hidden workarounds, and learn nothing from either.

I've written before about processes stuck in 1983. This is how they stay there. Nobody who knows the rule is broken feels safe saying so.

Hand out rebel capes, with one condition

Roland's idea, as it landed on our list of ideas from the episode: reward nonconformity, not compliance. I'd add one condition. Reward the deviation people bring into the light.

Here's how I'd do it.

Make "I broke the rule, here's why" a safe sentence

Add a standing slot to your retro. Who worked around a process this sprint? What did the rule get wrong? No blame for a bypass someone reports. If people have to choose between hiding a workaround and getting told off, they'll hide it every time.

Treat every workaround as a bug report against the process

A workaround is data. It tells you exactly where your process and your reality have split apart. Log it like a bug. Then either fix the rule, or tell the team why the rule stays and what risk it protects against. Both answers are fine. Ignoring it isn't.

Give every rule an owner and an expiry date

Rules nobody owns never die. Put a name and a review date on every process. If nobody will stand up and defend a rule at review, delete it.

Recognise the rebel in public

When someone's workaround turns into a better process, say so in front of the team. Name the person. Name what changed. The cape is a symbol. The message behind it is the point: we want to hear when our rules are wrong.

Draw the hard lines out loud

Some rules aren't up for debate. Customer data. Production access in regulated systems. Anything touching safety. Name them, and explain why. A short list of hard lines opens the rest of the rulebook to challenge, and people respect the hard lines more when there are fewer of them.

The one-question test

Try this at your next team meeting. Ask: "What's one process here you work around?"

If you get silence, your rebels are in hiding. Your process is failing in ways you'll learn about during an incident.

If you get a flood, good. You've got a backlog of free process improvements, and a team who trusts you enough to tell you the truth.

Roland spent years hiding what he knew because the system punished open disagreement. He's written about all of it in his autobiography, Breaking Barriers. Don't build a team where your best people have to do the same.

So who on your team has earned a cape? And which of your rules are they breaking right now?