11 min read
ROBERT
Friday, March 7, 2025 – 4:47 PM – Meridian Freight Headquarters, Atlanta
The Platform Team floor was quiet.
Robert Chen stood in the doorway, watching the last engineer pack a cardboard box. Forty desks, forty monitors, forty chairs. All empty now except for this one, where a woman named Jessica was carefully wrapping a small cactus in newspaper.
“Mr. Chen.” She looked up, startled. “I didn’t expect…”
“I wanted to say goodbye. To everyone.” He looked around the empty floor. “I’m too late.”
“Most people left around three. Once the email went out.” She tucked the cactus into her box. “It’s okay. We all knew it was coming.”
Robert nodded. They had known. The Platform Team had been building Meridian 2.0 for two years, and they were nowhere close to feature parity with the legacy system. Every quarter, the demo showed promise. Every quarter, the shipping date slipped. And every quarter, more of their best customers defected to Axiom.
“For what it’s worth,” Robert said, “I’m sorry.”
Jessica picked up her box. “You gave us a chance. That’s more than most companies do.” She paused at the door. “But Mr. Chen? Maybe next time, try something different. Whatever we were doing here, it wasn’t working. And I don’t think doing more of it would have helped.”
She left. Robert stood alone in the empty floor, fluorescent lights humming overhead.
Forty engineers. Two years. Fifteen million dollars in salaries. And nothing to show for it except a prototype that crashed whenever you tried to process more than a thousand shipments.
This was Meridian’s third transformation failure in a decade.
Friday, March 7, 2025 – 5:30 PM – Robert’s Office
Robert closed his door and sat in the dark.
On his desk was a folder. Inside the folder was a single sheet of paper. His CFO had prepared it at his request: a summary of Meridian’s transformation investments since 2015.
Failure One: The Aldric Partners Engagement (2015-2017)
– Goal: Complete platform rewrite
– Investment: $18 million
– Result: 30% functionality replicated, project cancelled
– Lesson learned: “Big bang” rewrites don’t work
Failure Two: The Vantage Digital Engagement (2018-2020)
– Goal: Strangler pattern migration
– Investment: $14 million
– Result: Microservices couldn’t match legacy performance
– Lesson learned: Gradual migration creates integration nightmares
Failure Three: The Platform Team (2023-2025)
– Goal: Build “Meridian 2.0” alongside legacy
– Investment: $15 million
– Result: Never reached feature parity, team disbanded
– Lesson learned: Internal teams get pulled back to legacy maintenance
Total investment: $47 million
Total shipped: Nothing
Robert stared at the numbers. Forty-seven million dollars. Three attempts over a decade. Three failures. And Axiom growing 40% year over year while Meridian’s stock sat flat.
His phone buzzed. A text from his wife, Ellen.
Dinner at 7? Or is it another late night?
He typed back: Late night. Sorry.
Everything okay?
He didn’t know how to answer. He typed and deleted three different responses before settling on: Just thinking.
About?
About whether I’m the problem.
Three dots appeared. Disappeared. Appeared again. Then: You’re not the problem. You’re the one who keeps trying to solve it. That’s not the same thing.
Robert smiled despite himself. Twenty-eight years of marriage, and Ellen still knew exactly what to say.
Come home when you’re ready, she wrote. I’ll keep dinner warm.
Friday, October 13, 2023 – 7:00 PM – Robert’s Office
Robert pulled up the quarterly analyst reports. He’d read them a dozen times, but he made himself read them again.
“Meridian Freight continues to struggle with legacy system modernization. While the company maintains a stable customer base, growth has stalled and market share erosion to cloud-native competitors like Axiom Logistics appears irreversible.”
“We maintain our HOLD rating on Meridian Freight. The company’s inability to execute on digital transformation raises questions about long-term viability.”
“Meridian’s latest attempt at platform modernization, the internal ‘Platform Team’ initiative, has reportedly been disbanded after failing to achieve feature parity with legacy systems. This marks the company’s third failed transformation in a decade.”
Three failed transformations. The analysts knew. The industry knew. Everyone knew except, apparently, the consultants who kept taking Meridian’s money.
Robert opened his laptop and scrolled through the post-mortem documents from all three failures. Hundreds of pages of analysis. Root cause investigations. Lessons learned workshops. Retrospectives and reviews and recommendations.
The consultants always had explanations. Scope creep. Insufficient executive sponsorship. Inadequate change management. Resistance to new ways of working.
Never once did they say: Maybe our approach doesn’t work.
Never once did they say: Maybe you can’t transform a living system.
Never once did they say: Maybe you need to start over.
Robert closed his laptop. Through his window, he could see downtown Atlanta, the lights coming on as the sun set. Somewhere out there, Axiom was probably working late too. Building features. Signing customers. Getting ready for their IPO.
The IPO. Robert had heard the rumors. Axiom was targeting mid-2026. If they went public, they’d have hundreds of millions in capital. They could hire the best engineers, buy the best companies, undercut Meridian on every deal.
If Axiom went public, Meridian would have maybe two years before the end.
Saturday, March 8, 2025 – 9:00 AM – Robert’s House, Buckhead
Robert sat on his back patio, coffee growing cold in his hands.
Ellen joined him after a while. “You didn’t come to bed until 3 AM.”
“Couldn’t sleep.”
“The Platform Team?”
“That’s part of it.” He set down his coffee. “Ellen, I’ve spent ten years trying to save this company. $47 million on transformations. Three failures. And we’re worse off now than when I started.”
“So try something different.”
“I’ve tried everything different. Consultants, contractors, internal teams. Big bang, gradual migration, parallel development. Nothing works.”
Ellen was quiet for a moment. Then: “Have you tried asking the people who actually know the system?”
“What do you mean?”
“All these consultants, all these fancy engineers. Have any of them actually worked at Meridian? Do they know why your system does what it does?”
Robert thought about it. Aldric had brought in a team from their Atlanta office. None of them had logistics experience. Vantage had specialized in “legacy modernization,” but they’d never worked with COBOL before. The Platform Team had hired fresh graduates, people who could build modern systems but didn’t understand the old ones.
“No,” he admitted. “None of them knew our systems.”
“So they were trying to rebuild something they didn’t understand.”
Robert stared at his wife. “That’s… yes. That’s exactly what they were doing.”
“And the people who do understand? The ones who’ve been there for decades?”
“We keep losing them. Harry Thornton retired last fall. Gloria Reyes is thinking about leaving. The institutional knowledge is walking out the door.”
“Then maybe you should ask them what they know before it’s too late.”
Robert picked up his coffee. It was cold now, but he drank it anyway.
“What if I could get them back?” he said, half to himself. “What if I could get the people who actually know the system, and pair them with engineers who can build modern technology?”
“Then you’d have something no consultant could give you. Knowledge and capability together.”
“It would never work.” Robert shook his head. “The board would never approve another transformation. Not after three failures.”
“So don’t call it a transformation.”
“What would I call it?”
Ellen smiled. “I don’t know. But you’ve got time to figure it out.”
Monday, March 10, 2025 – 9:00 AM – Meridian Headquarters
Robert walked past the empty Platform Team floor on his way to his office. Someone had already started dismantling the desks.
His assistant, Patricia Hawkins, met him at the door. “The board wants a post-mortem meeting. Friday at 2 PM.”
“I expected that.”
“And the analysts want a comment on the Platform Team disbanding. They’re publishing their quarterly reports next week.”
“Tell them we’re evaluating our strategic options.”
Patricia made a note. “Anything else?”
Robert paused at his door. “Set up a coffee with Harry Thornton. Used to be our senior systems architect, before he retired.”
“Any particular reason?”
“I want to have coffee with him.”
Patricia nodded and walked back to her desk.
Monday, March 10, 2025 – 9:30 PM – Robert’s Home Office, Buckhead
Robert sat in his home office, half a glass of bourbon on the desk, scrolling through the post-mortems again. Not the executive summaries. The engineer feedback. The exit interviews. The anonymous survey results nobody at the C-level had read because HR had flagged them as “not actionable.”
He read them now.
“We were building a copy of a system we didn’t understand. Nobody asked what the system was actually for. Nobody asked what customers needed. We just looked at the legacy code and tried to make it modern.”
“The specs were wrong because nobody could tell us what the application was actually doing in production. We had no observability. We were guessing. Expensively.”
“The people who understood the domain were in a different building — literally and organizationally. We could set up a meeting with Harry Thornton every two weeks. Two weeks. Like the man’s knowledge was a resource you book on a calendar.”
“Every time we got momentum, someone from the legacy team would pull us into a production incident. We couldn’t build the new system because we couldn’t stop maintaining the old one. The organization kept eating us.”
Robert set down his drink.
Three transformations over a decade. Three different vendors. Three different methodologies. The same failure, every time.
They’d tried to transform a living system. Tried to change the organization while it was running. And every time, the organism rejected the transplant. Not because the technology was wrong. Because the structure was wrong. You can’t rebuild a ship while it’s at sea. You can’t rewire a building while people are living in it. You can’t transform an organization that’s using every spare calorie to survive.
The forty-seven million dollars — he was starting to think of it as the fifty million dollar question, once you counted the time and attention it had consumed — was never a technology problem. It was three problems nobody had solved and one structural mistake nobody had named.
Problem one: they didn’t know what their customers actually needed. Not what the account managers reported. Not what the NPS scores said. What the customers actually did on a Tuesday morning when freight needed to move.
Problem two: they didn’t know what their own application was doing. Forty years of code. Nobody could tell you which modules were load-bearing and which were scar tissue from a 2008 feature request that had been cancelled in 2009. No observability. No signal. Just a system running in the dark.
Problem three: the people who understood the domain and the people who could build modern systems had never been in the same room. Not really. Two weeks between meetings with Harry Thornton. The man had forty years of institutional knowledge and they’d treated him like a shared printer.
And the structural mistake — the one that had cost them everything — was trying to change the existing organization. Trying to transform it.
You can’t transform it. The organization is optimized for what it does. Every process, every approval chain, every committee exists because someone created it to solve a problem that was real at the time. The Architecture Review Board exists because someone shipped a bad integration in 2011. The Security Council exists because of the breach in 2014. The steering committees exist because three VPs couldn’t agree on priorities in 2016.
Each one made sense when it was created. Together, they formed a structure that could maintain a legacy system and nothing else. A structure that absorbed every attempt at change and converted it into meetings, status reports, and eventually, failure.
Robert pulled out a fresh legal pad and began to write.
Stop transforming. Start building.
Don’t change the existing organization. Build a parallel one.
Separate team. Separate governance. Separate building. No connection to the legacy structure.
The old organization keeps running. Keeps generating revenue. Keeps the lights on. Fund the new one from the operating budget — we’re already spending the money on transformations that don’t work.
The new organization doesn’t ask the old one for permission. No Architecture Review Board. No Security Council. No steering committees. Just people who know the domain and people who can build.
Start with the signals: What do customers actually need? What is the application actually doing? Who are the people who can do this?
12 people. 14 months. Total secrecy.
Veterans who know the domain.
Engineers who know AI.
No committees. No roadmaps. No transformation theater.
Just build.
At the bottom of the page, he wrote a single word:
Prometheus.
In Greek mythology, Prometheus stole fire from the gods and gave it to humanity. He was punished for it, but the gift changed everything.
Robert looked at the empty Platform Team floor through his window.
Maybe it was time to steal some fire.
End of Chapter 1