In partnership with

Morning friend ☕️

Two weeks ago, the standard.
Last week, the self.
This week, the hands.

The force that says the work has to live somewhere other than your head, your calendar, and the goodwill of the person quietly absorbing it.

Grab your coffee.
Let’s chat.

Episode 3. Werner. The System.

It’s a Thursday afternoon.

Day five of Werner’s arrival.

The Sharks are gathered around the board for a standup he has already, twice this week, made non-negotiable.

Thandi runs through the things she is holding personally.

The Karen handover.
A late deliverable from another team.
Demo prep that nobody has owned yet.

Werner doesn’t interrupt.

When she finishes, he stays quiet for a beat too long.

Then he turns to the board.

“Where is any of that?”

Thandi opens her mouth.

“Don’t tell me what it is,” he says. “Show me where it is.”

She walks over. Picks up a marker. Writes the first item onto a sticky.

“Whose name is on it?”

She writes hers.

Werner nods.

“Now write what happens if you’re not here on Tuesday.”

She doesn’t write anything.

The room gets still.

Not hostile.
Attentive.

Her own name sits on the sticky like proof of responsibility.

Taking it off feels careless.
Leaving it there feels safer.

Eventually, she crosses it out.

The marker squeaks louder than it should.

“Good,” Werner says.

No praise.
No warmth.
Just the next move.

“Who actually owns it?”

Aisha lifts her hand slightly.

“I can take the handover template.”

“Date?”

“Tuesday.”

“Backup?”

Aisha glances across the room.

Jason leans back. “I can review it.”

Werner writes both names down.

Then he caps his marker.

“If it’s not visible, it doesn’t exist,” he says. “And if it’s only on one of us, it’s not a system. It’s a hostage.”

He moves to the next item.

By the end of the standup, the three things Thandi had been carrying were on the wall.

With names.
With dates.
With backups.

None of them were hers.

Two got done before lunch.

The Karen handover didn’t.

But it was now a visible task, with a visible owner, and a visible date two days out.

It didn’t move faster.

It just stopped being a secret.

That was Werner.

He didn’t make Thandi work harder.

He made the work visible.

A year later, Thandi could name what he installed.

At the time, it just felt like exposure.

Werner had one rule, repeated like a refrain:

If it’s not visible, it doesn’t exist.

The work that hides is rarely the work failing loudly.

It is the work someone is carrying privately because they can.

The check-in nobody else is doing.
The cross-team nudge that depends on one relationship.
The decision held in someone’s head because writing it down feels paranoid.
The favour done off-board because asking for proper ownership feels heavy.

Werner refused all of it.

If it lived in Thandi’s notebook and not on the wall, it didn’t exist.

If a team member was doing it as a favour, it didn’t exist.

If a stakeholder owed something and there was no ticket, it didn’t exist.

That sounds bureaucratic.

It wasn’t.

It was one of the most generous things anyone had done for the team in years.

Because once the work was visible, the team could see who was overloaded.

Who was disappearing.

Who was carrying twice their share.

Who was holding nothing and getting away with it.

Visibility was the diagnosis.

And you can’t fix what you can’t see.

Werner also refused to let people be heroes.

Heroics feel like leadership.

They feel like commitment.

They feel like the exact behaviour you should celebrate.

Werner saw heroics as debt.

A team that only ships because one person stays up on Tuesday nights is not a team that ships.

It is a team with a single point of failure.

And the failure just hasn’t met it yet.

One afternoon, Jason said it the way Jason always said things.

“I can take it.”

Werner looked at the board.

“You already have three.”

“I’ll manage.”

“That’s not the question.”

Jason folded his arms.

Werner tapped the empty space beside Jason’s name.

“Who else knows enough to help?”

Jason didn’t answer immediately.

That was the answer.

Werner didn’t smile.

He didn’t shame him either.

He just waited.

Eventually, Michael looked up from his laptop.

“I can pair for an hour.”

Werner wrote Michael’s name down.

“Now it exists.”

That was how he worked.

No speeches about teamwork.

No motivational language.

No applause for the person quietly dying under the load.

Just one repeated question:

“What happens if this person isn’t here?”

Sometimes the answer was: we’d be fine.

