The Fourteen Drafts of Marcus Horne

Chris Kranz · · 5 min read
A story about Marcus Horne, a VP of Engineering navigating corporate employee advocacy programmes. It explores the tension between authentic professional storytelling and organisational messaging, following how a genuine post about team resilience gets progressively diluted through rounds of editorial revision.

The Fourteen Drafts of Marcus Horne

The first draft was good.

Cass read it twice, which she almost never did. Marcus Horne, VP of Engineering at StratusEdge, had written four paragraphs about a production outage that had kept his team up for thirty-one hours straight. About the junior developer who’d spotted the cascading failure. About how he’d personally missed his daughter’s school play and how the junior dev had sent him a phone recording of it at 3am, no message attached, just the video.

It was honest. It was specific. It had the quality that Cass privately called texture - the thing you can’t manufacture, the thing that makes you stop scrolling because a real human is standing in front of you with their shirt untucked, saying something true.

“This is great,” Cass told him. “I’d barely touch it.”

Marcus looked relieved. Marcus always looked slightly startled to be in a room discussing LinkedIn, like a man who’d wandered into the wrong seminar and was too polite to leave. He was not a natural poster. He’d agreed to the employee advocacy programme because Helen Carmichael in Comms had asked him directly and he didn’t know how to say no to Helen. Nobody did.

“So we just… post it?” he said.

“We just post it,” Cass said.


The second draft came back from Helen.

Helen had added a line at the top: At StratusEdge, we believe resilience isn’t just a technical capability - it’s a human one. She’d also changed “production outage” to “service continuity event.”

Cass removed the added line. She kept “service continuity event” because she was choosing her battles.


The third draft came back from Legal.

Legal wanted the junior developer anonymised. Fair enough. Cass changed “Eira” to “a member of my team.” She felt something small leave the room.


The fourth draft came back from Helen again, who had shared it with Greg in Brand, who felt the tone was “a bit raw” and could they “elevate it slightly.” Greg had added the phrase “world-class incident response” to the second paragraph.

Cass stared at “world-class incident response” for a long time. She deleted it. She wrote in the margin: This is a personal post from Marcus’s account. It shouldn’t sound like a press release.


The fifth draft came back from Greg, who had re-added “world-class incident response” and also suggested replacing “kept us up for thirty-one hours” with “tested our operational resilience across a sustained period.”

Cass called Helen. Helen said she understood Cass’s concerns but Greg had a point about brand consistency.

Cass asked if brand consistency applied to a man talking about missing his daughter’s school play.

Helen said she’d check.


The sixth draft. Someone - Cass never found out who - had removed the school play entirely. In its place: Balancing professional demands with personal commitments is something every leader navigates.

Cass read the sentence four times. It was the verbal equivalent of holding a seashell to your ear and hearing nothing. Not even the sea. Just plastic.


The seventh draft went to Marcus’s boss, Rhys, who didn’t change anything but added a comment: Should we mention the Q3 uptime metrics? Feels like a missed opportunity.


The eighth draft now included Q3 uptime metrics.


The ninth draft went back to Legal because the Q3 uptime metrics hadn’t been publicly disclosed yet.


The tenth draft had the Q3 uptime metrics removed but a new line added by Helen: We’re proud of our track record in service reliability. Cass noted that this line communicated precisely nothing while somehow taking up space, like a decorative cushion on a bed you’re trying to sleep in.

She deleted it.

Helen re-added it.


Cass put drafts eleven through thirteen side by side on her screen one Wednesday afternoon and played a private game she called Find the Human.

Draft eleven: the thirty-one hours had become “an extended period.” The junior dev had become “our talented team.” The 3am video had become “the kind of support that defines our culture at StratusEdge.”

Draft twelve: someone had added a hashtag. #Resilience. Then someone else had added #Leadership. Then Greg had added #StratusEdge, which at least had the dignity of being functional.

Draft thirteen: Rhys had suggested opening with a question. “What does resilience really mean?” Cass could feel her soul trying to leave her body through her left ear. She’d seen that exact opening on LinkedIn approximately eleven thousand times. It meant nothing every single time.

She sat back. She pulled up Marcus’s original draft on her phone. She read it again.

We were thirty-one hours into the outage when Eira - six months out of university, still on probation - found the cascading failure that three senior engineers had missed. I don’t know when she slept. I don’t know if she slept. I do know that at 3am, without a word, she sent me a phone recording of my daughter’s school play. I’d forgot I’d even mentioned it.

I’ve managed engineering teams for fourteen years. I’ve never felt smaller or more grateful in the same moment.

It was forty-seven words of actual human experience and it was better than everything they’d produced in two weeks of collective improvement.


The fourteenth draft arrived on a Thursday.

Cass opened it. She read it slowly, the way you’d read an autopsy report on someone you’d known.

At StratusEdge, we believe resilience is more than a technical capability - it’s a human one. Recently, our team navigated a complex service continuity event that tested our operational resilience across a sustained period. Through the dedication and expertise of our talented engineers, we demonstrated the kind of collabourative problem-solving that defines our culture. Balancing professional demands with personal commitments is something every leader navigates, and I’m proud to work alongside people who embody our values every day. We’re proud of our track record in service reliability. What does resilience really mean to you?

#Resilience #Leadership #StratusEdge

Cass counted. Seven sentences. Zero texture. No Eira. No school play. No 3am video. No thirty-one hours. No feeling smaller or more grateful. Nothing that could only have been written by Marcus Horne, because nothing in it belonged to Marcus Horne. It could have been posted by any VP at any company in any industry on any day of any year, and no one would stop scrolling for it, because there was nothing to stop for.

It was perfectly safe. Perfectly branded. Perfectly aligned.

It was beige toast.

Cass forwarded the final draft to Marcus for sign-off. He replied in four minutes: Looks fine I think. Thanks for all the work on this.

She sat with that for a while. Looks fine I think. He didn’t recognise it. Of course he didn’t. There was nothing left to recognise.


She posted it on his behalf the following Monday at 8:47am, optimised for engagement. It received twenty-three likes, two of which were from Helen and Greg. One comment: Great perspective Marcus! from someone in Sales who Cass suspected had not read it.

Somewhere on Cass’s laptop, in a folder she never opened but couldn’t delete, the first draft sat untouched. Forty-seven words that would have made people stop. Forty-seven words that sounded like a specific man who’d been awake too long and missed something that mattered and been saved by someone he barely knew.

She thought about sending it to Marcus. Saying: this was the one. This was always the one.

She didn’t.

He had a Q4 post to write.