Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

Process Debt

A field guide for a team whose processes have grown bloated or stale: why they outlive their reason, and how to rebuild them for what the business needs.

Process Debt
92
process-debt

Why processes built for an earlier stage keep running after their reason has gone, and how to rebuild them for what the business needs now.

How things get done

The challenge: Our processes have grown bloated or stale

Steps get added when something goes wrong and seldom come out, because removing a safeguard feels risky while keeping it costs a little each time. As a company grows, procedures that once brought order turn into delay, and the slowness gets taken for a people issue when it is a design one. Each outdated step charges interest on the work that passes through it. Inside are ways to trace each step to a current need, retire the rest, and keep processes fitted to the business as it is now.

Who it’s for: Leaders of a function or a company that has grown: an operations head, a chief of staff, a general manager, anyone whose week is spent in reviews, reports and sign-offs built for an earlier stage. Read it on your own first, then take the conversation in part three to your team.

How it shows up

Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.

The scene

In her second week, a new operations manager asks a simple question in a staff meeting: why does a small purchase need three sign-offs? The room takes a while to answer. The first sign-off came in after a vendor problem years ago. The second was added when the company opened a second office. The third arrived with a new finance lead who has since moved on. Each one made sense on the day it was added, and each one has an owner who would defend it. It is hard to find anyone who remembers the last time one of them caught something. Meanwhile the weekly review that once ran an hour now runs most of the afternoon, and a report goes out each Friday that people struggle to name a reader for. The company grew and the market sped up, and the steps stayed. The manager’s question hangs in the room, and the meeting moves on to the next item.

Where it lands

  • In you: much of your week often goes to reviews, reports and sign-offs that exist because of a problem from an earlier stage, and some of the approvals the work waits on are yours.
  • In your team: exceptions tend to multiply, meetings stretch, and a workaround that most people use has become the real process while the official one sits on the shelf.
  • In your organization: cycle times typically lengthen as the company grows, and the slowness gets taken for a people problem when it is a design problem.

Questions to ponder

Think of the process that slows our team most, and ask:

  • How many steps, approvals or reviews does a piece of work pass through, and how many of those were added in the last few years?
  • Can the people who run it say what each step prevents?
  • Has the process changed since the business last changed in size, market or model?
  • Is there a workaround that people tend to use instead, and is it better?
  • Who owns the process, and when did anyone last review it on purpose?

Questions to discuss

With the oldest unchanged process on the table, and what three people said it was built to prevent:

  • Which of our processes was built for a problem we no longer have? Trace each step to a current problem before anyone defends it.
  • Where does a workaround do the real work while the official process sits on the shelf? People may not have felt free to say the workaround is better.
  • How could we change the way we keep our processes so that each of us helps retire the others’ steps, and nobody has to defend a step alone? Name one step each of you owns that you would take out this month, and what the others would do to make that safe.

Try this week

Pick the one process that has gone unchanged the longest: an approval, a review, a recurring report or a meeting rhythm. Ask three people who run through it what it was built to prevent. If they can’t name the problem, or the problem no longer exists, you have found debt. If the problem is real and current, the process is doing its job, and you can stop there. Either way, you will have asked a question that the process itself rarely gets asked.

Keep reading with a free account

  • How to tell whether a process is bloated, stale, or already replaced by a workaround people trust
  • A one-page way to lay out a process, with what each step prevents and when that last happened written beside it
  • Three questions for a scheduled process review, and why a process that hasn’t changed through two years of growth is a candidate for rebuilding
  • When a workaround is the better design, and how to make it the official process
  • Why automating a step before asking whether it should exist leaves you with a faster version of an outdated process
  • The research behind it, and books to read next
  • The toolkit: questions to ponder, questions to discuss, things to subtract, actions to take
  • The kit, as downloads: the full Field Guide, a Leader’s Guide, and slides for the team conversation
Create a free account

Free, no card.

Open the field guide >>

About the author

Mark D. Benson
Mark D. Benson
Founder of Resonant Vector™
Resonant Vector
Full profile →

Mark D. Benson is the founder and principal writer of Resonant Vector, the home of Pressure Intelligence, and the host of Pressure Rising™. He is a product and systems leader who has spent his career running global teams, complex platforms, and consequential decisions under real constraint.

His career sits where strategy, technology and large human systems meet, in places where high stakes are the norm.

Resonant Vector is his commitment to learning in public and sharing what helps leaders and teams perform under pressure.

More about Mark can be found at markdbenson.com.