Session 4: Truth early

Can people raise problems while there is still time to act?

Length: 45 to 60 minutes.
Format: short teach, real-work exercise, written output.

This is the highest-stakes session in the program. The point is not to practice perfect escalation language; it is to practice receiving bad news without punishing the messenger. If a leader gets the response wrong here, no one in the room will escalate next month.

Session at a glance

Length: 45 to 60 minutes.
You will need: the Issue Escalation Note template open or printed; the Scripts for hard moments page open; one currently blocked or at-risk issue picked in advance (see The week before).
Participants leave with: one better escalation path written down for a real, current issue — plus practice on both sides of an escalation conversation.

What we will teach

Early warning — the earlier the cheaper.
Escalation as a tool, not as failure.
Safe truth — what makes it possible to say a hard thing.
How leaders should respond to bad news.

Timed agenda

Time	Segment	Move
0:00 – 0:05	Open	State the question. Name what this session is not about (it is not about who escalated badly last quarter).
0:05 – 0:15	The teach	Walk early warning, escalation, safe truth, and leader response.
0:15 – 0:30	Side A: writing	Each person drafts an escalation note for the chosen issue.
0:30 – 0:50	Side B: responding	Pairs swap notes and practice the leader response.
0:50 – 0:58	Group sync	What patterns showed up? What landed; what stung?
0:58 – 1:00	Capture & close	Save the strongest version of the note. Confirm next steps.

Opening words

“We are practicing two things today: writing a hard note, and receiving one without making the writer regret it. We are not reviewing past escalations. We are not finding who got it wrong last quarter. We are working a real, current issue together so that by the time the next one hits, our muscles already know what to do.”

The teach (about 10 minutes)

Early warning. The cost of a problem grows the longer it is hidden. The first signal a project might miss its date is worth more than a perfect post-mortem after it does. Reward the early flag.
Escalation as a tool. Escalation is what we do with a problem that is too big for the current level. It is not an admission of failure. It is the next step in protecting the work.
Safe truth. People only raise problems early when they believe the room can hear it without retaliating, shaming, or piling on. Safe truth is built by the leader’s response, not the speaker’s phrasing.
Leader response. Compare the two patterns from the guide.
- Good: “Thank you for raising this now. What is the impact? What are our options? What do you recommend?”
- Poor: “Why did you let this happen?”

The phrase to plant:

The cost of bad news is paid up front. Hidden bad news compounds.

The exercise (about 35 minutes)

Side A — Writing the note (15 min)

Each person opens the Issue Escalation Note and drafts a note for the chosen issue. Use the pattern from Scripts:

Here is the issue.
Here is the impact.
Here are the options.
Here is my recommendation.
Here is what I need.

If two people are working on the same issue from different angles, that is fine — the differences are useful.

Side B — Responding to the note (20 min)

In pairs, swap notes. One person reads their note aloud as if for the first time. The other person responds as a leader using the Good pattern above — no improvising the Poor pattern, even as a joke.

Then swap roles.

After both pairs have run both sides, take 3 minutes for the group to share: which response landed? Which question helped the writer most?

Scenario for this session

Use this scenario as the day’s case if the team did not bring a real one. It is written generic enough to apply across any of our businesses.

The starting situation

A frontline contributor has discovered an operational problem on a project that crosses two reporting lines. Their direct manager has heard about it and signaled they think the contributor is overreacting. The matrixed project lead, however, would consider it a real risk if they knew.

The contributor does not know who to listen to. They are tempted to let it go because raising it could be read as “going around” their direct manager. They are also tempted to escalate past both of them, which they suspect will go badly.

They come to you for advice on what to do.

What the group should produce

One completed Issue Escalation Note for this scenario, plus a written escalation path describing:

Who the note goes to first.
What the contributor says to their direct manager about having sent it.
What happens if the direct manager pushes back on the escalation itself.
The chain-of-command precedent the company is setting by handling this case the way it does.

Practice both sides

Have one pair of leaders run this as a role-play:

The contributor reads the situation and asks the question verbatim: “Who do I actually listen to?”
The receiving leader practices the Good response from this session’s teach: thank them, understand the conflict, surface the constraint, name the call.
Then practice the Poor response on purpose, briefly, so the room feels the difference: “Well, you report to me — so listen to me.”

Where this goes wrong

The most common failure: the room resolves the chain-of-command question by rank rather than by constraint. The good answer is not “your direct manager wins because they sign your reviews.” The good answer is “your direct manager owns your time and priorities; the project lead owns the project’s integrity. If those two are in conflict, name the conflict explicitly and bring it to someone who can settle it — usually your manager and the project lead in the same room, not the contributor caught between them.”

If a leader in the room resolves the case by rank instead of by constraint, that is a teachable moment. Replay the scenario.

Closing words

“The note we land on today goes to [appropriate person] by [date]. We are practicing this so that when the next real one arrives unannounced, we do not freeze. If someone in this room raises a hard issue this week, every leader here remembers: thank them first.”

Common derailments and how to redirect

If you hear or see…	Then say…
The room avoids picking a real issue	“A fake issue teaches us fake habits. Use the one we picked. We will not name-and-shame.”
Someone slips into “Why did you let this happen?”	“Notice what that question does to the writer. Try a different first sentence.”
The writer apologizes for raising the issue	“Stop. You do not need to apologize for early information. Read the note as written.”
The room is silent during the writing block	Silence is correct here. Resist the urge to fill it.
A real grievance surfaces mid-exercise	“That sounds important. Let’s book a separate conversation about it. For this hour, we stay on the practice.”

Output

One better escalation path for a real, current issue, written down, with named recipient and named date.

Facilitator notes

This is the session where psychological safety either takes root or does not. Watch the room. Notice who is silent. If a quieter participant has not spoken by minute 30, invite them in — warmly, not as a test.
Avoid scripted role-play. Use real situations. Fake stakes produce fake habits.
If a leader in the room gets the response wrong, do not embarrass them in front of the team. Pause, say “let’s try the first sentence again,” and let them re-take it.

The week before

Pick the issue. Tell the issue’s owner so they arrive ready to describe it.
Re-read Scripts for hard moments so you can quote the patterns without breaking flow.

The week after

Send the final escalation note to its intended recipient within 48 hours. The point is not to keep practicing in the abstract.
Notice one moment this week where someone raises a hard thing. Notice your first sentence in response. Bring that observation to Session 5.