More often, the answer was a pause.

Sometimes the answer was: we’d be in trouble.

That last one was the answer Werner was hunting for.

Every “we’d be in trouble” was an unpaid bill the team didn’t know it was carrying.

He didn’t punish the hero.

He didn’t dramatise the gap.

He put the work on the board, found a second name, and stayed in the room until the bus question had a clean answer.

It looked like process.

It was protection.

That was the part Thandi misunderstood at first.

When discipline arrives, teams often assume someone is being watched.

Werner’s discipline didn’t watch the team.

It watched the work.

The standup wasn’t a status check on people.

It was a status check on the wall.

The retro wasn’t a blame session.

It was a maintenance window on the system.

The burndown wasn’t a dashboard for the manager.

It was a window for the team into its own state.

A team that thinks it is being watched gets quieter.

More careful.
More performative.
Less honest about what is stuck.

A team that thinks the work is being watched starts telling the truth about it.

Where it is slipping.
What is missing.
Who needs help.
What the manager is doing too much of.

The structure was the safety.

The visibility was the trust.

Eight weeks in, the Sharks weren’t more controlled.

They were freer.

They joked more.
They argued more cleanly.
They escalated earlier.
They stopped pretending things were fine when they weren’t.

Werner hadn’t softened.

He had become predictable.

And predictability, after years of chaos, felt like safety.

The real question to ask yourself

Most leaders, when they see a team struggling, ask:

Who needs to step up?

Werner reminds you to ask something less flattering:

Who is currently the system?

If the answer is one person, you, your senior engineer, your ops lead, the one who always stays late, the team is not a team.

It is a person with helpers.

That can work for a sprint.

It does not work for a year.

The job of the operator force is not to add rigour for its own sake.

It is to subtract dependency.

To turn private effort into public structure.

To find the places where critical work is being held by a single human, and gently, methodically, without drama, take it off their shoulders and put it on the board.

Then watch what happens.

The team is often more capable than the hero allowed.

The hero is often more tired than anyone admitted.

And the work usually looks less terrifying once it stops hiding inside one person.

Key takeaway

Anand handed her the standard.

Lebo held the mirror.

Werner installed the system that meant the standard could survive without Thandi always being the one carrying it.

A leader without a Werner becomes the system.

A leader with one builds it.

Until next time,
Vaugan ☕️

Next week on scarymanagement.com!

Thandi had a fourth force.

This one didn’t run her standups.

This one ran the room she walked into when the standups weren’t enough.

Next week: Forces Behind the Leader Episode 4. Richard, The Consequence.

Subscribe so you don't miss it!

Today’s Chess Puzzle

Black to play and force mate.

Solution here

Check out this week’s sponsors

Turn AI into Your Income Engine

Ready to transform artificial intelligence from a buzzword into your personal revenue generator?

HubSpot’s groundbreaking guide "200+ AI-Powered Income Ideas" is your gateway to financial innovation in the digital age.

Inside you'll discover:

  • A curated collection of 200+ profitable opportunities spanning content creation, e-commerce, gaming, and emerging digital markets—each vetted for real-world potential

  • Step-by-step implementation guides designed for beginners, making AI accessible regardless of your technical background

  • Cutting-edge strategies aligned with current market trends, ensuring your ventures stay ahead of the curve

Download your guide today and unlock a future where artificial intelligence powers your success. Your next income stream is waiting.

Learn AI in 5 minutes a day

You don't have to scroll every AI thread, track every new tool, or watch every demo. 

The Rundown AI breaks it all down for you — the latest AI news, tools, and tutorials in one free 5-minute email every morning. 

Trusted by 2M+ professionals at Apple, Google, and NASA.

Disclaimer:
This post contains parody and satirical references to well-known characters, shows, and cultural icons. It is created for educational and humorous commentary on management and leadership. ScaryManagement is not affiliated with, endorsed by, or sponsored by any television networks, film studios, comic publishers, production companies, or performers referenced. All trademarks and copyrights remain the property of their respective owners. No infringement is intended. This use is intended as parody and commentary under fair use and related protections in the US, UK, EU, and South African law.

Reply

Avatar

or to participate

Keep Reading