Blog
When Leadership Leaves the Room
Steering committee meetings are easy. Everyone’s prepared and the sponsor is in the room, so the right things get said.
Most ERP projects aren’t decided in those meetings. They’re decided on a Tuesday afternoon workshop with half the attendees missing. They’re decided in a Teams message at 9 p.m., and in the calls that get “pushed to next week” for the third time.
In Part 1, I argued that buy-in is where a project starts, not where it’s won. This part is about what comes next: keeping the client team motivated, supported and accountable when their leadership isn’t watching.
Status reports don’t show the difference
Troubled projects look the same on a status report: both kinds are red or amber. The difference is in how the people behave.
Signal
Recoverable project
Slow-motion failure
Decisions
Have an owner and a date
Get reopened every meeting or pushed because of attendance
Disagreement
Happens in the room
Happens in side channels and Teams messages
Scope changes
Are priced, chosen and scheduled
Are absorbed quietly while everyone tries to make it work
The team
Still says what it sees and stays engaged
Has stopped raising issues and stopped attending meetings
Every row in that table plays out day to day, not at steering committee. Try it now: score your current project, row by row.
A friendly VP and a tired team
Here’s another composite scenario from the session:
Build phase at a services company. A client VP messages your consultants directly at night with “small” changes. They say yes because he’s friendly and senior. Nothing is logged, the budget is thinning and the team is tired. When your account executive pushes back, the VP says: “Your program manager is the inflexible one.”
The hard part is that everyone in the scenario thinks they’re doing the right thing. Your consultants think they’re serving the client. The VP thinks he’s moving fast. No one is acting in bad faith, and the project is still being taken apart one small yes at a time.
Hold the boundary for the team, not against the client
The VP’s needs are usually legitimate. What’s breaking the project is the channel he’s using. The “run rules”:
- Hold it for your team. Every request routes through you, and you take the heat for it. The cost: you’re the villain for a while.
- Say yes to the need and no to the channel. Set up one intake point with fast turnaround and a queue he can see. The cost: the official path has to be faster than texting a consultant at night, or he’ll go back to texting.
- Align your own side first. Boundaries fail when sales or leadership folds behind you. Brief them before the VP calls them, because he will. The cost: a hard internal conversation comes first.
That third move is the one most people skip.
Supporting the client team, not just managing them
Being a partner means the support goes both ways. The client’s process owners and super users are carrying a day job and your project. When their leadership isn’t around, they need three things from us:
- Clarity. Who decides, by when, and where it’s written down. A RACI isn’t bureaucracy; it’s permission to act.
- A fast, visible path. If our process is slow, people will route around it. That’s on us.
- Cover. When a process owner raises a problem, they need to see us treat it as useful information, not as a complaint.
A boundary conversation in five steps
Confrontation isn’t easy, but sometimes it’s required. Be firm on the process and warm in the delivery:
- Name it. “This is the fourth request outside the queue.”
- Tie it to their goal. “You told me the date matters most.”
- Offer priced options. “Here are two ways to do this, and what each one costs.” Never offer just one option; one option is an ultimatum.
- Let them choose. Then stop talking. Most of us fill the silence and end up negotiating against ourselves.
- Document it. Do it the same day, in plain words, in one source of truth. For us, that’s Azure DevOps.
The takeaway
The client team takes its cues from us when their leaders aren’t around. If we keep side channels open, they’ll use them. If we make the official path fast, clear and safe, they’ll use that instead, and they’ll hold each other to it.
Your turn: Which boundary do you wish you’d set one month earlier?
Next in the series: the quiet phase. Testing is when no one is around, and it’s where projects are quietly won or lost.



