Fiction · Two Companion Novels
Essential or Ornamental
Two friends. Two companies. One question that will define every engineering leader by 2028: are you essential to what comes next, or ornamental to what came before?
The premise
Spring break, 2025. Edward Johnson and Marcus Webb sit across from each other at a family dinner in Fort Lauderdale. Both are CTOs. Both run large engineering organizations. Both believe they understand what AI means for their companies.
By Christmas 2027, one of them will have transformed his organization into something that ships faster than anyone thought possible. The other will be watching his company collapse under the weight of its own inaction.
The difference was never about AI adoption. It was about something much older: knowing where the waste is, having the courage to remove it, and shipping before your competitors do.
Book One: 2028
Novel · 14 Chapters
Edward Johnson is a CTO at a healthcare company with a feature stuck in the backlog for eighteen months. A medication tracking system that could prevent thousands of patient deaths a year. Forty teams, twelve governance committees, and zero shipped results.
His best friend Marcus is riding Axiom toward an IPO, confident that being cloud-native is enough. Marcus has never mapped his value stream. He has never asked where the waste is. He does not think he needs to.
Edward bets his career on ninety days and one feature. He maps eleven weeks of delivery time and finds nine weeks of waiting. Only three of his seven fixes involve AI. The rest is removing waste that has been there for years.
AI is process improvement, not tool adoption. The goal is not to use AI. The goal is to ship.
Read 2028 →Book Two: Meridian
Companion Novel · 14 Chapters
Robert Chen has watched three transformation failures burn through forty-seven million dollars at Meridian Freight. The platform team is gone. The stock has not moved in five years. Axiom is growing forty percent year over year and filing for an IPO.
Robert makes one last bet: Project Prometheus. Twelve people in a warehouse. No consultants, no committees, no eighteen-month roadmap. He recruits Zara Okafor for product vision and Dane Kowalski for engineering systems. Veterans contribute domain knowledge. Engineers build.
Direction comes from the customer, not from institutional memory. Domain experts are fuel, not architects. The question is whether twelve people can rebuild a legacy freight company before the market window closes.
Transformation succeeds when you bring in people who know how to build, who absorb domain knowledge fast, and who build a parallel organization.
Read Meridian →Why fiction
Every framework sounds reasonable in a slide deck. The hard part is watching someone make the wrong call with good intentions and recognize yourself in it.
These novels put real engineering decisions into the mouths of characters you will know. The CTO who maps value streams before buying tools. The one who assumes cloud-native means fast. The CEO who bets the company on twelve people in a warehouse. The veteran who watches his expertise become ornamental overnight.
Fiction lets you sit with the consequences before they are yours.
Reading order
Both novels share the same timeline and world. Characters cross between them. You can read either one first.
Start with 2028 if you want the personal story first. Edward and Marcus are friends navigating the same inflection point from opposite sides. It reads like a conversation you have had with someone you respect who is making the wrong bet.
Start with Meridian if you want the organizational story first. Robert Chen is betting everything on a small team that can outbuild an entire enterprise. It reads like a war room you have been in when the survival clock is ticking.
Get notified when the books publish
Leave your email and we will let you know when the first chapters go live.