Page 15 covered what to do inside your own head when something goes wrong: pause, don't assume the worst, break it into next steps before you react. That's the composure half. This page is the other half. Once you're calm, what do you actually say when you break the news to someone else?
That's a different skill. Plenty of people who've mastered the first one still get the second one wrong.
The problem isn't the problem
Nobody holds it against you that something broke, a deadline slipped, or a client is upset. Things go wrong constantly, and that's not the part people judge. What they remember is whether you showed up with just the alarm, or with the alarm and a direction.
Raising a problem with no proposed next step forces the other person to do two jobs: understand what happened, and figure out what to do about it. Raising it with even a rough plan leaves them one job, deciding whether your plan is right. That's a smaller ask, and it's why the second version earns trust faster.
What "bringing a plan" actually looks like
You don't need the full answer. You just can't show up empty-handed.
- Name the problem in one line. No build-up, no burying it in context. Say what's wrong first.
- Add your read on why it happened. Even a guess shows you've thought about it, not just reacted to it.
- Propose at least one next step. "Here's what I'd try" is enough. It doesn't have to be final.
- Say what you need from them. A decision, a resource, or just visibility. Make it easy to know how to help.
The same shape works whether you're escalating a broken process, pushing back on a deadline, disagreeing with a decision, or raising an objection mid-meeting. Different situation, same instinct: don't hand someone a fire. Hand them a fire and a bucket.
Where this picks up from staying calm
The pause from Page 15 is what makes this possible in the first place. You can't propose a clear next step while you're still reacting. But composure alone doesn't finish the job. Someone can stay outwardly calm and still deliver a problem with nothing attached to it, and that reads as passive, not composed. Calm gets you into the room in the right state of mind. This is what you do once you're in it.
Why this builds a reputation
This isn't a communication trick, it's a signal about how you operate under pressure. A colleague who consistently shows up with options gets handed the next ambiguous, high-stakes thing, because they've already proven what they do when something goes sideways. That trust is built in exactly these small moments, not in the big wins.
The trap to avoid
Don't over-correct into hiding problems until they're fully solved. That's a different mistake, not the same skill, and it usually costs more. The goal isn't a perfect plan before you speak up. It's to never arrive with a problem and nothing else, even if that something else is just your best guess.
Closing thoughts
The problem was never going to be the thing people remembered. What they remember is what you brought with it. A plan doesn't have to be right to change the conversation, it just has to be there. Show up with a direction often enough, and people stop bracing for the bad news and start waiting to hear your read on it instead.