Late-Stage Truth Is Expensive

Performance Mode is expensive.

If you run in-house Brand Ops / Creative Ops / Marketing Ops, you know the moment:

Everything looks aligned… right up until the final stretch.

Then approvals reopen. Stakeholders “just have a quick thought.” Someone escalates risk without naming the rule. And the timeline stays put while the work reopens.

And someone says: “Wait — this isn’t what I thought we agreed to.”

This isn’t a communication problem. It’s a truth-timing problem. And it’s a collaboration system problem.

Because the default is sneaky: Teams learn to perform alignment in the room… and deliver the real truth later, when it’s loud.

Late-stage truth is expensive. Early-stage truth is cheap.

The Breath-Holding Loop

I learned this pattern far from corporate.

As an actor, I spent years in rooms that sounded “all good”… while everyone was holding their breath.

People would say the right thing in the room. Then after-work drinks would tell the truth. Private threads would tell the truth. Sometimes the truth would only show up on social media.

Not because people were bad — but because honesty felt risky. So truth waited.

And when truth shows up late, it often shows up as a veto.

Rework is delayed honesty.

I’ve seen the same loop across nearly 100 high-stakes teams — nonprofit boards, commercial agencies, Ivy League institutions.

Different missions. Different politics. Same failure point: The process has no normal, predictable way for truth to land early — while the work is still shapeable.

Teams aren’t busy. They’re braced.

A quick reintroduction

Some people know me through arts and inclusion work. Some know me as a facilitator. Some know me as the person teams call when a room gets polite… in the way that means we’re one sentence away from an explosion.

Here’s the simplest way to say what I do:

I help teams install Rehearsal Mode — a lightweight operating system that makes it normal (and safe enough) to surface reality early, while it’s still cheap to fix.

Not to make teams “nicer.” To make decisions stick, and to combat unspoken tension that waits until the last minute.

Where truth gets stuck (a simple lens)

When approvals keep reopening, truth is usually stuck in one of three places:

Align — context is vague, false, or sanitized “We’re fine.” “We’re on track.” “Everyone’s aligned.” (Translation: the constraints didn’t make it into the room.)

Agreements — decision rights and rules of disagreement are implied (Who decides today? What counts as “done”? What happens if we disagree? If it’s not explicit, the system decides for you — usually at the worst time.)

Notes — decisions aren’t captured, so they can’t hold (If it’s not written down, it’s not real. The team relitigates. The work reopens. The loop continues.)

This is my shorthand for it: ACT

• Align with context.
• Co-create the agreements.
• Take notes like decisions matter.

Rehearsal Mode isn’t “more meetings.” It’s fewer surprises — because objections become usable constraints before they become rework.

And yes: it reduces approval cycles because it makes constraints visible early.

So here’s one mechanism you can install this week.

Stoplight Approval (the missing lane is Yellow)

Most approval systems are binary: yes / no.

But most real feedback is Yellow:

“I can live with this if…” “Here’s the constraint you need to design around.”

When teams don’t have an official Yellow, truth goes underground — and shows up late.

Yellow is disciplined honesty. It keeps momentum and protects trust. It also changes the nervous system of the work:

Instead of “don’t rock the boat,” the system says, “Name the constraint early. We can hold it.”

Copy/paste: Stoplight Approval

Try this (out loud, in the meeting):

“Before we call this approved: are you green, yellow, or red — and what would move you one step closer to green?”

Define it:

• Green: I approve as-is.
• Yellow: I approve if we honor this constraint: ________. (one constraint only)
• Red: I can’t approve because ________. (name the decision rule & what would move you off red)

Yellow rule: constraint, not a vibe. Not: “I’m not sure.”

• Yes: “If we add X disclaimer, proceed.”
• Yes: “If we remove Y claim, proceed.”
• Yes: “If we adjust the audience targeting to Z, proceed.”

In-house brand Yellow examples (steal these):

• Legal/Claims: “Yellow if we remove ‘guaranteed’ and add the approved disclaimer language.”
• Brand: “Yellow if we keep photography within [these 3 usage rules] and avoid [this tone/phrase].”
• Exec/Strategy: “Yellow if we clarify the primary audience to [segment] and cut the secondary message.”
• Comms/PR: “Yellow if we align on one approved line for [risk topic] before publishing.”
• Product: “Yellow if we don’t imply feature availability until [date / release condition].”

Close the loop (this matters more than the question):

Read back the Yellows as constraints → assign owners → set the re-green date → and write it down.

Two notes that make this hold inside real orgs:

• Where the Notes live: a single “Decision Log”. One place. No scavenger hunt.
• How you protect the boundary: if someone raises new constraints after the approval meeting, it becomes a new request with a new timeline. Not punishment. Physics.

Because decisions that aren’t captured don’t exist. They just haunt the next meeting.

Why this matters (especially right now)

If you’re implementing AI tools / CRMs / workflow platforms, adoption often fails right here:

Your system has nowhere safe to put the truth until it becomes resistance.

So leaders interpret resistance as attitude. Teams interpret leadership as pressure. And the tool becomes another stage for Performance Mode.

But the future isn’t just technological. It’s relational. And we are capable of building systems that can actually hold it.

That’s permission to lead differently: Not by demanding courage from individuals… but by designing conditions where truth is cheaper than silence.

Where does truth tend to show up in your org — in the room, in side threads, or at the finish line?