The Output #8: The Overdue Update
A great conversation I had just went life on my friend Diana's feed. We'd planned to release it together on both of our shows. A version of that is finally happening, months late, and nothing went wrong. Nobody fought. That's the part worth talking about.
It's a story about the six or seven weekly calls where I could have said what I was thinking ("this keeps dragging on. We should probably stop planning a joint launch") and said "no rush, take your time" instead.
I tell myself that was patience. It wasn't. This was avoidance wearing patience's clothes. I didn't want one mildly uncomfortable conversation, so I let the much more expensive thing happen instead: the plan we agreed to quietly died.
Here's the part that took me a while to admit. Agreeing on the plan was easy. Three-ish weeks, joint launch, both feeds. All of it said out loud, all of it hopeful. The hard part came when reality broke the plan and somebody had to update it. That's when it turned into a game of chicken: the first person to say "this isn't happening the way we agreed" becomes the one who made the death official. So neither of us said it, week after week, inside the standing call we built to keep the project alive.
Most advice about finding your voice points you at content: write the bolder post, say the sharper thing, stop hedging your captions. That's real, but it's not where I lost this one. I lost it in a weekly check-in. The version of me that hides isn't the one who's scared to have an opinion. It's the one who's scared to give the update that makes a plan's death real.
So here's the wording, since I promised it on the show. A real update has three parts: the status, your read, and a question.
"Real status check: this isn't going to be done by [date]. Here's what I think is true: I don't think coordinating the launch makes sense anymore. What do you want to do?"
Why it works: you're reporting on the project, not the person, so it can't land as an accusation. You say your read out loud instead of managing theirs. And the question hands the plan back to both of you, which is what keeps it from becoming an ultimatum. The inward version is the same move: "This draft has been in progress for three months. I don't believe I'm finishing it. Kill it or put it on the calendar."
If you're sitting on something with a shelf life (a launch, a collaboration, an opinion that only matters while it's current), the risk was never saying the wrong thing. It's staying so reasonable that the thing you wanted quietly expires on its own, and nobody even has to tell you no.
(This week's episode tells the full story: the three true things I never said out loud, and what each one cost. And the conversation that started all of this is finally live — Diana's "Be The Light: Thriving in Uncertainty" on Courage & Purpose. Go listen. It held up.)
The Output
Pick one project where what you privately believe and what you've been saying out loud have drifted apart. The collab, the launch, the draft you keep politely deferring. Give it its overdue update this week: say the true status to the person it involves, or write it where you can't avoid it if that person is you. Don't solve it in the same message. Don't pitch the new plan. Just get the true thing outside your head. Notice that it feels more uncomfortable to write than to keep waiting. That discomfort is the whole cost you've been avoiding.
Inputs
- Wiring Claude's SEO tooling into the Kajabi MCP beta, kicked off by a video on creator systems that finally made the pipeline click.
- A moon ceremony with horses: my wife, a visiting friend, and a genuinely good workshop in being present.
- Rewriting the Voiceprint pitch to lead with what it gets you, not what it is.
Before you go: if your AI still writes like everyone's AI, it's missing a file that tells it who you are. Voiceprint is my free 30-minute setup that fixes that. Get yours at shawnbuttner.com/voiceprint
Responses