When the System Starts Managing the Resources

timothyferguson1
Apr 26
3 min read

April 26, 2026

I've spent enough time around process design to notice a pattern. Smart, capable leaders — the kind who deliver results, hit their numbers, and earn their promotions — will sometimes redesign a process without ever looking up to see who they're affecting on either side of it.

It's rarely malicious. It's not even careless in the way we usually mean that word. It's a blind spot. They were promoted for what they delivered inside their box, and somewhere along the way no one taught them to see the edges of that box, or what flows across them.

I want to be careful here. This isn't a character flaw. It's a missing competency — and competencies can be built.

The unintended consequences aren't really unintended

When a leader changes a process in isolation, the downstream effects don't materialize out of nowhere. They were predictable. They just weren't investigated.

Maybe the new approval workflow shaves two days off the team's cycle time but adds five days to the supplier feeding them. Maybe the simplified intake form pushes the complexity onto a customer support team three departments over. Maybe the efficiency gain on paper translates into burnout, errors, and rework somewhere no one is looking.

The consequences aren't unintended. They're uninvestigated.

The revolving door

Here's where it gets expensive.

When suppliers — internal or external — are pushed into a process that overloads their resources, they eventually fail. And when they fail, they're often labeled as the problem. Performance issues. Capacity issues. The wrong fit.

Dissatisfaction sets in. Turnover follows. A successor steps in, inherits the same process, and fails for the same reason. A revolving door gets built around a process that no one stops to question.

This is what I've come to call a monster system — a process that has grown so demanding that it stops being a tool and starts being a force. The system is now managing the resources, instead of the resources managing the system.

And once you see it, you see it everywhere.

SIPOC: a tool for leaders who want to see the whole picture

There's a Lean Six Sigma tool called SIPOC — Suppliers, Inputs, Process, Outputs, Customers. It's deceptively simple. You map who supplies what to your process, what comes in, what your process does, what comes out, and who receives it.

That's it. Five columns.

But what SIPOC really does is force a leader to step outside their box and acknowledge the system their process lives inside. It surfaces the upstream people whose resources you're about to consume and the downstream people whose work you're about to shape. It makes the boundaries of your decision visible — before the decision is made.

Yes — building a SIPOC takes time. It requires conversations with suppliers and customers. It slows the start of an initiative. I won't pretend that's nothing.

But the time you invest in a SIPOC pays dividends, and not small ones.

Where the dividends show up

When suppliers and customers are part of mapping the process, they become part of owning it. Change management — the part of every initiative that quietly determines whether it succeeds or fails — becomes dramatically easier when the people affected helped shape what's coming.

The process you end up with is more sustainable, because it was designed against the actual capacity of the people who feed and consume it. The unintended consequences shrink, because most of them surface during the SIPOC conversation rather than three months in, after damage has already been done. And the revolving door slows, because suppliers aren't being set up to fail by a process that was never built with them in mind.

A few extra hours of mapping at the start can save you a year of churn at the end.

The competency worth developing

If I could put one expectation on every leader designing or redesigning a process, it would be this: before you change anything, map the system you're changing.

Not exhaustively. Not perfectly. Just enough to see who you're affecting, and to invite them into the conversation.

That's the competency. Systems thinking isn't an academic exercise — it's the difference between a leader who builds processes that endure and a leader who quietly creates monster systems for someone else to inherit.

The good news is it's learnable. The first step is picking up a tool like SIPOC and using it before the next time you change something that matters.

Because the alternative is what I've watched too many good organizations drift into: a system that has stopped serving its people, and started consuming them.

If this resonates with something you've seen, I'd be curious to hear about it in the comments.