What Senior Stakeholders Actually Hear When You Say It's Fine

"Yeah, we're fine. Bit tight in December, but fine."

I've said that sentence in a steering committee. More than twice. I believed it every time, and every time it cost me more than the truth would have.

In your head, "fine" means something quite precise. It means: the plan is under pressure, I know exactly where, I'm working it, and I'll shout the moment it gets worse.

None of that arrives. What lands on their side of the table is much simpler. No decision needed from me. No money needed from me. Nothing for me to raise with my own boss. I can stop thinking about this workstream until the next meeting.

And then it gets worse, because your sponsor doesn't keep your "fine" to themselves. They repeat it. By Thursday your carefully hedged, privately anxious "bit tight" has become a green box in somebody's board pack, with your name next to it. You've now got two problems: the original one, and the growing gap between what people believe and what's true.

Take a network refresh for a waste management company. 112 depots and transfer stations, new edge kit, a 12-week rollout window agreed around the collection calendar because nobody sane touches depot networks in the weeks either side of Christmas, when the rounds double and every vehicle is tracked.

Week 3: hardware delivery slips by two weeks. Annoying, recoverable, the team has a plan. Status reported: fine.

Week 5: the addressing plan turns out to be wrong for about 30 of the depots. Rework. Two engineers working weekends. Status reported: fine, bit tight.

Week 8: the first dozen installs take three nights each instead of one, because the depot comms rooms don't match the survey.

Week 9: the sponsor hears about it from the fleet operations director, who heard it from a depot manager. Not from you.

Here's the part that still stings. In week 3, that slip was cheap. The sponsor could have paid for expedited freight out of a contingency line you didn't know existed. Or moved 20 of the quieter depots into February and taken the pressure off the whole schedule. Both of those were live options in week 3. Neither existed in week 9, because by then the Christmas freeze was three weeks away and the only remaining option was to stop.

The two-week slip didn't do the damage. The six weeks of "fine" did.

A piece of bad news is worth the most on the day you learn it, because that's the day the largest number of options are still open. Every week you sit on it, options quietly close, and the same sentence you were scared to say gets harder to say, not easier.

There's a story people tell themselves here, and I've told it too: I didn't want to worry them until I had a solution. It sounds responsible. It isn't. You're not protecting your sponsor. You're protecting yourself from an uncomfortable ten minutes, and you're paying for that comfort with their options and their credibility.

And credibility is the actual currency. No sponsor expects a clean programme. Every one of them has watched delivery go sideways. What they're working out, meeting by meeting, is a much narrower question: when something goes wrong here, will I hear it from this person first, or from someone else? Answer that question well twice and you'll get the benefit of the doubt for years. Answer it badly once and you'll be chased for detail for the rest of the programme.

Most status updates fail because they describe weather. Here's the shape that works instead. Where we actually are, with a date or a number in it. What that means. What I'm already doing. What I need from you, and by when.

Compare these two.

Before: "The migration is progressing well. We've had some challenges with data validation but the team is working through them and we'll keep you posted."

After: "We're going to miss the 14 March cutover. Realistic date now is 4 April. The cause is validation failures on two legacy tables, roughly 90,000 records that don't map cleanly. I have two people on it full time. I need a decision from you by Thursday: hold for 4 April, or cut those two tables from scope and go live on 14 March without them. My recommendation is to cut them and migrate them separately in May."

The second one is horrible to type. It takes about forty seconds to read. And in my experience sponsors are visibly relieved by it, because you've handed them something to do. You've turned a vague worry into a decision with a deadline and a recommendation attached.

Notice the recommendation. Don't present two options and stand back like a waiter. You're the one with the detail. Say what you'd do.

Senior stakeholders exist to make decisions above your authority, spend money you can't spend, and move obstacles that sit in other people's departments. That's the role. Most of them have never had it explained to them in those terms, which is why so many steering committees turn into an hour of watching slides.

So explain it. First meeting, out loud: here's what I'll bring you every fortnight, here's what amber means when I say it, here's the kind of thing I'll escalate and how fast. Then do exactly that, boringly, for months. The cadence is what makes the bad news survivable when it comes, because by then you've proven you don't cry wolf.

The leaders I've watched do this well are never the ones with the fewest problems. They're the ones whose sponsors have stopped double-checking them.

Open the pack for your next steering meeting and read the top line. If it doesn't contain a date, a number, and a request, rewrite it until it does: where the work will genuinely land, the one decision you need, and the day you need it by.

Then send it the day before the meeting rather than presenting it in the room. The people who need to say yes will have had time to think, and you'll find out what they're worried about before you're standing in front of them.