I've run more of these programs than I can count. The onboarding call goes great. The voice guide lands. The first three or four posts go up, get engagement, get shared internally by people who are surprised the executive finally sounds like a human being. Everyone feels like it's working.
Then, around week ten or twelve, something quiet happens.
The posts I send back from drafts start taking longer. The interviews get rescheduled. The CEO has a board cycle closing, or a fundraising push, or a customer escalation. There's always a reason. By week sixteen, the cadence is maybe a third of what it was at launch. By month four or five it's over. Sometimes the executive emails to say so. More often they just stop responding to drafts and we both know what that means.
Here's what nobody wants to say out loud: the executive did not run out of things to say. The program was built to die.
"The program didn't fail because the executive lost discipline. It failed because the system around them wasn't built to survive contact with a real calendar."
The month-three cliff
Every executive publishing program has an easy phase and a hard phase, and almost all of them are designed to show off the easy phase.
The easy phase is month one. The conference post. The launch announcement. The piece tied to a hiring announcement the company was making anyway. The post that piggybacks on a customer win that was already going to be in the press kit. These are runway posts — the executive is doing something newsworthy, my job is shaping the take, and we publish something good in a few days.
Month three is where the runway runs out.
Now we're not announcing anything. There's no launch, no hire, no conference. We're producing an argument — a real, defensible, original argument — every week, on topics the executive hasn't been interviewed about, for an audience that has been reading executive LinkedIn for the better part of a year and has stopped scrolling for anything that doesn't have a point of view.
The pipeline problem in publishing is well-known. Agencies solve it with evergreen content banks, recycled frameworks, and topic lists that a junior associate used for the last twelve B2B clients. That works fine for posts nobody's reading. It does not work for posts the executive's name is on, because the readers can tell within a paragraph that this is the same post twelve other executives paid to have written last quarter.
So month three is where real ideas have to start showing up, on a cadence the executive's working life was never asked to absorb. And almost nobody planned for that.
The calendar problem nobody names
The hardest part of running a publishing program isn't the writing. It's the calendar.
An executive's real working life — by the time they're senior enough to have a voice worth publishing — is structurally full. Fundraising prep. Board prep. Hiring loops and the meetings about hiring loops. Customer escalations that someone put on their desk because no one else can resolve them. Acquisition conversations. The fifteen minutes between calls that looked open on the calendar but were actually load-bearing for something else.
Publishing has no forcing function. There's no deadline. There's no customer on the other end. There's no engineer who will be blocked. The only person waiting for the post to ship — with no consequences if it doesn't — is the ghostwriter. So when the executive's calendar gets real, the post gets bumped. Every time. Until the ghostwriter stops asking.
This is the unspoken mechanism behind nearly every publishing program that quietly dies. The executive did not abandon the program. The post got bumped six times in a row, the executive felt mildly bad about it, the next time the ghostwriter brought up the calendar the executive said "let's push for a quieter quarter," and from there the program went cold in three weeks.
Compare that with how PR-driven content gets made: reactive to news cycles, anchored to announcements, motivated by someone else's calendar. That has a forcing function — but it's the wrong one, because it bends to whatever's loud that week and produces executive content that reads like a press release the moment you click past the headline.
Both of these are wrong, in different ways. The first dies from lack of urgency. The second dies from too much of the wrong urgency. The fix is something else.
What the programs that survive share
The publishing programs I run that survive past year one share three traits. They are not particularly clever traits. They are mostly the absence of the things that kill programs.
First, the program is anchored to something the executive is already doing. Not parked as a side project that lives in the ghostwriter's inbox. The content plan is built against the executive's own calendar — board cycles, quarterly planning, customer reviews, the speeches they're already giving at conferences — and inherits the cadence from those things. The ghostwriter's job is to find the post inside the work. The executive's job is to do the work.
Second, the content is shaped into patterns the executive can riff from without a full interview every time. Not templates. Patterns. The structural shape of "here's a post that comes out of a customer conversation I had this week." "Here's a post that comes out of a board argument I lost and have been thinking about since." The voice — which was the hardest thing to find in month one — becomes reusable. The essay becomes something the executive can draft in twenty minutes, not something I have to spend three hours extracting from a forty-minute interview. That's the difference between a writing program and a publishing program.
Third, there is a forcing function, and it is the executive's. Not mine. A quarterly board memo. A customer-facing speech. A scheduled LinkedIn newsletter that goes out the first of every month whether the executive remembers to write the content or not — so the writing becomes a means to an end the executive already cared about, not an end of its own.
Months three to six are the danger zone. If the program is still running at six months, it tends to make it to year two. If it isn't, it almost never recovers, because by then the executive has quietly decided the program isn't working and every subsequent attempt to revive it carries the weight of that prior failure.
What I've learned after enough of these: the executive who publishes through month three wasn't more disciplined than the executive who didn't. They had a setup where the default path was to publish. The other executive had a setup where publishing required a new decision every week, and the decision kept being no.
That's not a writing problem. That's an infrastructure problem. And it's one a good ghostwriter solves in the first two months — or doesn't, and the program quietly closes itself out before the quarter ends.
What this looks like in practice
Here's what a program that survives month three usually looks like by that point. The onboarding phase is short — two weeks, maybe three — and ends with a voice document the executive can hold in their hand and say yes or no to. After that, the program stops asking the executive for new interviews every week and starts drawing from the things they're already doing. Board prep becomes a post. The customer call they took on a flight delay becomes a post. The argument they lost with their head of product last Tuesday becomes a post. The interviews get shorter and less frequent as the patterns get clearer. The drafts don't need as much shaping because the voice work has already been done.
The flip side: a program that's going to fail at month three usually shows it well before month three. The interviews get harder to schedule. The drafts come back with light, vague edits because the executive didn't have the time or the energy to engage with them. The "go ahead and ship it" answer starts showing up. By the time the executive is barely reading the drafts anymore, the program has about a month of life left. None of these are surprises — they're all visible signals in real time — and the fix is structural, not creative.
The ghostwriter who is willing to point this out in month two, and to change the rhythm of the program in response, usually keeps the engagement. The one who pretends nothing is changing until the executive cancels the call usually doesn't.
The good news about all of this is that it's a fixable problem. The structure is straightforward once you can see it. Most of the executives I work with are capable of publishing good content for years. They just need a system where publishing is the path of least resistance — where doing it is easier than not doing it — instead of one where publishing requires fresh initiative every week.
Build the system that way in month one. The next ten months almost take care of themselves.