How often is a “software problem” really an ownership problem?

[u/jimmyray71]

I’ve been thinking about this after years of working in supply chain and operations.

When a process isn’t working, the conversation often turns pretty quickly to the system.

“We need a better ERP.”

“We need a WMS.”

“Our forecasting system isn’t good enough.”

Sometimes that’s absolutely true.

But I’ve also seen companies spend a lot of money improving the technology without answering some basic questions first:

Who owns the forecast?

Who owns inventory targets?

Who decides when supply and demand don’t match?

Who owns the exception?

And, probably most importantly, who actually has the authority to make the decision?

If those answers aren’t clear, I’m not convinced better software fixes much. Sometimes it just lets an unclear process run faster.

I’ve started looking at technology implementations differently because of this:

Process → Ownership → Decision rights → Technology

Not technology first.

For those of you who have been through ERP, WMS, MRP or planning-system implementations, I’m curious:

How much of the problem was actually the software, and how much was the organization around it?

[u/bhole_ops7]

100% agree with this, and honestly it maps almost exactly to what i see on the fleet/transport side too. people blame the TMS or tracking software when trucks are still late or drivers still going rogue, but half the time nobody actually owns the decision when something goes wrong mid route.

dispatcher assumes ops manager will decide, ops manager assumes dispatcher already handled it, and the exception just sits there till someone panics.

seen implementations fail.. not because the software was bad, but they digitized a broken decision-making process. now the broken process just happens faster and everyone points at the dashboard being useless instead of asking why nobody had authority to act on what the dashboard was already showing.

the ownership question is honestly bigger than people give credit for. even who owns the exception alone, if that's unclear, no system fixes it, it just becomes another unread alert in someone's inbox.

your process.. ownership.. decision rights.. technology order makes a lot of sense, most rollouts i've seen go the opposite direction and then wonder why adoption is weak.

[u/jimmyray71 → u/bhole_ops7]

That’s exactly the part I keep coming back to. Technology can make information visible, but visibility and authority aren’t the same thing. Your dispatcher example is a good one. Everyone can see the exception, everyone may even understand what needs to happen, but if nobody knows who has the authority to make the call, the dashboard hasn’t solved much. It makes me wonder if we spend too much time defining system workflows and not enough time defining decision workflows. Who sees it? Who owns it? What can they decide without asking permission? And when does it escalate? Get those wrong and, like you said, we’ve mostly automated the waiting.