Apologize for the Timing, Never the Ask

Most leadership content tells you to pick a side. Defend your person. Hold the line. Don't back down.

The harder skill — the one nobody talks about — is what to do when someone you're coaching is right, a senior peer is reacting badly to their correctness, and the project itself is hanging in the balance. Add one more layer if you lead the way I do: as a fractional CMO embedded inside a client's organization, where you have no formal authority over anyone in the room. You can't escalate. You can't pull rank. You can't issue a directive.

You have your judgment, your relationships, and your words. That's the whole toolkit.

Here's the principle I keep coming back to: apologize for the timing, never the ask.

Those are two different things, and most leaders collapse them into one. When the room gets tense, they soften the underlying message until it disappears, just to lower the temperature. The temperature drops. So does the work. Everyone goes back to their corners, and the original problem — the one that triggered the exchange in the first place — stays exactly where it was.

There's a better move.

The setup

A project had been dragging for months. In a 1:1 with the marketing manager I work alongside at one of my clients, I asked her the only two questions that matter when work stalls: who is doing it, and by when? She didn't have the answers. So I coached her: go ask. Get accountability assigned. Get a date on the calendar. Otherwise this never moves.

She did exactly that. Her email was textbook — specific, named the right people, asked clear questions, requested a deadline.

The senior operations peer on the receiving end read it as pressure and pushed back. Twenty-four hours, he said. Give him twenty-four hours before chasing him for deadlines.

He wasn't entirely wrong about the timing. He was wrong about almost everything else — including the fact that the project had been open for months, not a day. But the senior dynamic, the seasonal pressure, and the public CC line meant the marketing manager was about to absorb a hit she didn't earn for coaching she correctly executed.

So I wrote back.

The reply, annotated

Four sentences. Here's what each one is doing.

"Thank you for the partnership. I know opening the season involves many moving pieces, and we understand the necessary prioritization to support the customer

experience."

Gratitude that names his actual role. Specific, not generic. People de-escalate when they feel seen. This sentence makes him visible before it asks anything of him.

"During my 1:1 with [her], I asked her about accountability and the associated timelines to wrap up this project. Her email is a response to my request for clarity regarding accountabilities and timelines."

This sentence does the most work in the email. It locates her message in context — she was doing what I asked her to do — which quietly defends her without making it adversarial. It also signals that snapping at her is, functionally, snapping at me. Reframe complete, in two sentences, with zero accusatory language.

"I realize now that the timing of the request naturally added extra pressure, which wasn't my intention. That's my fault, my apologies."

This is the sentence most leaders get wrong. I apologized for the timing, not the ask. The underlying need — accountability, named owners, a date on the calendar — stayed completely intact. The apology covered only the unintended pressure my coaching created.

Nothing else.

"Thank you for all you do. I know it's a heavy lift, and we appreciate your leadership and focus on the customer experience."

Re-elevates him and re-anchors the shared goal. Ends the exchange on the thing that matters more than either of our egos.

The conversation nobody saw

There was a second exchange, in private.

The marketing manager wrote back to me — frustrated, and rightly so. She'd been chasing this for months. She'd followed up multiple times. She had absorbed his snap and watched me publicly apologize for the timing of a request she'd been making, in various forms, for far longer than 24 hours. From her seat, it could have read as me going easy on the wrong person.

So I told her the truth.

She was right. The frustration was earned. The project should have moved months ago. And — the public reply wasn't about who was right. It was about what would actually move the work forward in the next 48 hours. Matching his tone would have hardened him. The honey was strategic, not soft. The underlying ask never moved. The deadline question still needed an answer. We just lowered the temperature enough that someone could give it to us.

De-escalation isn't capitulation. It's choosing the outcome over the optics. But it only works if the person who was right hears, in private, that you saw it too.

Why this matters

Amy Edmondson's research on psychological safety — the foundation of what Google's Project Aristotle identified as the #1 factor in team effectiveness — found that 85% of employees have withheld important information from their manager because they feared the consequences of speaking up.  Getleda

Eighty-five percent. That silence is where projects die.

If the marketing manager had absorbed that snap without backing, she would have stopped asking the hard questions. She would have hedged her follow-ups. She would have softened the accountability ask until it disappeared. And if I had publicly defended her without addressing her in private, she would have learned that her fractional leader manages optics, not truth.

Simon Sinek puts it cleanly: people will trust their leaders when their leaders do the things that make them feel psychologically safe.  QuoteFancy

When you lead without formal authority — as a fractional, an advisor, a consultant embedded in someone else's organization — you don't get to rely on titles or org charts. You only have the quality of the moves you make in moments like this. Public ones and private ones. Honey and honesty.

Apologize for the timing. Never the ask. And make sure the person who was right knows you knew it.