Optified - The person who can kill your project isn't always the person in the room

You consulted everyone. The project still stalled. Here's why.

You ran the meeting. Sales was there, ops was there, the warehouse lead was there. Everyone nodded. Six weeks later, the new process still isn't being used properly — and the reason usually isn't in that room. It's the person who wasn't.

Two questions, not one

Most owners only ask one question when planning change: who's affected by this? The question that actually predicts whether a project survives is different: who has the power to slow this down, and how much do they care?

Plot every person who touches the process on two lines — power (can they actually block or delay this, formally or informally) and interest (do they care enough to act on that power). Four groups fall out:

• High power, high interest — manage these people closely. They can make or break the project and they're paying attention. This is usually the smallest group and the most obvious.
• High power, low interest — the group that actually kills most projects, quietly. A senior manager who isn't opposed, just indifferent, who doesn't attend the second meeting, doesn't read the update, and then — three months in — asks why the project is "still not sorted," having never engaged with why it's taking time.
• Low power, high interest — keep informed. They care and they'll notice if you go quiet, but they can't unilaterally stop anything. Good source of early warning on real usability problems.
• Low power, low interest — monitor lightly. Don't spend your limited attention here.

Where owners get this wrong

The instinct is to focus effort on whoever is loudest in the room — usually high interest, sometimes low power. Meanwhile the person who could have flagged a real blocker in week one — a warehouse manager who knows the current workaround exists for a genuine reason, or a finance lead who knows a regulatory deadline nobody mentioned — sits in the high-power, low-interest quadrant, unengaged, until it's expensive to involve them.

The fix isn't more meetings. It's five minutes, before you start, honestly naming who actually has the power to slow this down — including the people who don't seem interested yet — and deciding deliberately how you'll get and keep their attention.

Why this matters most for system changes specifically

A new ERP or process change touches more people than any other kind of business decision — everyone who works with quoting, invoicing, or inventory has a stake, whether or not they show up to the kickoff. Skipping this exercise is how a technically successful implementation still gets quietly abandoned six months later, because the person who could have made it stick was never actually engaged.

This kind of stakeholder mapping is part of every Value Discovery engagement — not as a separate workshop, but built into how we scope the process from day one, so the plan accounts for who actually needs to be on board, not just who was in the room.

Want this measured for your business?

Book a free 20-minute Value Scan and we'll tell you whether there is a commercially meaningful opportunity in the process that hurts most. If there isn't, we'll say so.

Not ready to talk? Estimate what one process costs you a year with our free calculator.