Performative Process and Other Workplace Rituals

There’s a special kind of organizational dysfunction where people stop solving problems and start performing problem-solving. You know the feeling. The Jira ticket is immaculate. The template is filled. The meeting happened. The action items were “captured”. The stakeholders were “aligned”. Everyone leaves feeling productive, and nothing changes except the number of new rituals you have to attend next week. That’s ritualized process.

It looks like progress. It sounds like maturity. It feels like “we’re being responsible”. It is, more often than not, a beautifully choreographed way to avoid thinking.

Ritualized process is when the process becomes the goal. Not “we follow a process to reliably ship good work”. More like “we follow a process so nobody can blame us when nothing ships”.

It shows up when an organization values:

• Compliance over outcomes

• Predictability over learning

• Optics over clarity

• Documentation over decisions

• Ceremony over execution

The process becomes a prop. People perform the steps because the steps are visible and measurable, even if they do not make the work better.

And yes, some process is necessary. Without it, you get chaos, heroics, and a pile of tribal knowledge held together with gut feel. But ritualized process is what happens when you keep adding process as a substitute for leadership, judgement, and ownership.

If you’re wondering whether you’re in a real operating system or a corporate stage production, look for these patterns.

You have a weekly meeting to prepare for the biweekly meeting where you prepare for the monthly steering committee where you prepare for the quarterly business review where somebody asks why delivery is slow.

Every meeting has a deck. Every deck has a “status”. Every status has a colour. Nothing is green enough to be safe, and nothing is red enough to be honest.

The org has “standardized” updates:

• One-pagers

• RAID logs

• RACI matrices

• Weekly status notes

• Architecture decision records

• Postmortems

And yet, decisions still get re-litigated weekly because the point was never the content. The point was to prove the ritual happened. If the only time anyone looks at the doc is when leadership asks “did you fill out the doc?”, that is performance, not progress.

Velocity. Story points. Number of tickets closed. Number of meetings attended. Number of docs created.

All of that is fine as diagnostic data. It becomes a problem when it is treated as proof of impact. If you can hit your metrics by doing busywork, your metrics are rewarding busywork.

When you ask:

• “Why do we do this?”

• “What problem does this solve?”

• “Can we stop doing this?”

…and the response is some mix of “that’s just how we do it” and “it’s important for alignment”, you are not in a process. You are in a belief system. And belief systems do not tend to welcome hecklers.

Ritualized process usually shows up for reasons that feel rational in the moment.

If people get punished for failure, they start optimizing for safety. Not delivery. Not learning. Safety.

And ritualized process is safe because:

• It spreads responsibility across committees.

• It creates plausible deniability.

• It provides receipts.

When work fails, you can say: “We followed the process.” Which is the corporate version of “I technically did the thing.”

A lot of process is just management trying to reduce uncertainty without actually engaging with reality. If a leader does not understand the work, they often reach for mechanisms they can understand:

• status reports

• checklists

• approval gates

• steering committees

These tools create the illusion of control. They also slow everything down and erase nuance.

Maturity is the ability to make good decisions repeatedly. Standardization is the ability to do the same thing repeatedly. These are not the same.

You can standardize a bad workflow and become consistently mediocre. Congratulations, you are now “mature”.

Here’s the annoying part: ritualized process is often made of good intentions. Somebody once got burned by:

• missing a dependency

• unclear ownership

• ambiguous scope

• a launch that went sideways

• stakeholders being surprised

So they added a ritual to prevent it. Then another ritual to make sure the first ritual happened. Then a template to track the rituals. Then a dashboard to prove it.

Soon you have a system designed to prevent the last failure, not to enable the next success, and it keeps growing because nobody wants to delete the rituals that feel safe.

This stuff does not just “waste time”. It changes how people behave.

When the process is the boss, nobody is accountable for outcomes. Everyone is accountable for compliance. People stop asking “Did we solve the problem?” and start asking “Did we follow the steps?”

The performance rewards mechanical completion. Thinking is messy, slow, and sometimes uncomfortable. So people learn to:

• fill out the template

• say the right words

• show the right artefacts

…and avoid making real calls.

If every decision needs:

• a review meeting

• an approval gate

• a sign-off checklist

• an alignment pre-meeting

…you do not have a process. You have a queue. And queues are where urgency goes to die.

People are not stupid. They can tell when the rituals are hollow. So they become:

• disengaged

• sarcastic

• transactional

• resistant to change

Then leadership complains about “culture” without noticing they built the machine that produces it.

Not all ceremony is empty performance. Some process is genuinely valuable.

Process is worth keeping when it:

• reduces recurring mistakes

• makes work easier to coordinate

• improves clarity and decision-making

• shortens feedback loops

• increases autonomy, not dependency

Good process makes the work smoother. Bad process makes the work louder.

A quick test:

• If the process disappeared tomorrow, would the work get worse?

• Or would people just be slightly less annoyed?

If the answer is “less annoyed”, you’ve found a ritual that needs to justify its existence.

You do not fix this by adding a new framework. Please do not do that. That is how we got here.

You fix it by changing what the organization rewards, and by trimming the rituals that do not serve outcomes.

If a meeting does not produce a decision, it is probably a status performance.

Try this:

• Start the invite with: “Decision needed: X”

• End the meeting with: “Decision made: Y”

• If no decision is needed, it should likely be async.

For docs, treat them as tools, not proof. If the doc does not change a decision, it is optional.

Approvals feel safe because they distribute risk. They also distribute delay.

A better model is:

• one accountable owner for the outcome

• explicit constraints (budget, security, SLA, brand, legal)

• lightweight review only when risk is high

If everything needs approval, nobody is trusted. And if nobody is trusted, your best people will leave.

Every artefact should have a clear purpose:

• What problem does this solve?

• What decision does it support?

• Who uses it?

• How often?

• What happens if we stop?

If you cannot answer those questions, you do not have a process. You have a habit.

Yes, delete. Not “optimize”. Not “revamp”. Delete. Make a list of recurring rituals:

• meetings

• reports

• dashboards

• templates

• gates

Then ask:

• Keep (it creates value)

• Change (it is valuable but bloated)

• Kill (it is performative)

Treat deletion as a leadership skill. The capacity you save is real.

If your team ships nothing but your dashboards look great, congratulations, you have built a machine for producing dashboards. Pick a small set of outcome metrics that are hard to fake:

• cycle time (end-to-end)

• defect rates and customer pain

• adoption or usage

• incident frequency and time-to-recover

• customer support volume tied to a product area

Then use activity metrics only to diagnose why outcomes are bad, not to congratulate yourselves when outcomes are absent.

Teams do not usually create ritualized process because they love process. They create it because it is what the system rewards.

If leaders reward:

• neat decks

• perfect status reporting

• spotless compliance

• “alignment” without decisions

…that is what people will produce.

If leaders reward:

• clarity

• delivery

• honest risk

• learning

• outcomes

…the performance starts to collapse, because it stops being useful.

If you cannot change the whole system, you can still reduce the damage locally. Try this for a month:

• Cancel one recurring meeting and replace it with an async update.

• Delete one template section that nobody uses.

• Change one meeting agenda to be decision-first.

• Make one “status” meeting optional and see who still shows up.

• Remove one approval step by giving an owner a clear boundary and letting them run.

Small changes, repeated, are how you move from performance to progress.

And if someone asks why you are changing things, you can say: “Because we are here to ship work, not stage it.”

Which is still a performance, technically. Just a better one.