Essential or Ornamental 2028

Chapter 1: Spring Break

March 28, 2025

Friday, March 28, 2025 – 6:00 PM – Fort Lauderdale

The steaks were overcooked, the kids were loud, and Marcus Webb was checking his phone under the table.

Edward Johnson watched his best friend’s thumb moving across the screen and said nothing. Twenty-five years of friendship had taught him when to push and when to wait.

“So tell me about the switch,” Marcus said, finally pocketing the phone. He turned to Sophia, Edward’s oldest. “Pre-med to computer science. Your mom almost had a stroke.”

“She did not—”

“She called Sarah crying.”

“She called Sarah concerned.” Jennifer’s voice carried from across the table. “There’s a difference.”

Sophia was eighteen, home from Georgia Tech for spring break. She rolled her eyes. “It wasn’t that dramatic. Something clicked in AP Computer Science. I was actually making things instead of memorizing what dead people figured out a hundred years ago.”

“That’s—” Marcus started.

“Don’t say ‘that’s what I’ve been telling her.’ You haven’t been telling her anything. You’ve been working.” Sarah didn’t look up from helping Isaiah cut his steak.

Marcus closed his mouth. Opened it again. “Walk me through the hackathon thing. The one you won.”

Sophia set down her fork. “Forty-eight hours. Four people. We built a functioning app that would’ve taken a whole semester two years ago. Maybe longer.”

“How?”

“The AI doesn’t write code for you. Everyone thinks that.” She paused. “You know how Dad describes his first commanding officer? The guy who could look at any problem and ask the one question that made everything click?”

Edward looked up from his plate.

“It’s like that,” Sophia continued. “Except it never sleeps and knows every programming language ever invented. But it only works if you know what you’re trying to build.” She stabbed a piece of steak. “The teams that lost? Way better programmers than us. They just kept changing their minds. The AI made them faster at going in circles.”

“So the bottleneck is clarity,” Edward said. “Not technical skill.”

“Basically.”

Marcus’s phone buzzed. He glanced down—Victoria Hartwell, something about pre-IPO compliance—and his thumb was typing before he’d made a conscious decision.

”…and my professor says by 2026, anyone who can’t—”

“Sorry, what?”

Sophia’s expression flickered. Just for a moment. Then she smoothed it over. “I was saying the skills are changing fast.”

“Right. Right.” Marcus pocketed the phone. “That’s really cool, Soph.”

The conversation moved on. MJ’s basketball season. Isaiah’s science project. Whether Emma was actually applying to the Naval Academy or just trying to make her parents nervous.

But Edward watched Sophia. She’d noticed Marcus checking his phone. She’d shortened her answer, wrapped it up, made it easy for him to move on.

Eighteen years old and already learning to read a room.

Friday, March 28, 2025 – 9:30 PM – The Dock

The water was black and still. Somewhere across the Intracoastal, a neighbor was playing music too loud for a Friday night.

“You’re still thinking about it.” Marcus cast his line into the darkness. Not a question.

“Aren’t you?”

“I’m thinking about eighteen months of clean execution and ringing the bell at the NYSE.” The reel clicked as he let out more line. “After that, we can play with AI tools. Do the whole transformation thing.”

“And if eighteen months is too long?”

“It’s not.” Marcus turned to face him. “Ed, it took us four years to build Axiom. Meridian’s still running green screens. TransGlobal just figured out GPS tracking. Nobody’s catching us in eighteen months.”

“What if the rules changed?”

“Rules don’t change that fast.”

Edward didn’t answer. The music across the water switched to something slower.

“There was this guy Harold,” he said finally. “At my first job. Defense contractor. Ran the tape library for the mainframes. Knew every tape, every backup, every recovery procedure. The guy you called when everything went sideways.” Edward reeled in his line slowly. “Then they moved to disk-based backup. Eighteen months. And Harold’s whole career became irrelevant. They gave him a desk in compliance. Make-work stuff. He’d gone from the guy everyone needed to the guy nobody called.”

“That’s depressing as hell.”

“Essential to ornamental. In eighteen months.”

“You’re not gonna become Harold.”

“How do you know?”

“Because you’re paranoid enough to worry about it.” Marcus grinned. “Besides, I won’t care if I’m irrelevant in 2028. I’ll be rich.”

Edward looked at him. Really looked.

“What?” Marcus said.

“Nothing.”

“You’re doing that thing where you think something and don’t say it.”

“I’m not.”

“You are. Twenty-five years. I know the face.”

Edward cast his line. Watched it arc into the darkness. “I just wonder if the IPO is the finish line or the starting gun.”

“It’s thirteen million dollars.” Marcus checked his phone again. Victoria. “That’s a finish line.” He stood, brushing off his jeans. “Look, I gotta deal with this. Board stuff.”

“Go.”

Marcus headed back toward the house, phone already at his ear. Edward stayed on the dock, watching the lights on the water.

I won’t care if I’m irrelevant in 2028. I’ll be rich.

Maybe he was right. Maybe the money would be enough.

The music across the water had stopped.

Chapter 2: After the IPO

April – May 2025

MARCUS

Tuesday, April 8, 2025 – 7:45 AM – Axiom Headquarters, Fort Lauderdale

Fifteen months to the bell.

The phrase had become Marcus Webb’s mantra. Every decision, every meeting, every strategic choice filtered through that single constraint. Fifteen months until Axiom went public. Fifteen months until he rang the opening bell at the New York Stock Exchange. Fifteen months until the four years of sacrifice finally paid off.

Marcus had grown up on a cattle ranch outside Tulsa. His father was still the foreman there, sixty-four years old, up at 4 AM, working cattle in weather that would kill most men. Marcus had learned to ride before he could read. Learned that delayed work meant dead cattle. Learned that you solved problems with your hands and your back and your stubborn refusal to quit.

He’d been a cowboy. A real one. Not the hat-and-boots kind you saw at country bars in Fort Lauderdale, but the kind who’d castrated bulls and pulled calves and mended fences in the August heat until his skin cracked and bled.

Wrestling had been his ticket out. State champion at 171 pounds, good enough to catch the eye of a Coast Guard Academy recruiter. His father had driven him to New London in a truck held together by rust and prayer, shook his hand at the gate, and said three words: Make it count.

Marcus had made it count.

He’d met Sarah at The Rusty Anchor, a dive bar near the Academy where cadets went to escape. She was at Connecticut College with her cousin Jennifer. Two sorority sisters who’d wandered in on a Thursday night looking for cheap beer and bad decisions. Marcus made her laugh so hard she snorted her drink. By the time he graduated, they were inseparable. Jennifer was dating his roommate Edward, which meant the four of them spent every weekend together. Family before they were family.

They’d gotten married two weeks after graduation—June 14, 2003, a small ceremony at the ranch. His father had worn a suit for the first time in thirty years. Sarah’s parents had flown in from Connecticut, clearly wondering what their Ivy-bound daughter saw in an Oklahoma cowboy. But they’d seen it by the end of the weekend. The same thing Sarah saw. The same thing everyone eventually saw: Marcus Webb didn’t quit.

The Coast Guard sent them to Kodiak, Alaska. Two years on a remote island in the Gulf of Alaska, population 6,000, where the nearest Target was a two-hour flight away. Sarah had deferred Stanford for a year to come with him—she wasn’t starting a marriage with a two-year separation. They lived in base housing, watched the northern lights from their back porch, and learned to be married in a place where there was nothing to do but be together.

Marcus worked search and rescue coordination, but the real education happened after hours. He’d brought a laptop and taught himself to code in the long Alaskan winters—dark by 4 PM, nothing but time. He built tools for the base: a better scheduling system, a parts inventory tracker, small utilities that solved real problems. By the time they left Kodiak, he had a portfolio of working software and a certainty that he wanted to build things for a living.

His last three years of service were in San Francisco, port security and maritime law enforcement. Sarah was at Stanford by then, close enough for weekends. She dragged him to startup mixers in Palo Alto, introduced him to founders who saw his side projects and didn’t care about his uniform. The Valley was hungry for engineers who could actually build things.

When his five-year commitment ended in 2008, Marcus had options. Four startups made offers based on his side projects. He took the one that felt most like building something real.

It wasn’t.

The next twelve years were a blur of startup chaos. Dev #1 at a company that flamed out in eighteen months. First engineering manager at another that made it to Series B before the founders imploded. Director of Platform at a third, then a fourth, then a fifth. MJ was born in 2010. Isaiah in 2013. Each time Marcus told Sarah this was the one. Each time he was wrong.

By 2018, he’d spent ten years betting on other people’s visions. Six startups. Six failures. Each time he’d taken less money for more equity, believed he could build something that mattered, and watched it fall apart.

Soren recruited him with the pitch that always works on tired startup veterans: stability. Senior Software Development Engineer, then Senior Manager within a year. The money was real. The stock vested on schedule. The health insurance was excellent. His shoulders dropped two inches the day the first direct deposit hit.

He hated it.

Two years in the Valley, watching his RSUs vest while the commute ate his soul. Sitting in meetings, staring at screens, making more money in a month than the ranch made in a year. But he wasn’t building anything. He was maintaining. Optimizing. Playing defense. The cowboy who’d grown up solving problems with his hands had become a cog in a machine.

Then Sarah got the call from the Garlands.

An old Florida family wanted her to run their charitable trust. $120,000 a year, two days a week—enough to stay in the game while being home for the boys. It was the kind of opportunity you didn’t turn down. In summer 2020, they sold the Bay Area house at the peak of the market, rolled the equity into a four-bedroom in Coral Ridge—one of those old Fort Lauderdale neighborhoods where the houses had yards and the streets had sidewalks—and started over.

Marcus figured he’d find a remote job, maybe another big tech company. Instead, he went to a local startup meetup in Fort Lauderdale—just to see what was out there. That’s where he met Kyle Mercer and Darren Choi, two guys with a PHP app and a dream.

Marcus was done playing it safe. He was ready to bet on himself again.

And he’d bet everything.

When Marcus walked into Axiom in early 2021, the company had two customers and $30,000 in annual recurring revenue. The entire tech stack was a PHP app running on the free tier of a cloud hosting platform. Kyle was still working his day job. Darren was coding in his spare bedroom between consulting gigs.

Sarah thought he was crazy. But Marcus saw something Kyle and Darren couldn’t execute alone: the best product in a $40 billion market, built by founders who couldn’t scale. Two customers and a PHP app, but those two customers loved it. The product worked. It just needed someone who could actually build a team. Marcus could do that. He knew he could do that.

They offered him twelve percent of the company. Twelve percent of nothing. But Marcus saw what it could become.

The problem was money. They needed to hire their first real development team. Kyle and Darren were tapped out. VCs wouldn’t fund a company with no revenue and no senior management.

So Marcus did something he’d never done before. He walked into the bank and took out an equity loan.

The Bay Area house had been their foundation. $800,000 when they sold it in 2020, after a decade of appreciation and mortgage payments—that was $300,000 in equity. They’d rolled $200,000 into the Fort Lauderdale house and paid off the last $120,000 of Sarah’s college loans. Finally free of that debt, thirteen years after graduation. It had felt like they were building something permanent.

Then Kyle and Darren called.

The cash reserves went first. Then the $50,000 equity loan against the new house. Sarah signed the papers with shaking hands. Then the retirement accounts—his 401(k) from Soren, cashed out with the early withdrawal penalty; Sarah’s modest IRA. All of it poured into Axiom during the two years he took no salary, surviving on her trust income and rotating 0% balance transfers between credit cards.

Everything they’d built. Gone. Converted into shares of a company that barely existed.

That money hired the first five engineers. Derek Huang and Prakash Venkataraman were the ones who stayed. Derek was the ambitious one, hungry, always looking for the next level. Prakash was the steady hand, a veteran architect who’d seen three companies fail and wanted to build one that wouldn’t. They were Marcus’s people.

Those engineers built the features that landed the first enterprise customer. That customer’s logo went on the pitch deck that raised the Series A.

And Marcus had been right. That was the thing. He’d been right.

Four years later, Axiom had 400 engineers, $240 million in annual recurring revenue, and a billion-dollar valuation. The PHP app had become an enterprise platform. The two-person startup had become a company preparing to go public.

But Marcus’s 12% hadn’t stayed 12%.

The Series A diluted him to 9%. Series B brought him to 6.5%. Series C to 4%. The Series D down round, when Blackwood Capital came in with rescue terms and pushed out the founders, crushed him to 2%. Employee pool expansions took another bite. They’d issued him additional shares over the years—performance bonuses, retention grants—but none of it made up for the brutal math of dilution.

Now he held 1.4% of a company valued at $950 million. Thirteen million dollars on paper.

Sometimes, late at night, Marcus did the math he tried not to do. If he’d kept that original 12%? At $950 million? That was $114 million. Enough to never work again. Enough for his grandchildren to never work again.

Instead: $13 million. Still life-changing, if it held. But a fraction of what might have been. Big money had become small money, one funding round at a time, each dilution dressed up as “growth” and “opportunity” while his stake shrank and shrank.

He still drove the twelve-year-old minivan they’d bought when Isaiah was born. MJ’s college was four years away, and Marcus had no idea how they’d pay for it if the IPO didn’t work. The 529 accounts they’d started when the boys were babies sat empty, raided in year two when the credit card juggling ran out. They still owed $50,000 on the equity loan.

He’d mortgaged his family’s future on this bet. The house. The retirement. The college funds. Four years of hundred-hour weeks and missed basketball games and dinners cut short. All of it riding on July 6, 2026.

If the IPO failed, if the stock cratered, if $13 million became $3 million, he’d have risked everything, built a billion-dollar company, and ended up no better than if he’d just stayed at Soren. Four years of sacrifice for nothing.

That was why he couldn’t afford to take risks now. Not with the IPO fifteen months away.

He’d seen what happened to founders who rocked the boat. Kyle and Darren had built Axiom from nothing, and Blackwood had pushed them out the moment they became inconvenient. Advisory role. That’s what you got for creating something. Marcus wasn’t even a founder, which meant he was even more expendable. One wrong move, one “unnecessary risk,” one experiment that spooked the board, and he’d be out too. Watching his equity vest from the sidelines while someone else rang the bell.

After the IPO, he told himself. After the IPO, we can experiment. After the IPO, we can take risks. After the IPO, this all becomes worth it.

The phrase had become a mantra. A prayer. A way to defer every hard question until the finish line was behind him.

What if I’m wrong?

The thought surfaced sometimes, late at night, when the house was quiet and he was staring at projections that all pointed up and to the right. He’d push it down. Not now. Not when he was this close.

First, he had to get there. Then he had to survive the lockup. Then, maybe, he could finally exhale.

Tuesday, April 8, 2025 – 8:00 AM – Executive Conference Room

The leadership sync started at eight.

Catherine Bell sat at the head of the long conference table, Marcus to her right. The CEO ran these meetings with the efficiency of a metronome. Fifteen minutes per agenda item, no tangents, no philosophical discussions. She’d been brought in three months ago during the Series D to fix what the founders couldn’t: a company growing faster than its leadership could manage.

Catherine was good at what she did. Two successful exits. A reputation for execution. The board trusted her implicitly. She spoke their language. ARR growth, gross margins, CAC payback periods. Technology was a black box that produced metrics. As long as the metrics were clean, she didn’t care what happened inside the box.

That was Marcus’s domain. He ran the technical organization. She ran everything else. Three months in, they’d found their rhythm.

The agenda was the same as it had been for months: Q4 close-out, Q1 projections, IPO timeline review. Clean quarters, predictable growth, no surprises.

Derek Huang, VP of Engineering, cleared his throat. Twenty-nine, ambitious, one of the first five engineers Marcus hired after Axiom stopped being just the founders and a prototype. Derek had the hunger of someone who’d built himself from nothing and wasn’t done climbing. His options would fully vest in April 2026.

But lately, Derek had been increasingly agitated.

“Before we get into the quarterly review,” Derek said, “I wanted to raise something that keeps coming up with the team.”

Marcus nodded. “Go ahead.”

“AI development tools. GitHub Copilot, Claude, GPT-4 for code generation. The team keeps asking about them. Our competitors are starting to announce AI initiatives. Developers are asking questions.” He paused. “What’s our position?”

Across the table, Prakash Venkataraman leaned forward. Principal Architect, the technical conscience of the company. Another one of the original five. Prakash was older than most of the team, a veteran of three enterprise software companies who’d taken a chance on Marcus’s vision when it was just a PHP app and a dream. He had the calm demeanor of someone who’d seen technology cycles come and go, which made his support for Derek’s question all the more notable.

“Marcus,” Prakash said, “the developers are going to use these tools whether we sanction them or not. I’d rather we get ahead of it. Define guidelines, evaluate options, build an AI strategy. Shouldn’t take more than a few months to have a real plan.”

Marcus set down his coffee cup. He’d been expecting this conversation. He’d been dreading it, too.

Catherine cut in before Marcus could respond.

“Is not having AI coding tools going to directly cause us to lose customers in the next fifteen months?” Her voice was flat, analytical. “Can you prove that?”

Derek hesitated. “I can’t prove…”

“Then this conversation is over.” Catherine looked up from her laptop, her eyes cold. “Let me be very clear. No unauthorized AI development tools. None. I am not updating our S-1 risk factors because some engineer wanted to use ChatGPT to write code.” She looked around the table slowly. “Anyone caught using unauthorized AI tools in their development workflow will be terminated. Immediately. And they’ll forfeit their unvested equity.”

The room went still.

“We’re fifteen months from the bell,” Catherine continued. “Fifteen months from the liquidity event that makes everyone in this room wealthy. I will not let experimental technology introduce variance into our metrics. I will not explain to the SEC why our development process changed mid-registration. And I will not watch this IPO fail because someone couldn’t follow instructions.”

She turned to Marcus. “Anything to add?”

What Catherine didn’t say — what she’d never say in front of the board — was that she’d watched this exact pattern destroy a company before. Helix Health, her second exit. Their CTO had approved a last-minute platform migration nine months before closing. “Just modernizing the stack.” Three months later, two major bugs in production. Revenue restatement. The acquirer walked. She’d spent six weeks on the phone with lawyers while 400 people lost their jobs.

She wasn’t stupid about technology. She was strategic about timing. There was a difference, and she was tired of people not understanding it.

The hard truth was simpler: she didn’t trust Marcus to manage the risk. He was a builder, not a governor. Give him permission to experiment and the experiment would consume everything. She’d seen his type before — brilliant engineers who confused motion with progress and speed with control. Fifteen months was not long. The margin for error was not wide. And the consequences of getting it wrong fell on her, not on Derek Huang with his unvested options and his impatience.

So yes, she’d been harsh. She’d rather be harsh and employed than kind and explaining to the SEC why Axiom’s development metrics showed unexplained variance during the quiet period.

Marcus leaned forward. “Look, I get it. The tools are exciting. I’ve played with them.” He spread his hands. “But we’re not some legacy company trying to catch up. We ARE the transformation. Meridian’s still running green screens. TransGlobal can’t spell ‘cloud.’” A few chuckles around the table.

He stood and walked to the window, warming to his point. “Here’s what everyone forgets. The Agile transformation movement is in its twentieth year. DORA metrics, DevOps, both over a decade old. And most enterprises still can’t do basic CI/CD.” He turned back to face the room. “Things don’t evolve quickly in the enterprise. That’s why startups like us get so valuable. We’re already where they’re trying to go. We don’t need to chase the next shiny thing. We ARE the shiny thing.”

“So we just… wait?” Derek asked.

“We execute. We ship. We go public.” Marcus sat back down. “What message does it send if we announce some big AI initiative right before our IPO? ‘Hey investors, we’re not sure our platform is good enough, so we’re scrambling to adopt whatever’s trending on Hacker News.’“

“That’s not what I’m saying,” Derek cut in.

“I know. But that’s how it reads.”

Derek started to respond, but Catherine cut him off.

“IPO or bust. That’s the priority. Everything else waits.”

The Blackwood partners around the table nodded in agreement. They’d invested $150 million at a valuation that only made sense if the IPO succeeded. They weren’t paying for experimentation.

Prakash caught Derek’s eye across the table. Neither said anything. What was there to say? The decision had been made. The threat had been issued. Fifteen months of their equity was on the line.

The meeting lasted another ninety minutes. Clean quarters. Predictable growth. IPO timeline on track.

Marcus walked back to his office feeling like he’d handled it well. The team had concerns. That was natural. But he’d addressed them. Catherine had been clear. The board was aligned. Everyone understood the stakes.

Forfeit their unvested equity. That would keep the engineers in line. Nobody was going to risk years of stock options to play with ChatGPT.

He was winning. He’d already won.

Everything else was noise.

Tuesday, April 29, 2025 – 2:00 PM – Axiom Boardroom

The board meeting at the end of April was supposed to be routine.

Axiom’s board was dominated by Blackwood Capital, who’d led the Series D down round. Lower valuation, rescue terms, more control. The original founders had been pushed out as part of that deal. Kyle to an “advisory” role that meant nothing. Darren with a secondary buyout that let him cash out $8M.

The partners around the table weren’t aggressive anymore. They were defensive. Every decision ran through one filter: Does this protect the IPO timeline?

Victoria Hartwell, the lead independent director, was the exception. She’d been a COO at two enterprise software companies and had a reputation for asking the questions nobody wanted to answer.

“Marcus,” she said, during the strategic update section, “I’ve been reading some market analysis.” She pulled up a report on her iPad. “More enterprises are using AI to build their software. Not just adding AI features. Using AI in the development process itself. McKinsey says it’s accelerating. Gartner says it’s inevitable. Our competitors are all in the conversation.” She paused. “We’re not. What’s our response?”

Marcus had prepared for this. He’d spent an hour rehearsing his answer with his communications director.

“Victoria, we already have AI. ML team, data science, predictive features. Route optimization, demand forecasting. Some good people.” He leaned back. “What you’re reading about is using AI to build software. Different thing. And honestly? Why would I introduce experimental tools into our dev process right before an IPO? That’s how you ship bugs, miss deadlines, spook the underwriters.”

He clicked to the next slide. “Our competitors are still figuring out cloud. We’re already there.”

The board nodded. They liked this answer. It was confident without being reckless. It acknowledged the trend without committing to expensive experimentation.

“And the timeline?” Victoria pressed.

“After the IPO. Capital, profile, room to breathe. We can do a proper evaluation then. Right now?” He shrugged. “Execute the plan.”

Victoria leaned back in her chair. “I’ve seen companies lose market position because they were watching the finish line instead of the road.”

“I hear you. But fifteen months, we’re at the NYSE. Then we can have this conversation properly.”

Kwame Okonkwo shifted in his chair. He was the newest board member, former CTO with digital transformation experience at two Fortune 500s.

“For what it’s worth, I think that deserves more than ‘post-IPO.’” He glanced at Marcus. “Competitors experimenting now will have fifteen months of learning by the time you start.”

Marcus kept his voice even. “Kwame, with respect, you’ve been on this board three months.”

“Long enough to recognize the pattern.”

Catherine cut in before it escalated. “We’re aligned. Let’s move to financials.”

The Blackwood partners nodded. Three votes. That was what mattered.

Later, Kwame caught Marcus in the hallway.

“I wasn’t trying to…”

“I know.”

“It’s just, I’ve watched companies do this. ‘After the acquisition.’ ‘After the integration.’ Always ‘after’ something.”

“We’re not those companies.”

Kwame looked at him for a moment, then nodded. “Okay.” He walked away.

Marcus went back to his office. Kwame would learn. They all learned eventually.

Thursday, May 1, 2025 – 11:00 PM – Marcus’s Home Office, Fort Lauderdale

Marcus sat in his home office with his laptop open.

He told himself he was reviewing the quarterly projections. But he kept finding himself on competitive intelligence sites, searching for news about Meridian Freight.

The results were sparse. Their last product announcement had been eight months ago. A minor feature update to their legacy platform. Their conference presence had evaporated. Their job postings were minimal.

He pulled up their stock chart. A flat line stretching back a decade. $9.12 today. $9.08 a year ago. $8.95 five years ago. The four percent dividend was the only reason anyone held the stock. Steady income for investors who’d given up on growth.

Marcus scrolled through their website. The design looked dated, the messaging stale. “Enterprise Freight Solutions” was the tagline. No mention of AI, no mention of cloud, no mention of anything modern.

That’s what a dying company looks like, he thought. Paying dividends because they’ve got nothing else to offer.

He pulled up their company page online. Their engineering team seemed smaller than it had been a year ago. The VP of Engineering had left. Two senior architects had departed. The profile photos that remained were mostly older, less likely to be the kind of talent that built cutting-edge systems.

Classic death spiral. Talent leaves, product stagnates, customers start looking elsewhere. I’ve seen it a dozen times.

He checked their latest quarterly earnings. Revenue flat. Margins steady but not growing. The analyst commentary was brutal: “Meridian continues to serve its existing customer base but shows no signs of innovation or growth. We maintain our HOLD rating. The dividend remains the primary value proposition.”

Marcus closed the laptop and went to bed, satisfied.

Meridian was exactly what he thought they were: a legacy company coasting on existing contracts, paying shareholders to stay patient while the business slowly wound down. Nothing to worry about. Nothing to watch.

He’d check again after the IPO. By then, they’d probably be even further behind.

Saturday, May 3, 2025 – 9:00 AM – Webb Family Home, Kitchen

Sarah found Marcus at the kitchen table, reviewing board materials.

“You missed MJ’s game last night.”

“I know. The board prep…”

“He scored twelve points. His coach said it was his best game of the season.” Sarah sat down across from him. “He stopped asking if you’d be there.”

Marcus set down his coffee. “That’s not fair.”

“I’m not trying to be fair. I’m telling you what’s happening.” She looked at him. “You came home from spring break talking about nothing but the IPO. Edward was asking questions, getting curious about something. You were checking your phone.”

“Fourteen months, Sarah. Fourteen months and all of this becomes worth it.”

“You said fifteen months at the spring dinner. You said a year before that.” She took a sip of her own coffee. “The boys are growing up. That’s not waiting for the IPO.”

“This is different.”

“You always say that.”

He didn’t have an answer. Or maybe he did, but it would’ve started an argument neither of them had time for.

Sarah stood. “I’m not saying you’re wrong about the business. I don’t understand half of what you do. But I understand that MJ’s stopped expecting you to show up. Isaiah barely talks to you anymore.” She paused at the doorway. “That’s what worries me.”

She left. Marcus stared at the board materials until the words blurred.

Sunday, May 4, 2025 – 1:47 AM – Marcus’s Home Office

Marcus couldn’t sleep.

Sarah’s words kept circling. MJ’s stopped expecting you to show up. He’d dismissed her concern the way he dismissed most concerns lately, filed it under “deal with after the IPO” and moved on. But something about the conversation had lodged itself somewhere uncomfortable.

He sat at his desk in the dark, laptop casting blue light across his face. The house was silent. Sarah and the boys had been asleep for hours.

He opened a blank document. Typed a heading: Where does work get stuck?

It was the kind of question Edward would ask. The kind of question Sophia had been describing at the spring dinner. The teams that struggled were the ones who didn’t know what they were building. What was Axiom building? What was stopping them from building it faster?

He started typing.

Feature request to deployment. What’s the actual timeline?

He pulled up Jira. Looked at the last three major features they’d shipped. Traced them backward through the system.

The average was fourteen weeks.

Fourteen weeks from “we should build this” to “customers can use it.” He’d known the number was long, but he’d never actually mapped it. Never asked where the time went.

He started breaking it down.

Requirements gathering: two weeks. Waiting for product committee approval: one week, sometimes two. Design review: another week. Sprint planning: if you missed the window, you waited two more weeks. Development: three weeks on average. Code review: a week in the queue, sometimes longer. QA: two weeks. Security review: one week. Deployment approvals: another week.

Fourteen weeks. Maybe four of them were actual work. The rest was waiting. Queues. Approvals. Committees that met on fixed schedules regardless of urgency.

Marcus stared at the screen.

This was exactly what Edward had been talking about. What Sophia had described. The process was optimized for control, not speed. Every handoff was a checkpoint. Every checkpoint was a delay.

He could fix this. He could map the value stream properly, identify the bottlenecks, streamline the approvals that didn’t add value. It would take effort. It would require changing how teams worked. Catherine wouldn’t like it. The board would ask questions.

But if he didn’t fix it, what happened when someone else did? When a competitor figured out how to ship in seven weeks instead of fourteen? When the market moved faster than Axiom could follow?

His cursor blinked at the end of the document.

He thought about the IPO. Fourteen months away. Clean quarters. No surprises. The board wanted predictability. Catherine wanted metrics that told a simple story. Any significant process change would introduce variance. Variance spooked investors. Spooked investors meant a lower valuation. A lower valuation meant his equity was worth less. His family’s security was worth less.

The math was simple. Fix the process now and risk the IPO. Fix it after and risk nothing.

After the IPO, he told himself. After the IPO, we can do this properly. After the IPO, there’s time.

He highlighted the document. All of it. The analysis, the breakdown, the questions he’d finally started asking.

He pressed delete.

The screen went blank. Marcus closed the laptop and sat in the dark for a long time.

He knew what he’d just done. He’d seen the problem. He’d understood it. And he’d chosen to look away.

It’s not looking away, he told himself. It’s prioritizing. There’s a difference.

He went back to bed.

Friday, May 16, 2025 – 7:15 PM – Marcus’s Home Office

The text exchange with Edward happened on a Friday evening.

Marcus: Hey brother. How’s Miami treating you?

Edward: Good. Been experimenting with some new stuff at work. You?

Marcus: IPO prep is brutal but exciting. Board meeting went well last week.

Edward: Glad to hear it.

Edward: Hey, we should talk sometime about what I’ve been working on. Some interesting results around the AI stuff we discussed at spring break.

Marcus: Definitely. After the IPO, let’s grab dinner. Lots to catch up on.

Edward: Sure. After the IPO.

Marcus pocketed his phone. He’d respond properly later. After the board meeting, after the quarterly close, after the IPO. There was always time for Edward.

He turned back to his laptop and the projections that would carry him to the NYSE.

Chapter 3: The Medication Feature

April – September 2025

EDWARD

Thursday, May 1, 2025 – 5:30 AM – The Dock, Edward’s House on the Intracoastal

The dock was quiet at dawn.

Edward sat at the edge, fishing pole balanced loosely in his hands, watching the Intracoastal turn from black to gray to silver as the sun climbed over the horizon. He’d been coming here every morning since spring break, since the conversation with Marcus, since Sophia’s stories about AI and hackathons.

Five weeks now. Over thirty mornings of watching the water and wrestling with one phrase that wouldn’t leave his head: I won’t care if I’m irrelevant in 2028. I’ll be rich.

Marcus had laughed when he said it. Brushed off Edward’s story about Harold, the tape library guy from his first job at a defense contractor, like it was ancient history. But Edward couldn’t stop thinking about Harold. The expert who became obsolete overnight. The guy who went from essential to ornamental because he waited to see what happened instead of figuring it out.

Edward had always been the cautious one. Marcus used to joke about it at the Academy—“Johnson doesn’t take a bathroom break without a contingency plan.” But caution had kept Edward alive in the Persian Gulf. Two years on the Boutwell, running maritime security operations while Jennifer taught English in Istanbul—close enough to meet him whenever he got leave. Stolen weekends in Cyprus, Athens, wherever his ship docked. Two years of watching the horizon, checking the radar, anticipating threats before they materialized. You didn’t survive that by being reckless.

When he finally got stateside—New York, then the MS at NYU, then the defense contractor job in Virginia—he’d brought that caution with him. Northrop Grumman was perfect for someone who’d learned to triple-check everything. Regulated software. Compliance reviews. Documentation for documentation. The kind of work where careful was a feature, not a bug.

But caution could curdle into paralysis. He’d seen it happen to Harold. He’d seen it happen to entire companies. The organizations that were so careful about avoiding the wrong decision that they never made the right one.

The calculus had changed. That’s what kept gnawing at him.

He’d spent twenty years building expertise. Twenty years of learning systems, understanding architectures, developing judgment about what worked and what didn’t. That expertise had made him valuable, valuable enough to become CTO of a public company.

But expertise had a half-life now. He could see it in the quarterly reports from Gartner and Forrester. He could see it in the way junior engineers were getting comparable results in hours instead of days. The productivity multiplier was real, and it was compounding.

If Edward didn’t figure this out, his board would eventually bring in someone who would. Maybe not this year. Maybe not next year. But by 2028? His experience might be as relevant as Harold’s tape schedules.

Edward didn’t resent the change; resenting market forces was a waste of energy. But he needed to understand the new math. If a junior engineer with the right tools could match a senior engineer’s output, what happened to the value of seniority? If institutional knowledge could be captured in AI systems, what happened to the premium companies paid for experience?

The board wouldn’t ask these questions directly. They’d just start wondering if maybe a younger CTO, one who’d grown up with these tools, might be a better fit for the next phase.

He was forty-three years old. Sophia was eighteen now, a freshman at Georgia Tech. Emma was fifteen, three years from college. Lily was eleven, still young enough to think her dad knew everything.

Twenty years of fatherhood. Twenty years of watching himself become someone he hadn’t expected to be.

He’d missed Sophia’s entire pregnancy. Four months on a ship in the Persian Gulf while Jennifer grew their daughter inside her. He’d gotten emergency leave once—seventy-two hours, eighteen of them spent in the air each way. One night to hold his pregnant wife, to feel the baby kick against his palm, to whisper promises to a belly he wouldn’t see again until it was empty. Then back on a plane, back to the Gulf, back to watching the horizon while Jennifer’s mother drove her to doctor’s appointments.

When he finally came home, Jennifer was seven months pregnant and exhausted. They got married two weeks later—small ceremony, just family, Jennifer in a dress that accommodated the belly he’d missed watching grow. Sophia arrived in August. Edward held his daughter for the first time and his hands wouldn’t stop shaking.

He’d made a promise that day. Never again. Never miss the moments that mattered. Never let the job take him away from the people who needed him.

Emma came three years later, when they were settled in Virginia. Edward was there for every appointment, every ultrasound, every 3 AM craving run to the 7-Eleven. He held Jennifer’s hand in the delivery room and cried when Emma screamed her first breath. He hadn’t cried when Sophia was born. He’d been too overwhelmed, too shell-shocked, too aware of everything he’d missed.

Lily came four years after that. By then, Edward knew who he was. Not the young officer watching horizons for threats. Not the anxious new father trying to make up for lost time. Just a dad. A husband. A man who’d figured out that the job was supposed to serve the family, not the other way around.

Forty-three years old. The age his father had been when Edward graduated from the Academy. His father had seemed so old then, so settled, so certain about everything. Edward didn’t feel certain about anything. He felt like he was still figuring it out, still learning, still trying to become the man his daughters thought he already was.

Jennifer had given up her career to raise them. She’d been teaching English in Istanbul when they met, twenty-two years old with plans for graduate school, maybe international development, maybe something that used her languages. Instead, she’d followed him to New York, then Virginia, then Florida. Three kids in eight years, and by the time Lily started kindergarten, Jennifer’s career had become motherhood. She’d made that choice willingly, but it meant everything rode on Edward’s salary. His equity. His relevance.

The house they’d bought eight years ago, when he’d made VP of Engineering: back then, waterfront on the Intracoastal was attainable, not aspirational. Now the insurance had tripled. Hurricane premiums, flood insurance, windstorm coverage. Every year Jennifer would show him the renewal notice and they’d have the same conversation: Should we move?

If he lost this job, they’d have to sell. Twenty more years on the mortgage. No safety net. Three daughters who were counting on him to figure it out, the same way he’d counted on his own father to figure it out, back when he thought forty-three was old.

But there was something else gnawing at him. Something more immediate than career anxiety.

The medication tracking feature.

It had been in the backlog for eighteen months. Hospitals kept asking for it, a way to flag potential drug interactions before discharge. The CDC estimated 7,000 to 9,000 patients died annually from medication errors. This feature could catch some of those. It could save lives.

And it sat there. Stuck. Because the engineering team was buried in maintenance work, code reviews, and technical debt. Because every time someone tried to prioritize it, something else came up. Because the process was designed to produce activity, not outcomes.

That’s what kept Edward up at night. Not “AI strategy.” The fact that his company was too slow to ship the things that mattered.

Monday, May 5, 2025 – 9:00 AM – Edward’s Office, Riverton Health Systems, Brickell

Rachel Torres was waiting in his office when he arrived. She looked worried.

Rachel had been Edward’s chief of staff for seven years now. She’d started working for him right out of college, when he was still at his previous company. Eager, sharp, with a computer science degree she wasn’t sure she wanted to use for coding. Edward had seen something in her, an ability to translate between technical and business that most engineers lacked. When he made CTO at Riverton, she made the move with him. She knew how he thought, anticipated what he needed, and wasn’t afraid to tell him when he was wrong.

“We have a problem.”

Edward set down his bag. “What kind of problem?”

“Engineers are using AI tools. On their own. Without approval.”

He sat down slowly. “What do you mean?”

“I mean they’re copying code into ChatGPT. Using Copilot with personal accounts. Pasting patient data schemas into AI chatbots to get help debugging.” Rachel handed him a printout. “I found this in a Slack channel. An engineer was celebrating that he’d ‘saved four hours’ by having AI write his unit tests.”

Edward stared at the printout. His first instinct was alarm. HIPAA violations, IP exposure, security risks. His second instinct was to ban everything immediately.

But then he stopped.

“If they’re doing this despite the risk,” he said slowly, “there’s a need we’re not meeting.”

“That’s… not what I expected you to say.”

“Me neither.” Edward leaned back. “But think about it. Smart people. They know the rules. They’re doing it anyway.”

“So what do we do?”

“Figure out why they’re in pain.”

Tuesday, May 6, 2025 – 2:00 PM – Conference Room B, Riverton Health Systems

The consultants arrived at 2 PM sharp. Three of them from Stratton McKelvey, dark suits, leather portfolios, confident handshakes. Edward had brought them in because the board kept asking about “AI strategy” and he needed to understand what the market was recommending.

“Thank you for making time,” the lead consultant said, pulling up a slide deck. “What we’re proposing is a comprehensive AI SDLC transformation roadmap. Twenty-four to forty-eight months, depending on organizational readiness.”

Edward nodded. “Walk me through it.”

“Phase one is assessment. We’ll evaluate your current state across twelve dimensions of AI SDLC maturity: data infrastructure, talent readiness, governance frameworks, change management capacity. That’s a ninety-day engagement.”

“Ninety days just to assess?”

“Transformation requires understanding before action. You can’t build a house without blueprints.”

The slides kept coming. Phase two: pilot selection. Phase three: Center of Excellence establishment. Phase four: scaled rollout with governance oversight. Phase five: continuous improvement and maturity advancement.

“What’s the timeline to ROI?” Edward asked.

The consultant checked his notes. “Assuming no major blockers, you’d see measurable returns by Q1 2027. That’s aggressive but achievable.”

Edward did the math. Two years minimum. Maybe four. Before they saw any return at all.

“I have a feature that saves lives sitting in my backlog right now,” Edward said. “The medication tracking feature. It’s been stuck for eighteen months. Hospitals are asking for it. Patients could be dying because we can’t ship fast enough.”

“That’s exactly why you need a transformation roadmap. The feature is stuck because your organization isn’t ready. “

“What if I told you I don’t have two years?”

The consultant smiled patiently. “Transformation takes time. You can’t rush organizational change. Companies that try to move too fast end up with failed implementations, change fatigue, and worse outcomes than if they’d never started.”

Edward leaned back. A question had been forming in his mind, one he wasn’t sure he wanted to ask. But he asked it anyway.

“Do any of you build software with AI tools?”

The room went quiet.

The lead consultant glanced at his colleagues. Neither spoke.

“I’m not asking about your clients,” Edward pressed. “I’m asking about you. Personally. Do you use Copilot? Cursor? ChatGPT? When you write code, if you write code, do you use these tools?”

More silence.

“We’re consultants,” the lead finally said. “Our job is to help organizations adopt. “

“You’re selling a forty-eight-month roadmap for tools you’ve never used.” Edward stood up slowly. “You’re telling me how to transform my engineering organization, and none of you have ever built anything with these tools yourselves.”

“With respect, implementation experience isn’t necessary for strategic advisory. “

“It’s the only thing that matters.” Edward walked to the window, looking out at Biscayne Bay. “I’ve spent twenty years in this industry. I’ve seen a dozen transformation initiatives. The consultants always have the same pitch: assess, plan, pilot, scale. Twenty-four to forty-eight months. And 70% of them fail. You know why?”

Nobody answered.

“Because the people designing the transformation have never done the work.” He turned back to face them. “Thank you for your time. We won’t be moving forward.”

The consultants packed up their leather portfolios with the stiff politeness of people who’d just been fired. Edward walked them to the elevator, shook hands, and watched the doors close.

Rachel was waiting when he got back to the conference room.

“You just fired Stratton McKelvey.”

“Saved us two million and two years of nothing.”

“The board wanted an AI SDLC strategy.”

“The board wants results.” Edward sat down. “Those guys can’t teach what they’ve never learned. I need to figure this out myself.”

“You’re going to learn to code with AI?”

“I’m going to learn to build again. Haven’t written production code in eight years.” He shook his head. “Maybe that’s the problem.”

“So what’s the plan?”

“First, I learn. Actually use the tools. Then we map the software process, the real one, not the documentation. Find out where the medication feature is stuck.” He paused. “Then we fix it.”

“That’s not an AI SDLC strategy.”

“No. It’s process improvement. AI might help. Might not. Won’t know until I try.”

Tuesday, May 6, 2025 – 4:00 PM – Edward’s Office, Riverton Health Systems

After the consultants left, Edward tried the vendors.

Over the next two weeks, he sat through eleven demos. Established players. Hot startups. Enterprise giants rebranding legacy products as “AI-powered.”

The pattern was always the same. Slick slides. Impressive demos. Metrics that measured tool activity—lines generated, keystrokes saved, task completion time—but nothing about what the business actually needed. Edward kept asking the same question: Can this help me ship the medication tracking feature? The one that’s been stuck for eighteen months while hospitals keep asking for it?

Not one of them could answer it. They had demos and case studies, but they couldn’t connect any of it to his actual problem.

One sales engineer was honest enough to admit it. “Look,” she said after Edward’s third pointed question, “the truth is, we’re all figuring this out. The technology is moving faster than anyone’s ability to implement it. Most of our case studies are six months old, which means they’re basically ancient history in AI terms.”

Edward appreciated the honesty. He didn’t buy the product.

He tried one more avenue. Tom Hirsch, an old colleague with a boutique consulting firm, sent over a team. Edward recognized two of them from a previous DevOps engagement. They had new AI certifications, but when Edward asked what they’d actually built, the answer was roadmaps and readiness assessments. None of them had written code with AI tools.

He’d have to figure this out on his own.

Thursday, May 22, 2025 – 2:17 AM – Master Bedroom, Edward’s House on the Intracoastal

Edward couldn’t sleep.

He’d been staring at the ceiling for two hours, running the same calculation over and over. He’d fired Stratton McKelvey. Dismissed Tom’s team. Rejected eleven vendors. The board was expecting an AI SDLC strategy, and he had nothing to show them except a list of people he’d decided weren’t good enough.

What if I’m wrong?

The thought kept circling back. What if the consultants knew something he didn’t? What if the 24-month roadmap was actually the right approach, and his impatience was going to cost the company everything? What if his instinct to “figure it out myself” was just arrogance dressed up as initiative?

He slipped out of bed, careful not to wake Jennifer, and went downstairs to his home office. The laptop was still open from the evening, email drafts unsent.

He started typing.

Dear Michael,

I’ve reconsidered our conversation from Thursday. While I still have concerns about the timeline, I recognize that Stratton McKelvey has transformation experience that Riverton lacks. I’d like to discuss resuming our engagement, perhaps with a modified scope that focuses on…

Edward stopped typing. Read it back. His finger hovered over the trackpad.

Send it. Just send it. Let the professionals handle this. You’re a CTO, not a transformation consultant. You don’t know what you’re doing.

The cursor blinked.

But they don’t know either. They’ve never built anything. They’re selling confidence, not competence.

Maybe confidence is what the board needs. Maybe looking like you have a plan is more important than actually having one.

He stared at the draft for a long time. The house was silent. Through the window, he could see the dock, the water black and still beyond it.

Jennifer’s voice came from the doorway. “You’re up.”

“Couldn’t sleep.”

She walked over, wearing the old Coast Guard sweatshirt she’d stolen from him in 2006, right before Sophia was born. She’d been wearing it for twenty years now. He’d stopped asking for it back around year three.

She looked at the screen. Read the email. Didn’t say anything for a moment.

“You’re going to call them back.”

“I’m thinking about it.”

“Because you’re scared.”

“Because maybe they know something I don’t.”

Jennifer sat on the arm of his chair. The same way she’d sat when he told her about Iraq. When he told her about the job offer in Florida. When he told her Sophia was switching majors. She’d been sitting on the arm of his chair for twenty years, and he’d been making better decisions because of it.

“Ed, I’ve watched you for twenty years. I know when you know something’s wrong. You knew the consultants were wrong the moment they said ‘forty-eight months.’ You knew it in your gut.”

“My gut isn’t a strategy.”

“Neither is hiring people you don’t believe in.” She put her hand on his shoulder. “What are you actually afraid of?”

Edward was quiet. The answer came slowly.

“That I’ll fail. That I’ll try to figure this out myself, and I’ll get it wrong, and the board will fire me, and we’ll lose the house, and Emma won’t go to the college she wants, and it’ll all be because I was too proud to admit I needed help.”

“That’s a lot of catastrophizing for 2 AM.”

“It’s 2 AM. That’s what 2 AM is for.”

Jennifer smiled slightly. “Delete the email.”

“What if I’m wrong?”

“Then you’ll be wrong. And you’ll learn something. And you’ll try again.” She stood up. “But you won’t learn anything by handing this to people who’ve never done it themselves. You said it yourself: they can’t teach what they’ve never learned.”

Edward looked at the email. At the cursor still blinking.

He highlighted the text. All of it. And pressed delete.

“Come back to bed,” Jennifer said.

“In a minute.”

She paused at the door. “You remember what you told me when you left the Coast Guard? When you took the Northrop job?”

“That I was ready to start our real life.”

“You said you’d spent five years learning to watch for threats. And now you wanted to learn to build something.” She smiled. “You’ve been building things ever since. The defense contractor, the healthcare work, Riverton. You know how to build, Ed. Trust that.”

She left. Edward sat alone in the dark office, laptop glowing, feeling the weight of what he’d just decided. No consultants. No vendors. No safety net.

Just the questions he didn’t know how to answer yet.

But Jennifer was right. He’d spent five years in the Coast Guard learning to navigate uncertainty. Two years in a war zone learning to make decisions with incomplete information. Fifteen years in corporate America learning to build systems that worked.

Maybe that was enough. Maybe the consultants’ confidence was just a different kind of fear—fear of admitting they didn’t know, dressed up as a process.

He closed the laptop and went back upstairs. Sleep came eventually, fitful and thin.

Saturday, May 24, 2025 – 5:00 AM – Home Office, Edward’s House on the Intracoastal

Edward sat at his desk with his laptop, a cup of coffee growing cold beside him. The sun wouldn’t be up for another hour. Through the window, he could see the dock, the water black and still.

He’d downloaded Claude Code, Copilot, and Cursor the night before. Now he was staring at a blank screen, trying to remember the last time he’d written code that wasn’t a quick script or a proof of concept.

Eight years. Maybe nine.

He started small. A simple Python script to parse some log files, something he’d asked an engineer to do the month before. It took the engineer two days. Edward wanted to see what happened with AI.

Three hours later, he had a working script. Not just working, elegant. The AI had suggested patterns he wouldn’t have thought of, caught edge cases he’d missed, refactored his clunky first attempt into something clean.

But that wasn’t what surprised him.

What surprised him was how it felt.

For eight years, coding had been something other people did. Edward reviewed code, approved architectures, made decisions about technical direction. But he didn’t build anymore. He’d told himself that was fine; his job was leadership, not implementation.

Now, sitting on the dock with the sky turning pink over the Intracoastal, he picked up the laptop again. Opened a new file. Started typing. He didn’t stop until the sky was dark.

Saturday, June 7, 2025 – 3:00 PM – The Dock, Edward’s House on the Intracoastal

Sophia was home for spring break. She’d arrived two days ago, a week off from Georgia Tech before the final push to finals. Edward found her on the dock that Saturday afternoon, laptop open, feet dangling over the water.

“What are you working on?”

“Side project.” She didn’t look up. “Building an AI agent that can navigate codebases. You feed it a repo and it learns the architecture, then you can ask it questions.”

Edward sat down beside her. The dock creaked the way it always did.

“I wrote a Python script this morning,” he said. “Log parser. First real code I’ve written in eight years.”

Now she looked up. “Wait, seriously?”

“It was…” He searched for the right word. “Fun.”

Sophia’s face lit up in a way that reminded him of her at six years old, showing him a drawing she was proud of. “Dad. That’s amazing. Show me.”

He pulled out his laptop. For the next hour, they sat on the dock together, two generations of Johnsons staring at screens, the Intracoastal lapping beneath them. Sophia walked him through her workflow. Claude for architecture, Copilot for implementation, ChatGPT for debugging. Prompt patterns. Context windows. How you had to think with the AI, not just at it.

“People treat it like a magic box,” she said. “Type in a question, get an answer. But it’s more like a really smart collaborator who doesn’t know your codebase yet.”

“Like onboarding a new engineer.”

“Exactly! Except this one works at 3 AM and never gets tired.”

They pair programmed for three hours. Sophia showed him how she’d automated her entire testing workflow. “I haven’t written a manual test in six months. The AI generates them from my code. Better coverage than anything I could write by hand.”

She showed him the prototype generator one of her classmates had built. “James made this. You give it a product requirements document and it generates a working prototype. Not production-ready, but 80% of the way there in an hour instead of a week.”

Edward asked about failure modes. The hallucinations. The context limits. The times the AI confidently produced garbage. Sophia was honest about the limitations.

“It’s not magic,” she said. “It’s a tool. A really good tool. But you still have to know what you’re building.”

What struck Edward wasn’t the technology. It was his daughter’s attitude.

She didn’t think of AI as a threat or a disruption or a transformation challenge. She thought of it as a tool, like a really good IDE or a smart pair programmer. She wasn’t afraid of it. She wasn’t resistant to it. She just used it, the same way she used Git or developer forums or a search engine.

“How do you stay current?” Edward asked. “The tools change so fast.”

Sophia laughed. “I don’t try to stay current on tools. I stay current on outcomes. What do I need to build? What’s the fastest way to build it? The tools are just means to an end.” She shrugged. “My professor keeps saying the same thing. ‘Don’t fall in love with the hammer. Fall in love with the house you’re building.’“

Edward thought about the consultants he’d fired. They’d been obsessed with tools. AI Readiness Assessments, governance frameworks, maturity models. His nineteen-year-old daughter didn’t care about any of that. She just built things.

Jennifer came out around six with sandwiches and lemonade. She found them still on the dock, still coding, still talking.

“I don’t think I’ve ever seen you two like this,” she said, setting down the tray.

Edward looked at Sophia, then at his laptop, then at the water. “I don’t think I’ve ever been like this.”

“Like what?”

“Learning from my kid.” He smiled. “It’s humbling. And kind of wonderful.”

Sophia rolled her eyes, but she was smiling too. “Dad, you’re being weird.”

“I’m being honest.” He picked up a sandwich. “The consultants I fired—they had decades of experience. Certifications. Frameworks. Roadmaps. They couldn’t answer simple questions about what actually works. You answered them in three hours.”

“That’s because they’ve never built anything with these tools,” Sophia said. “They’re selling expertise they don’t have.”

Edward stopped chewing. That was it. That was exactly it.

The transformation industry was selling expertise it didn’t have. The real expertise was in dorm rooms and on docks, built by people too young to know they were supposed to wait for permission.

That evening, after Sophia went inside and Jennifer was cleaning up dinner, Edward sat alone on the dock with his notebook.

Stop asking “how do we adopt AI?” Start asking “what do we need to build?”

The tools are changing too fast to standardize. Standardize on outcomes instead.

Sophia isn’t afraid because she’s never known anything else. My engineers are afraid because they remember the before times. Different problem, different solution.

Sophia’s testing workflow: AI generates tests from code. Why aren’t we doing this?

James’s prototype generator: 80% in an hour vs 100% in a week. When is 80% good enough?

He looked at the water, then at the house, then at the window where he could see Sophia’s silhouette moving around her room.

The consultants had wanted two years and three million dollars to tell him how to think about AI. His daughter had done it for free in an afternoon. Because she wasn’t trying to sell him anything. She was just excited about what she was building.

For the rest of spring break, they built together. Every morning on the dock, laptops open, coffee cooling beside them. Sophia showed him her workflows; he showed her how enterprise systems actually worked. She’d never seen a codebase with fifteen years of technical debt. He’d never seen someone build a working prototype in an afternoon.

Edward rebuilt an internal dashboard that had been on the backlog for six months. He prototyped a new API endpoint that his team had estimated at three weeks. He did it in four days. When he got stuck, Sophia unstuck him. When she got stuck, he reminded her to step back and think about the problem differently.

It was the best week he’d had in years.

When Sophia flew back to Atlanta on Sunday, Edward kept building. Small projects at first: utilities, prototypes, experiments. He’d text her screenshots, ask questions, get back emoji reactions and quick voice memos explaining what he’d done wrong. The mentorship had reversed—his nineteen-year-old daughter teaching him to code again.

And somewhere in those weeks, something clicked.

If the tools were this good now, in early 2025, what would they be like in 2028? The improvement curve wasn’t linear. Every few months, the models got significantly better. The things that felt like magic today would be table stakes in three years.

He thought about Harold again. The tape library guy. Harold had been an expert in systems that stopped mattering. He’d spent his career building competency in something that became obsolete.

Edward couldn’t let that happen to Riverton. He couldn’t march his organization toward today’s standards; by the time they got there, the standards would have moved. It would be like planning a trip to Mars by aiming at where Mars was today, instead of where it would be when you arrived.

He needed to build the organization for 2028, not 2025.

That meant learning first, then scaling. You couldn’t teach what you’d never learned. You couldn’t lead a transformation you didn’t understand. The consultants had failed because they’d never done the work. Edward refused to make the same mistake.

Saturday, June 21, 2025 – 2:00 PM – Klaus Advanced Computing Building, Georgia Tech Campus, Atlanta

The invitation came through Sophia.

“Dad, this is kind of embarrassing, but my computer club figured out who you are.”

She’d called him the week after spring break, sounding mortified.

“What do you mean, figured out who I am?”

“One of our TAs was looking for entry-level jobs. She saw Riverton’s posting online and noticed you were in my connections. Same last name.” Sophia groaned. “Now they want you to come speak at a meeting. About AI transformation in industry.”

“Your computer club wants to hear from me?”

“They want to hear from anyone in industry. Last month they had a startup founder. Month before that, an engineer from a tech giant.” She paused. “You don’t have to do it. I know it’s weird.”

Edward thought about the consultants he’d fired. Thought about how disconnected they’d been from actual building. Thought about how much he’d learned from Sophia over spring break.

“I’ll do it,” he said. “But I want something in return.”

“What?”

“I want to learn from them too. Not a lecture—a conversation. I want to know what they’re building, how they’re using AI, what works and what doesn’t.”

The computer club meeting was in a cramped room in the Klaus Advanced Computing Building. About thirty students, mostly sophomores and juniors, some grad students in the back. Laptops everywhere. Energy drinks. The particular intensity of people who loved what they were doing.

Sophia had met him at the airport that morning, clearly nervous about her dad invading her college world. But when Edward walked into the room and saw the whiteboards covered in architecture diagrams, the monitors showing half-finished projects, the energy of people building things—he felt at home.

Edward had prepared remarks. He threw them out in the first five minutes.

“I’m supposed to tell you about AI transformation in enterprise healthcare IT,” he said. “But honestly? I’m here to learn from you. I’ve spent the past two months trying to figure out how to help my organization adopt AI. The consultants I hired couldn’t answer basic questions. So I want to ask you instead.”

The room shifted. Students sat up. This wasn’t what they’d expected.

“What are you actually building?” Edward asked. “Show me.”

For the next two hours, they showed him.

A junior named Cora was building an AI agent that could navigate codebases and answer questions about architecture. “I’m training it on open source projects,” she said, pulling up her screen on the projector. “It already knows React better than most senior developers.”

A senior named Priya—the one who’d noticed the online connection—had automated her entire testing workflow. “I haven’t written a manual test in six months. The AI generates them from my code. Better coverage than anything I could write by hand.”

Another student named James was building something that made Edward’s stomach drop: an AI system that could take a product requirements document and generate a working prototype. “It’s not production-ready,” James admitted. “But it gets you 80% of the way there in an hour instead of a week.”

Edward asked about workflows, about prompts, about failure modes. He asked about what didn’t work: the hallucinations, the context limits, the times the AI confidently produced garbage. The students were honest about the limitations.

At the end of the meeting, Priya raised her hand. “Mr. Johnson, can I ask you something?”

“Of course.”

“Why did you really come here? CTOs don’t usually fly to Atlanta to ask college students for advice.”

Edward thought about it. “Because the consultants I hired have never built anything with these tools. They have certifications and frameworks and roadmaps. But they couldn’t answer simple questions about what works and what doesn’t.” He looked around the room. “You can. That’s why I’m here.”

The room was quiet. Then Priya smiled. “That’s the most honest thing an industry speaker has ever said to us.”

On the flight back to Miami, Edward made notes.

The irony wasn’t lost on him. He’d met with four consulting firms. Stratton McKelvey. Chicago Consulting Group. Detroit DevOps. A boutique AI consultancy with a slick website. Combined, they’d probably had two hundred years of enterprise experience. And not one of them could show him a working demo of something they’d built with AI.

These students, some of them twenty years old, had more hands-on experience with AI development than all those consultants combined. Priya’s testing automation alone was more sophisticated than anything the consultants had described. James’s prototype generator would have been a six-figure consulting deliverable, and he’d built it as a side project.

The transformation industry was selling expertise it didn’t have. The expertise was in dorm rooms and computer clubs, built by people too young to know they were supposed to wait for permission.

Friday, June 27, 2025 – 9:00 AM – Large Conference Room, Riverton Health Systems

Edward reserved the large conference room, the one with the windows facing Biscayne Bay and the whiteboard wall that stretched twenty feet.

He’d spent five weeks learning to build again—first on his own, then with Sophia over spring break, then flying to Atlanta to learn from her computer club. Now he understood, viscerally not just theoretically, what the tools could do. He’d felt the joy of coding come back. He’d experienced the productivity gains firsthand. And he’d realized that aiming for 2025 standards was already aiming too low.

Now he needed to understand what was stopping the organization from shipping.

He’d invited six engineers from different teams. People he trusted. People who would tell him the truth.

“Here’s what I want to understand,” he said, standing at the whiteboard. “The medication tracking feature. It’s been in the backlog for eighteen months. Walk me through what actually happens when a feature like this moves through our system. Not the official process, the reality. Where does it wait? Where does it get stuck?”

For the first hour, they talked. Edward wrote. Rachel asked questions.

But something became clear quickly: the engineers struggled to articulate what they actually did.

“And after the pull request is opened, what happens?” Edward asked.

“It goes into review.”

“What does ‘goes into review’ mean? What are the actual steps?”

Long pause. Shrugging.

“I mean, Kevin looks at it. He does his thing. Approves it or sends it back.”

“What does Kevin look for? What’s his process?”

“I don’t know. He just… reviews it.”

A junior engineer named Derek spoke up. “The queue isn’t a real blocker. Kevin’s fast. A day, maybe two.”

Edward wrote it on the whiteboard. “One to two days. Okay. What happens before the PR gets to Kevin?”

“Development.”

“How long?”

“Depends on the feature. Two weeks, usually.”

Edward wrote that down. “And before development?”

Silence. The engineers looked at each other.

“Before development,” Edward repeated. “What happens after a feature gets assigned but before anyone writes code?”

“Environment setup,” someone said.

“How long?”

“A week? Sometimes two?”

“Why?”

More silence. Then a woman named Maria, a ten-year veteran, leaned forward. “Because the infrastructure team is backlogged. They provision environments manually. If you submit a request on Monday, you might get access by Friday. If you submit on Friday, you wait until the following Thursday.”

“So a feature can sit for two weeks before anyone writes a line of code?”

“Sometimes longer.”

The engineers leaned forward. They could see it now, the picture emerging from fragments they’d never assembled.

“What about before that? Before environment setup?”

“Design review.”

“How long?”

“Three weeks.”

“Three weeks?” Edward stopped writing. “For design review?”

“Product has to sign off. And they meet weekly. So if you miss the Thursday meeting, you wait until the next Thursday.”

“And if there’s feedback?”

“You wait another week.”

The room was getting quieter. Edward kept writing. The whiteboard was filling up with boxes and arrows and wait times that nobody had ever seen collected in one place.

“What about after code review? After Kevin approves?”

“QA.”

“How long?”

“Two weeks for test script writing. Another week to run the tests.”

“Why two weeks for test scripts?”

“Because we write them manually. From scratch. Every time.”

Edward stepped back from the whiteboard. The diagram covered the entire surface. Twelve boxes. Dozens of arrows. Wait times adding up to something nobody wanted to say out loud.

“I’m going to add up the numbers,” he said. “Tell me if I get it wrong.”

He worked through the diagram, writing totals next to each stage.

The room was silent.

Edward realized he was seeing something important. These were good engineers, smart, experienced, capable. But they’d been doing the same work for so long that the knowledge had become tacit. Unconscious. They couldn’t externalize what they knew because they’d never had to.

It was the same pattern he saw with onboarding. When new engineers joined, the veterans would say “just shadow Kevin for a week” because they couldn’t actually explain what Kevin did. The expertise existed, but it was locked in people’s heads. impossible to transfer, impossible to scale, impossible to improve because no one could see it clearly enough.

And now AI tools were asking engineers to do exactly what they’d never learned to do: externalize their context. Tell the AI what you’re trying to accomplish. Explain the constraints. Describe the codebase. But if they couldn’t explain it to a new hire, how would they explain it to an AI?

“Let me try something different,” Edward said. “Instead of telling me what happens, show me. Walk me through the last feature you shipped. Pull up the PRs, the comments, the tickets. Let’s trace the actual path.”

That worked better. With artifacts to anchor them, the engineers could reconstruct what had happened. Rachel took notes. Edward drew diagrams.

By noon, they had a map. Twelve stages from requirement to deployment:

Edward stepped back from the whiteboard.

“Twelve weeks,” he said. “Minimum. To ship a single feature.”

“Wait.” Priya Sharma raised her hand. “We’re missing something. Before requirements even get to design, there’s another step.”

“What step?”

“The agile coaches have to approve the acceptance criteria. Before any story gets prioritized into a sprint, Mike Donovan’s team reviews it. They meet on Fridays.”

Edward felt his eye twitch. “The agile coaches approve acceptance criteria?”

“They say it’s to ensure ‘definition of ready.’ Stories can’t enter the sprint backlog until the acceptance criteria meet their standards.”

“What standards?”

Priya shrugged. “Nobody really knows. Sometimes they approve everything. Sometimes they send stories back with comments about ‘user value statements’ or ‘testability concerns.’ One time they rejected a story because it didn’t have enough ‘acceptance test scenarios.’“

“And if you miss the Friday meeting?”

“You wait until the next Friday.”

Edward added a line to the top of the chart:

“So a story can sit for up to two weeks before it even enters the prioritization queue?”

“Depending on when it’s submitted. If you submit on a Thursday, you might get approved Friday. If you submit on a Saturday, you wait twelve days.”

Rachel was shaking her head. “I’ve been here four years. I didn’t know this step existed.”

“Neither did I,” Edward said. “And I’m the CTO.” He turned to the engineers. “How long has this been happening?”

“Since the Agile transformation. 2021? Mike’s team was brought in to ‘improve story quality.’ They set up the Friday review as a checkpoint.”

“Has anyone ever measured whether story quality actually improved?”

Silence.

“Has anyone asked if this step is still necessary?”

More silence.

Edward wrote on the whiteboard in large letters: THIRTEEN WEEKS. NOT TWELVE.

“We just found another week of waste hiding in the process. A meeting nobody questioned because it was called ‘agile.’“

Edward stepped back from the whiteboard again.

“Thirteen weeks,” he said. “Minimum. To ship a single feature.”

“That’s… longer than I thought,” one of the engineers said.

“Look at the breakdown.” Edward circled numbers on the board. “Development is two weeks. Actual coding. Everything else is waiting. Waiting for sign-offs. Waiting in queues. Waiting for people to review things. Waiting for a Friday meeting.”

Rachel did the math. “Eleven weeks of waiting. Two weeks of work.”

“Eighty-five percent of our cycle time is queue time.” Edward set down the marker. “This isn’t a technology problem. This is a process problem.”

The room was quiet.

“Now here’s the question,” Edward said. “Where can we reduce that wait time? And does AI help with any of it?”

They went through the list item by item.

Friday Agile Coach Approval (1-2 weeks): A meeting that existed because someone decided stories needed “quality gates.” Nobody measured whether it improved anything. AI didn’t help with this. Eliminating the meeting did.

Requirements to Design (3 weeks): The wait was for product sign-off. A committee met weekly to approve requirements. If you missed the meeting, you waited another week. AI didn’t help with this, but changing the approval process did.

Design to Development (2 weeks): Environment provisioning. Every new feature needed a development environment, and the infrastructure team was backlogged. AI didn’t help with this, but automation did. They’d been asking for automated environment provisioning since 2019.

Development (2 weeks): Actual coding. AI could potentially speed this up. Copilot, Claude, AI-assisted development.

Code Review Queue (4 days): Kevin Nakamura was the bottleneck. He reviewed everything for the Claims Processing team. AI pre-review could flag obvious issues before code reached Kevin, reducing his queue.

Writing Test Scripts (2 weeks): Manual test script writing. This was a clear AI opportunity. AI could generate test scripts from requirements.

HIPAA Compliance (3 weeks): A checklist that hadn’t been updated since 2018. Half the items were for risks that no longer existed. AI didn’t help with this, but reviewing the checklist did.

Approval Queue (1 week): A three-day approval queue that existed because in 2016, someone deployed bad code and crashed a system. No one remembered why the step existed, but no one wanted to remove it.

Edward stood back and looked at the board.

“Eight bottlenecks,” he said. “How many of them involve AI?”

Rachel counted. “Three. Maybe three.”

“And the other five?”

“Process problems. A Friday meeting nobody questioned. Approval queues that exist because someone was nervous five years ago. Checklists that haven’t been updated. Automation we never prioritized.”

“So if we fix all eight bottlenecks…”

“Thirteen weeks becomes maybe three or four.”

“And the medication tracking feature ships.”

The room was quiet. Then one of the engineers, Priya Sharma, team lead for Claims Processing, said: “This isn’t AI transformation. This is just… fixing things.”

“Exactly.” Edward smiled. “AI is one tool. Maybe it helps with three of these bottlenecks. But the other four have nothing to do with AI. They’re just waste we’ve never bothered to remove.”

Monday, June 30, 2025 – 10:00 AM – CEO’s Office, Riverton Health Systems

David Aldridge listened carefully as Edward laid out the value stream map.

“Eleven weeks from requirement to deployment,” Edward said. “Two weeks of actual work. Nine weeks of waiting.”

“And you think you can fix this?”

“I think we can ship the medication tracking feature in ninety days. Not by adopting AI, but by fixing the process. AI helps with some of the bottlenecks. But most of what’s slowing us down has nothing to do with technology.”

David leaned back. “The board is expecting an AI strategy. Johnny’s been building his governance framework. “

“Johnny’s governance framework is designed to manage AI adoption. But we don’t have an adoption problem. We have a shipping problem. Features get stuck because our process has nine weeks of waste built into it.”

“What are you proposing?”

“Give me ninety days and one feature. The medication tracking feature, the one that’s been stuck for eighteen months. If we can ship it in ninety days, I’ve proven the approach works. If we can’t, I’ll admit the consultants were right and we’ll do it their way.”

David was quiet for a long moment.

“Johnny won’t like this.”

“Johnny’s measuring workshop attendance. I’m proposing to measure features shipped.”

“And if something goes wrong? If there’s a HIPAA violation, a security breach. “

“I’ll own it. Personally. This is my bet.”

David was quiet. Twenty years they’d worked together, in various configurations. He knew Edward wasn’t prone to bold claims.

“Ninety days,” David said finally. “Ship the medication feature. And Edward, don’t make me regret this.”

Monday, June 30, 2025 – 11:00 AM – CEO’s Office, Riverton Health Systems

Victoria Hale, the independent board director, caught them in the hallway.

“David, Edward. I have concerns.”

David gestured toward his office. “Five minutes.”

Victoria sat down, her expression skeptical. “I just saw the board materials Edward submitted. Value stream mapping? Removing approval queues?” She shook her head. “Edward, this is elementary. Every organization knows they should map their processes. Every Lean Six Sigma workshop teaches this. Where’s the AI strategy? Where’s the innovation?”

Edward had been expecting this.

“You’re right that it’s elementary. But elementary doesn’t mean easy.” He leaned forward. “Everyone knows they should map their value stream. Everyone knows they should remove waste. But have you asked why they don’t do it?”

Victoria waited.

“Because consultants sell complex frameworks,” Edward said. “Thirty-six-month roadmaps. Centers of Excellence. Maturity models. They sell complexity because complexity justifies fees. Nobody pays $2 million for ‘look at your process and fix what’s broken.’“

“So you’re saying the entire transformation industry is wrong?”

“I’m saying the entire transformation industry has an incentive to make simple things complicated. The framework isn’t the hard part. The hard part is discipline, doing simple things consistently. That’s what organizations can’t do. Not because they lack knowledge. Because they lack the discipline to apply what they already know.”

Victoria was quiet.

“The medication tracking feature has been stuck for eighteen months,” Edward continued. “Not because we lack AI tools. Because we have a three-week compliance review that hasn’t been updated since 2018. That’s not an AI problem. That’s a discipline problem.”

“And you think ninety days of discipline fixes eighteen months of delay?”

“I think ninety days of actually looking at the problem beats two years of workshops about how to look at the problem.” Edward met her eyes. “The consultants have frameworks for everything except shipping. I’m proposing we skip the frameworks and just ship.”

David intervened. “Victoria, let’s give Edward his ninety days. If it works, we’ve found something. If it doesn’t, we go back to the traditional approach.”

Victoria nodded. “Fine. But I want weekly updates. And I want to understand why this works, if it works, when the frameworks don’t.”

“Fair,” Edward said. “But I’ll warn you: the answer isn’t going to be satisfying. The answer is going to be that we actually looked at the process and fixed what was broken. No magic. Just discipline.”

“That’s what I’m afraid of,” Victoria said. “Because if that’s true, it means we’ve been wasting money on consultants for twenty years.”

“Only one way to find out.”

Tuesday, July 1, 2025 – 2:00 PM – Conference Room B, Riverton Health Systems

Johnny Morrison was not happy.

Edward had known Johnny for three years now, ever since Johnny had been brought in to lead digital transformation at Riverton. Before that, Johnny had been VP of Technology at MedFirst Health, a regional hospital chain in the Midwest. What happened at MedFirst still followed him around like a shadow.

In 2019, a MedFirst engineer had used an early AI tool to generate code for a patient data export feature. The tool hallucinated a database connection string that happened to match a production server. The code went through review, passed testing, and deployed. Nobody caught the error. For six weeks, patient records were being exported to an unsecured staging environment. A routine audit found the breach. HIPAA violations. Class action lawsuit. $47 million settlement. The engineer was fired. Johnny resigned, even though he hadn’t approved the tool or known about the experiment. He was the VP. It happened on his watch.

He’d spent the next two years consulting, rebuilding his reputation. When Riverton hired him to lead AI transformation, he’d been explicit about his approach: governance first. Structure before speed. Never again would something deploy without proper oversight.

Edward understood the scars. He just thought Johnny had learned the wrong lesson.

“You went to David without consulting me,” Johnny said, his voice tight. “AI strategy is my domain. The CEO hired me to manage this.”

“I’m not doing AI strategy,” Edward said. “I’m shipping a feature.”

“By using AI tools. Without proper governance. Without. “

“By fixing our process. AI is involved in maybe three of seven bottlenecks. The rest is removing waste that’s been there for years.”

Johnny sat down. “I don’t understand what you’re trying to accomplish.”

“Let me ask you something. The medication tracking feature. It’s been in the backlog for eighteen months. Why?”

Johnny blinked. “That’s not really an AI question.”

“Exactly. It’s a process question.” Edward leaned forward. “And until we answer the process question, all the AI tools in the world won’t help us ship faster. I’ve been mapping the value stream. Eleven weeks from requirement to deployment. Two weeks of actual work. Nine weeks of waiting.”

“So you need AI to speed up the waiting?”

“No. I need to understand why the waiting exists. Some of it is real, compliance reviews for patient safety. Some of it is theater, approval queues that exist because someone was nervous five years ago.” Edward paused. “AI can help with some bottlenecks. But treating this as an ‘AI adoption’ problem is like treating a broken leg with a new pair of shoes.”

Johnny was quiet.

“Here’s what I think,” Edward continued. “You’ve seen transformation failures up close. The HIPAA violation at MedFirst. You know what ungoverned experimentation can cost. Those concerns are legitimate.”

Johnny nodded. “They are.”

“But your solution, ban everything until we have perfect governance, creates a different risk. It drives usage underground. It makes the problem invisible instead of solving it.” Edward stood. “I’m proposing we fix the process. AI where it helps. Governance where it matters. Not governance as a way to avoid doing anything.”

“And if something goes wrong?”

“Then we learn from it. Fast. That’s the difference between process improvement and process theater.”

Johnny didn’t agree. But he didn’t escalate either.

It was a start.

Friday, July 4, 2025 – 3:00 PM – Edward’s Office, Riverton Health Systems

Edward dissolved every existing governance body and created one new one.

“We’re calling it the AI-SDLC Board,” he told Rachel. “Not because AI is magic. Because AI is infrastructure now. It touches every part of how we build software. So governance has to be embedded in the SDLC, not bolted on top.”

He wrote the charter on the whiteboard:

AI-SDLC Board Charter

Mission: Reduce toil. Reduce risk. Deliver better software outcomes.

Principles:
– We are AI-biased, but adopting AI alone won’t create these outcomes
– We reduce handoffs and protect nothing that doesn’t protect patients
– We act now, not later. Waiting is not safe.
– Any team member can ask for a decision. Answer in 24 hours or less.

“Any team member?” Rachel asked. “That’s going to be chaos.”

“That’s going to be accountability. If someone on the ground sees a blocker, they shouldn’t have to wait for it to bubble up through three layers of management. They ask. We answer. In a day.”

The board:
– Edward (CTO) – accountable for outcomes
– Sandra Williams (CFO) – accountable for spend
– Maria Santos (Legal/Compliance) – accountable for risk
– Rachel Torres (Chief of Staff) – accountable for execution and coordination
– One rotating engineer from the pilot team – accountable for ground truth

“What about Johnny’s steering committee? The Architecture Review Board? The Security Council?”

“Gone. All of them. One board. One place where decisions happen.” Edward underlined the charter. “We’re not waiting to improve anymore. Every committee that doesn’t decide is overhead. We’re cutting the overhead.”

“That’s aggressive.”

“That’s the point. We’ve been protecting process for years. Now we’re protecting outcomes.”

The first meeting was Thursday, April 3.

Agenda:
1. Approve automated environment provisioning (bottleneck #2)
2. Review updated HIPAA checklist (bottleneck #6)
3. Authorize AI-assisted code review pilot (bottleneck #4)

All three items were approved in forty-five minutes. No escalation. No “let’s socialize this with stakeholders.” Decide or defer, but don’t delay.

That afternoon, an engineer from the Provider Portal team sent an email: “Can I get approval to use AI for test generation? My manager says it needs board review.”

Edward replied within two hours: “Approved. Document what you learn. Share results in Friday standup.”

Word spread fast. By the end of the week, the AI-SDLC Board had fielded eleven requests. Nine were approved same-day. Two needed more information and were resolved within 48 hours.

“This is insane,” Johnny told Edward in the hallway. “You can’t run governance this fast. Something’s going to slip through.”

“Something might. And when it does, we’ll fix it fast. That’s the difference between process improvement and process theater.” Edward paused. “Johnny, we spent two years building governance structures that made us feel safe. Did they actually make us safe? Or did they just make us slow?”

Johnny didn’t answer. They both knew the answer.

“Twenty-four hours or less,” Edward said. “That’s the new standard. If we can’t decide that fast, we don’t understand the problem well enough.”

Monday, July 14, 2025 – 9:00 AM – Small Conference Room, Riverton Health Systems

The pilots started with the medication tracking feature.

Priya Sharma’s Claims Processing team would handle the core development. They’d already mapped the value stream. They knew where the waste was. Now they needed to prove they could eliminate it.

Week 1: Automated environment provisioning deployed. Wait time: 2 weeks → 2 hours. No AI involved.

Week 2: Updated HIPAA checklist approved. 47 items reduced to 23. Wait time: 3 weeks → 1 week. No AI involved.

Week 3: AI-assisted code review pilot launched. Kevin Nakamura was skeptical, but he’d agreed to try.

The first week was rocky. Kevin couldn’t get the AI to understand what he was looking for. He’d type “review this code” and get generic feedback about style and syntax. Nothing about the business logic, the security considerations, the HIPAA implications.

“The tool is useless,” Kevin complained to Edward. “It doesn’t know anything about our codebase.”

“Have you told it about our codebase?”

“What do you mean?”

“The AI doesn’t know we’re a healthcare company. It doesn’t know about HIPAA. It doesn’t know what the medication tracking feature is supposed to do.” Edward paused. “Have you given it that context?”

Kevin was quiet. “I just… asked it to review the code.”

“That’s the same thing your junior engineers do. They drop code in your queue without explanation, and you have to figure out what they were trying to accomplish.”

“So I have to explain things to the AI like I’m onboarding a new hire?”

“Exactly like that. Except the AI can actually remember what you told it.”

This was the breakthrough. Once Kevin started treating the AI like a very fast but very ignorant junior engineer, one who needed explicit context about every review, the results improved dramatically.

“The AI catches the obvious stuff,” Kevin reported after the second week. “Style violations. Common security patterns. Syntax issues. That’s maybe three hours of work I don’t have to do.”

“And?”

“And I’m finding things I never had time to look for before. Logic errors. Architectural problems. The stuff that actually matters.” He paused. “But here’s the weird thing. Writing the context for the AI is making me better at onboarding new people. I’m finally articulating things I’ve just… known. For years.”

Edward nodded. This was exactly what he’d seen in the value stream mapping session. The AI wasn’t just a tool; it was forcing engineers to externalize knowledge that had been locked in their heads. The same engineers who couldn’t explain their review process to Edward could now explain it to an AI. And in doing so, they were making that knowledge visible, transferable, improvable.

“That’s the real unlock,” Edward said. “The AI doesn’t just do the work. It forces you to understand your own work well enough to explain it.”

Kevin was quiet for a moment. “I still don’t trust it. But I’m starting to see why this might matter.”

Week 4: AI-generated test scripts. The QA team was nervous, but the first batch of scripts caught two bugs the manual scripts had missed.

“The AI doesn’t understand our business logic,” the QA lead said. “It generates tests based on the code, not based on what the code should do. But it’s finding edge cases we never thought to test.”

Week 5: Edward called a meeting that would reshape how Riverton built software.

“We’re keeping the gates that matter,” he announced to the leadership team. “HIPAA compliance. Patient safety reviews. Anything that protects patients stays. But the gates that exist because someone got nervous five years ago? Those are coming down.”

He drew two columns on the whiteboard. “Important gates” on the left. “Waste gates” on the right.

“The approval queue that exists because someone deployed bad code in 2016? Waste. The three-person sign-off for production changes when one person would do? Waste. The Friday agile coach meeting that adds two weeks to every story? Waste.”

“What happens to the people running those gates?” Sandra Williams asked. The CFO’s question, always.

“That’s the key.” Edward turned to face her. “Most companies attack EBITDA by firing people. Cut the waste, cut the headcount. I’m proposing something different. We take the people who’ve been causing wait time and reassign them to actually adding value.”

“Adding value how?”

“The QA team has twenty people doing manual regression testing. That’s waste. But those twenty people know our system better than anyone. They know every edge case, every failure mode, every bug that’s ever shipped.” Edward pointed to the value stream map. “What if they stopped running tests and started building features? What if their knowledge of what breaks became knowledge of how to build things that don’t break?”

Rachel jumped in. “Lisa Martinez has been doing QA for eight years. She’s been asking to learn development the whole time. She knows more about our system’s failure modes than most of our senior engineers. If she transitions to development, she’s not starting from zero. She’s bringing eight years of context.”

“Same with Security,” Edward continued. “Ben, your team spends 60% of their time on routine code audits. What if they built tooling that automated the routine stuff? Then they could focus on the hard problems, the ones that actually need human judgment. And we’d have capacity freed up for new products.”

Ben Adler was skeptical. “You’re talking about a fundamental change to how we operate.”

“I’m talking about taking people who are currently creating wait time and turning them into people who create value.” Edward met his eyes. “The important gates stay. Patient safety, HIPAA, anything with real consequences. But the gates we built out of fear? Those go. And the people manning them become builders.”

Sandra was doing math in her head. “If this works, you’re not cutting costs. You’re increasing output with the same headcount.”

“Exactly. The CFO playbook says cut waste by cutting people. But waste isn’t people. Waste is how we’re using people. Those twenty QA engineers aren’t the problem. Having them click through the same screens a thousand times instead of building things, that’s the problem.”

“And if some of them can’t make the transition?”

“Some won’t. That’s true of any change this big. But I’d rather have fifteen people building features than twenty people creating wait time.” Edward paused. “And honestly? Most of them are going to thrive. They’ve been bored for years. Running the same tests, manning the same gates, watching engineers ship things while they waited. This gives them a chance to build.”

Ben Adler was quiet for a moment. Then: “The important gates stay?”

“The important gates stay. Your expertise on the hard security problems, that’s irreplaceable. I’m not asking you to give that up. I’m asking you to stop wasting your team’s talent on things a tool could catch.”

“You know,” Edward said as the meeting broke up, “in my experience, no one can ever make security people happy.”

Ben raised an eyebrow.

“Give security more budget, they want more headcount. Give them more headcount, they want more authority. Give them more authority, they want everyone to stop shipping code entirely.” Edward grinned. “The only thing that actually makes security people happy is when engineers start thinking about security themselves. Then security becomes a partnership instead of a police force.”

Ben laughed despite himself. “That’s actually true.”

“So let’s make your team happy. Build the tools. Train the engineers. Keep the gates that matter. Tear down the ones that don’t.”

Week 6: Edward formed three focused feature teams for the medication tracking feature. Each team had everything they needed: developers, a former QA engineer transitioning to development, access to security tooling, and authority to make decisions without waiting for committee approvals.

The people who used to create wait time were now creating value. The gates that mattered stayed. The gates that didn’t were gone.

Priya’s team started coding. Actually coding. Not waiting for approvals or environments or sign-offs. Coding.

Thursday, August 14, 2025 – 4:00 PM – Edward’s Office, Riverton Health Systems

The Infrastructure team pushed too fast.

They’d seen the results from Claims Processing, the automated provisioning, the streamlined approvals, and they wanted the same thing. But they skipped the value stream mapping. They deployed changes without testing them properly. They assumed the approach would work without understanding why it worked.

Thursday afternoon, the staging environment went down. Twelve hours of downtime. Three board members wanted to shut everything down.

Sandra Williams, the CFO, called Edward at home that night.

“The board is asking questions. They want to know if this is going to happen again.”

“It might,” Edward said honestly. “Process improvement has failures. The question is whether we learn from them.”

“That’s not going to satisfy the board.”

“Tell them this: the approach didn’t prevent this failure. It made the failure visible and learnable. Under the old system, this would have happened anyway. we just wouldn’t have known why. Now we do. The Infrastructure team skipped the value stream mapping. They won’t make that mistake again.”

Sandra was quiet for a long moment.

“I’ll back you,” she said finally. “But Edward, the next failure can’t be this visible.”

Friday, August 29, 2025 – 11:30 AM – Edward’s Office, Riverton Health Systems

Day 60.

The medication tracking feature was in code review. Halfway done. On track to ship by day 87.

Edward stood at his window, looking out at Biscayne Bay. Sixty days ago, he’d made the 90-day bet with David. Two months of proving the approach could work.

The value stream map was still on his wall. Thirteen weeks → four weeks. Eleven weeks of waiting → two weeks of waiting.

Only three of the eight improvements involved AI:
1. AI-assisted code review (Kevin’s queue)
2. AI-generated test scripts (QA bottleneck)
3. AI-assisted development (faster coding)

The other five were just removing waste:
1. Eliminated the Friday agile coach approval meeting
2. Automated environment provisioning
3. Updated HIPAA checklist
4. Removed unnecessary approval queue
5. Streamlined requirements sign-off

More than half the improvement had nothing to do with AI.

Rachel knocked on his door.

“The medication feature passed code review. Kevin signed off this morning.”

“How long did it take?”

“Two days. Including the AI pre-review.”

“What was it before?”

“Four days in the queue. Two days of review. Six days total.”

Edward nodded. “And the test scripts?”

“Generated and running. QA found two bugs already, both from edge cases we never would have tested manually.”

“So we’re on track?”

“Day 87. Maybe earlier.”

Edward turned from the window. “When I was at the Academy, my commanding officer had a phrase. ‘Know where you are before you decide where you’re going.’ Captain Drake said it before every operation. I must have heard it a hundred times.”

“What made you think of that?”

“Because that’s what we did. We started with the thing we were trying to ship. Not ‘adopt AI.’ Ship the medication feature. That was the outcome.” He paused. “Then we mapped where work actually waited. Eleven weeks. Two of them work. Nine of them waste nobody had questioned. That was reality, not the version on the PowerPoint.”

“And you fixed the bottlenecks.”

“Some of them. But first we had to figure out which constraints were real and which ones we’d invented. HIPAA review? Real. A three-week compliance checklist because someone got nervous in 2018? Invented. Once you see the difference, you know what to cut.” He turned back to the window. “Then we bet on ninety days and one feature. That’s it. Not a transformation roadmap. Just prove the approach works on something small enough to measure.”

Rachel smiled. “That’s not going to fit on a consulting slide.”

“Good. If it fit on a slide, it wouldn’t work.”

Thursday, September 25, 2025 – 6:00 AM – The Dock, Edward’s House on the Intracoastal

Six months since spring break now. Day 87. The problem had changed.

He wasn’t worried about Harold anymore. Wasn’t worried about becoming obsolete. Because he’d discovered something: the threat wasn’t AI. The threat was process debt. years of accumulated waste that made it impossible to ship the things that mattered.

AI was just one lever. Maybe it helped with three bottlenecks out of seven. But the other four had nothing to do with technology. They were just approval queues and outdated checklists and automation that had been on the backlog since 2019.

His phone buzzed. Text from Priya:

Feature passed final QA. Heading to compliance review Monday. We might beat day 87.

Edward smiled.

The medication tracking feature, the one that could save lives, the one that had been stuck for eighteen months, was going to ship. Not because of AI strategy. Not because of transformation roadmaps. Because they’d asked a simple question: what’s stopping us?

And then they’d fixed it.

Jennifer found him there around nine, carrying two mugs of coffee. His was black, hers had enough cream to make it barely coffee. Twenty years of marriage and she still couldn’t understand how he drank it that way.

“You’ve been out here since six,” she said, handing him a mug.

“I know.”

“The girls are asking when you’re coming in. Lily wants you to make the shrimp and grits.”

Edward smiled. His grandmother’s recipe, the one he’d learned in Savannah as a kid. Lily had requested it every Sunday since she was six. “Tell her twenty minutes.”

“I’ll tell her an hour. You always underestimate.” Jennifer sat down beside him on the dock, legs dangling over the edge the way they’d done in New York, back when they were young and the only waterfront they could afford was the East River. “You seem different lately. More energized. But also more… peaceful?”

“I figured something out.”

“The AI thing?”

“It’s not about AI. That’s what I figured out.” He sipped his coffee. “Everyone keeps asking ‘how do we adopt AI?’ That’s the wrong question. The right question is what are you trying to ship. For us it was the medication feature. That was the outcome. Everything else was noise.”

“And?”

“And once you know the outcome, you map where work actually waits. Eleven weeks from requirement to deployment. Two weeks of real work. Nine weeks of sitting in queues.” He laughed. “Nobody had ever traced a feature through the system. We all had theories about why things were slow. Nobody had the picture.”

Jennifer was quiet for a moment. Then: “That’s not very exciting.”

“No. It’s not. That’s why nobody does it.” He turned to look at her. “Then you have to be honest about which constraints are real. HIPAA compliance? Real. An approval queue that exists because someone got nervous in 2018? Not real. We’d been treating invented limits the same as actual ones for years.”

“So what did you do about it?”

“We bet on ninety days and one feature. Not a transformation roadmap. Not a twelve-month plan. Just ship the medication feature and prove the approach works.” He set down his coffee mug. “We went from eleven weeks to under five. AI handled three of the bottlenecks. The other four were just process bloat we’d accumulated over years.”

“That’s the one for hospitals? For drug interactions?”

“That’s the one. It could save lives, Jen. Real lives. And it was stuck because of process debt. Approvals that didn’t need to exist. Handoffs that added no value. A governance structure designed for a company we used to be, not the one we are now.”

They sat in silence for a while, watching the boats go by.

“So what’s next?” Jennifer asked.

“We scale it. Not AI. the approach. Value stream mapping. One governance board. Fix the bottlenecks, whatever they are.” He paused. “Johnny’s not going to like it.”

“Johnny’s the transformation guy?”

“Johnny thinks transformation means workshops and maturity models and Centers of Excellence. I’m proposing we just… fix things.”

Jennifer smiled. “That doesn’t sound like something you need permission for.”

“It’s not. That’s what I’m starting to realize.” Edward stood, picking up his fishing pole. “You don’t need a transformation strategy to ship faster. You need to know what you’re trying to build, see where the process is broken, and fix it. AI is just one tool in the toolkit.”

He walked back toward the house, Jennifer beside him.

The medication tracking feature would ship on day 87. Hospitals would start using it by July. And somewhere, eventually, a nurse would get an alert about a drug interaction that might have been missed.
The medication tracking feature would ship on day 87. Hospitals would start using it by October. And somewhere, eventually, a nurse would get an alert about a drug interaction that might have been missed.

That was the goal. Not AI adoption. Not digital transformation. Shipping the things that mattered.

Everything else was just process improvement.

Chapter 4: Protect the Trajectory

June – August 2025

MARCUS

Tuesday, June 3, 2025 – 8:00 AM – Axiom Headquarters, Conference Room A

Thirteen months to the bell.

Catherine Bell sat at the head of the table, running the S-1 preparation session with her usual precision. Marcus was to her right, Diana Reeves, CFO and former Whitfield partner, to her left. The investor relations team filled the remaining seats. The S-1 draft lay on the table, bleeding red ink from a hundred annotations.

“From the top,” Catherine said. “The thirty-second elevator pitch.”

Diana stood and delivered the pitch for the hundredth time that week:

“Axiom Logistics is the company that disrupted freight management. We brought cloud-native, API-first architecture to an industry still running on 1990s technology. Today, we have 12% of the market. That’s up from 8% two years ago. 1% growth every quarter, consistent and compounding. We have 240 million in ARR, growing 35% year-over-year. Our competitors are years behind. We’re not just winning; we’ve already won.”

Marcus nodded. “Good. Now sharpen the competitive differentiation. Pull up the landscape slide.”

The slide showed a two-by-two matrix: “Technology Modernity” on one axis, “Market Position” on the other. Axiom sat alone in the upper right quadrant. Meridian, TransGlobal, and FreightFlow clustered in the lower left.

“This is the story investors need to understand,” Marcus said. “Our competitors aren’t just behind; they’re structurally incapable of catching up. Meridian’s drivers still call into central dispatch on flip phones. TransGlobal just upgraded from BlackBerries last year, and half their fleet still doesn’t have real-time GPS. FreightFlow is running out of runway.” He shook his head. “We gave specialty chemical haulers tablets with live routing, hazmat compliance, and automatic ELD logging. Our competitors are still faxing bills of lading.”

“What about the AI question?” Diana asked. “Investors will ask on the roadshow. Every tech IPO gets asked about AI now.”

Catherine looked at Marcus. Technology questions were his domain.

“Keep it simple. No material changes to our development methodology are planned or anticipated during the registration period.” Marcus had practiced this language with their securities lawyers. “Our current SDLC has delivered eight consecutive quarters of predictable growth. We see no reason to introduce process variance prior to the offering.”

Diana nodded, making notes. “And if they push? Ask about Copilot, AI code generation, that space?”

“Then we pivot to the risk factors section. ‘We continuously evaluate emerging technologies as part of our normal R&D process. Any significant changes to development methodology would be disclosed in accordance with SEC requirements.’” Marcus spread his hands. “That’s it. No commitments, no timelines, no specifics that could become material omissions if we change course.”

“What about competitors using AI?” Diana pressed. “That’s a risk factor question.”

“Already covered. Page 47, competitive risks section: ‘Competitors may adopt new technologies that could reduce our competitive advantages.’ Standard language. Doesn’t commit us to anything, doesn’t admit we’re behind.” He’d spent three hours with outside counsel on that paragraph alone.

Catherine tapped the table. “This is exactly right. The S-1 is a legal document, not a strategy deck. We disclose risks, we don’t telegraph plans. No material changes means no material changes. Anyone who deviates from that language, in investor meetings, in press interviews, anywhere, creates 10b-5 liability for the entire executive team.”

She glanced around the table, her expression making clear this wasn’t a discussion.

“The quiet period starts when we file. From that moment until pricing, we say nothing that isn’t in the prospectus. Technology questions go to Marcus, and Marcus gives the approved answer. Business questions go to me. Nobody freelances. Nobody gets creative. We protect the registration.”

The team nodded. They believed it.

So did Marcus.

Friday, June 13, 2025 – 4:30 PM – Marcus’s Office

Prakash Venkataraman appeared in Marcus’s doorway, folder in hand. He’d built the original platform architecture, mentored half the engineering team, and had a reputation for seeing around corners. When Prakash closed the door behind him, never a good sign, Marcus gave him his full attention.

“I’ve been tracking Meridian,” Prakash said. “They’ve gone dark. No product announcements. No conference presence. Nothing.”

“They’re dying. We’ve known that for months.”

“That’s what our analysis says.” Prakash opened the folder. “But look at this. I pulled up their website yesterday. The copyright still says 2018. Their last press release is from fall 2022. ‘We’re back in the office post-COVID.’ That’s it. Nothing since.”

Marcus shrugged. “So they stopped updating their website. That’s what dying looks like.”

“Maybe. But look at their public filings. revenue flat, guidance flat, analyst coverage minimal. They’re a value stock trading at nine dollars with a four percent dividend. Nobody on Wall Street is paying attention.” Prakash spread papers across Marcus’s desk. “All I can tell you is they’re still renewing customer contracts. Still servicing accounts. Customers aren’t complaining. They’re just… quiet.”

“Quiet because they have nothing to say. No innovation, no roadmap, no future.” Marcus leaned back. Through his window, a container ship was passing. Maersk, blue hull. Twelve percent of the market. One percent growth every quarter. Respectable. Compounding. The numbers didn’t lie.

“Prakash, Meridian is a forty-year-old company trading at the same stock price they had a decade ago. Their website copyright is from 2018. They’re a value trap for retirees; they pay a dividend because they’ve given up on growth.” Marcus spread his hands. “And even if they wanted to rebuild, it took us four years to build what we have. Four years. You think they’re going to catch up while paying shareholders four percent a year?”

“I hope you’re right.”

“I am. We have a four-year head start. That’s our moat. Now let’s focus on our roadmap. Q2 features. Customer commitments. Execution.”

Prakash gathered his papers. At the door, he paused. “The companies that dismiss their competitors, the ones who think they’ve already won, they’re usually the ones who get surprised.”

“We’re not dismissing them. We’re prioritizing.”

“Is there a difference?”

He left before Marcus could answer.

Thursday, July 17, 2025 – 10:00 AM – Hartley Shipping Headquarters, Manhattan

Hartley Shipping was one of Axiom’s largest customers. 8% of ARR, with Axiom since the early days. Their CTO, Margaret Sullivan, had been a champion for Axiom in the industry for years.

The quarterly review started smoothly. Usage metrics, renewal terms. But then Margaret pulled up her list of feature requests, the same list she’d been maintaining for eighteen months.

“Marcus, I need to talk about the roadmap.”

“Of course. What’s on your mind?”

“AI-powered route optimization. You promised it Q4 2024. Then it slipped to Q1 2025. Now I’m hearing Q3 2025, maybe Q4.” She set down her pen. “Predictive capacity planning. same story. Natural language interface. same story. Everything we asked for keeps sliding further out.”

“We’re prioritizing stability ahead of the IPO. These features are coming. “

“When?” Margaret leaned forward. “We picked Axiom because you shipped fast. Now I’m looking at features that won’t land until 2026.”

“We’re still shipping. “

“Bug fixes. Minor enhancements.” She shook her head. “My team jokes you’ve gone ‘business casual.’ Four hundred engineers and the stuff we actually need is eighteen months out?”

Marcus didn’t have a good answer. Most of the capacity was going to IPO prep, compliance, board reporting.

“After the IPO, we’ll accelerate.”

“That’s what you said last quarter.”

Near the end, she brought up something that had been puzzling her.

“Have you noticed Meridian’s gone dark?”

Marcus nodded. “No product announcements. No conference presence. We think they’re winding down.”

“That’s the thing: they’re not winding down. They’re still renewing contracts, still servicing customers. They’re just quiet.” Margaret tilted her head. “Either they’re done, or something big is coming. And honestly, Marcus? If they shipped the features you keep promising us, I’d have to take a serious look.”

Marcus laughed, but it felt forced. “Maybe their last COBOL developer finally retired.”

Margaret didn’t laugh. “God, I hope you’re right. Because right now, you’re the only game in town. But if that changes…”

She didn’t finish the sentence. She didn’t have to.

They moved on to the renewal terms. The moment passed.

But on the flight back, Prakash’s words kept echoing in Marcus’s head.

Thursday, August 7, 2025 – 3:00 PM – Small Conference Room, Axiom Headquarters

Derek Huang had been acting strange for weeks, distracted, laptop closed more than open. Marcus assumed it was burnout. IPO prep was hard on everyone.

Their one-on-one clarified things.

“Our last three senior engineer hires declined,” Derek said. “All three wanted AI tools in their workflow.”

“But attrition is flat.”

“Because everyone’s holding equity and hoping.” Derek shook his head. “They’re not engaged. They’re waiting.”

“We’ll deal with retention after. “

“After the IPO. I know.” He walked to the window. “We used to push a release a day. Now it’s these big-bang releases every other week. I feel like I need to iron my jeans.”

Marcus tried to smile. “We’re about to go public. That’s not stagnation.”

“Then what are we building toward? I’ve been here four years. I don’t know what we’re trying to become anymore. Just what we’re protecting.”

Silence.

“Trust the process,” Marcus said. “After the IPO. “

“The world’s changing faster than our roadshow timeline.” Derek turned from the window. “I’m not quitting. But I’m asking you to hear me.”

He left.

Marcus sat alone in the conference room, staring at the empty chair. Through the window, container ships moved cargo in endless streams. Twelve percent of the market. One percent growth every quarter.

The numbers didn’t lie.

But neither did Derek.

Friday, August 15, 2025 – 6:45 PM – Axiom Parking Garage

Marcus caught Derek at his car.

“Hey. Got a minute?”

Derek leaned against the driver’s door, keys in hand. The parking garage was almost empty. Most of the engineers had left hours ago. This wasn’t the Axiom of three years ago, when people stayed late because they were excited, not because they were required.

“What’s up?”

Marcus hesitated. He’d rehearsed this conversation in his head a dozen times since their one-on-one. Never quite found the right words.

“I want to ask you something. And I need you to be honest with me.”

“I’m always honest with you.”

“Are we moving fast enough?”

Derek didn’t answer right away. The fluorescent lights hummed overhead. Somewhere in the distance, a car door slammed.

“No.”

“No?”

“No. We’re not.” Derek crossed his arms. “We’re protecting a trajectory instead of building a future. We’re optimizing for an IPO instead of optimizing for customers. We’re telling ourselves that eighteen months from now, everything will be different, but nothing about how we work is going to magically change because a bell rings on Wall Street.”

Marcus felt the words land. Heavier than he’d expected.

“What would you do? If you were me?”

“I’d map the process. Actually look at where work gets stuck. Figure out why features take fourteen weeks instead of four.” Derek shrugged. “I’d ask the question you just asked me, and then I’d actually do something with the answer.”

“That’s a lot of change. Right before an IPO.”

“Yeah. It is.” Derek unlocked his car. “But the alternative is pretending the problem doesn’t exist until it’s too late to fix it. That’s what legacy companies do. That’s what Meridian did.” He paused. “That’s what we’re becoming.”

He got in the car and drove away.

Marcus stood in the empty garage for a long time.

Derek was right. He knew Derek was right. The process was broken. The culture was drifting. The technical debt was accumulating faster than they were paying it down. Every warning sign he’d been taught to recognize, he was seeing at Axiom. And he was ignoring all of them.

He could fix this. He could call an all-hands meeting Monday morning. Announce a process review. Form a tiger team. Start mapping the value stream the way Edward was doing at Riverton.

He could. He should.

But the IPO was twelve months away. Clean quarters. No surprises. Catherine would ask questions. The board would get nervous. Blackwood would wonder if Marcus had lost confidence in the plan.

After the IPO, he told himself. After the IPO, I’ll fix everything Derek talked about. After the IPO, there’s time.

He walked to his car and drove home.

He didn’t mention the conversation to anyone.

Monday, September 1, 2025 – 9:00 AM – Axiom Headquarters

Another customer mentioned Meridian’s silence. Then another. Then a third.

Marcus filed each mention away and went back to the roadshow deck.

Ten months to the bell. The trajectory was protected.

Chapter 5: Prove It Works

October 2025 – February 2026

EDWARD

Tuesday, October 7, 2025 – 10:00 AM – Corner Coffee Shop, Brickell

The second wave of pilot selection.

Edward and Rachel had taken over a corner booth at the coffee shop on the first floor of their office building. It was nice to get out of the building to review the team applications. The morning light came through the windows, and the ambient noise gave them privacy without the sterile feeling of a conference room. Between them were twelve applications from engineering teams who wanted to participate in what Rachel had started calling “the pilot program.”

“Twelve teams,” Rachel said, spreading the applications across the table. “All of them want in. Only three got selected in the first round. The word is spreading.”

“What’s the criteria?”

“Same as before. They have to map their value stream first. Show us where work gets stuck. No vague answers, no aspirational thinking, no ‘we want to adopt AI because everyone else is.’ They need to know exactly what’s slowing them down.”

Edward picked up the first application. The Security team. Their stated outcome: “Reduce vulnerability response time from 14 days to 3 days.” Their value stream map showed a detailed flowchart: where reviews got stuck, which handoffs added delays, how much was actual work versus waiting.

“This one’s good,” he said.

“I agree. They’ve done the work. They know what’s blocking them.”

The second application was from the Mobile team. Their goal: “Improve mobile app quality using AI.” Their value stream: “Standard Agile with two-week sprints.”

“This one’s not ready,” Edward said.

Rachel nodded. “Too vague. ‘Improve quality’ doesn’t mean anything. Which quality? Measured how? And their process description is the PowerPoint version, not the real one. They haven’t actually mapped where work gets stuck.”

They went through all twelve. Four were ready. These teams had genuinely mapped their process and knew their bottlenecks. Three were close but needed more work on the value stream, which turned out to be the hardest part. Five weren’t ready at all. They wanted AI because AI was exciting, not because they had a specific bottleneck to fix.

Rachel set down two applications. “These two said they didn’t have time to create a value stream map.”

Edward chuckled. He pulled out his phone and drafted an email to their VPs. “Hi. Your team applied for the AI pilot program but said they don’t have four hours to map their value stream. I’d like to help. Can we talk about what’s consuming their time?”

He hit send.

“That’ll fix it,” he said, picking up his coffee.

Rachel laughed. “You’re terrible.”

“I’m curious. If a team doesn’t have four hours to understand their own process, that tells me something important about their process.” He shrugged. “Either they’re genuinely slammed and need help, or they’re not prioritizing this. Either way, the VP should know.”

By the time they finished their coffees, both VPs had replied. One apologized and said the team would have the value stream map by Friday. The other asked if Edward could meet with the team directly to help them find the time.

“You know what I am doing?” Edward said, watching Rachel stack the approved applications. “I’m using the AI vibes from the engineers to get my middle management to fix the process.”

“What do you mean?”

“Everyone wants AI tools. The engineers are excited about it. So I created this application process for deep AI investment, and now I’m measuring my leaders in a kind way.” He smiled. “The ones whose teams can map their value stream and articulate their bottlenecks? Those are the leaders who actually understand their operations. The ones who can’t? Now I know where to focus.”

Rachel raised an eyebrow. “So the AI pilot program is secretly a management assessment tool.”

“Not secretly. It’s both. And to be clear, I’d never block my ICs from using AI tools – do I want them to quit? Everyone gets the tools. That’s table stakes now.” He leaned back. “But the pilot program is about deep investment. Dedicated support. Process redesign. Training budgets. The teams that can articulate their bottlenecks get the extra resources. The ones that can’t?” He shrugged. “Their leaders get extra help from me.”

“Help.”

“Coaching. Mentorship. Whatever you want to call it.” He finished his coffee. “I’m not punishing anyone. I’m identifying where the organization needs development. Some leaders have their houses in order. Some have been hiding behind activity metrics for years. Now I know which is which.”

Rachel nodded. “AI is the carrot. Process improvement is the meal.”

“And leadership development is the side dish nobody ordered but everyone needs.”

“Here’s what I’m learning,” Edward said, setting down the last application. “The value stream mapping isn’t just a filter. It’s a forcing function. Teams that can’t map their process have problems they don’t know they have. The mapping surfaces the problems.”

“The Mobile team doesn’t know where their time goes. That’s why they can’t map it.”

“Exactly. And until they figure that out, no amount of AI is going to help them. They’d just be automating confusion.”

Rachel smiled. “Outcome before tools.”

“Outcome before tools.”

THE CRISIS

Thursday, October 16, 2025 – 6:47 AM – Edward’s Phone

Three weeks after the medication feature shipped.

Edward was making coffee when his phone exploded with notifications. Slack messages. Emails. A missed call from Rachel at 6:32 AM.

He called her back.

“We have a problem.” Rachel’s voice was tight. “St. Augustine Memorial. The medication tracking system.”

Edward’s stomach dropped. St. Augustine was one of their first pilot hospitals. The feature they’d shipped on Day 87. The proof that the approach could work.

“What happened?”

“A nurse accessed the system during a code blue. The medication reconciliation module locked up. Spinning wheel for eleven seconds. She had to abandon the system and do manual verification.” Rachel paused. “The patient was fine. But if she’d trusted the system and waited…”

“Eleven seconds during a code blue.”

“Eleven seconds. In a situation where every second matters.” Rachel’s voice cracked. “Edward, this is exactly what Johnny warned about. ‘When something goes wrong, and it will, remember I warned you.’“

Edward set down his coffee. His hands were steady, but his mind was racing. Forty-five days of work. The 90-day bet with the CEO. The board approval he’d fought for. All of it suddenly fragile.

“I’m coming in. Get the team together.”

Thursday, October 16, 2025 – 8:00 AM – Emergency War Room, Riverton Health Systems

The war room was silent except for the hum of laptop fans.

Edward looked at the faces around the table. Rachel. Priya Sharma, whose team had built the feature. Kevin Nakamura, who’d reviewed every line of code. Dr. Amira Patel from Compliance, looking pale.

“Walk me through what happened,” Edward said.

Priya pulled up the logs. “6:14 AM Eastern. Nurse Bridget Okafor at St. Augustine Memorial accessed the medication reconciliation screen for a patient in cardiac arrest. The system initiated a drug interaction check against 23 current medications. The query took 11.3 seconds to complete.”

“Why?”

“The HIPAA audit logging.” Priya’s voice was hollow. “When we streamlined the compliance review, we removed the three-week manual audit. We replaced it with automated logging. But the logging query wasn’t optimized for real-time access. It was designed for batch processing.”

“So we fixed one bottleneck and created another.”

“We didn’t test under load. Under normal conditions, the logging adds 200 milliseconds. Under code blue conditions, with multiple systems accessing the same patient record simultaneously, it compounds. The nurse hit a perfect storm.”

Edward closed his eyes. He’d pushed to streamline the compliance review. He’d celebrated when they cut three weeks from the process. He hadn’t asked what they were trading away.

“What’s the patient status?”

“Stable. Recovered.” Dr. Patel spoke up. “But the near-miss report is already filed. The hospital’s risk management team is asking questions. If this had gone differently…”

She didn’t finish the sentence. She didn’t need to.

Thursday, October 16, 2025 – 10:00 AM – Edward’s Office

Edward closed his door and sat alone.

The feature had shipped three weeks ago. The approach had been validated. And now, in its first real-world test, it had nearly failed at the worst possible moment.

He thought about what he would tell David Aldridge. What he would tell Sandra Williams. What he would tell the board.

The approach failed. The value stream mapping identified bottlenecks correctly. But we didn’t validate the fixes under real-world conditions. We optimized for speed and created a new risk.

His phone buzzed. Text from Jennifer.

Heard something went wrong. Are you okay?

He typed back: Not sure yet. Might have made a serious mistake.

You’ll figure it out. You always do.

He wished he shared her confidence.

Thursday, October 16, 2025 – 2:00 PM – CEO’s Office

David Aldridge listened without interrupting.

Edward laid out everything. The incident. The root cause. The near-miss. The risk that a patient could have been harmed because they’d moved too fast.

When Edward finished, David was quiet for a long moment.

“What do you want to do?”

“I want to pause the rollout to additional hospitals. Fix the logging issue. Re-validate under load conditions. Add a pre-flight checklist for any process change that touches patient-facing systems.”

“That sounds like the responsible thing to do.”

“It is. It means the expansion slows down. The board was expecting us to be in fifty hospitals by Q4. This could push that back months.”

David leaned back. “Edward, the 90-day bet was about proving an approach could work. It worked. The feature shipped. Does a bug in production mean the approach doesn’t work?”

“It means the approach has gaps. Gaps I didn’t see.”

“Then name the gap correctly,” David said. “You proved you could get a real feature out the door inside ninety days. Now you’re learning what it takes to harden it for production. Those are different proofs.”

“So now you see them. What are you going to do about it?”

Edward thought about Johnny Morrison. About the warnings he’d dismissed. About the arrogance of thinking he’d fixed problems that had defeated other transformation attempts.

“I’m going to add a step to the approach. Before any feature goes to additional hospitals, stress testing under production conditions. Not just does it work, but does it work under the worst conditions we can imagine?”

“That sounds like learning.”

“It’s learning that almost cost a patient’s life.”

“Almost.” David’s voice was firm. “Almost. The nurse caught it. The patient recovered. The system failed gracefully enough that manual backup was possible.” He leaned forward. “This is what scaling looks like, Edward. Not perfection. Learning. Fast learning. Learning from the first hospitals before we expand to fifty more.”

“Johnny would say I was reckless.”

“Johnny would say you were reckless because he’s risk-averse to the point of paralysis. You were aggressive. There’s a difference.” David paused. “The question isn’t whether you made a mistake. You did. The question is what you do next.”

Friday, October 17, 2025 – 9:00 AM – Engineering Floor

Edward gathered the team.

“I owe you an apology.”

The room went silent.

“I pushed to streamline the compliance review. I celebrated when we cut three weeks from the process. I didn’t ask hard enough questions about what we might be missing.” He looked around the room. “The logging issue was foreseeable. If we’d stress-tested under real conditions, we would have caught it. We didn’t, because I was too focused on shipping fast.”

Priya spoke up. “We all missed it. The code review didn’t catch it. QA didn’t catch it. It’s not just on you.”

“The approach is on me. The culture that said move fast, we’ll fix it later. That’s on me.” Edward walked to the whiteboard. “Here’s what changes.”

He wrote: STRESS TESTING REQUIREMENT

“Every process change that touches patient-facing systems gets stress-tested before deployment. Not synthetic load tests. Realistic scenarios. Code blues. Multi-system access. Edge cases we can imagine and edge cases we can’t.”

He wrote: PRE-FLIGHT CHECKLIST

“Before any value stream optimization ships, we answer three questions: What could go wrong under pressure? What’s our manual fallback? Have we tested the fallback?”

He wrote: NEAR-MISS REVIEWS

“Every near-miss gets a full retrospective. Not to assign blame. To find the gaps in our thinking.”

Kevin Nakamura raised his hand. “This is going to slow down the expansion.”

“Yes. It will.” Edward met his eyes. “We might not hit fifty hospitals by Q4. But every hospital we do add will be safe.” He paused. “I’d rather explain a slower rollout to the board than explain a patient death to a family.”

The room was quiet.

“Questions?”

Dr. Kapur spoke up. “What do we tell St. Augustine?”

“The truth. We identified a performance issue during their pilot. We’re fixing it. We’re implementing additional safeguards. We’re grateful the nurse followed protocol and used manual backup.”

“They might pull out of the pilot.”

“They might. That’s their right.” Edward’s voice was steady. “But I’d rather lose a pilot hospital than lose their trust.”

Friday, October 17, 2025 – 4:00 PM – Phone Call with St. Augustine

The call with St. Augustine Memorial’s CIO, Dr. Marcus Greene, lasted forty-five minutes.

Edward explained everything. The incident. The root cause. The fix. The new safeguards.

Dr. Greene listened, asked questions, and was silent for a long moment.

“Most vendors would have buried this,” he said finally. “Blamed the nurse. Called it user error. Quietly patched it and hoped nobody noticed.”

“That’s not how we operate.”

“I can see that.” Dr. Greene paused. “We’re staying in the pilot. But I have conditions.”

“Name them.”

“I want weekly updates on the fix. I want to review the stress testing protocol before you redeploy. And I want you to present this incident at our patient safety committee. Not to shame you. To show our staff what good vendor behavior looks like.”

Edward closed his eyes for half a second. “Done. All of it.”

“One more thing. The nurse, Bridget Okafor. She’s been worried she’ll get blamed for ‘not trusting the system.’ I want you to send her a personal note thanking her for following protocol. For doing the manual backup instead of waiting for the screen to load.”

“I’ll do it today.”

“Good.” Dr. Greene’s voice warmed slightly. “Most CIOs in my position would have pulled out. Most vendors in your position would have lawyered up. We’re both choosing to do this differently. Let’s see if it works.”

Saturday, October 18, 2025 – 6:00 AM – The Dock, Edward’s House

Edward sat on his dock in the pre-dawn darkness, coffee in hand, watching the first light touch the water.

The crisis had been close. Closer than he wanted to admit. A patient could have died because he’d been too focused on shipping, too confident in his approach, too eager to scale.

But the patient hadn’t died. The nurse had followed protocol. The system had failed in a way that allowed recovery.

Learning that almost cost a patient’s life.

Almost. The word hung in the air.

He thought about what Dr. Greene had said. Most vendors would have buried this. Most CTOs would have too. Blamed the team. Hidden the report. Moved on without examining their own role in the failure.

He’d been tempted. For about thirty seconds in that war room, he’d been tempted to point at the code, at the logging design, at anything except his own push to ship faster than was safe.

But he hadn’t. And that choice, the choice to own it publicly, to apologize, to change the approach, felt like the most important decision he’d made in months.

His phone buzzed. Text from Priya.

Stress testing framework ready for review. Also, Bridget Okafor at St. Augustine sent a message. She said your note made her cry. The good kind.

Edward smiled in the darkness.

The expansion would be slower now. But it would be safer.

And he’d learned something that all the value stream mapping in the world couldn’t teach: The approach doesn’t prevent failure. It makes failure visible. And what you do when failure is visible, that’s the real test.

Monday, October 20, 2025 – 10:00 AM – Riverton Boardroom

Johnny Morrison had called an emergency session of the Technology Steering Committee. Except the Technology Steering Committee no longer existed. Edward had dissolved it months ago.

So Johnny went to the board instead.

Edward found out about the meeting from Rachel, who’d heard about it from Maria Santos in Legal. By the time he reached the boardroom, Johnny was already presenting.

“The incident at St. Augustine represents exactly the kind of risk I’ve been warning about.” Johnny stood at the head of the table, a slide deck open on the screen behind him. Victoria Hale, the independent director, was present, along with David Aldridge and Sandra Williams. “Edward dissolved governance structures that existed for a reason. He pushed changes without proper oversight. And now we have a near-miss that could have killed a patient.”

Edward took a seat at the far end of the table. He didn’t interrupt.

“I’m not saying Edward’s approach is wrong in theory,” Johnny continued. “But the execution has been reckless. Moving fast is one thing. Moving fast without adequate safeguards is something else entirely.”

“What are you proposing?” Victoria asked.

“Pause the pilot program. Reinstate the governance committees. Create a proper review process before we make any more changes to patient-facing systems.”

“And the 90-day bet?”

“The 90-day bet was always unrealistic. What happened at St. Augustine proves it.” Johnny looked at Edward. “I’m not trying to destroy what you’re building. I’m trying to make sure we don’t destroy ourselves in the process.”

Victoria turned to Edward. “You’ve heard the concerns. What’s your response?”

Edward took a breath. He’d been expecting something like this ever since the St. Augustine incident. Johnny had legitimate concerns. The question was whether the response was proportionate.

“Johnny’s right that the incident at St. Augustine was serious. A patient could have been harmed. That’s unacceptable.” Edward stood and walked to the screen. “But the incident also proved something important: the system failed in a way that allowed recovery. The nurse followed protocol. The patient was fine. The near-miss process worked.”

“You’re saying the failure was acceptable because nothing bad actually happened?”

“I’m saying the failure was visible. That’s different from the old approach, where failures were hidden in process complexity until they became catastrophic.” Edward pulled up his own data. “Under the old governance structure, we had three patient-facing incidents last year. Two of them weren’t discovered until customer audits found the problems. One took four months to resolve because nobody could figure out which committee owned the decision.”

“And under your approach?”

“One incident. Discovered immediately. Root cause identified within hours. Fix deployed within a week. The nurse who caught the problem received a personal thank-you for following protocol.” Edward looked at Johnny. “The old governance didn’t prevent problems. It hid them. My approach doesn’t prevent problems either. But it makes them visible. And visibility is how you actually improve.”

The room was quiet.

Victoria leaned back. “I’m going to ask a direct question. Should we pause Edward’s pilot program?”

Johnny spoke first. “Yes. The risk is too high.”

David Aldridge spoke next. “No. The incident was handled well. The learning was real. Pausing now sends the wrong message.”

Sandra Williams hesitated. “I want to say yes. The CFO in me hates uncontrolled experiments. But…” She looked at Edward. “The old committees weren’t preventing anything. They were just generating paperwork. If Edward’s approach actually works, it’s worth the discomfort.”

Victoria nodded. “Then we continue. But with conditions.” She turned to Edward. “Johnny joins the AI-SDLC Board. His concerns get heard, not dismissed. And any changes to patient-facing systems go through a pre-flight checklist that Johnny approves.”

Edward felt his jaw tighten. Johnny on the board meant friction on every decision. It meant slower approvals, more documentation, endless debates about acceptable risk.

But it also meant Johnny’s concerns were addressed. It meant the board had confidence in the approach. It meant the 90-day bet could continue.

“Agreed,” Edward said.

Johnny looked surprised. He’d expected a fight.

“Agreed,” Johnny said. “But I want it noted that I still have concerns about the pace of change.”

“Noted.” Victoria stood. “Meeting adjourned. Edward, Johnny, I expect you to work together. Not against each other.”

They filed out of the boardroom. In the hallway, Johnny caught Edward’s arm.

“That wasn’t what I expected.”

“What did you expect?”

“You to fight. To argue. To dismiss my concerns the way you’ve been dismissing them for months.”

Edward stopped walking. “Johnny, I’m not dismissing your concerns. I never was. What happened at MedFirst was real. The consequences were real. You carry that, and you should.” He paused. “But the lesson isn’t ‘move slow and nothing bad happens.’ The lesson is ‘make failures visible before they become catastrophic.’ We’re trying to learn the same thing. We’re just learning it differently.”

Johnny was quiet for a long moment.

“I still think you’re moving too fast.”

“I know. And I still think you’re moving too slow. That’s why we need each other.” Edward started walking again. “First AI-SDLC Board meeting is Thursday. I expect you there. With concerns, with questions, with pushback. That’s your job now.”

“And if I think a decision is wrong?”

“Then you say so. Loudly. That’s how this works.”

Johnny nodded. He uncrossed his arms.

“Thursday,” he said. “I’ll be there.”

Monday, October 20, 2025 – 11:00 AM – Edward’s Office

The Security team pilot was Edward’s proudest second-wave result. They’d mapped their value stream, found a 14-day vulnerability response cycle with 3 days of actual work and 11 days of approvals, and cut it to 3 days. Three of the gates they’d removed were escalation sign-offs that added nothing. One was a manual compliance review, where a member of the compliance team visually inspected each patch’s audit trail formatting before deployment.

Edward had approved cutting it. The gate added 2 days. The compliance reviewer was checking formatting, not content. The automated test suite verified that audit trails existed and contained the required fields. Redundant.

Two weeks later, Rachel walked into his office and closed the door.

“We have a HIPAA audit finding.”

Edward looked up. “From what?”

“Three patches deployed by the Security team since the manual review was removed. The automated tests confirmed the audit trails existed. But the formatting standard changed in a framework update six weeks ago. The new format uses different field separators. The automated tests check for field presence, not field format. The auditor flagged inconsistent formatting across the three patches.”

“How is that possible? The compliance reviewer was checking formatting?”

“Patricia Hendricks. She’s been doing the manual review since 2017. When the framework update changed the format, she noticed. She’d been silently correcting the output for eighteen months. Converting the new separators back to the standard format before sign-off.”

Edward stared at his desk. “Nobody told us she was doing that.”

“Nobody asked her what she was doing. The Security team asked what the gate was. The answer was ‘manual compliance review.’ They wrote ‘waste’ on the whiteboard and moved on.”

“Set up a meeting with Patricia.”

The meeting was short. Patricia Hendricks was a woman in her late fifties with reading glasses on a chain and a reputation for being the last person in the building on audit weeks. She wasn’t angry. She was tired.

“I tried to explain what I was checking when your team asked about my process,” Patricia said. “They heard ‘manual review’ and wrote it on the whiteboard as a bottleneck. Nobody asked what I was reviewing. Nobody asked why.” She folded her hands. “I’ve been catching format drift for eighteen months. It’s not glamorous work. It’s the kind of thing people assume is automated. It wasn’t.”

Edward restored the gate. He issued a formal correction to the three audit trails. He wrote the incident up for the AI-SDLC Board, with Johnny Morrison’s I-told-you-so visible in every line of the minutes.

Rachel found him at his desk afterward, staring at the whiteboard where the Security team’s value stream map was still taped.

“You assumed every gate you didn’t understand was waste,” she said. “Some of them were load-bearing.”

“The framework says separate real constraints from invented ones.”

“The framework doesn’t say you can tell the difference by looking at a whiteboard for twenty minutes. Patricia’s gate looked invented. It was load-bearing. The only way to know the difference was to ask her what she was actually doing, not what her process was called.”

Edward added a step to the methodology that afternoon. Before removing any constraint, map it to its origin. Interview the person who performs it. Test removal in a staging environment for one full cycle. Verify no downstream dependencies break. Then, and only then, declare it waste.

It wasn’t elegant. It slowed down the pilot teams. Johnny Morrison called it “the least Edward could do.” But it was honest. And it was the first time Edward had been wrong about something fundamental, not a technical error like St. Augustine but a judgment error about what mattered.

Wednesday, October 22, 2025 – 3:00 PM – Compliance Department, Third Floor

Rachel went back to see Patricia Hendricks. Not about the audit trail. That was fixed. She went because she’d noticed something during the meeting that Edward hadn’t.

Patricia’s team had its own bottleneck problem.

“Walk me through what happens when an engineering team requests a compliance review,” Rachel said. She pulled a chair up to Patricia’s desk and opened her notebook.

Patricia looked surprised. Nobody from the CTO’s office had ever asked her about her process. They asked about her output. They asked about her timelines. They never asked how the work actually moved.

“Engineer submits a review request through the portal,” Patricia started. “It goes into our shared inbox. I triage it within a few days, assign it to one of my three reviewers.”

“How long does the actual review take?”

“Two to three days. Depends on complexity.”

“And then?”

“Then it comes back to me for sign-off. I review the reviewer’s work, check for anything they missed.”

“How long does your sign-off take?”

“A day. Maybe two if I’m backed up.”

“And then?”

Patricia hesitated. “Then it goes to the department head for second sign-off. And then to the legal liaison for third sign-off.”

“How long do those take?”

“The department head signs off in about a week. The legal liaison, about the same.”

Rachel was writing. She looked up. “So from submission to approval. How long, total?”

Patricia counted on her fingers. “Five to seven weeks. Usually closer to seven.”

“And the actual review work?”

“Eight days. Maybe nine.”

Rachel set down her pen. “When was the triple sign-off added?”

Patricia leaned back. “2017. After the audit finding. We had a compliance gap in a patient records module. It wasn’t caught during review. The VP at the time added the department head sign-off for visibility. Then Legal wanted a look because of the HIPAA implications. Three sign-offs.”

“Do the department head and legal liaison read the reviews?”

Patricia was quiet for a moment. “The department head approves everything I send him. I’ve never seen him send one back. The legal liaison reads about one in ten. She told me once that she trusts my team and mostly skims for keywords.”

“So the review is real. The triple sign-off is theater.”

“The review is real. I catch real problems. My team catches real problems. The sign-off queue is where reviews go to wait for people who don’t read them.”

Rachel proposed a change. Keep Patricia’s review. Keep the reviewer’s review. Eliminate the triple sign-off queue. Replace it with a single approval from Patricia, with legal notified automatically on any review that flagged HIPAA-sensitive changes, and the department head receiving a weekly digest instead of blocking individual reviews.

Patricia stared at her. “That would cut our cycle from seven weeks to eight days.”

“Would anything break?”

“Nothing that matters. The department head doesn’t add value to individual reviews. He adds value to the quarterly summary I write for him anyway. And legal only needs to see the ones that touch patient data.”

“Then let’s try it.”

The compliance team implemented the change the following Monday. Within two weeks, engineering teams that had been waiting seven weeks for compliance sign-off were getting reviews back in eight days. The same quality. The same rigor. Patricia’s reviewers were doing the same work. The only thing that changed was the queue that nobody was reading.

Edward watched Rachel present the results at the next AI-SDLC Board meeting. No AI involved. No technology change. Pure process improvement applied to a non-engineering function.

“Half my pilot teams couldn’t do what Rachel just did,” he said afterward. “She asked the right question, mapped the real process, and fixed it without a single line of code. The compliance team, two weeks ago I nearly broke them by cutting a gate they needed. Rachel fixed them by cutting the gates they didn’t.”

Patricia Hendricks attended the following week’s board meeting as a guest. She brought her own value stream map, drawn on graph paper in pencil. She’d found two more bottlenecks in her own process without being asked.

Thursday, October 23, 2025 – 2:00 PM – Engineering Floor, Riverton Health Systems

The Kevin Nakamura conversation.

Priya Sharma, team lead for Claims Processing, had been sending increasingly urgent Slack messages. One of her senior code reviewers was threatening to quit. He thought the AI pilot was going to replace him.

Edward found Kevin in his cubicle, staring at his screen with the expression of someone contemplating a funeral.

“Mind if I sit?” Edward pulled up a chair without waiting for an answer.

Kevin was fifty-two, a fifteen-year veteran of code review who could spot a security vulnerability in his sleep. He’d been at Riverton longer than Edward had, and he’d earned the respect of every engineer who’d ever submitted code to his queue.

“I know why you’re here,” Kevin said, not looking away from his screen. “Priya told you I’m being difficult.”

“Priya told me you have concerns. I wanted to hear them directly.”

Kevin finally turned to face Edward. His expression was a mixture of anger and fear.

“I’ve been doing code review for fifteen years. Fifteen years of learning patterns, building intuition, understanding what makes code good or bad. And now you’re telling me a machine can do it?”

“That’s not what I’m telling you.”

“That’s what it sounds like. AI-assisted code review. What does that even mean? The AI does the review, and I assist? Is that the future?”

Edward leaned back in his chair. He’d been expecting this conversation, not necessarily with Kevin, but with someone. The fear was real. The fear was valid. Dismissing it would be a mistake.

“How much of your time goes to obvious stuff? Syntax, style violations, common patterns?”

Kevin shrugged. “Maybe forty percent.”

“And the hard stuff? Architecture, business logic, healthcare-specific problems?”

“The rest.”

“What if AI handled the forty? So you could focus on the sixty?”

Kevin was quiet. “You’re saying it’s a filter, not a replacement.”

“I’m saying the best code reviewer I know is still Kevin Nakamura. But Kevin with AI handling the routine stuff catches twice as many real problems.”

“And what do I do?”

“Teach it what good looks like for us. Not generic good. Riverton good. The AI knows code. You know healthcare.”

Kevin’s eyes narrowed. “You’re offering me a job teaching an AI?”

“I’m offering you a promotion.”

The anger in Kevin’s expression faded slightly, but not the skepticism. Edward could see him processing, calculating.

“I’d need to understand how it works,” Kevin said. “The AI. How it makes decisions. What it catches and what it misses.”

“That’s exactly what we need. Someone who can audit the AI’s work and identify the gaps.”

“And I’d still review code?”

“The hardest stuff. The problems only a human can solve.”

Kevin was quiet. “One week. If it’s as bad as I think, I reserve the right to say I told you so.”

“Fair.”

“And I veto anything that compromises quality. No questions.”

“That’s not a condition. That’s the point.”

“One week.”

Monday, November 3, 2025 – 9:00 AM – Engineering Floor, Riverton Health Systems

Kevin Nakamura was still skeptical.

Edward heard it from Priya first: Kevin was finding every flaw in the AI’s suggestions. He’d sent three emails in the first week documenting cases where the AI missed obvious problems. One email had fourteen screenshots.

“He’s not wrong,” Priya said. “The AI misses context. It doesn’t understand our business rules. But Kevin’s treating every mistake like proof the whole thing is broken.”

Edward found Kevin at his desk, surrounded by printed code snippets covered in red ink.

“You’ve been busy,” Edward said.

“Your AI approved a null pointer dereference on Thursday. It would have crashed in production.” Kevin pointed to a highlighted section. “It also suggested removing a validation check that’s required for HIPAA compliance. The AI has no idea what it’s looking at.”

“You caught both issues.”

“I caught them because I was looking. If this goes to production without me reviewing everything, you’ll have lawsuits.”

Edward sat down. This was the conversation he’d been expecting. “How many reviews did you do last week?”

Kevin checked his notes. “Sixty-three.”

“How many before the AI pilot?”

A pause. “Maybe forty.”

“So you did fifty percent more reviews. How much of that extra capacity came from not having to flag the obvious stuff?”

Kevin didn’t answer immediately. Edward could see him running the numbers.

“The AI caught thirty-two style violations I would have flagged. Nineteen common security patterns. Eight syntax issues.” Kevin’s voice was grudging. “That’s maybe three hours of work I didn’t have to do.”

“And you used that time to catch the null pointer and the HIPAA issue. Things the AI would have missed.”

“I would have caught those anyway.”

“Maybe. But you had more time to look. More time to think. The question isn’t whether the AI is perfect; it’s whether the combination of AI plus Kevin Nakamura produces better outcomes than Kevin Nakamura alone.”

Kevin was quiet for a long moment. Then he picked up one of his printed screenshots.

“The AI got this one wrong. Suggested refactoring a loop that would have broken the medication reconciliation logic.” He set it down. “But it also caught six issues I missed on first pass. Things I would have caught eventually, but didn’t on the first review.”

“So it’s not replacing you. It’s…”

“Making me slower at some things and faster at others.” Kevin’s expression was complicated, frustration mixed with something that might have been curiosity. “I still don’t trust it. But I’m not ready to shut it down yet.”

“That’s all I’m asking. Give it another two weeks. Keep documenting the failures. But also document what’s working.”

Kevin nodded. “Two weeks. Then we talk again.”

Wednesday, November 5, 2025 – 4:30 PM – Edward’s Office, Riverton Health Systems

Rachel closed the door behind her. Never a good sign.

“Kevin’s threatening to quit. For real this time.”

Edward looked up from his laptop. “What happened?”

“You happened.” Rachel sat down across from him, her expression careful. “He told Priya you’re pushing too hard. That you’re more interested in proving the pilot works than in whether it actually works.”

“That’s not fair. I’ve been listening to every concern he raises.”

“You’ve been answering every concern he raises. That’s different.” Rachel paused. “Edward, I warned you about this two weeks ago. Kevin doesn’t need answers. He needs to feel like his expertise matters. And every time you explain why the AI is actually helping, you’re telling him his fifteen years of experience are less important than your ninety-day experiment.”

Edward felt his jaw tighten. “So what am I supposed to do? Let him sabotage the pilot because his feelings are hurt?”

“His feelings aren’t hurt. His identity is threatened. There’s a difference.” Rachel leaned forward. “And frankly, you’re not listening to me either. I told you to give him space. You scheduled three check-ins in two weeks. I told you to let him document failures without commentary. You sent him a four-paragraph email explaining why each failure was actually a learning opportunity.”

“I was trying to help.”

“You were trying to convince. It’s not the same thing.”

Edward was quiet. The feedback stung because it was accurate.

“What do you suggest?”

“Back off. Completely. Let Kevin run the evaluation his way for the next two weeks. No check-ins unless he asks. No explanatory emails. No helpful suggestions.” Rachel stood. “And maybe apologize. Not for the pilot. For not listening when he told you what he needed.”

“And if he quits anyway?”

“Then you’ll have learned something about how not to manage change. Which is still more valuable than pretending you got it right.”

She left. Edward sat alone, replaying the last two weeks. Every conversation with Kevin. Every email. Every moment where he’d been so focused on proving the approach worked that he’d stopped asking whether Kevin was okay.

You’re becoming the thing you fired the consultants for being. Confident you have the answer. Not curious about whether you might be wrong.

He picked up his phone. Typed a message to Kevin.

Can we talk? Not about the pilot. About how I’ve been handling this. I think I owe you an apology.

The reply came an hour later.

Tomorrow. 8 AM. Coffee shop on Brickell. Not the office.

Thursday, November 6, 2025 – 8:00 AM – Coffee Shop, Brickell

Kevin was already there when Edward arrived. Two coffees on the table. The gesture said something.

“I ordered for you. Black, right?”

“Thanks.” Edward sat down. “I appreciate you meeting me.”

“I almost didn’t.” Kevin stirred his coffee, not looking up. “I had my resignation letter drafted. Was going to send it yesterday afternoon.”

“What stopped you?”

“Your text. The part about owing me an apology.” Kevin finally met his eyes. “In fifteen years, I’ve never had a CTO apologize to me. Not once. Not for anything.”

“Then I’m long overdue.” Edward took a breath. “I’ve been so focused on making this pilot work that I stopped asking whether I was making it work for you. I treated you like an obstacle instead of a partner. That was wrong.”

Kevin was quiet for a moment. “You know what the hardest part has been?”

“Tell me.”

“Not the AI. The AI is just a tool. I can learn to work with tools.” He set down his coffee. “The hardest part is feeling like my judgment doesn’t matter anymore. Like the decision’s already been made, and I’m just here to validate it.”

“That’s not what I intended.”

“I know. But intention and impact aren’t the same thing.” Kevin leaned back. “Here’s what I need. I need to run this evaluation my way. No check-ins. No helpful emails. Just me, doing what I do, and documenting what I find. And at the end, if I say it’s not ready, you listen. Really listen. Not ‘listen and then explain why I’m wrong.’“

“What if you’re right and it’s not ready?”

“Then we shut it down. Or we fix it. Or we try something else.” Kevin shrugged. “But the answer has to come from looking honestly at the data, not from deciding in advance what we want the answer to be.”

Edward recognized his own words being reflected back at him. The approach he’d been preaching to everyone else, applied to himself.

“Fair,” he said. “Two weeks. Your way. And whatever you find, I’ll listen. Really listen.”

“Okay then.” Kevin picked up his coffee. “And Edward?”

“Yeah?”

“Thank you. For actually hearing me this time.”

They finished their coffee. Talked about Kevin’s daughter’s wedding, about the Dolphins’ chances next season, about nothing related to AI or pilots or transformation. Just two people remembering they were more than their roles.

Walking back to the office, Edward called Rachel.

“You were right. I almost lost him.”

“I know.”

“How did you know?”

“Because I’ve watched you for six months. You’re good at asking questions about process. You’re terrible at asking questions about people.” She paused. “The consultants you fired? They had the same blind spot. All frameworks, no empathy. Don’t become them.”

“I’m trying not to.”

“Try harder.”

She hung up. Edward walked the rest of the way in silence, thinking about the difference between being right and being effective.

Friday, November 14, 2025 – 3:00 PM – Rachel’s Office, Riverton Health Systems

The early results came in through November.

Claims Processing saw 40% faster code review cycles in the first month. But the number that mattered more to Edward was the quality metric: production bug rate stayed flat. The AI wasn’t just making things faster; it was maintaining the standard Kevin Nakamura had spent fifteen years building.

Kevin himself had become something unexpected: the pilot’s most rigorous quality auditor. He still documented every AI failure, but now he also documented the successes. His weekly reports to Edward showed a system slowly earning his trust, one review at a time.

“It’s not perfect,” Kevin said during their third check-in. “But it’s getting better. And I’m catching things I never had time to look for before.”

It wasn’t a conversion. It was something more durable: a skeptic becoming a critical collaborator.

And then there was Priya Sharma’s “toil repayment” metric, the ratio of time saved on repetitive work to time reinvested in high-value work. Her team had moved from 60% toil to 35%, and that freed-up 25% was going straight into the backlog.

Into the medication tracking feature.

The one that had been sitting there for eighteen months while hospitals kept asking for it. The one that could flag potential drug interactions before discharge. The one Priya’s sister, a nurse, had told her about, a patient at her hospital who’d had a bad interaction because the discharge paperwork didn’t catch a conflict.

That feature was already live in three hospitals. Real people would be safer because Priya’s team had time to build what mattered.

Friday, November 21, 2025 – 2:00 PM – Engineering Floor

A month after the St. Augustine crisis, the expansion had resumed.

The stress testing framework was in place. Every hospital now went through a rigorous validation before going live. It added a week to each deployment, but the team understood why.

Edward found Kevin Nakamura at his desk, reviewing the latest batch of AI-generated code suggestions.

“How’s the new protocol working?” Edward asked.

Kevin looked up. “The stress testing caught two issues this week. Both would have caused problems in production.” He shrugged. “I still don’t love the AI. But I trust the process.”

“That’s all I’m asking.”

Kevin turned back to his screen. “Also, the feature is in seven hospitals now. One of the nurses at Tampa General sent a message to Priya. Said the system flagged a potential interaction she might have missed.”

Edward nodded. That was why they did this. Not the productivity metrics. Not the AI adoption rates. Real outcomes.

“Keep documenting everything,” he said. “The good and the bad.”

“Always do.”

Monday, November 24, 2025 – 10:00 AM – Riverton Health Systems

Provider Portal finished their process mapping and discovered something unexpected. Three of their review stages were redundant, holdovers from a compliance requirement that had been changed two years ago. They eliminated them before deploying any AI tools, cutting their delivery time by 30%.

Documentation reduced their turnaround from six days to three, without implementing a single new tool. Just by answering the third question honestly, they’d discovered inefficiencies nobody had noticed.

Rachel brought the results to Edward’s office on a Friday afternoon.

“The pattern is consistent,” she said, spreading the data across his desk. “Teams that map their value stream are seeing gains. Teams that can’t map it are getting stuck, but they’re getting stuck on problems they needed to address anyway.”

“The mapping is the intervention.”

“Exactly. The AI is accelerating what they already know how to do. But understanding the process is what surfaces what they need to know.”

Edward went through the numbers. They were good. Maybe too good. Good enough that people would start noticing.

“Sandra Williams wants a meeting,” he said. Sandra was Riverton’s CFO. a by-the-numbers finance executive who kept close tabs on anything that affected budget or risk.

“About the pilots?”

“About ‘unauthorized technology experimentation.’ Those were her words.” Edward smiled grimly. “The board asks her about AI strategy. She doesn’t have an answer. She hears rumors about pilots happening without board approval. She puts two and two together.”

“Are you worried?”

“I’m cautious.” He looked at the data again. “But I’m also holding a stack of results that are hard to argue with. If Sandra wants to talk about AI strategy, I can show her what works. Not theory, evidence.”

Wednesday, November 26, 2025 – 11:00 AM – Sandra Williams’s Office, Executive Floor

The Sandra Williams meeting.

Sandra’s office was on the executive floor, with windows overlooking Biscayne Bay. She kept it sparse: a desk, two chairs, a single framed photo of her MBA class at Northwestern. She was notoriously direct.

“Close the door,” she said when Edward arrived.

Edward closed it and sat down.

“The board meeting is next week,” Sandra said. “They’re going to ask about AI. They always ask about AI now. It’s the only thing anyone wants to talk about.” She folded her hands on her desk. “I need to know what you’re doing.”

“I’m running pilots. Small scale, low risk, documented results.”

“Without board approval.”

“Within my discretionary authority as CTO. Nothing I’ve done requires board approval.”

Sandra’s expression didn’t change. “That’s a fine line.”

“It’s a line I’ve been careful not to cross.” Edward leaned forward. “Sandra, let me show you what I have.”

He spent the next twenty minutes walking her through the results. Claims Processing, 40% faster, no quality degradation. Provider Portal, 30% improvement from process optimization alone. Documentation, turnaround cut in half. All of it documented, all of it measurable, all of it tied to a repeatable approach.

Sandra listened without interrupting. When Edward finished, she was quiet for a long moment.

“Value stream mapping,” she said finally.

“That’s where every team starts. Before we talk about tools, they have to map their actual process. Where does work wait? Where does it get stuck? What’s really slowing them down?”

“And the teams that can’t map it?”

“Don’t proceed. Not as punishment, but as protection. If you don’t know what’s blocking you, no amount of AI will help you.”

“What’s your goal, Edward? What’s Riverton trying to accomplish?”

Edward didn’t hesitate. “Build better software, faster and safer, so we can actually impact patient lives. We had a medication tracking feature sitting in the backlog for eighteen months. Hospitals kept asking for it. It could prevent drug interaction errors at discharge. Real patients, real safety.” He paused. “That feature is finally being built. Not because of AI. because our team has time to work on what matters now.”

Sandra raised an eyebrow. “The goal doesn’t mention AI at all.”

Edward laughed. “I know. Kind of ironic, isn’t it? I might be kissing my consulting career goodbye by admitting it.” He shrugged. “But that’s the point. The AI is just a means. The goal is patient lives.”

Sandra spread the data sheets across her desk. Her expression was unreadable.

“The board is going to ask what you’ve been doing,” she said. “They’re going to want to know why you didn’t ask permission.”

“What would you like me to tell them?”

Sandra looked up. For the first time, approval flickered across her face.

“Tell them you were proving it works. Tell them you have evidence, not theory. Tell them the process improvement is the innovation, not the AI.” She gathered the data sheets and stacked them neatly. “And then tell them you’re ready to scale.”

Edward blinked. “You’re supporting this?”

“I’m supporting results. These results.” She handed the stack back to Edward. “Don’t make me regret it.”

Monday, December 8, 2025 – 9:00 AM – CEO’s Office, Executive Floor

The Johnny Morrison confrontation.

Edward walked into the CEO’s office expecting a one-on-one with David Aldridge. Instead, Johnny Morrison was already seated, binder open, expression triumphant.

“Edward, please sit,” David said. His tone was neutral, carefully so. “Johnny has raised some concerns about your pilots.”

Johnny didn’t wait. “You’ve been running unauthorized AI experiments for four months. You dissolved the Architecture Review Board. You eliminated the Security Council. You created some kind of rogue governance structure without my approval.”

“The AI-SDLC Board. It’s not rogue. It’s faster.”

“You didn’t go through my transformation office. You didn’t follow the governance process I put in place.”

“I replaced it. One board. Twenty-four-hour decisions. Any engineer can ask for an answer and get one. That’s not undermining governance. That’s making it work.”

Johnny’s jaw tightened. “What’s not interpretation is that you’ve undermined a company-wide transformation initiative. My initiative. The one the board approved and funded.”

David held up a hand. “Let’s keep this constructive. Edward, what results are you seeing?”

Edward spent fifteen minutes walking through the data. Claims Processing, Provider Portal, Documentation. The toil repayment metrics. The medication tracking feature finally moving. He watched David’s expression shift from neutral to interested.

Johnny countered with his own presentation. Prompt coaching workshop attendance. AI Readiness Assessment completion rates. Center of Excellence membership growth.

“These are participation metrics,” Edward said. “Not outcome metrics. How many features shipped faster? How many bugs prevented? What’s the actual impact on the business?”

Johnny’s face reddened. “We’re building organizational capability. That takes time. You can’t measure transformation in weeks.”

“You can if you’re doing it right. My pilots have been running for four months. Johnny’s program has been running for eight. I have outcome data. He has attendance sheets.”

David was quiet for a long moment. Then he turned to Johnny.

“Johnny, I appreciate what you’ve built. The governance is important. But Edward’s raising a fair question. Where are the outcomes?”

“The outcomes are coming. We need to complete the assessment phase before. “

“Your assessment phase started eight months ago. Edward’s pilots started four months ago. He’s shipping results. What are you shipping?”

Johnny looked like he’d been slapped.

“David, you can’t compare. “

“I can. I have to. The board is going to ask me about AI strategy next week. I can show them Edward’s results or your attendance metrics. Which one do you think they want to see?”

The meeting ended with David asking both of them to prepare board presentations. But Edward could see the writing on the wall. Johnny’s $400,000 program had eight months of workshops and zero measurable outcomes. Edward’s $50,000 pilots had four months of experiments and a 40% improvement in delivery time.

The data spoke for itself.

Wednesday, December 24, 2025 – 2:00 PM – CEO’s Office, Executive Floor

The reassignment meeting.

Edward walked in expecting a debrief. Instead, David Aldridge was seated with Johnny Morrison on one side and the CHRO on the other.

“Gentlemen,” David began, “the board has reviewed both approaches to AI transformation. They’ve made a decision.”

Johnny straightened in his chair, confident.

“Effective immediately, all AI initiatives, pilots, governance, and strategy, will report to the CTO. Johnny, your transformation office will be reassigned under Edward’s organization.”

The silence lasted three seconds. Then Johnny exploded.

“You’re putting me under the CTO?” His voice cracked with disbelief. “I was brought in to lead transformation. I have a direct line to the board.”

“You had a direct line,” David said. “The board wants results. Edward is producing results. This is about alignment, not demotion.”

“Alignment?” Johnny stood up, face red. “I’ve given PowerPoint decks to half the Fortune 500. I’ve led transformations at companies three times this size. And you’re telling me to report to someone who’s been running unauthorized experiments in a back room?”

Edward stayed silent. There was nothing to say.

“This is a mistake,” Johnny continued. “You can’t just let engineers run wild with these tools. There needs to be governance. There needs to be control. When this falls apart, and it will fall apart, you’ll regret this.”

David stood. “Johnny, I think you should take some time to consider your options.”

“My options?” Johnny laughed bitterly. “My option is to watch someone with no transformation experience dismantle everything I built. My option is to explain to my network why I’m suddenly reporting to the CTO instead of the CEO. My option is to pretend this isn’t a humiliation.”

“That’s not what this is. “

“That’s exactly what this is.” Johnny gathered his binder, the same 52-page AI Readiness Assessment he’d been carrying for eight months. “I’ve given PowerPoint decks to half the Fortune 500. I’ve been in rooms you’ll never see. And this is how you treat me? You’ll regret this. All of you.”

He walked out. The door slammed behind him.

David turned to Edward. “I’m sorry you had to see that.”

“He’s not wrong about the need for governance.”

“He’s not. But he’s wrong about what governance means.” David rubbed his temples. “HR will handle the transition. I expect his resignation by end of week.”

Friday, January 2, 2026 – 10:00 AM – HR Conference Room

Johnny Morrison’s resignation was formalized that morning.

Edward wasn’t in the room when it happened, but Rachel told him later. The severance package was generous; the CEO didn’t want a lawsuit or a viral post about “toxic leadership.” Johnny took the money and left quietly.

His parting words, delivered through the HR director: “You can’t just let engineers run wild with these tools. There needs to be governance. There needs to be control. When something goes wrong, and it will, remember I warned you.”

Edward thought about that for a long time. Johnny wasn’t wrong about the need for governance. He was wrong about what governance meant.

Johnny’s version of governance was stopping everything until a perfect plan existed. Edward’s version was understanding what was already happening and building guardrails around reality.

They’d both wanted top-down change. They’d both wanted control. They’d just had fundamentally different ideas about how to get there.

Johnny wanted to stop the flood. Edward wanted to build channels for the water.

The flood always wins.

But Johnny’s warning stayed with Edward: When something goes wrong, and it will, remember I warned you. The man had seen transformation failures up close. He’d watched careers end and companies bleed. His solution was wrong. You can’t stop technological change by banning it. But his fear wasn’t irrational.

Edward made a note to himself: Don’t let winning make you forget what Johnny got right. Ungoverned experimentation kills. Governance has to be real, not just a box to check.

Thursday, January 8, 2026 – 2:00 PM – Riverton Boardroom

The board meeting went better than Edward expected.

He presented the pilot results with Sandra standing beside him, a visual signal that Finance was on board. He walked them through the approach, the selection criteria, the early wins. He showed them Kevin Nakamura’s transformation from skeptic to champion. He showed them the medication feature, shipped in 87 days after sitting stuck for 18 months.

“This isn’t a technology initiative,” he concluded. “It’s a process improvement initiative. The AI accelerates some bottlenecks. But most of what we fixed had nothing to do with AI. We just finally looked at where work was getting stuck and fixed it.”

The questions were skeptical but not hostile. How do we scale? What are the risks? What happens when something goes wrong?

Edward had answers for all of them. Not because he’d planned for every scenario, but because he’d done the work. He’d lived through the Kevin Nakamura conversation. He’d seen the Documentation team eliminate redundant processes. He’d watched Provider Portal discover problems they didn’t know they had.

By the end of the meeting, he had approval to expand. Six more teams in Q3. A dedicated budget line. A mandate to document the approach for enterprise-wide adoption.

Walking back to his office, Edward loosened his tie. He pulled up the medication tracking dashboard and watched the numbers tick.

The medication feature was live. Priya’s sister was using it. Nurses across the country would be using it soon. Real patients, safer because they’d finally asked: what’s stopping us from shipping?

Monday, January 12, 2026 – 10:00 AM – Infrastructure Team War Room

The Infrastructure team’s pilot failed.

Edward found out from Rachel, who found out from the team lead, who had spent the weekend watching their AI-assisted deployment pipeline corrupt three staging environments.

“They mapped their value stream,” Rachel said, standing in Edward’s doorway. “Their goal was clear: faster deployments with fewer rollbacks. Their bottlenecks were documented. They knew where work got stuck.”

“So what happened?”

“They skipped the validation step. The approach was to pilot small, gather data, iterate. They got excited about early results and pushed to production infrastructure too fast.” Rachel set an incident report on his desk. “Twelve hours of downtime on the staging systems. The CFO already knows.”

Edward felt his stomach drop. This was exactly what Johnny had warned about. When something goes wrong, and it will, remember I warned you.

The next three days were damage control. Meetings with Sandra Williams. A presentation to the CEO explaining what happened and why. A retrospective with the Infrastructure team that revealed the real problem: the team lead had been so eager to show results that he’d ignored the “start small” guidance.

“The mapping worked,” Edward told Sandra. “They knew what they were trying to accomplish. But knowing the bottlenecks doesn’t prevent human error. It doesn’t prevent people from getting overconfident.”

“So the approach failed.”

“The approach surfaced what went wrong. Without it, we’d still be guessing.” Edward pulled up the incident timeline. “Look, they documented everything. The moment they deviated from the pilot parameters, it’s visible. We can learn from this.”

Sandra flipped a page. “The board isn’t going to see it that way.”

“Then help me frame it correctly. This is proof that the approach works, not because it prevents all failures, but because it makes failures visible and learnable.”

The emergency board update happened that Friday. Edward presented the failure alongside the successes, full transparency, no spin. Three board members pushed back hard. One suggested shutting down the pilots entirely.

But Sandra surprised him.

“Every transformation has setbacks,” she said. “The question isn’t whether we have failures; it’s whether we learn from them. Edward’s approach didn’t prevent this incident. But it did make the incident understandable. That’s more than most transformation programs achieve.”

The pilots continued. But Edward went home that weekend knowing the easy wins were over. Now came the hard part: scaling something that could fail, with real consequences, and learning fast enough to stay ahead of the failures.

He sat on his dock that Saturday night. 5 AM, his usual time now, notebook in hand, and wrote: The approach doesn’t prevent failure. It makes failure visible. That’s the difference between transformation theater and actual process improvement.

Wednesday, January 14, 2026 – 3:00 PM – Analytics Team Review

The Analytics team’s pilot results came in that week. Not a failure. Not a success. Just… underwhelming.

Rachel presented the numbers in Edward’s office. “They mapped their value stream. Goal was clear: faster report generation for hospital administrators. They identified the bottlenecks. Implemented AI-assisted data analysis.”

“And?”

“Twelve percent improvement. Cycle time down from eight days to seven.”

Edward read the report. The Infrastructure team had been a disaster. Kevin’s team had been a triumph. But this was something harder to categorize: a team that had done everything right and gotten mediocre results.

“What happened?”

“Nothing happened. They just… didn’t have that much waste to remove.” Rachel set down the report. “Their process was already pretty good. The bottlenecks they found were real, but small. AI helped with some tasks, but the gains were incremental.”

“So the approach failed?”

“The approach worked perfectly. It just revealed that this team didn’t have a dramatic transformation waiting to happen.” Rachel paused. “Not every team is sitting on eighteen months of stuck features. Some teams are just… okay. And ‘okay’ doesn’t become ‘amazing’ just because you map the value stream.”

Edward thought about this for a long time after Rachel left. The medication feature had been a home run precisely because so much waste had accumulated. Kevin’s team had been a success because years of dysfunction had created massive improvement potential.

But the Analytics team was a reminder: process improvement only finds what’s there to find. If a team is already reasonably efficient, the gains will be reasonable, not revolutionary.

Not every transformation is dramatic, he wrote that night. Sometimes you do everything right and get 12%. That’s still 12%. But it won’t make anyone’s keynote speech.

Thursday, January 15, 2026 – 11:00 AM – Conference Room D, Riverton Health Systems

The Billing Integration team tried the approach on their own.

Rachel brought Edward the aftermath. The team lead, a senior manager named Darren Foss, had attended one of the pilot showcases and decided his team could run their own value stream mapping session. No trained facilitator. No guidance from Edward’s team. Just the template and the confidence that came from watching someone else make it look easy.

The result was a three-hour argument about whose process was worse, a value stream map that bore no resemblance to what actually happened, and two competing proposals that contradicted each other. Darren had called Rachel afterward, frustrated.

“He said they mapped the same process twice and got completely different results,” Rachel told Edward. “Then the team lead from Mobile saw what Billing was doing, took the template, and modified it. Now they have their own version that doesn’t match anyone else’s. When they hand off to App Dev, the documentation doesn’t align.”

“How many teams are trying this without us?”

“At least four. Maybe more.” Rachel set down her coffee. “The pilot results are spreading. Teams hear about Claims Processing being 40% faster and they want in. But they’re copying the artifact—the template, the workshop format—without understanding the thinking behind it.”

“So the methodology is fragmenting.”

“It’s not fragmenting. It’s cargo culting. They’re going through the motions because the motions look simple. Map the stream, find the waste, fix it. But without someone who understands the approach in the room, they end up mapping symptoms instead of root causes, or they identify bottlenecks they have no authority to fix, or they just redraw the existing process and call it done.”

Edward thought about this for a long time. The medication feature had worked because he’d been in the room. Claims Processing worked because he’d been in the room. Every success story had one common factor, and it wasn’t the methodology.

It was him.

Monday, January 12, 2026 – 2:00 PM – Post-Board Debrief, Edward’s Office

An industry analyst named Rebecca Harmon had been observing the board meeting as part of a healthcare IT benchmarking study. She caught Edward in the hallway afterward.

“Impressive results,” she said, falling into step beside him. “But I have to be honest. I’m skeptical.”

“Most people are. What’s your concern?”

“Value stream mapping. Process improvement. Looking at where work gets stuck.” She shook her head. “This is elementary, Edward. Every Lean Six Sigma workshop teaches this. Every DevOps maturity model includes it. I’ve seen a hundred companies do exactly what you’re describing.”

“And?”

“And most of them fail. Not because the approach is wrong, but because organizations can’t sustain simple practices.” Rebecca stopped walking. “So what makes you different? What makes Riverton succeed where everyone else has failed?”

Edward thought about the question. It was a fair one.

“Maybe nothing makes us different,” he said. “Maybe we’ll fail too. But here’s what I’ve learned: the reason consultants sell complex frameworks isn’t that transformation is complicated. It’s that doing simple things consistently is hard. The framework is a crutch for discipline.”

“You’re saying the entire transformation industry exists because organizations lack discipline?”

“I’m saying the transformation industry has an incentive to make simple things seem impossible without expensive help. ‘Map your value stream and fix what’s broken’ doesn’t justify a $5 million consulting engagement. ‘Implement our proprietary 36-month AI Readiness Framework’ does.”

Rebecca smiled slightly. “That’s a cynical view of my industry.”

“It’s an honest one. Look at Johnny Morrison. He had eight months and $400,000 for workshops about AI readiness. Zero features shipped faster. We had four months and $50,000 for actual pilots. The medication feature shipped in eighty-seven days after being stuck for eighteen months.” Edward shrugged. “The approach is elementary. The discipline to execute it isn’t. That’s the only secret.”

“And if the discipline fails? If Riverton backslides into old patterns?”

“Then we’ll have failed at something simple. Which is more honest than failing at something complex.” He paused at his office door. “Write whatever you want in your report. But don’t call this innovation. It’s just process improvement with the courage to actually look at the process.”

Rebecca left looking thoughtful. Edward wondered if she’d understood what he was really saying: that the hardest part of transformation isn’t the frameworks or the tools. It’s having the discipline to do what you already know you should do.

Elementary. But not easy.

Tuesday, January 13, 2026 – 9:00 AM – Leadership Team Meeting, Riverton Health Systems

Edward looked around the conference table at his leadership team. Twelve people. VPs, directors, senior managers. The people who would make or break the scaling effort.

“I have a new requirement,” he said. “Starting this week, every leader in this room needs to start building with AI tools. Not reviewing. Not approving. Building.”

The silence was immediate.

“I don’t mean you need to become engineers,” Edward continued. “But you need to understand, viscerally, not just theoretically, what these tools can do. You need to experience the capability for yourself. Otherwise you’re making decisions about something you don’t understand.”

Linda Park, VP of Platform Engineering, nodded. She’d been coding for twenty years. This wouldn’t be a stretch for her.

But others looked uncomfortable.

“Edward.” It was Patricia Okonkwo, Director of QA. She’d been with Riverton for eleven years, had built the testing organization from five people to forty. “I need to be honest with you. I’ve never written a line of code in my life.”

The admission hung in the air.

“My background is quality management,” Patricia continued. “Process design. Test strategy. I know how to build a QA organization. But I’ve never been a developer. I don’t know Python or JavaScript or any of it.”

“Then this is your chance to learn.”

“I’m fifty-two years old. I’ve spent thirty years building expertise in quality management. And now you’re telling me that expertise doesn’t matter?”

“I’m telling you the expertise matters more than ever, but only if you understand the new context.” Edward leaned forward. “Patricia, your knowledge of testing strategy is invaluable. But AI is changing what’s possible. If you don’t understand the tools, you can’t lead a team that uses them.”

“So learn to code or get out?”

“Learn to build or get left behind. There’s a difference.” Edward leaned forward. “I’m not asking you to become a software engineer. I’m asking you to spend two hours a day for the next month using these tools. Build something small. A script. A prototype. Anything. So you understand what your team is experiencing.”

Rachel Torres spoke up. “I’ve been doing this for six weeks. It’s uncomfortable at first. But Patricia, the testing applications are incredible. AI can generate test cases, find edge cases, write automation scripts. Your expertise in knowing what to test becomes even more valuable when the how gets easier.”

Patricia didn’t look convinced.

Mike Donovan, the Scrum Master lead, raised his hand. “Edward, what about us? The Agile coaches, the scrum masters? We don’t write code either. We facilitate. We coach. We remove blockers.”

“What blockers are you removing that AI couldn’t handle faster?”

Mike opened his mouth, then closed it.

“I’m not trying to eliminate your jobs,” Edward said. “I’m trying to help you see where you add value that AI can’t replace. But you can’t see that clearly if you don’t understand what AI can do.”

The meeting ended with assignments. Every leader would spend two hours daily for the next month building something, anything, with AI tools. Edward would check in weekly. Those who couldn’t or wouldn’t engage would need to have a different conversation.

Friday, January 23, 2026 – 4:00 PM – Edward’s Office

The first two weeks were revealing.

Linda Park thrived. She’d started using Copilot for her own coding projects and reported that it felt “like having a senior engineer looking over my shoulder, but one who never gets impatient.”

Tom Bradley, the Chief Architect, had automated three documentation tasks he’d been procrastinating on for months. “I finally understand why the junior engineers are so excited,” he told Edward. “This isn’t about writing code faster. It’s about removing the friction that makes you not want to start.”

But others struggled.

Mike Donovan and the Agile coaches were lost. They’d spent years perfecting facilitation techniques, retrospective formats, sprint planning rituals. Now they were being asked to write Python scripts, and the dissonance was profound.

“I don’t know what I’m supposed to build,” Mike admitted in their one-on-one. “My job is helping teams work together. That’s not something you can code.”

“What if it is?” Edward asked. “What if AI could handle the scheduling, the note-taking, the action item tracking, all the logistics you currently manage? What would be left?”

“The human stuff. The conversations. The coaching.”

“Exactly. That’s where you add value. But you need to understand what AI can automate so you can focus on what it can’t.”

Mike left looking thoughtful, if not convinced.

Patricia Okonkwo was the hardest case.

She’d tried. Edward could see she’d tried. But after two weeks, she came to his office and closed the door.

“I can’t do this.”

“Can’t or won’t?”

“Can’t.” Her voice was tired. “I’ve spent thirty hours over the past two weeks staring at tutorials, watching videos, trying to write basic scripts. I managed to get a ‘Hello World’ program to run. That’s it. That’s all I have to show for thirty hours.”

“That’s a start.”

“It’s not enough. And we both know it.” Patricia sat down heavily. “I’m good at what I do, Edward. I’ve built quality processes that have caught thousands of bugs. I’ve trained dozens of testers. I’ve designed test strategies for products that handle patient data for millions of people.”

“I know. Your work has been essential.”

“But I can’t learn to code in a month. I can’t learn to code in a year. Not at the level where I’d actually understand what my team is doing.” She met his eyes. “So what happens now?”

Edward was quiet for a long moment.

“What do you want to happen?”

“I want to keep doing what I’m good at. But I can see where this is going. The manual testing team is already shrinking. The automation engineers are doing things I don’t understand. My QA directors are talking about AI-generated test suites, and I nod along like I know what they mean, but I don’t.”

“Then let’s find a role where your expertise matters and the coding doesn’t.” Edward pulled up an org chart. “Customer Success. Implementation. Training. You know our product better than almost anyone. You know quality better than anyone. Those skills translate.”

“You’re moving me out of QA.”

“I’m moving you to where you can succeed. The alternative is watching you struggle with something that doesn’t play to your strengths while the organization moves in a direction you can’t follow.”

Patricia was quiet for a long time.

“I appreciate you being honest,” she finally said. “Most executives would just wait for me to fail and then fire me.”

“That’s not how I operate. And for what it’s worth, this isn’t a demotion. Customer Success is critical. We need someone who understands quality, who can help hospitals implement our software correctly, who can train nurses to use features like the medication tracker. That’s you.”

Patricia nodded. “When?”

“Let’s take a month to transition. Find the right person to take over QA. someone technical who can grow into the role. And let’s make sure Customer Success is set up for you to succeed.”

After she left, Edward sat alone in his office, staring out at Biscayne Bay.

This was the part nobody talked about. The human cost. Patricia Okonkwo had given eleven years to Riverton, had built something real, and now the ground had shifted beneath her. She wasn’t wrong or bad or lazy; she was just in a role that required skills she’d never needed before.

How many Patricias were there across the organization? Across the industry? Good people, experienced people, who’d built careers on expertise that was suddenly insufficient?

He thought about Harold again. The tape library guy. Harold hadn’t failed either; the world had just changed faster than he could adapt.

The difference was that Edward could see it happening and try to find soft landings. Not everyone would be that lucky.

Saturday, February 7, 2026 – 9:00 PM – The Dock, Edward’s House on the Intracoastal

Edward sat on his dock with Jennifer, watching the stars emerge over the Intracoastal.

“The board approved expansion,” he said.

“I know. You texted me. Three exclamation points.” She smiled. “You never use exclamation points.”

“It felt like an exclamation point kind of moment.”

“So what happens now?”

Edward was quiet for a moment, listening to the water lap against the pilings.

“Now I prove it scales. Now I document the approach so other teams can use it. Now I take what started as a quiet experiment and turn it into something that changes how the whole organization thinks about process improvement.”

“That’s a big responsibility.”

“I know.” He looked at her. “I’m also scared. Every morning, I wake up wondering if this is the day something goes wrong. If this is the day I find out the results were a fluke, or the approach doesn’t work at scale, or I’ve been fooling myself the whole time.”

“But you keep going.”

“But I keep going. Because the alternative is worse. The alternative is watching the world change and being too afraid to change with it.” He thought about Marcus. confident Marcus, who was preparing for an IPO while the ground shifted beneath him. “I’d rather fail trying than succeed at standing still.”

Jennifer didn’t reach for his hand. Her expression had shifted, something harder in it now.

“You missed Emma’s recital.”

Edward blinked. “What?”

“Last Tuesday. Her fall piano recital. The one she’s been practicing for since August.” Jennifer’s voice was flat. “You said you’d be there. Then Rachel called about another crisis, and you said you’d catch the second half, and then you didn’t come at all.”

“I told her I was sorry. I explained.”

“You explained to me. You texted her.” Jennifer turned to face him fully. “She played Chopin, Edward. The piece she’s been working on for three months. She looked for you in the audience. Twice. Lily told me.”

He’d known. He’d known when he made the choice to stay at the office. He’d told himself it was temporary. Emergency. That Emma would understand.

“The medication feature is saving lives.”

“I know. You’ve told me. You’ve told everyone.” Jennifer’s voice cracked. “But you used to say the same thing about being present for your family. About not becoming the kind of executive who sacrifices everything for work.”

“This is different.”

“Is it?” She stood up. “You were up at 5 AM every day this month. You missed three dinners last week. You didn’t even know Lily had a math test on Friday. You asked her about her ‘spelling test’ and she just looked at you.”

Edward opened his mouth to defend himself. Closed it.

“The transformation is working. That’s wonderful. Really.” Jennifer turned her wine glass by the stem. “But Marcus isn’t the only one protecting something without examining it. When’s the last time you mapped the value stream of this family? Where does work wait? Where does it get stuck?”

The question landed like a blow.

“That’s not fair.”

“No, it’s not. None of this is fair.” She sat back down, but further away now. “I’m proud of you. I am. But I’m also tired of being proud of someone who’s never here. Emma’s going to be sixteen next year. Lily’s growing up. And you’re shipping features.”

They sat in silence. The water lapped against the pilings.

“I don’t know how to do both,” Edward finally said. “That’s the truth. I don’t know how to be the CTO this organization needs and the father my kids deserve. I keep thinking I’ll figure it out after the next milestone. After the board approval. After the expansion. After.”

“‘After’ sounds familiar.”

Edward winced. “That’s not fair either.”

“Maybe not.” Jennifer reached over and took his hand, finally. “But I’d rather have this conversation now than watch you become someone you don’t recognize. The way Marcus is becoming.”

“I’m not Marcus.”

“No. But you’re closer than you think.” She squeezed his hand. “Promise me something. Not grand promises. Just one thing. Emma’s winter concert is December 12th. Put it in your calendar. In ink. And be there.”

“I’ll be there.”

“Not ‘I’ll try.’ Not ‘unless something comes up.’ Be there.”

Edward thought about the St. Augustine crisis. About the twelve-hour days. About the board meeting and the conference keynote and the scaling plan that consumed every waking hour.

“I’ll be there,” he said. “I promise.”

Jennifer leaned her head on his shoulder. “That’s the Edward I married. The one who remembers what matters.”

They sat in silence, watching the lights of boats move on the Intracoastal. The night was warm, the air thick with the salt smell of low tide.

“I love you,” Jennifer said. “Even when you’re obsessed with process improvement.”

Edward laughed, but it was softer now, more tired. “Even then?”

“Especially then. Just don’t let it eat you alive.”

Friday, February 13, 2026 – 4:00 PM – Riverton Health Systems

By mid-November, Edward’s pilots had produced consistent results. The value stream mapping approach was spreading organically. teams who hadn’t been selected were doing it anyway, mapping their own processes, preparing themselves for the next round.

Word was starting to spread beyond Riverton. Rachel had been invited to speak at a healthcare IT conference. A vendor had asked for an interview about “the process improvement approach that’s changing Riverton’s culture.”

And the medication tracking feature was now in 23 hospitals. Already catching drug interactions that might have been missed. Real patients, safer.

Something was building. Edward could feel it.

Monday, February 16, 2026 – 10:00 AM – DevOps Team War Room, Riverton Health Systems

The CI/CD breakthrough happened almost by accident.

Rachel Torres brought Edward to the DevOps team’s war room. a converted conference room covered in architecture diagrams and deployment pipeline visualizations.

“Remember the environment provisioning problem we fixed in February?” Rachel asked. “Two-week wait time reduced to two hours?”

“That was one of our first wins.”

“Well, it opened a door nobody expected.” She gestured to Marcus Okafor, the DevOps lead. a different Marcus, younger, more technical than the one Edward had watched dismiss AI tools. “Tell him what happened.”

Marcus Okafor pulled up a screen full of metrics. “We mapped the entire deployment pipeline. From code commit to production. Everything.”

“How long?”

“Forty-seven days. Average. For a single feature to go from ‘code complete’ to ‘running in production.’“

Edward stared at the number. “Forty-seven days?”

“And that’s after the development work is done. That’s just the deployment pipeline. CI builds, test environments, staging, compliance gates, production rollout.” Marcus Okafor shook his head. “We’ve been talking about CI/CD for eight years. Leadership approved a ‘continuous deployment initiative’ in 2017. Never shipped. Approved again in 2019. Partially shipped. The joke on the team was that we had ‘continuous meetings about continuous deployment.’“

“What changed?”

“The value stream map.” Marcus Okafor pulled up the diagram. “When we actually mapped where time went, we found thirty-two separate handoffs between code commit and production. Thirty-two. Some of them were automated. Some were manual. Some were just… waiting. Waiting for someone to click a button. Waiting for a meeting. Waiting for approval from someone who’d been on vacation.”

“And AI helped?”

“AI helped with maybe a third of it. We used AI to generate the pipeline-as-code configurations we’d been hand-writing for years. We used AI to auto-generate test fixtures and deployment scripts. We used AI to document the runbooks nobody had ever documented.” He paused. “But the bigger wins were just removing waste. We found approval gates that existed because of incidents from 2018 that nobody remembered. We found manual checks that were duplicating automated checks. We found entire staging environments that hadn’t been used in two years but were still part of the ‘official’ deployment process.”

“So what’s the number now?”

Marcus Okafor smiled. “Seven days. Average. From code complete to production.”

Edward did the math. “That’s an 85% reduction.”

“And it’s not magic. It’s not some revolutionary new tool. It’s just actually looking at the pipeline and fixing what was broken.” He pulled up another screen. “The really embarrassing part? Half of what we fixed was stuff we’d been complaining about for years. Stuff everyone knew was broken. We just never had permission to fix it because ‘the deployment process is too critical to experiment with.’“

“Permission from whom?”

“Ourselves, mostly. Leadership would say ‘focus on features, not infrastructure.’ DevOps would say ‘we can’t change the pipeline during feature freeze.’ And the pipeline kept getting slower, and nobody looked at why.” Marcus Okafor shrugged. “The value stream mapping gave us permission. Once we could show the actual numbers. forty-seven days, thirty-two handoffs. suddenly everyone wanted to fix it.”

Edward thought about all the DevOps initiatives that had been proposed and rejected over the years. The consulting engagements. The maturity assessments. The “transformation roadmaps” that promised CI/CD in eighteen months.

“You did this in three months,” he said.

“Twelve weeks. With a team of four.” Marcus Okafor looked almost embarrassed. “We’d been told for years that true CI/CD was ‘too complex’ for healthcare IT. Too many compliance requirements. Too much risk. Needed a ‘phased approach’ with ‘proper governance.’” He shook his head. “Turns out it just needed someone to map the actual process and fix what was broken.”

Rachel caught Edward’s eye. This was the pattern. over and over again. Problems that had seemed impossible for years, solved in weeks, once someone actually looked at where the work was getting stuck.

“What’s next?” Edward asked.

“Continuous deployment to production. Right now we still have a manual approval gate before prod. HIPAA requirement, need human sign-off. But we’re working on automating the compliance checks so the human just has to verify the AI’s work instead of doing it from scratch.” Marcus Okafor grinned. “Eight years of ‘continuous meetings about continuous deployment.’ Twelve weeks of actually doing it.”

Saturday, February 21, 2026 – 2:00 PM – The Dock, Edward’s House on the Intracoastal

Sophia came home for the weekend.

She was in her spring semester at Georgia Tech. She had a few free days, and time to catch up with her father. Edward picked her up at the airport on Friday night and spent Saturday afternoon on the dock with her, fishing poles in hand, catching up.

“Tell me about what you’ve been doing,” Sophia said. “Mom says you’ve been obsessing over it.”

“Obsessing is a strong word.”

“Dad. She said you were up at 5 AM every morning for three months. That’s obsessing.”

Edward smiled. “Fair. It’s process improvement. Value stream mapping. Teams map their actual process. where work waits, where it gets stuck, where time gets wasted. Then we fix the bottlenecks. Some fixes involve AI. Most don’t.”

“That’s it?”

“That’s it. The medication tracking feature. the one that had been stuck for eighteen months. shipped in eighty-seven days. Not because of AI. Because we finally looked at what was slowing us down and fixed it.”

Sophia was quiet for a moment, reeling in her line. “At spring break, I told you and Uncle Marcus about the hackathon. About how the teams that struggled were the ones who didn’t know what they were building.”

“I remember.”

“You listened. He checked his phone.”

Edward looked at his daughter. Nineteen now, a sophomore in computer science, already seeing things he’d missed for decades.

“I almost didn’t listen,” he admitted. “My first instinct was the same as Marcus’s. ‘That’s great for school projects.’ But something you said stuck with me. About clarity being more important than technical skill.”

“And now you have an approach that works.”

“Now I have an approach. But it’s not really about the approach. It’s about looking at reality before you jump to solutions.” He paused. “The Infrastructure team failed back in January. Twelve hours of downtime. Three board members wanted to shut everything down.”

“What happened?”

“They got overconfident. Mapped their process, saw early wins, and pushed too fast.” Edward set down his fishing pole. “The approach didn’t prevent the failure. It just made the failure visible. Learnable.”

Sophia turned that over. “That’s still valuable. Most failures are invisible. People don’t even know what went wrong.”

“That’s what I told the board. They weren’t convinced.”

“But the pilots are continuing?”

“They’re continuing. Sandra. the CFO. backed me up. She said every improvement effort has setbacks. The question is whether you learn from them.”

They fished in silence for a while. The afternoon sun was warm, the water calm.

“Dad,” Sophia said finally, “can I tell you something?”

“Always.”

“I’m worried about Uncle Marcus. He’s so certain about everything. Every time I see him, he has answers. Confidence. But he never seems to wonder if his process is actually working.”

Edward felt a chill despite the warm air. “I’ve been thinking the same thing.”

“Have you talked to him?”

“I’ve tried. He’s focused on the IPO. Everything is ‘after the IPO.’ Like the IPO is the finish line and nothing exists beyond it.”

“But the IPO isn’t a finish line. It’s a milestone. What comes after? What’s he actually trying to build?”

“That’s what I keep wondering. And he’s not.”

Sophia reeled in her line. empty hook, no fish. “Maybe he’ll start asking after the IPO.”

“Maybe.” Edward didn’t believe it. “Or maybe by then it’ll be too late.”

They packed up the fishing gear as the sun started to set. Walking back to the house, Sophia slipped her arm through his.

“I’m proud of you, Dad. For actually looking at your process. For fixing what was broken. For building something that matters.”

“I’m proud of you too. For being the one who started this whole thing. At that dinner in March, with your hackathon stories.”

“I didn’t start anything. I just talked about what I was learning.”

“That’s how most important things start. Someone talks about what they’re learning. Someone else listens.”

They went inside, where Jennifer and the girls were waiting with dinner.

Chapter 6: The Widening Gap

February – May 2026

TWO PATHS

EDWARD

Friday, February 13, 2026 – 10:00 AM – Large Conference Room, Riverton Health Systems

The quarterly review told a story that numbers rarely told. Just not the story Edward had hoped for.

Edward sat in the conference room with Rachel Torres, watching her present the pilot results to the expanded leadership team. The headline number was 10%. That was it. Ten percent faster across the organization. The pilot teams had done better — Claims Processing was up 40%, Provider Portal 30% — but averaged across all of engineering, the number was ten.

Ten percent. After a year of mapping, training, coaching, fighting for budget, surviving the St. Augustine crisis, and personally facilitating dozens of workshops.

The room’s reaction told the rest of the story.

“Ten percent,” said Linda Park, VP of Platform Engineering. Her tone was careful. “For all the disruption, all the workshops, all the time my leads spent in mapping sessions instead of shipping… ten percent.”

“The pilot teams are much higher,” Rachel said quickly. “Claims Processing alone is—”

“The pilot teams have Edward in the room,” Linda said. “My teams don’t. They tried the mapping on their own and it was a mess. Three different interpretations of the framework. Two teams mapped the same process and got completely different results. One team spent two weeks on a value stream map and then went right back to the old way because nobody could tell them what to do with it.”

Miguel Santos, one of the pilot team leads, shifted in his chair. “It’s not that simple. The approach works when—”

“When Edward is there. Yes. That’s the problem.”

Edward listened, saying nothing. She wasn’t wrong.

“And then there’s the medication tracking feature,” Rachel said, pivoting. “Shipped in June. Now in twenty-three hospitals. One of them reported catching a potential drug interaction in the first week. A patient who might have been discharged with a dangerous combination.”

The room was quiet. That mattered. That was real.

“That’s what this is about,” Edward said. “Not productivity metrics. Not AI adoption rates. Building software that helps people.”

But Linda’s question hung in the air. Ten percent. For all of that, ten percent.

Wednesday, February 18, 2026 – 9:00 AM – Edward’s Office

The variance was worse than the average.

Edward spent the morning reviewing what had happened in the teams that tried the framework on their own. Rachel had compiled the data. The picture was ugly.

The Infrastructure Automation team had mapped their value stream correctly. Clean diagram. Accurate timing. They identified deployment as their bottleneck: 4 hours to push a change to production. They optimized it to 20 minutes. Impressive engineering. Edward reviewed their results and saw the problem immediately.

“They optimized the wrong thing,” he told Rachel. “Deployment was the loudest complaint. It wasn’t the longest wait. Look at the upstream.” He pointed at the map. “Requirements gathering takes three weeks. Three weeks of back-and-forth with Product before a single line of code gets written. They reduced deploy time from 4 hours to 20 minutes and didn’t touch the 3-week wait that happens before anyone starts building.”

“They’re deploying the wrong things faster.”

“They’re deploying the wrong things faster.” Edward sat back. “They read the map correctly and drew the wrong conclusion. They measured the noisiest bottleneck, not the biggest one.”

The Mobile team was worse, but for a different reason. They’d been rejected from the pilot program in October for vague goals. They reapplied in January with a better application and were accepted. They mapped their value stream. They identified bottlenecks. They applied the framework by the book. Cycle time improved 35%. On paper, a success.

Rachel pulled up the customer satisfaction data. “Customer NPS dropped 12 points in the same period.”

“They shipped faster without talking to customers,” Edward said. “They skipped the step that matters most. They never asked ‘what are we trying to accomplish.’ They just asked ‘what’s slowing us down.’ Faster delivery of features nobody wants.”

But the worst was Claims Processing.

Dennis Okafor, a senior manager on Claims Processing who’d been a skeptic from the start, scheduled a meeting with Edward’s office. He arrived with a value stream map, printed and laminated, and a proposal.

“The data shows QA is a bottleneck,” Dennis said, laying the map on Edward’s desk. “Two QA engineers reviewing every change. Average wait time in the QA queue: three days. If we eliminate the dedicated QA review and shift to developer-owned testing with AI assistance, cycle time drops 30%.”

Edward looked at the map. Dennis had done the work. The timing was accurate. The QA queue was real. Three days of waiting.

“What happens to Renata and James?” Edward asked. Renata Singh and James Cho were the two QA engineers.

“Reassignment. Or reduction.”

“Reduction meaning fired.”

“The data supports it.” Dennis pointed at the map. “You said remove what doesn’t add value.”

Edward felt something cold in his chest. His own framework, his own language, being used to justify cutting two people whose expertise had prevented three production incidents in the last quarter alone.

“The map shows QA is a queue, Dennis. Not a bottleneck. The bottleneck is the handoff between development and QA. The three-day wait. Not the two-day review.” Edward stood up. “You’re proposing to remove the work because you measured the wait. Renata caught a HIPAA data exposure in September that would have cost us $2 million in fines. James found a drug interaction logic error that Priya’s team missed. That’s not waste. That’s the last line of defense before code touches patients.”

“You said remove constraints that don’t add value.”

“I said remove constraints that don’t protect patients. QA protects patients. The three-day wait for QA to start doesn’t. Fix the handoff. Don’t fire the people.”

Dennis left the meeting angry. Edward sat in his office for a long time after the door closed. His own methodology, weaponized. A middle manager using value stream mapping to build a case for headcount reduction, complete with laminated diagrams and Edward’s own language turned against its purpose.

Rachel found him staring at the whiteboard.

“Dennis filed a formal objection with HR,” she said. “He’s arguing that you’re selectively applying your own framework.”

“He’s not wrong.” Edward rubbed his face. “I am selectively applying it. Because the framework doesn’t have a built-in check for ‘is someone using this to fire people they don’t like?’ I assumed good faith. That was naive.”

“What do you want to do?”

“Add a rule. Before any value stream change that affects headcount, it comes through the AI-SDLC Board. Not because we don’t trust managers. Because the methodology is powerful enough to be misused, and we need a check.”

The one bright spot: the Security team. They’d been Edward’s second-wave pilot, the team with the clean value stream map and the specific goal. Without Edward in the room, their team lead had applied the framework and achieved 25% improvement. Not the 40% Claims Processing got with Edward present. But real. Measurable. Sustained.

The difference, when Rachel analyzed it, was simple. The Security team lead had mapped constraints with genuine curiosity. She’d interviewed every person who touched the vulnerability response process. She’d asked Patricia Hendricks what the compliance review actually checked, not what it was called. She’d tested removing gates in staging before cutting them in production. She’d done what Edward did, at a smaller scale, with less authority and more patience.

Twenty-five percent. Not forty. But proof that the framework could work without Edward in the room, if the person applying it was willing to do the investigation, not just the mapping.

Linda Park’s critique, when Edward presented the full picture at the next leadership meeting, was sharper than before.

“The pilot teams have Edward in the room. My teams don’t. And some of my teams are now worse off than before. Dennis is using your framework as a headcount reduction tool. The Mobile team is shipping garbage 35% faster. Infrastructure deploys the wrong things in 20 minutes instead of 4 hours.” She paused. “Ten percent is the average. The variance is the problem. The Security team got 25% without you. Claims got weaponized. Mobile shipped faster in the wrong direction. That’s not a scaling challenge. That’s a methodology that works when the practitioner has judgment and fails when they don’t.”

Wednesday, February 18, 2026 – 2:00 PM – Conference Room C, Riverton Health Systems

Not every team wanted to be mapped.

Edward stood at the whiteboard in Conference Room C, facing the Infrastructure Operations team. Twelve engineers, all of them staring at him with expressions ranging from skeptical to hostile.

“Walk me through what happens when a change request comes in,” Edward said. “Not the documented process. The real process.”

Silence.

Tom Reinhardt, the team lead, crossed his arms. “The real process is the documented process. We follow the runbook.”

“The runbook says change requests take three days for review and approval. Your metrics show average completion time of eleven days. Where do the other eight days go?”

More silence. A few engineers shifted uncomfortably in their seats.

“Look,” Tom said finally. “We’ve been through this before. Leadership comes in, asks us to expose our inefficiencies, promises it’s not about headcount. Then six months later, half the team is gone.”

“That’s not what this is.”

“You say that. Every transformation leader says that.” Tom leaned forward. “We’ve been burned before. At my last company, at the company before that. ‘Trust the process’ always ends with layoffs.”

Edward set down the marker. He understood the fear. He’d seen it before, in different contexts, with different teams. The instinct to protect territory, to hide problems, to avoid becoming the next efficiency target.

“Let me tell you what I’m actually trying to do,” he said. “There’s a medication tracking feature that’s been stuck for eighteen months. Nurses need it. Patients need it. Every day it doesn’t ship, someone might die because of a drug interaction we could have caught.” He paused. “I’m not here to cut your headcount. I’m here to figure out why work gets stuck. Some of that stuck work is in Infrastructure Ops. Some of it is in Product. Some of it is in my own office. I need to see all of it.”

Tom crossed his arms. “And if what you see is that we’re understaffed? That we’re drowning in requests and can’t keep up?”

“Then I need to see that too. Because right now, I don’t know. I have theories. Everyone has theories. But nobody has actually mapped where work waits.” Edward picked up the marker again. “Give me two hours. Show me the real process. If what I find is that you need more resources, I’ll fight for more resources. If what I find is waste that nobody’s ever questioned, we’ll cut the waste. But I can’t help if I don’t see.”

The room was quiet. Then one of the junior engineers, a woman named Amy Koh, spoke up.

“The handoff from Platform Engineering takes four days on average. They say it takes one. But they don’t have the context we need, so we have to chase them for clarification.”

Tom shot her a look, but she kept going.

“And the approval queue for production changes. Three people have to sign off, but one of them is always traveling. So we wait. Sometimes for a week.”

“Keep going,” Edward said.

For the next two hours, the team talked. They drew on the whiteboard, argued with each other, corrected each other’s assumptions. By the end, Edward had a map of the Infrastructure Ops process that bore almost no resemblance to the documentation.

Eleven days for a change request. Four days of waiting for clarification. Three days waiting for approvals. Two days of rework because requirements changed mid-stream. The actual work took about a day and a half.

“This is what I needed,” Edward said. “This is what nobody else has been willing to show me.”

Tom Reinhardt stood up, his expression still guarded but softer now. “What happens next?”

“I fix what I can fix. The approval queue with the traveling executive. That’s governance bloat. I can cut that. The handoff from Platform Engineering. That’s a communication problem. We can solve that.” Edward paused. “The clarification delays. That’s a specification problem. We need Product to write better requirements. That one’s harder, but it’s fixable.”

“And the headcount?”

“You’re understaffed. I can see it in the numbers now. But I can also see that half your capacity is being wasted on waiting and rework. Fix the waste, and your capacity doubles without adding a single person.” Edward extended his hand. “Thank you for trusting me enough to show me the truth.”

Tom shook it. “Don’t make us regret it.”

“I won’t.”

MARCUS

Friday, February 20, 2026 – 7:30 PM – Private Jet, Over Manhattan

The private jet banked over Manhattan, giving Marcus a perfect view of the skyline at sunset.

He was returning from his third investor meeting of the week, traveling with Catherine on the pre-IPO circuit. Boston to Chicago to New York, with San Francisco scheduled for tomorrow. Catherine handled the business narrative; Marcus handled the technology questions. Presentations in glass-walled conference rooms, dinners with institutional investors who managed more money than most countries.

The story was working. Every meeting, Catherine delivered the business narrative, Marcus explained the technology moat, and the investors nodded.

His phone buzzed. Sarah.

How was New York?

Good. Wellington Partners is in for $50M. That’s our anchor institutional investor.

Proud of you.

Marcus smiled and settled back into his seat. Eleven months from ringing the bell at the NYSE.

He was winning. He’d already won.

Everything else was noise.

EDWARD

Tuesday, March 3, 2026 – 9:00 AM – Edward’s Office, Riverton Health Systems

The industry conference invitation arrived the following week.

Rachel brought it to Edward’s office. “Healthcare IT Innovation Summit. They want you to keynote. Forty-five minutes on ‘AI in the SDLC: Why Process Improvement Beats Tool Adoption.’“

“How did they hear about us?”

“Word of mouth. Someone mentioned Riverton’s results, it got repeated.” Rachel sat down. “If you speak about this approach, it’s not just Riverton anymore; it’s the entire healthcare IT sector.”

“That’s a lot of exposure.”

“That’s a lot of impact.” Rachel paused. “Unless you want to stay below the radar?”

Edward considered the question. They’d been deliberately quiet, building proof, accumulating evidence. But at some point, “below the radar” became “hiding.”

“Set it up. But I want to focus on process improvement, not tools.”

“That’s exactly why they want you. Everyone else is talking about tools. You’re talking about actually looking at the process.”

MARCUS

Tuesday, March 10, 2026 – 2:00 PM – Axiom Boardroom

The board meeting in December was a celebration disguised as a meeting.

Diana Reeves presented the financials with barely suppressed excitement. Revenue up 12% quarter-over-quarter. Customer retention at 97%.

“IPO pricing discussions start next month,” Diana said. “We’re targeting $16 per share. $950 million valuation. Marcus, your stake would be worth approximately $13 million.”

The number landed in Marcus’s chest like a small explosion. Thirteen million dollars. Four years of sacrifice would pay off.

Victoria Hartwell smiled, a rare expression for her. “Congratulations are in order. You’ve built something remarkable.”

Afterward, Prakash texted: Can we talk? Something you should see.

Tuesday, March 10, 2026 – 4:30 PM – Marcus’s Office

Prakash arrived with a manila folder. He looked older than Marcus remembered.

“Three more customers this quarter mentioned private demos under NDA. They’re calling it ‘Project Prometheus.’ The capabilities they’re describing match our roadmap. Feature for feature. Plus things we haven’t even scoped.”

“Private demos aren’t a product. They’re vaporware.”

“I found a job posting. Anonymous company, ‘AI-native logistics platform.’ VP of Customer Success to manage ‘large-scale customer transitions.’” Prakash pulled another document. “Shell companies in Delaware. Engineers from legacy freight companies quietly going dark. Someone is building something big.”

Marcus opened the documents. His instinct was to dismiss them.

“Let’s say you’re right. So what? Even if someone ships something, it’ll be years before they threaten us.”

“What if Project Prometheus isn’t a startup? What if it’s someone with deep pockets and existing customer relationships?”

“Then we deal with it after the IPO.”

“After the IPO might be too late.” Prakash leaned forward. “The case studies talk about 4x, 5x productivity gains with AI. What if whoever’s behind this is experiencing those gains right now?”

Through the window, a container ship was passing. probably carrying a billion dollars in goods,

“Keep watching,” Marcus said. “Document what you find. After the IPO, we’ll address it properly.”

Prakash took the folder. His expression said he wanted to argue further.

“One more thing. Derek Huang. He’s been interviewing.” Prakash paused. “He mentioned ‘finding something worth building.’ And Marcus… he seemed excited. Like he knows something we don’t.”

EDWARD

Wednesday, April 15, 2026 – 2:00 PM – San Diego Convention Center

Edward stood backstage at the San Diego Convention Center, watching several hundred healthcare IT executives settle into their seats.

Jennifer had flown out with him. She was in the front row, giving him an encouraging thumbs-up.

He walked on stage.

“Good afternoon. I’m Edward Johnson, CTO of Riverton Health Systems. I’m here to tell you about a transformation we’ve been through, and why most AI transformations fail.”

He clicked to his first slide: What’s stopping you from shipping?

“We had a medication tracking feature stuck for eighteen months. So we mapped the value stream. Eleven weeks from requirement to deployment, but only two weeks of actual work. Nine weeks of waiting.”

He spent thirty minutes walking through case studies. Kevin Nakamura’s transformation. The Documentation team that eliminated redundant processes without any new tools.

“Start with where work waits. Not with what tools to buy.”

The applause was enthusiastic.

Afterward, Edward was surrounded by executives asking questions, exchanging business cards.

A CTO from a major hospital system: “We’ve been wrestling with AI adoption for two years. Now I think I know why: we’ve been buying tools instead of looking at our process.”

Rachel found him at the hotel bar.

“You’re going to need more business cards,” she said.

“I’m going to need more staff.” Edward ordered a bourbon. “This is bigger than I expected.”

MARCUS

Saturday, April 4, 2026 – 8:00 PM – Webb Family Home, Fort Lauderdale

The weekend conversation with Sarah happened over quiet dinner. The boys were at a tournament in Orlando.

“What are you hearing about Project Prometheus?”

Marcus set down his wine glass. “Rumors. Same ones I told you before.”

“It’s more than rumors now. One of the Garlands’ grantees heard a shell company called MAI Research LLC is approaching companies. Free migration from Axiom, free training, free support.” Sarah’s expression was carefully neutral. “They’re specifically targeting Axiom customers.”

“It’s a competitive tactic. Some startup trying to create uncertainty before our IPO.”

“‘After the IPO’ isn’t a strategy.” Sarah pulled her hand back. “Every time I raise concerns, you defer. What happens if ‘after’ is too late?”

“It won’t be too late.”

“How do you know?”

“Because I know this industry. I know our competitors.”

Sarah set her fork down.

“I hope you’re right,” she said finally.

She didn’t smile.

EDWARD

Sunday, April 12, 2026 – 7:00 PM – The Dock, Edward’s House on the Intracoastal

Sophia had spent the previous summer at Axiom. Marcus had offered her the internship back in February, a favor to family, a chance for Sophia to see “how a real company works.” Edward had been grateful. Sophia had been excited.

Now, six months later, she was home for winter break, and she looked troubled.

“How was the internship?” Edward asked.

“It was… educational.”

“That doesn’t sound like a ringing endorsement.”

Sophia was quiet for a moment. “Dad, can I ask you something? And you have to promise not to tell Uncle Marcus I said anything.”

Edward set down his fishing pole. “Of course.”

“Is it normal for a software company to not let engineers use AI tools? Like, at all?”

“What do you mean?”

“Catherine, the CEO, she sent out this memo before I started. Anyone caught using unauthorized AI tools would be terminated and lose their unvested equity. The engineers weren’t even allowed to experiment.” Sophia shook her head. “At school, we use AI for everything. Debugging. Code generation. Documentation. But at Axiom, everyone was typing everything by hand. It felt like going back in time.”

Edward felt a chill. He’d heard Marcus mention the policy, but hearing it from Sophia made it feel different. More real.

“Did you talk to Marcus about it?”

“I tried. Once.” She picked at a splinter on the dock railing. “He said the same thing he always says. ‘After the IPO.’ He said the board didn’t want any variables, and AI tools were a variable they couldn’t control.”

“What did the engineers think?”

“The ones who would talk to me? They were frustrated. A few of them were using AI on personal projects, just to stay current, but they couldn’t touch it at work.” She paused. “And I overheard something I probably wasn’t supposed to hear. Two senior engineers in the break room, complaining about the VP of Engineering. Derek something. They said he’d been interviewing, that he wasn’t even trying to hide it anymore. One of them said, ‘If Derek leaves, I’m right behind him. I don’t want to wake up in two years with obsolete skills.’“

Derek Huang. Edward knew the name. One of Marcus’s original hires.

“But here’s what really got me,” Sophia continued. “Things that would take me an afternoon at school? They took a week there. Maybe more. Not because the work was harder. Because of all the handoffs. I’d finish something, send it to someone for review, wait two days, get feedback, fix it, send it to someone else, wait another day.” She shook her head. “The actual writing the code part was fast. Everything around it was slow. Is this what my career is going to be like? Waiting for approvals and sitting in meetings about meetings?”

“It doesn’t have to be.”

“But that’s how it was at Axiom. And they’re supposed to be the innovative startup.” She picked at another splinter. “Dad, I started this internship thinking I wanted to work at a startup. Be like Uncle Marcus. Build something from nothing. Now I’m reconsidering. Is this what startups are actually like? Moving slower than everyone else because they’re afraid of risk?”

“Not all of them. Some startups are exactly what you imagined. Fast, experimental, willing to try new things.” Edward chose his words carefully. “But some get cautious as they get closer to big milestones. An IPO is a huge milestone. Marcus is trying to protect what he’s built.”

“Protect it from what? From getting better?”

Edward didn’t have a good answer.

“The thing is,” Sophia continued, “Uncle Marcus isn’t stupid. He’s really smart. But he’s so focused on the IPO that he can’t see anything else. Every question I asked about technology, about AI, about competition, he had the same answer. ‘After the IPO.’ Like the IPO is going to solve everything.”

“I’ve noticed the same thing.”

“So why don’t you say something? You’re his best friend. He might listen to you.”

“I’ve tried. At spring break. A few times since. He has answers for everything. Meridian is dying. Their competitors are years behind. The IPO is the finish line.” Edward sighed. “He’s never mapped his own process. Never identified where work actually gets stuck. He’s protecting a trajectory instead of examining it.”

Sophia was quiet for a long time. The sun had dropped below the horizon, painting the sky in reds and purples.

“I’m worried about him, Dad. And Aunt Sarah. And MJ and Isaiah.” She pulled her knees up to her chest. “What happens if the IPO doesn’t go well?”

“I don’t know. I’ve never been through an IPO.” Edward put his arm around her. “But I’m worried too.”

“Should I say something? Next time we’re all together? About what I saw?”

“I think Marcus needs to figure some things out for himself. But if you want to share what you observed, that’s your choice.” Edward paused. “Just be gentle. He’s carrying a lot of weight right now.”

They sat in silence until the stars came out. Somewhere on the water, a boat’s running lights blinked in the darkness.

“Dad?”

“Yeah?”

“I’m glad I’m at Riverton’s competitor.” She smiled slightly. “I mean, not competitor. But you know what I mean. Healthcare instead of logistics. At least you’re looking at your process instead of just protecting it.”

Edward hugged her tighter. “I learned from you. At spring break. ‘You have to know what you want.’ Start with the end in mind. Then figure out what’s actually stopping you.”

“I was just talking about hackathons.”

“Sometimes that’s how the important lessons get delivered.”

Wednesday, April 22, 2026 – 3:00 PM – Engineering Floor, Riverton Health Systems

Lisa Martinez stopped Edward in the hallway. She was beaming.

“I shipped my first feature today.”

Edward smiled. “Tell me about it.”

“The medication dosage calculator. The one that adjusts recommendations based on patient weight and kidney function.” Lisa had been a QA engineer for eight years. Six months ago, when Edward had restructured QA into a platform team, she’d asked to transition to development. “I never thought I could do this. I spent my whole career telling developers what was wrong with their code. Turns out I learned more than I realized.”

“Your QA background is an advantage. You think about edge cases that developers miss.”

“That’s what my team lead said. The other developers keep asking me ‘what could go wrong here?’ before they even write the tests.” She laughed. “I went from being the person who found the bugs to being the person who prevents them.”

Edward thought about the reorganization. QA and Security had become platform teams six months ago. Some people had struggled with the change. A few had left. But Lisa was the third QA engineer who’d transitioned to development, and all three were thriving.

“How’s the security tooling working out?”

“Ben Adler’s team built something amazing. The static analysis catches maybe 70% of the security issues before code review even starts. The developers are actually learning to think about security because the tools give them instant feedback.” She paused. “Ben told me he’s happier than he’s been in years. His team used to be the department everyone complained about. Now they’re building things that make everyone’s life easier.”

“No one can ever make security people happy,” Edward said. “Except apparently when you let them build tools instead of being a gate.”

Lisa laughed. “That’s what he said you’d say.”

Thursday, April 23, 2026 – 2:00 PM – AI-SDLC Board Meeting

Edward stood at the whiteboard, marker in hand. The AI-SDLC Board was assembled: Sandra Williams, Maria Santos, Johnny Morrison, Rachel, and this week’s rotating engineer, Priya Sharma.

“Let me walk you through what the pilot teams have built,” Edward said. He listed the agents: scrum master, security review, QA, SRE. Each one doing routine work so humans could focus on judgment calls. In the pilot teams, it was working. Security issues that used to sit in a queue for a week got a PR within minutes. Lisa Martinez went from running regression tests to shipping the medication dosage calculator. The audit trail was cleaner than when humans did everything ad hoc.

“Within the pilot teams, the results are real,” Edward said. “Forty percent faster in Claims Processing. Thirty percent in Provider Portal.”

Johnny leaned forward. “And outside the pilot teams?”

The room got quiet. Johnny had seen the same quarterly numbers everyone else had.

Edward didn’t flinch. “Ten percent across the organization.”

“Ten percent.” Johnny let that sit. “We spent $400,000 on AI tooling. You restructured governance. You’ve had my full support for six months. And the org-wide number is ten percent.”

“The pilot teams prove the approach works. The org-wide number proves we can’t scale it the way we’ve been trying.” Edward set down the marker. “I’m not going to stand here and spin 10% into a victory. It’s not what I promised. It’s not what I expected.”

Sandra was doing mental math. “Walk me through the economics honestly.”

“We cut $300,000 in retention offsites. Spent $400,000 on tools. Net cost of $100,000.” Edward paused. “Attrition in the pilot teams dropped from 18% to 9%. Outside the pilots? Attrition is actually up. Fourteen percent to 19%. Some of that is people frustrated by the inconsistency. Some is teams that tried the approach without support and got burned.”

The room absorbed that.

“So we have islands of excellence surrounded by organizational chaos,” Sandra said.

“Yes. That’s an honest description.”

Maria Santos from Legal spoke up. “The compliance implications of inconsistent methodology across teams…”

“Are real. We have three different versions of the mapping framework in use. Two teams that modified the agent configurations without going through governance. And the hospitals we onboarded too quickly are reporting performance issues.” Edward sat down. “The approach works. The approach at scale, inside an existing organization, with twenty years of legacy process? That’s a different problem. And I don’t have the answer yet.”

Johnny was quiet for a moment. Then, unexpectedly: “I appreciate the honesty.”

Edward raised an eyebrow.

“Six months ago, you would have spun this. Found a way to make 10% sound like a win.” Johnny shook his head. “The fact that you’re standing here saying it’s not enough? That’s more credible than any slide deck.”

“The medication feature is in twenty-three hospitals,” Rachel said. “Twenty-three potential drug interactions flagged. That’s lives saved.”

“That’s real,” Johnny agreed. “But it’s not an organizational transformation. It’s a pilot that worked and an org that couldn’t absorb it.”

Edward nodded. “That’s exactly what it is.”

The meeting ended without applause. No one owed anyone an apology. The pilot teams were proof of concept. The organization was proof that proof of concept isn’t enough.

Friday, May 1, 2026 – 4:00 PM – Edward’s Office

Success was supposed to bring better problems. Instead, it brought chaos.

Rachel knocked on Edward’s door. She didn’t sit down. “We have a situation.”

“Which team?”

“All of them.” She leaned against the doorframe. “Infrastructure Ops tried to run their own value stream mapping session. Without a trained facilitator. They ended up in a three-hour argument about whose process was worse. Tom Reinhardt walked out. Two of his engineers updated their LinkedIn profiles that afternoon.”

Edward closed his laptop. “That’s one team.”

“It’s not one team. The Platform Engineering group took our mapping template and modified it. Now they have their own version that doesn’t match anyone else’s. When they hand off to App Dev, the handoff documentation doesn’t align. It’s actually slower than before we started.” Rachel sat down. “And the medication tracking feature expansion? The three hospitals we onboarded last month without proper stress testing? Two of them reported performance issues. Not dangerous. But the kind of thing that makes compliance nervous.”

“How many teams are trying the mapping on their own now?”

“Twelve. Maybe fourteen. We trained six. The rest just started doing it because they heard about the pilot results.” She handed him a printed email chain. “Linda Park’s team created a Slack channel called ‘value-stream-skeptics.’ Forty-seven members.”

Edward read the email chain. Screenshots of botched mapping sessions. Complaints about inconsistent methodology. One engineer’s post: ‘Another management framework that works great in the demo and falls apart in production.’

“The pilot teams are producing real results,” Rachel said. “Claims Processing is still up 40%. The medication feature is saving lives. But outside the pilots? It’s a mess. And the mess is making the pilot results look like a fluke.”

“What’s the aggregate number?”

“Ten percent. Across the whole org, ten percent improvement.” Rachel paused. “That’s real. In a 400-person engineering organization, 10% is meaningful. But it’s not the story we told the board. And it’s not the story they’re going to want to hear.”

Edward stared out the window. Ten percent. The pilot teams were proof the approach worked. But the org couldn’t absorb it. Not like this. Not one team at a time, with him personally in every room, facilitating every session, resolving every conflict.

“I’m the bottleneck,” he said.

“You’re the bottleneck. And the approach doesn’t work without you in the room. Not yet.” Rachel’s expression was both sympathetic and brutal. “You built something that requires Edward Johnson to be in twelve places at once. That’s not a transformation. That’s a dependency.”

“So what do we do?”

“I don’t know. I wrote a proposal for training facilitators. Certification programs. Self-service toolkits.” She handed it to him. “But honestly? I’m not sure that fixes it. The problem isn’t that we need more facilitators. The problem is that you can’t transform an organization sequentially. One team at a time. One mapping session at a time. One Edward at a time.”

Edward read the proposal. It was thorough. It was also a band-aid.

“What would it take to do this in parallel? All teams at once?”

Rachel shook her head. “A completely different organizational structure. You’d need to rebuild from scratch. Parallel teams, parallel governance, parallel everything. You can’t retrofit that onto a company that’s been running serially for twenty years.”

“So I go to the board. Propose an org restructure.”

“Edward.” Rachel’s voice was careful. “The board backed you on one feature. One pilot program. They aren’t going to back you to restructure four hundred engineers, dissolve three VPs’ empires, and rebuild the reporting lines from scratch. That’s not a process improvement proposal. That’s a coup.”

“It’s what the data says we need.”

“The data says you got 10% improvement across the org. That’s not a crisis. That’s a respectable result. No board is going to authorize tearing down a functioning organization because 10% isn’t enough.” She paused. “You spent your political capital getting the pilots approved and surviving the Infrastructure failure. You don’t have enough left to propose what you’d actually need to propose.”

The words landed like a diagnosis.

“So what we built works,” Edward said. “It just can’t scale inside what already exists.”

“Not without tearing everything down and starting over. And you don’t have the political capital to tear everything down. Nobody does, from the inside.” Rachel stood up. “The medication feature is real. The pilot results are real. Twenty-three hospitals are safer because of what we did. That matters. But the dream of transforming the whole org from the inside?” She paused. “I think we hit the ceiling.”

“So there’s no path that doesn’t require tearing it down.”

“Not inside a company that’s been running serially for twenty years. The only way to do what you want is to start from scratch somewhere. Build it right from the beginning.”

Edward sat with that for a long time after she left.

Monday, May 4, 2026 – 9:00 AM – Edward’s Office

The recruiters started calling in January.

Not headhunters. Not small companies. The calls were coming from the biggest names in technology: a major cloud provider, a Fortune 50 tech company, an enterprise software giant.

The pitches were similar: We’ve been watching the medication tracking story at Riverton. We need someone who understands AI transformation.

Edward listened politely and declined. He had a job. He had teams counting on him.

But the calls kept coming. And after the quarterly review, after Rachel’s diagnosis, after staring at that 10% number, he started listening differently.

One call stood out. Cascade Technologies. 150,000 employees. The VP of Engineering said something that stuck:

“We’re not looking for someone to transform our existing org. We’re building a parallel organization from scratch. New structure, new processes, new governance. The old org keeps running. The new one proves a different model. When it works, teams migrate voluntarily.”

A parallel organization. Built from zero. No legacy to retrofit. No twenty-year-old processes to fight.

Edward didn’t say yes. But for the first time, he didn’t say no.

MARCUS

Tuesday, May 19, 2026 – 3:30 PM – Marcus’s Office, Axiom

The Whitfield analyst call changed everything.

Marcus had been preparing for the worst. February had been rocky: more questions about Meridian, more whispers about Project Prometheus, more nervous glances from his engineering leads. He’d started to wonder if the doubters were right.

Then Allison Marsh from Whitfield Capital called.

“Marcus, I wanted to give you a heads-up before we publish.” Her voice was warm, collegial. “We’re upgrading Axiom to ‘Strong Buy’ with a $22 price target.”

Marcus nearly dropped his phone. “$22? That’s 37% above our IPO range.”

“The fundamentals are compelling. Your retention numbers are industry-leading. The logistics market is consolidating, and you’re positioned to be the acquirer, not the acquired.” She paused. “We’re not seeing the Meridian threat that some of your competitors are hyping. Their platform is dated. Their customer base is shrinking. Whatever they’re building internally, it’s not showing up in market share.”

After the call, Marcus sat alone in his office, staring out at the port.

I was right.

All the doubters. Prakash with his manila folders. Sarah with her warnings. Even Edward with his value stream questions. They’d all been worried about nothing.

Meridian was dying. The analysts confirmed it. The institutional investors confirmed it. The IPO was going to be a success, and everything Marcus had sacrificed would be worth it.

He texted Sarah: Whitfield upgraded us to Strong Buy. $22 price target. Told you we’d be okay.

Her reply came an hour later: That’s wonderful news. Proud of you.

That night, Marcus slept through until 6 AM. No 2 AM anxiety spirals. No obsessive checking of competitor news.

Thursday, May 28, 2026 – 10:00 AM – Executive Conference Room, Axiom

The renewal report came in nine days later.

Customer Success had flagged twelve accounts as “at risk for renewal.” Twelve. In a single quarter.

“What’s driving this?” Marcus asked, the Whitfield glow still lingering.

Amanda Wong, Derek’s replacement, pulled up the customer feedback.

“Two themes. First: Project Prometheus. Some customers got approached by MAI Research LLC. They’re asking if we’re going to get leapfrogged.”

“Whitfield just upgraded us to Strong Buy. They said Meridian isn’t a threat.”

Amanda shifted uncomfortably. “Analysts measure market share. Customers measure features.”

“And the second theme?”

Amanda hesitated. “Our roadmap. Or lack thereof.”

“We have a roadmap.”

“Features they asked for in 2024 are now scheduled for late 2026. One customer said, and I’m quoting, ‘You’re slower than the dinosaurs we left.’“

Marcus felt the Whitfield glow fade. “We’re still nimble.”

“Nobody’s churning. But they’re signing one-year deals instead of long-term contracts.” Amanda paused. “They keep asking about AI features. About Project Prometheus. We keep saying ‘after the IPO.’“

EDWARD

Monday, May 11, 2026 – 6:45 PM – The Dock, Edward’s House

The text exchange with Marcus happened on a quiet Monday evening.

Edward was watching the sunset when his phone buzzed.

Hey brother. How’s Miami treating you?

Good. Been busy. Some interesting developments at work.

Edward wanted to tell Marcus everything: the value stream mapping, the medication feature, the conference keynote. But also the 10%. The org chaos. The teams that tried and failed. The feeling that he’d built something real but couldn’t make the rest of the organization absorb it.

But he remembered Marcus dismissing Sophia’s stories. He remembered “after the IPO” and the wall of confidence that nothing seemed to penetrate.

Our AI pilots are showing results in the teams that adopted it. The medication feature shipped. Industry conferences are asking me to speak.

That’s great. Glad it’s working out.

It’s more complicated than that. The pilot teams are strong but the org-wide numbers are… humbling. We should talk sometime.

Definitely. After the IPO, let’s grab dinner.

Edward stared at the response. After the IPO. The same phrase Marcus had been using for almost a year.

He wanted to push harder. He wanted to say Marcus, the world is changing faster than your IPO timeline.

But you couldn’t help someone who wasn’t asking for help.

Sure, he typed. After the IPO.

He set down his phone and watched a boat’s running lights move across the darkening water.

THE DINNER

Thursday, February 26, 2026 – 3:00 PM – Webb Family Home, Fort Lauderdale

Marcus insisted on hosting dinner at the Webb house. He wanted everything perfect: fresh flowers on the table, the good wine open, steaks on the grill.

The Johnsons arrived at three. Edward climbed out first, stretching after the drive from Miami. Sophia was home from Georgia Tech, a sophomore now, more confident than she’d been a year ago.

Sarah met them at the door.

“You look tired,” Jennifer said.

“It’s been a month.” Sarah didn’t elaborate.

Thursday, February 26, 2026 – 4:00 PM – Living Room

Edward noticed Marcus immediately: the tension in his shoulders, the rigid posture, the way his easy confidence had calcified into rigidity. Marcus looked like a man carrying weight he couldn’t set down.

When dinner conversation turned to Sophia’s semester, the energy shifted.

“Tell us about your classes,” Sarah said.

Sophia set down her fork. “The thing my professor keeps emphasizing is clarity. You can’t build well if you don’t know what you’re building. The AI amplifies whatever you bring to it, good thinking or bad thinking.”

Marcus looked up sharply. “In the real world, it’s more complicated. You need execution. Discipline. The ability to protect what you’re building from distractions.”

Sophia’s expression flickered but she didn’t argue.

Thursday, February 26, 2026 – 6:30 PM – Kitchen

Jennifer and Sarah loaded the dishwasher in silence.

“He’s not listening,” Sarah finally said. “To anyone. Every time I bring up AI, every time someone mentions competition, every time anyone suggests maybe the world is changing faster than his timeline, he says ‘after the IPO.’“

“How long has it been?”

“Since spring break. Nearly a year of ‘after the IPO.’ It’s become a reflex. A way to defer every conversation he doesn’t want to have.”

Jennifer set down a plate. “Edward’s pilots are producing results. The medication tracking feature shipped. But the rest of the organization…” She trailed off. “He doesn’t talk about it much, but I can tell. Some teams are thriving. Others are a mess. He’s frustrated.”

“I know. I’ve been hearing the success stories through my network.” Sarah’s voice was bitter. “‘Did you see that CTO from Riverton? The process improvement guy?’ My cousin’s husband is becoming a thought leader while my husband refreshes the ARR dashboard before breakfast. Meanwhile the thought leader comes home and stares at spreadsheets trying to figure out why it only works when he’s in the room.”

Through the window, the husbands were walking toward the dock.

“Maybe tonight,” Jennifer said. “Maybe Edward can get through to him.”

Sarah didn’t look hopeful.

THE BREAKTHROUGH

EDWARD

Monday, February 23, 2026 – 9:00 AM – Engineering Floor, Riverton Health Systems

That Monday, Rachel showed him what Claude Opus 4.6 could do.

Edward was in his office when Rachel burst through the door, laptop open, eyes wide.

“You need to see this.”

She set the laptop on his desk. A code review was open on the screen. Not an ordinary review. A complete architectural analysis of Riverton’s medication tracking module, with suggested optimizations, security improvements, and performance enhancements.

“How long did this take to generate?” Edward asked.

“Forty-seven seconds.”

Edward stared at the screen. The suggestions weren’t just syntactically correct. They reflected deep understanding of healthcare compliance, HIPAA requirements, the specific edge cases their domain experts had documented over decades. The model wasn’t just generating code. It was reasoning about the domain.

“Run it again,” he said. “Different module. Something complex.”

Rachel pulled up the patient scheduling system. The legacy component they’d been afraid to touch for three years.

Forty-two seconds later, they had a complete refactoring plan. Not a generic suggestion. A plan that accounted for their specific database schema, their API contracts, their deployment constraints.

“This changes everything,” Rachel said.

“Stop.” Edward’s voice was sharp. “What’s the business outcome?”

Rachel blinked. “What?”

“You just showed me a faster way to generate code. That’s a task improvement. What’s the business outcome? How does this reduce days to ship? How does it affect patient care? Where does it fit in the macro flow?”

It was the culture he’d built at Riverton. Nobody talked about individual task improvements in isolation. Every conversation started with the business outcome and worked backward. The AI-SDLC Board had drilled it into every team: if you can’t connect an improvement to a measurable business result, you haven’t finished thinking.

Rachel nodded, recalibrating. “The patient scheduling system has been a bottleneck for eighteen months. Hospitals complain about double-bookings, missed appointments, cascading delays. If we can refactor it safely, we reduce scheduling errors by an estimated 30%. That’s fewer missed treatments, fewer patient complaints, fewer support tickets.”

“And the macro flow?”

“Scheduling feeds into the medication tracking module. Better scheduling means patients are where they’re supposed to be when medications are administered. The two systems compound.”

“Now you’re speaking Riverton.” Edward stood and walked to the window. “The model is more powerful. But the discipline doesn’t change. We start with outcomes, not capabilities. We map the flow before we optimize the pieces. The AI amplifies what we already know, but only if we know what we’re trying to accomplish.”

“So the framework matters more, not less.”

“Exactly. A year ago, AI could help with pieces. Now it can help with systems. But only if you know what system you’re trying to build. Only if you’ve mapped where work gets stuck. Only if you have domain experts who can validate what it generates.”

He turned back to Rachel. “Call a meeting. Everyone on the AI-SDLC Board. I want to understand what this means for our roadmap. And I want every proposal framed as a business outcome, not a capability demo.”

Monday, February 23, 2026 – 2:00 PM – Conference Room B

The AI-SDLC Board gathered around the table. Edward, Rachel, Johnny Morrison, Linda Park, and Dr. Amira Patel from Compliance.

“I’m going to show you something,” Edward said. “And then we’re going to talk about what it means. Not what it can do. What it means for our business outcomes.”

He demonstrated the Opus 4.6 capabilities. The architectural analysis. The refactoring suggestions. The speed.

Johnny Morrison leaned forward, his skepticism visible. “This is impressive. But it’s also dangerous. We don’t have governance frameworks for this level of capability.”

“Wrong framing,” Edward said. “You’re talking about the tool. What’s the business outcome we’re trying to achieve?”

Johnny paused. It was the question everyone at Riverton had learned to expect. No one presented a capability without connecting it to a measurable result. No one proposed an improvement without mapping it to the macro flow.

“Fair point.” Johnny sat back. “The business outcome is faster delivery of patient-facing features. Fewer medication errors. Better scheduling. Reduced support burden.”

“And what’s stopping us from achieving those outcomes today?”

“Legacy systems we’re afraid to touch. Technical debt we’ve been accumulating. The patient scheduling module that’s been a bottleneck for eighteen months.”

“Now we’re having the right conversation.” Edward pulled up the board charter. “The AI-SDLC Board exists to reduce toil, reduce risk, and deliver better software outcomes. That mission doesn’t change because the tools got more powerful. The question is always the same: what are we trying to accomplish, and what’s stopping us?”

“So what’s different with this model?”

“The amplification factor.” Rachel took over. “Before, AI could help with individual tasks. Code generation, documentation, testing. Now it can help with system-level thinking. Architecture. Integration. Optimization. But only if we frame the problem correctly.”

“Which means starting with the macro flow,” Edward added. “The medication tracking module worked because we’d already mapped the value stream. We knew the business outcome: reduce medication errors. We knew what was stopping us: an eighteen-month backlog. The AI didn’t replace that understanding. It accelerated the solution. Same discipline applies here.”

Dr. Kapur spoke up. “What about compliance? If the AI is generating architectural suggestions, how do we validate they’re HIPAA-compliant?”

“The same way we always do. Human review. Domain expertise. The AI is a tool, not an authority.” Edward paused. “But here’s what changes: the review gets faster because the AI can flag potential issues before we even look. It’s not replacing the compliance check. It’s enhancing it.”

Johnny was quiet for a long moment. Then: “What do you propose?”

“Controlled expansion. We take three teams that have already been through value stream mapping. We give them access to Opus 4.6 with specific guardrails. We measure the results. If it works, we scale.”

“And if it doesn’t work?”

“Then we learn why and adjust. That’s what the 90-day proof points are for.”

The board voted. Four to one in favor. Johnny abstained rather than oppose.

After the meeting, Johnny caught Edward in the hallway.

“I’m not convinced this is safe,” he said.

“I know.”

“But I’m also not convinced you’re wrong.” Johnny’s expression was complicated. “The approach you’ve built, the value stream mapping, the board structure, it’s more rigorous than anything I’ve seen. If anyone can make this work, it’s this team.”

“That’s not a ringing endorsement.”

“It’s the best I can do.” Johnny extended his hand. “Don’t make me regret it.”

Edward shook it. “I won’t.”

Tuesday, February 24, 2026 – 6:00 PM – Edward’s Home Office

That night, Edward sat in his home office, staring at his laptop.

The Opus 4.6 results were still open. The architectural analysis. The optimization suggestions. The speed.

Jennifer appeared in the doorway. “You’ve been in here for two hours.”

“I’m trying to understand something.”

“What?”

“Why this feels different.” Edward turned to face her. “Every AI advancement for the past two years has been incremental. Better code generation. Faster documentation. Improved testing. But this…” He gestured at the screen. “This is a step change. The model isn’t just executing tasks. It’s reasoning about systems.”

“Is that good or bad?”

“Both.” Edward stood and walked to the window. “It’s good because it amplifies everything we’ve built. The value stream mapping. The domain expertise. The process improvements. Teams that have done the hard work of understanding their own processes can now move faster than ever.”

“And the bad part?”

“Teams that haven’t done that work will fall further behind. The gap between organizations that understand their processes and organizations that don’t is about to get much wider.”

Jennifer was quiet for a moment. “You’re thinking about Marcus.”

“I’m always thinking about Marcus.” Edward sighed. “He’s five months from an IPO, and he’s never mapped his value stream. He doesn’t know where work gets stuck. He’s protecting a trajectory instead of examining it.”

“Can you help him?”

“I’ve tried. At spring break. Several times since. Every time I bring it up, he says ‘after the IPO.’” Edward shook his head. “You can’t help someone who thinks they’ve already won.”

“What happens when he finds out he hasn’t?”

“I don’t know. But I think we’re about to find out.”

Wednesday, February 25, 2026 – 10:00 AM – Engineering Floor

That Wednesday, Edward gathered the pilot teams.

“I want to share something with you. Yesterday, the AI-SDLC Board approved a controlled expansion of our approach. Three teams. Opus 4.6 access. Specific guardrails.”

Murmurs rippled through the room.

“But before we talk about what the model can do, let’s talk about what we’re trying to accomplish.” Edward walked to the whiteboard. “What are the business outcomes we’re pursuing?”

A senior engineer raised her hand. “Reduce medication errors. That’s the north star.”

“Good. What else?”

“Improve patient scheduling accuracy. Reduce support ticket volume. Faster time-to-market for patient-facing features.”

“Those are business outcomes.” Edward wrote them on the board. “Now, where does work get stuck in achieving those outcomes?”

The team called out bottlenecks. Legacy systems. Compliance reviews. Integration testing. Code review queues.

“This is how we think at Riverton. What outcome are we chasing? Where does work actually get stuck? What constraints are real and which ones did we invent? What ships this week?” Edward circled the bottlenecks. “The new model is more powerful than anything we’ve worked with. It can reason about systems, not just tasks. It can suggest architectural improvements, not just code fixes. But that makes the discipline more important, not less.”

“Why?” someone asked.

“Because it’s tempting to get excited about capabilities. To show off what the AI can do. To measure task improvements in isolation.” Edward’s voice was firm. “That’s not how we work. Every improvement connects to a business outcome. Every optimization maps to the flow. If you can’t explain how a change reduces days to ship or improves patient care, you haven’t finished thinking.”

He drew a simple diagram: a foundation labeled “Business Outcomes” with “Macro Flow” above it and “AI Capabilities” at the top.

“This is what we’ve built. The foundation is knowing what we’re trying to accomplish. The middle layer is understanding how work flows through our systems. The AI capabilities sit on top. They amplify the layers below.”

He drew another diagram: “AI Capabilities” floating with nothing beneath it.

“This is what happens when you adopt AI without the foundation. Impressive demos. Fast task completion. No connection to business results. One strong wind, a competitor who actually understands their process, and it all collapses.”

“What’s the strong wind?” Rachel asked.

“Reality. A customer who needs something you can’t deliver because you optimized tasks without understanding the flow.” Edward set down the marker. “Opus 4.6 is a gift. But only if we use it to accelerate outcomes, not to skip the hard work of knowing what outcomes we’re pursuing.”

Thursday, February 26, 2026 – 7:00 PM – Webb Family Dock

After dinner, Edward and Marcus walked out to the dock.

The evening air was warm, the Intracoastal still and dark. They’d stood here a hundred times over the years, at cookouts, after football games, during late-night conversations that ranged from business to family to the meaning of everything.

“Five months to the bell,” Marcus said.

“Are you ready?”

“Ready as I’ll ever be.” Marcus stared at the water. “Victoria keeps asking about AI strategy. Prakash keeps bringing up Project Prometheus. Even Sarah’s worried.” He shook his head. “But I know what I’m doing. We’ve already won. We just need to execute.”

“What if the surprise is coming whether you’re ready or not?”

Marcus turned. “What do you mean?”

“The approach I’ve been developing. Value stream mapping. Looking at where work actually gets stuck.” Edward paused. “The pilot teams are seeing 40% improvement. But the honest number across the whole org is 10%. The teams I’m personally in the room for are transforming. The rest are struggling.”

“So it works but it doesn’t scale.”

Edward blinked. Marcus had cut right to it.

“That’s… yeah. That’s the problem I’m trying to solve.”

“That’s great for healthcare IT. We’re a startup. We move fast already.”

“Have you mapped your value stream?”

“We don’t need to. We’re cloud-native.”

“That’s an architecture choice, not a process metric.” Edward stepped closer. “Marcus, do you know how long it actually takes from idea to production? Have you measured it?”

Marcus didn’t answer. He’d never measured it.

“What if five months is too late?”

“It won’t be.” Marcus’s voice hardened. “I know this industry. I know our competitors.”

“You know what you knew a year ago. The question is whether the world is still the same.”

They stood in silence.

“Five months,” Marcus said finally. “Then all of this becomes permanent. Something I can give my kids.”

“I hope you’re right.”

“I’m going to ring that bell. When I do, all of this, worries, rumors, won’t matter.”

“Come on,” Marcus said. “The kids want to play cards.”

They walked back toward the house.

Thursday, February 26, 2026 – 10:00 PM – Back Deck

After the Johnsons drove home, Sarah found Marcus on the deck, staring at his boat.

“Edward tried to help you. To tell you about what he’s been doing.”

“He’s mapping value streams while I’m running a company. Different games.”

“Maybe they’re the same game.”

“They’re not.” Marcus didn’t turn around. “Five months, Sarah. That’s what matters. Everything else is noise.”

Sarah stood in the doorway for a long moment.

“I love you,” she finally said.

“I love you too.”

She went inside.

Chapter 7: The Point of No Return

January – June 2026

MARCUS

Friday, January 9, 2026 – 9:00 AM – Axiom Headquarters, Conference Room

The S-1 filing happened on a cold January morning.

Catherine Bell stood in the conference room with Diana Reeves and the legal team, watching as the final documents were transmitted to the SEC. Marcus was beside her. this was the moment she’d been hired for, and she wanted the technical leadership visible.

“That’s it,” Diana said. “We’re officially in the quiet period. No more public statements until the IPO.”

“How long until we’re through the SEC review?” Catherine asked.

“Four to six weeks for initial comments. Then we iterate. Then we price.” Diana looked at her. “Six months, Catherine. Maybe less if everything goes smoothly.”

Catherine nodded, satisfied. Two years of execution, and this was the result. The founders who’d built the product but couldn’t build a company were long gone. Kyle checking in quarterly from his “advisory” role, Darren fully cashed out and running his own small fund. She’d turned their chaos into a machine, and the machine was about to go public.

Marcus glanced at the stack of documents on the table. the S-1 was hundreds of pages, including thirty-two pages of risk factors the lawyers had insisted on. Competition from legacy providers who may modernize their platforms. Customer concentration risks. Technology obsolescence. Dependence on key personnel. Every conceivable way the company could fail, spelled out in excruciating legal detail.

“The risk factors are comprehensive,” Diana said, following his gaze. “Whatever happens, we’ve disclosed it. That’s what protects us.”

Protects us from lawsuits, Marcus thought. Not from actually being wrong.

Six months. The countdown that had been abstract for so long was suddenly, terrifyingly real.

“Let’s tell the team,” Catherine said. “This is their moment too.”

Friday, January 9, 2026 – 11:00 AM – Axiom Headquarters, Main Auditorium

The all-hands announcement was electric.

Marcus stood in front of three hundred employees. the largest gathering Axiom had ever held. with a PowerPoint slide behind him showing one word: IPO.

“This is it,” he said. “The moment we’ve been building toward. In six months, Axiom Logistics is going public. We’re going to ring the bell at the NYSE. We’re going to show the world what we’ve built.”

The applause was thunderous. People were crying, hugging, cheering. These were engineers and product managers and customer success reps who’d poured years into the platform, who’d sacrificed weekends and holidays and personal time to make this happen.

Marcus let the moment wash over him. This was why he’d worked so hard. This was what it all meant.

“But we’re not there yet,” he continued, and the room quieted. “Six more months of execution. Six more months of discipline. Clean quarters, predictable growth, no surprises. We’ve come too far to stumble at the finish line.”

More applause. Marcus smiled and stepped back from the microphone.

In the front row, Prakash Venkataraman sat with his arms crossed, not clapping.

Tuesday, March 17, 2026 – 2:00 PM – Axiom Boardroom

The spring board meeting happened in March.

Victoria Hartwell raised her hand during the strategic update. “Marcus, I’ve been getting questions from other board members at my companies. They’re asking about Project Prometheus. Private demos under NDA, a shell company called MAI Research targeting our customers. What’s our current assessment?”

Marcus had prepared for this. He’d been preparing for it for months.

“Victoria, we’ve been tracking these rumors for six months. Some stealth startup. probably well-funded, possibly backed by private equity. is running demos and making noise. That’s what startups do.” He pulled up a slide showing his competitive analysis. “But there’s no product in market. No customers using it in production. No revenue. It’s vaporware designed to create uncertainty before our IPO.”

“Our competitive intelligence says there’s a pattern. Shell companies in Delaware, aggressive hiring through intermediaries, engineers from legacy freight companies going dark online. Someone is building something big.”

“That’s speculation.” Marcus kept his voice calm, confident. “What we know for certain is that whoever’s behind Project Prometheus hasn’t shipped anything. They have demos, not customers. Presentations, not revenue. That’s not what winning looks like. that’s what fundraising looks like.”

Victoria tilted her head, then nodded. “I hope you’re right.”

“I am.”

Thursday, April 9, 2026 – 10:00 AM – Hartley Shipping Headquarters, Manhattan

The customer meeting in April was a warning Marcus chose not to hear.

Hartley Shipping was back. the same Fortune 500 company whose CTO had mentioned Meridian’s silence last summer. But this time, Margaret Sullivan wasn’t laughing about COBOL developers retiring.

She arrived with a folder of printed materials and an expression that made Marcus’s stomach tighten.

“Marcus, we need to talk about our contract.”

“The renewal? That’s not until. “

“I signed a one-year contract with an option to renew. That option comes up in ninety days.” Margaret set the folder on the table. “Where are we on the features you committed to six months ago?”

Marcus felt heat rise to his face. The features. The AI-powered route optimization, the predictive capacity planning, the natural language interface. He’d promised them in October to secure the renewal. They were nowhere close to delivery.

“We’ve made significant progress on the roadmap. “

“Have you?” Margaret opened the folder. “Let me show you what we received last week.”

She spread documents across the conference table: screenshots of a modern interface, capability comparisons, pricing sheets. All branded with a sleek logo Marcus didn’t recognize. a stylized “P” in a circle. Project Prometheus.

“MAI Research LLC sent them directly. To our procurement team, our CEO, our board.” Margaret’s expression was grim. “Free migration from Axiom, free training, free support. Ninety-day switchover guaranteed. We still don’t know who’s actually behind it. they won’t say, and the NDA we signed for the demo forbids us from sharing specifics. But Marcus…” She leaned forward. “They’re specifically targeting Axiom customers. Whoever they are, they know exactly who we are and what we need.”

Marcus felt ice in his stomach. Free migration. Free training. Free support. Targeting a competitor’s customers with aggressive offers to switch.

This is our playbook, he realized. This is exactly what we did to Meridian in 2022. Exactly.

He opened the materials. Every feature he’d promised Hartley. the ones nowhere close to delivery. was already built in Project Prometheus. Plus ten more features Axiom hadn’t even scoped yet.

Someone knows our playbook. Someone is using it against us.

His mind went to Derek. The silence about where he was going. The excitement Prakash had described. “The future of how software gets built.”

Was it Derek? Did he take our playbook to whoever’s behind this?

“This is vaporware. Some stealth startup trying to create uncertainty before our IPO.”

“One of my engineers sat through a live demo last week. It looked real, Marcus. Production-ready.” Margaret gathered her materials. “I’m not renewing my option. Not until I see you actually deliver what you promised.”

She paused at the door. “You know what my team calls you now? ‘Business casual.’ Like you’ve got a dress code. Like the scrappy startup that won our business is gone, and now we’re dealing with just another slow-moving vendor.” She shook her head. “We picked you because you were fast. Because you shipped. Now you’re slower than the legacy vendors we left. At least they had an excuse. they were dinosaurs. What’s yours?”

Marcus had no answer.

“And if whoever’s behind Project Prometheus goes live before you do…”

She didn’t finish the sentence. She didn’t have to.

After she left, Marcus sat alone in the conference room, staring at the empty chair.

The features we committed to six months ago are nowhere close to delivery.

She signed a one-year contract with an option to renew.

Ninety days.

It wasn’t possible. You couldn’t rebuild a platform in fourteen months. You couldn’t transform a forty-year-old company in fourteen months. The fundamental constraints of software development didn’t allow it.

It took us four years, Marcus thought. Four years. That’s what I’ve been telling everyone. Four years to build what we have. Four-year head start. Four-year moat.

Unless they changed the constraints.

Unless they found a way to move faster than anyone thought possible.

Unless what took four years in 2020 could be done in fourteen months in 2026.

Marcus pushed the thought away. The IPO was three months away. There was no time for doubt now. No time for questions. Only time for execution.

The four-year moat had always been his answer. Now it was starting to feel like an anchor.

Tuesday, April 21, 2026 – 6:00 AM – Marcus’s Home Office

Derek Huang’s resignation letter arrived early in the morning.

Marcus found it in his inbox at 6 AM, timestamped from the night before. The subject line was simple: Resignation – Effective April 30.

April 30. The day Derek’s options fully vested. Not a coincidence.

Marcus,

I’m resigning from Axiom, effective end of month.

I’ve tried for a year to have this conversation with you. Every time I raised concerns about AI, you said “after the IPO.” Every time I proposed experiments, you said “protect the trajectory.” Every time I warned about competition, you said “they’re dying.”

I no longer believe “after the IPO” is a strategy. I believe it’s a deferral that will cost this company its future.

I’ve been building with agents at home for the past year. Side projects. Open source contributions. Learning what’s possible when you’re not afraid to experiment. I’ve become quite skilled at it. and I miss building. I miss the craft of writing software, not just managing people who write software.

I’ve accepted a position as a Staff Engineer at another company. Not a VP role. Not management. Just building. with tools that actually leverage what’s possible in 2026, so I’ll still have relevant skills in 2028.

You wouldn’t let my org use these tools here. So I’m going somewhere that will.

Before you try to convince me to stay: my shares will be fully vested on April 30. Even if the IPO tanks by fifty percent, I’m set for life. Money isn’t why I’m leaving. I’m leaving because I want to build.

I wish you well.

Derek

Marcus read the letter three times, his coffee growing cold on his desk.

Derek Huang. One of the first five engineers Marcus had hired once Axiom became a real company instead of two founders living on adrenaline. Four years of building the platform that made everything else possible. The ambitious one who’d always been looking for the next level.

Gone. Not to a bigger VP role. to an IC position. A Staff Engineer. He’d rather step down from leadership than stay somewhere that wouldn’t let him build with modern tools.

To where? Derek didn’t say.

He called Derek immediately. This time, Derek answered.

“Marcus.”

“Derek, don’t do this. We can work something out. More equity, retention bonus, whatever you need. Name your number.”

There was a long pause. Then Derek said: “It’s not about money. My shares vest in nine days. Even if the IPO tanks by half, I’m set.”

“Then what? What do you want that I’m not offering?”

“I want to build. With modern tools. With agents and copilots and everything you’ve been saying ‘after the IPO’ about for a year.” Derek’s voice was flat, exhausted. “You’re offering me more equity in a company that’s about to become obsolete. I’m not interested in being rich and irrelevant.”

“We’re not becoming obsolete. “

“Marcus.” Derek cut him off. “You haven’t shipped a major feature in eight months. Your best engineers are leaving for places that let them use AI tools. Your customers are asking questions you can’t answer. And you’re still saying ‘after the IPO’ like the IPO is going to fix everything.”

“It will. Once we have public capital. “

“Once you have public capital, you’ll have public scrutiny. Quarterly earnings calls. Analysts asking why your competitors are moving faster. The IPO isn’t the finish line. It’s the starting gun for a race you’re not prepared to run.”

Marcus felt ice in his stomach. “Where are you going?”

“Somewhere that’s asking the right questions. That’s all I’ll say.” Derek paused. “I hope I’m wrong about Axiom. I really do. But I’ve been waiting a year for you to start asking questions, and you’re still giving answers.”

The line went dead.

Marcus stared at his phone for a long time.

You’re offering me more equity in a company that’s about to become obsolete.

The IPO isn’t the finish line. It’s the starting gun for a race you’re not prepared to run.

At nine o’clock, he gathered the leadership team and told them. The shock on their faces mirrored what he was feeling inside.

“We’ll find a replacement,” Amanda Wong said. “There are great candidates out there.”

“In the middle of the quiet period? While we’re preparing for the IPO?” Marcus shook his head. “We can’t. We’re going to have to promote from within. At least until after we’re public.”

He looked at Prakash Venkataraman. “Prakash, you’ve been here since the beginning. You know the platform better than anyone. Will you take over as VP of Engineering?”

Prakash hesitated. The pause lasted a beat too long.

“Of course,” he finally said. But there was no enthusiasm in his voice. No pride. Just resignation.

“What do we tell the board?”

“The truth. Derek had personal reasons for leaving. We wish him well. Prakash is stepping up. The transition plan is in place.”

“And the S-1?” Amanda asked. “Legal is asking if we need to file an amendment.”

Marcus felt his jaw tighten. The lawyers had been clear: any material change to the company during the registration period required disclosure. A VP of Engineering departure. especially one who’d been there four years. was arguably material.

“File the amendment,” he said. “Standard language. Executive departure, transition plan in place, no material impact to operations.”

It wasn’t entirely a lie. But it wasn’t the truth either.

Thursday, April 30, 2026 – 5:47 PM – Axiom Headquarters, Engineering Floor

Derek’s last day.

Marcus found him at his desk, the one he’d sat at for four and a half years, now stripped clean. A single cardboard box held whatever he’d decided to take. Not much.

“I thought you’d already left.”

“Just finished.” Derek stood up, tucked the box under his arm. “Wanted to wait until the floor cleared out. Less awkward that way.”

They stood there, two men who had built something together, watching it end.

“You were one of the first five,” Marcus said. “You and Prakash. I hired you out of that startup that was falling apart. You stayed up three nights straight to get our first demo working.”

“I remember.”

“I keep thinking about what you said on the phone. That the IPO is the starting gun, not the finish line.” Marcus paused. “What if you’re right?”

Derek stopped walking. For a moment, the exhaustion and frustration fell away, and he stood a little straighter.

“Then you still have time. The IPO’s in two months. You could start asking questions now. Really asking them. Not ‘after the IPO.’ Now.”

“The board would never. “

“The board doesn’t have to know everything you’re thinking about.” Derek set down the box. “Look, you’re not going to change the S-1. You’re not going to delay the roadshow. But you could start listening differently. Start noticing what your engineers are actually doing. Start asking what’s stopping you from shipping.”

Marcus was quiet for a long moment. “Where are you going? You never told me.”

“A company that’s trying to do what Meridian’s doing. Small team. Modern tools. Asking questions instead of giving answers.” Derek picked up the box again. “I can’t tell you more than that. NDA.”

“Is it going to work?”

“I don’t know. That’s what makes it interesting.” Derek extended his hand. “Goodbye, Marcus. I hope you prove me wrong about Axiom. I really do.”

Marcus shook it. “And if I don’t?”

“Then maybe we’ll work together again someday. When you’re ready to build instead of protect.”

Derek walked out through the engineering floor, past the empty desks of the teams he’d led, past the whiteboards covered in roadmaps that would never ship, past the future he no longer believed in.

Marcus watched him go until the elevator doors closed.

Start asking what’s stopping you from shipping.

He went back to his office and pulled up the roadmap. Looked at the features that had been “in progress” for six months. Looked at the customer requests that had been pushed to “after the IPO.”

Then he closed the document and went back to the IPO preparation materials.

There would be time for questions later.

Friday, May 1, 2026 – 2:17 AM – Marcus’s Home Office

Marcus sat in the dark, staring at a blank document.

The house was silent. Sarah asleep. The boys asleep. Even the neighborhood was quiet, that deep Florida stillness that settled over everything after midnight.

He typed two words: Dear Catherine

Then he stopped.

He’d been thinking about this for hours. Since Derek walked out. Since Margaret Sullivan called him “business casual.” Since Prakash looked at him with that expression that said he knew something Marcus didn’t want to admit.

He started typing.

I’m writing to inform you of my intention to resign from my position as Chief Information Officer, effective immediately.

Over the past year, I have repeatedly raised concerns about our competitive position, our technical capabilities, and our ability to respond to market changes. Those concerns have been dismissed, deferred, or overruled. I no longer believe that remaining in this role serves the company or its shareholders.

The decisions made during my tenure, particularly the prohibition on AI development tools and the focus on IPO preparation over product innovation, will have consequences that become apparent in the coming months. I do not wish to be associated with those consequences.

He read it back. It was honest. It was accurate. It was also career suicide.

Resigning two months before an IPO. Walking away from thirteen million dollars in equity. Admitting publicly that he’d lost faith in the company he’d helped build for five years.

Catherine would spin it as instability. The board would question his judgment. The industry would whisper that he’d cracked under pressure. And Sarah would have to explain to MJ and Isaiah why they weren’t getting the financial security their father had promised.

He thought about Derek’s words. The IPO isn’t the finish line. It’s the starting gun for a race you’re not prepared to run.

He thought about Margaret Sullivan. At least the dinosaurs had an excuse. What’s yours?

He thought about Prakash, staring at industry feeds, watching everyone else use tools they’d been forbidden to touch.

He thought about his grandfather’s ranch. The old man had never run from anything in his life. Had never quit a job, abandoned a responsibility, walked away from a fight. Marcus had been raised to finish what he started, no matter the cost.

Was resignation courage or cowardice? Was it admitting the truth or running from consequences?

His cursor blinked at the end of the letter.

He could send it. Right now. Copy Catherine, Diana, the board. Burn the whole thing down and walk away clean. Find a company that was asking the right questions. Start over at forty-five with nothing but his reputation and his skills.

Or he could stay. See it through. Hope he was wrong about everything. Hope the IPO succeeded and the stock held and the competition never materialized. Hope that “after the IPO” actually meant something.

The cursor blinked.

Marcus thought about thirteen million dollars. About the house. About MJ’s college. About the retirement accounts they’d emptied.

He thought about the look on Sarah’s face if he told her he’d walked away from all of it.

He highlighted the letter. All of it.

He pressed delete.

The screen went blank.

I’ll stay, he told himself. I’ll see it through. Maybe I’m wrong. Maybe everything works out. Maybe Derek was just bitter and Margaret was just frustrated and Prakash is just tired.

Maybe.

He closed the laptop and sat in the dark for a long time, wondering if he’d just made the bravest decision of his life or the most cowardly.

Thursday, April 23, 2026 – 10:30 PM – Webb Family Home

Marcus got home late, again.

The house was quiet. Sarah already in bed, Isaiah’s light off, MJ’s door closed. He dropped his bag in the hallway and headed for the kitchen, thinking about a bourbon and some time alone with his thoughts.

MJ was sitting at the kitchen table, basketball shoes still on, a glass of water untouched in front of him.

“Hey.” Marcus stopped, surprised. “What are you doing up?”

“Waiting for you.”

Something in MJ’s voice made Marcus set down his bag. He sat across from his son. sixteen now, taller than Marcus, with the same Oklahoma stubborn jaw.

“What’s going on?”

“I had my best game tonight. Twenty-three points. Eight rebounds. Coach said I might get looked at by scouts next year.” MJ’s voice was flat. “You weren’t there.”

“The IPO. “

“It’s always the IPO. Before it was the funding round. Before that it was the board meeting. Before that it was some customer thing.” MJ looked up, and Marcus saw something in his son’s eyes he’d never seen before: not anger, not resentment, but something worse. Exhaustion. Resignation.

“You’re always going to be at the next thing, aren’t you? There’s always going to be something more important than us.”

“That’s not fair. Everything I’m doing is for this family. “

“Is it?” MJ cut him off. “Or is it for you? Because Isaiah’s been struggling in school and you haven’t noticed. Mom’s been doing everything alone and she won’t say it but she’s tired. And I stopped telling you about my games six months ago because you stopped asking.”

Marcus felt the words land like punches.

“I…” He didn’t know what to say. “I thought you understood. The IPO, the equity. it’s our future. It’s college funds and financial security and. “

“Dad.” MJ looked at him. “I don’t care about the money. I care about you being there. Being present. Knowing what’s happening in my life.” He stood up, leaving the water untouched. “But you’re not going to change. Not until the IPO. And then it’ll be something else.”

“MJ. “

“It’s fine.” The word carried the weight of acceptance. “I just wanted you to know. When you’re counting all your millions someday, I want you to remember that we asked you to show up and you didn’t.”

He walked out. Marcus heard his footsteps on the stairs, the soft click of his bedroom door.

The kitchen was silent.

Marcus sat there for a long time, staring at MJ’s abandoned water glass. His son had learned to stop expecting him. Had made peace with his absence. Had given up asking.

Everything I’m doing is for this family.

He’d believed that. He still believed that.

But sitting in his kitchen at 10:30 PM, three months from the IPO that was supposed to make it all worth it, Marcus wondered for the first time if he’d been lying to himself.

When you’re counting all your millions someday, I want you to remember that we asked you to show up and you didn’t.

He thought about the games he’d missed. The dinners he’d worked through. The weekends he’d spent in his office while his sons grew up without him.

After the IPO, he told himself. After the IPO, I’ll be present. I’ll coach MJ’s team. I’ll help Isaiah with his homework. I’ll be the father I’ve been promising to be for four years.

After the IPO.

The phrase felt hollow now. A promise he kept making to everyone. his family, his friends, himself. Always the same promise. Always after the IPO.

He poured a bourbon and drank it alone.

Saturday, April 25, 2026 – 7:00 AM – Webb Family Kitchen

Marcus was making coffee when MJ walked in. Early for a Saturday. The kitchen was quiet, Sarah still asleep, Isaiah at a sleepover.

“Dad. Can we talk?”

Marcus turned, surprised. After Thursday night, MJ had been avoiding him. Polite nods in the hallway. One-word answers at dinner.

“Of course.” Marcus poured a second cup, set it on the table. MJ sat but didn’t touch the coffee.

“I’ve been thinking about what I said. About you not being there.”

“MJ, I—”

“Let me finish.” MJ’s voice was calm. Measured. The voice of someone who’d rehearsed this. “I see what you’re going through. The stress. The late nights. The way you check your phone every thirty seconds like something’s about to explode.”

Marcus didn’t deny it.

“I’ve been watching you for four years, Dad. Since before the Series B. Since before you started talking about IPOs and equity and ‘after.’ I’ve seen what this company does to you.” MJ met his father’s eyes. “And I don’t want it.”

“Don’t want what?”

“Any of it. The stock options. The pressure. The corporate ladder where you climb and climb and never get to stop climbing.” MJ pushed the untouched coffee aside. “I don’t need a college fund.”

Marcus blinked. “What?”

“I’ve been thinking about Grandpa. About how he ran his ranch. Worked with his hands. Built something small that was his. No board of directors. No investors. No IPO.” MJ smiled slightly. “I want to be an electrician. Or a plumber. Learn a trade. Someday have my own little company. Webb Electric. Or Webb Plumbing. Just me. One shareholder.”

“MJ…” Marcus didn’t know what to say. His son, turning down the financial security Marcus had sacrificed everything to build.

“I’m not trying to hurt you, Dad. I’m trying to tell you that you don’t have to carry all this for me.” MJ stood. “I see the weight. I see what it costs you. What it costs our family. And I’m telling you: I don’t need the money. I need a dad who’s present.”

He walked to the door, then paused.

“Grandpa was happy, Dad. He worked hard, but he was home for dinner. He showed up for his kids. He didn’t have millions in the bank, but he had something you don’t have right now.” MJ paused at the door. “He had time.”

Marcus sat alone in the kitchen for a long time after MJ left. The coffee grew cold. The morning light crept across the table.

His son didn’t want the IPO. Didn’t want the equity. Didn’t want the future Marcus had been killing himself to build.

MJ wanted a plumber’s life. A small business. One shareholder.

Marcus thought about his father’s ranch in Oklahoma. The early mornings. The honest work. The way his dad had been there for every football game, every birthday, every moment that mattered.

He thought about all the moments he’d missed.

After the IPO, he told himself. After the IPO, I’ll be different.

But MJ’s words echoed: You don’t have to carry all this for me.

What if the weight he’d been carrying wasn’t for his family at all? What if it had always been for himself?

Wednesday, April 29, 2026 – 3:00 PM – Axiom Customer Success War Room

The Customer Success team had converted Conference Room D into a war room. Whiteboards covered with account names. Red, yellow, and green dots next to each one.

Too many red dots.

Amanda Wong had called the emergency meeting. She stood at the front of the room, pointing at the board.

“Atlantic Container Group. Renewal conversation yesterday. They asked point-blank: ‘What’s your response to Project Prometheus?’ I didn’t have an answer.”

“What did you tell them?” Marcus asked from the back of the room.

“I told them we’re evaluating the competitive landscape. That our platform is proven. That we’re committed to our roadmap.” Amanda’s voice was flat. “They said they’ve seen the demos. They said whoever’s behind Project Prometheus showed them real-time capabilities that beat our current platform by 4x on every metric.”

Marcus felt ice in his stomach.

“Then there’s Hartley Shipping.” Amanda moved to another section of the board. “Margaret Sullivan called this morning. She’s not renewing the option. She wants month-to-month until she sees our response to ‘the Prometheus situation.’“

“Month-to-month. On a three-year contract?”

“On a one-year contract with an option to renew. She’s exercising the option for thirty days, not twelve months.” Amanda paused. “She said she can’t commit to a vendor that’s moving slower than the dinosaurs they replaced.”

The room was quiet. Marcus counted the red dots on the board. Fourteen accounts. Fourteen conversations that had gone wrong in the past week.

“What are they asking for?” he said finally.

“The same thing. AI-powered route optimization. Predictive capacity planning. Natural language interface.” Amanda set down her marker. “The features we promised six months ago. The features that are nowhere on the current sprint.”

“Those are on the roadmap. Post-IPO.”

“Marcus.” Amanda’s voice was careful, the tone someone uses when delivering bad news they’ve been rehearsing. “The customers don’t care about post-IPO. They care about what we’re shipping now. And we’re not shipping anything they asked for.”

“We’re in a quiet period. We can’t change the roadmap during the quiet period.”

“Then we’re going to lose these accounts.” Amanda gestured at the board. “Atlantic Container is $2.4 million ARR. Hartley is $1.8 million. GlobalFreight Partners, $3.2 million. If they all churn, that’s $7.4 million in revenue at risk.”

“They won’t churn. They have switching costs.”

“The demos they’re seeing include free migration. Free training. Free support. Ninety-day switchover guaranteed.” Amanda paused. “The switching costs are being eliminated by whoever’s behind Project Prometheus.”

Marcus stared at the board. Red dots everywhere. Accounts he’d won personally, relationships he’d built over years, all of them suddenly at risk.

“Keep them warm,” he said finally. “Promise them updates. Tell them we’re working on it.”

“They’ve heard that before.”

“Then tell them again. We’re two months from the IPO. Once we have public capital, we can accelerate everything.”

Amanda looked at him for a long moment. Then she nodded and turned back to the board.

Marcus left the war room and walked to his office. He closed the door and sat in the dark for twenty minutes, staring at nothing.

Seven point four million dollars. At risk because he’d been saying “after the IPO” for over a year.

Monday, May 4, 2026 – 5:30 PM – Prakash’s Office

Two weeks into his new role, Prakash sat alone in the office that had been Derek’s.

The badge on his desk said “VP of Engineering.” The salary was better. The equity was significant. if the IPO went well, he could retire early.

If.

He opened a professional networking app on his phone, something he’d been doing more and more lately. His feed was full of former colleagues, engineers he’d mentored, people who’d left Axiom over the past year. They were all posting about the same things: agents in the SDLC, AI pair programming, autonomous code review, automated testing pipelines.

One post from a Stanford classmate: “My team just shipped in 3 days what used to take us 3 sprints. The agents handle the boilerplate, we focus on architecture.”

Another from a former Axiom engineer: “Finally working somewhere that lets me use the tools everyone else is using. Night and day difference.”

Prakash looked at the Jira board on his monitor. Sixty-three tickets in the current sprint. His teams typing every line of code by hand. Manual code reviews that took days. Test suites that ran for hours.

All his friends outside of work were using agents in the SDLC. Prakash was still pushing Jira tickets.

He opened a private browser window and navigated to the Project Prometheus marketing site. Someone had shared the link in a Slack DM that morning, marked “DO NOT SHARE,” which meant everyone had shared it.

The screenshots were beautiful. Clean interface, modern design, features that made Axiom’s platform look like it was built in 2019. Because it was.

He clicked on the “For Developers” section. There it was: “Built with AI-native tooling. Our engineers ship 4x faster using modern development workflows.”

Prakash thought about his teams. His engineers were good. Some of them were great. But they were fighting with one hand tied behind their backs, building software the way people built software three years ago while the rest of the industry had moved on.

He thought about Derek’s departure. The resignation letter that talked about wanting to build “with tools that actually leverage what’s possible in 2026, so I’ll still have relevant skills in 2028.”

Derek had been right. Prakash knew Derek had been right. But Prakash had stayed because the equity was too valuable to walk away from, and because Marcus was his friend, and because he’d convinced himself that “after the IPO” meant something.

Now he sat in Derek’s old office, pushing Derek’s old Jira tickets, watching Derek’s old warnings come true.

His phone buzzed. A text from his wife: “How was your day?”

He typed back: “Fine.”

It wasn’t fine. It hadn’t been fine for months. But what was he supposed to say? “I’m watching everything I’ve built for five years become obsolete while being forbidden to use the tools that could save it?”

He thought about the equity. At $16 a share, his stake would be worth over a million dollars. Enough to retire. Enough to never write another line of code.

But the stock had to hold. The IPO had to succeed. And every day, Prakash saw the gap widening between what Axiom was building and what the rest of the industry had already built.

Will my equity be enough to let me retire?

Or will it be worth nothing by the time I can sell it?

He closed the browser window and went back to the Jira board. Sixty-three tickets. Every line of code typed by hand.

The bell was two months away. He just had to hold on.

But holding on was starting to feel like drowning.

Monday, May 18 – Friday, June 19, 2026 – Global Roadshow

Marcus was oblivious to Prakash’s quiet despair. The IPO machinery demanded his attention.

Catherine led the roadshow. London, Singapore, Tokyo, San Francisco, New York. Private jets, luxury hotels, conference rooms with panoramic views. Institutional investors who controlled more money than most countries. Marcus joined for the technology deep-dives, the sessions where investors wanted to understand the platform architecture and competitive moat.

The pitch was the same everywhere: Axiom Logistics is the company that disrupted freight management. We’ve already won. The IPO is the proof.

The investors asked about competition. Marcus had his answers ready.

Meridian is a value stock paying four percent dividends. They’re trading at nine dollars, same price for a decade. Their customers are happy enough to stay, but nobody thinks they’re going anywhere. Our technology advantage is insurmountable.

The investors asked about AI. Marcus had his answers ready for that too.

We’re already modern. AI is infrastructure we can add. Post-IPO, we’ll have the resources to invest properly.

The investors nodded. They signed term sheets. They committed capital.

Friday, June 26, 2026 – 4:00 PM – Axiom Headquarters, Executive Conference Room

The pricing meeting happened.

“Sixteen dollars per share,” Diana Reeves announced. “Nine hundred fifty million dollar valuation. Marcus, your 1.4% stake is worth approximately thirteen million.”

Thirteen million dollars.

On paper. Still on paper. But in eight days, the paper would become real. The lockup would start. 180 days before he could sell. but the shares would be tradeable, valued, no longer theoretical.

Thirteen million meant paying off the house. Funding the boys’ college accounts. Rebuilding the retirement they’d raided during the lean years. Not the generational wealth he’d once imagined. but finally, finally secure.

Eight days from now, Marcus Webb would ring the bell at the NYSE. Eight days from now, the kid from Stillwater, Oklahoma would finally be okay.

Friday, June 26, 2026 – 10:00 PM – The Langham Hotel, Manhattan

He called Sarah from his hotel room.

“We did it,” he said. “Sixteen dollars. July 6th is official.”

“I’m so proud of you.” But there was something in her voice. a hesitation he didn’t want to examine.

“What’s wrong?”

“Nothing. I’m just… be careful, Marcus. The finish line isn’t always where you think it is.”

“The finish line is eight days away. I can see it.”

“I know.” She paused. “I love you.”

“I love you too.”

He hung up and stared out at the Manhattan skyline. The city sparkled below him, millions of lights representing millions of people, all of them unaware that Marcus Webb was about to achieve everything he’d ever wanted.

Eight days.

Everything was going according to plan.

Saturday, June 27, 2026 – 6:00 PM – First Class, JFK to Fort Lauderdale

Eight days.

Marcus settled into his first-class seat. he’d splurged on the upgrade, something he never would have done during the lean years. For two years he’d flown Southwest middle seats, hoarding credit card points and watching every dollar. Now, finally, he could breathe.

Thirteen million dollars. Enough to pay off the $50,000 equity loan. Enough to fund the boys’ college for real, not just on spreadsheets. Enough to rebuild the retirement accounts they’d emptied in 2021 and 2022. Enough to finally, finally exhale.

He watched the country pass beneath him in the fading light. He thought about Sarah’s words. the finish line isn’t always where you think it is. and pushed them away.

The finish line was visible now. Eight days.

He ordered another bourbon and closed his eyes.

Chapter 8: The Day Before

July 5, 2026

MARCUS

Sunday, July 5, 2026 – 3:30 PM – Henderson Residence, Fort Lauderdale

The Fourth of July weekend barbecue was winding down when Marcus’s phone buzzed.

He was standing in the Hendersons’ backyard, neighbors they’d known for years, with a cold beer in one hand and his phone in the other. American flags hung from the porch. Kids splashed in the pool. The smell of grilled burgers drifted through the humid Florida air.

The buzz was a news alert. Marcus glanced at it automatically, expecting something routine: market news, maybe, or political coverage.

Instead, he saw: BREAKING: Project Prometheus Revealed – Meridian Freight Behind Mystery Platform

The words didn’t make sense. He read them again.

Meridian. The dying company. The value trap. The four-percent dividend they paid because they had nothing else to offer investors.

The beer slipped from his hand and shattered on the patio. He didn’t notice.

His vision narrowed. The sounds of the party, the splashing kids, the laughter, faded into a distant hum. All he could see was the screen. All he could feel was his heart hammering in his chest.

He stepped away from the crowd, nearly tripping over a lounge chair, and found a quiet corner near the Hendersons’ fence. His hands were shaking as he opened the full article. His mouth had gone completely dry.

MeridianOne: Legacy Giant Was Behind “Project Prometheus” All Along

Meridian Freight, the forty-year-old logistics company many analysts had written off as dying, revealed today that it was behind the mysterious “Project Prometheus” demos that have been circulating under NDA for the past year.

The shell company MAI Research LLC, which had been approaching Axiom customers with private demos and migration offers, was a Meridian subsidiary all along. MAI stands for “Meridian AI.”

The new platform, MeridianOne, represents a ground-up reconstruction of Meridian’s entire technology stack. According to the company, the development took just 14 months, a timeline the company attributes to aggressive use of AI development tools.

“What took our competitors three years to build as a startup, we rebuilt in fourteen months,” said Meridian’s CEO. “AI wrote 80% of our code. We kept it secret because we wanted to build, not market. Now it’s time to ship.”

Sources say the development was led by a “tiger team” of just 14 engineers working outside Meridian’s traditional governance structures, with unlimited access to AI development tools. Among the team members was Harold “Harry” Thornton, 62, whose departure last year was widely reported as “Meridian’s last COBOL developer retiring.”

Fourteen months. Fourteen engineers.

The numbers hit Marcus like a physical blow. He’d spent two years saying it: It took us four years to build Axiom. Four years. No one can replicate that. We have a four-year head start.

Four years had been his moat. His certainty. His answer to every question about competition.

And Meridian, the “dying” competitor he’d dismissed for the past year, had done it in fourteen months. They’d been behind Project Prometheus the entire time. Every demo, every NDA, every approach to his customers. It was Meridian.

The silence hadn’t been them dying. It was them building.

Marcus scrolled down, his heart hammering.

Capability Comparison:
– Real-time tracking: Meridian 50ms, Axiom 200ms
– API response time: Meridian 10ms, Axiom 80ms
– Concurrent users: Meridian 100K, Axiom 25K

Every metric beat Axiom. Every single one.

The Migration Offer:
– Free migration from legacy Meridian systems
– Free migration from Axiom
– “Switch in 90 days or less”
– Data migration, training, support, all included

Free migration from Axiom. They were specifically targeting his customers.

Feature Roadmap (next 12 months):
– Predictive capacity planning
– Automated carrier negotiations
– Real-time route optimization
– Carbon footprint tracking
– Natural language interface
– …and ten more features Axiom hadn’t even scoped

Marcus read the article again. Then again. Then he opened other news sources. TechSignal, MarketWire, the wires. They all had the same story.

“Project Prometheus Unmasked: Meridian Was Building All Along”

“Legacy Giant Leapfrogs Industry Disruptor”

“Meridian’s AI Bet Pays Off as Axiom IPO Looms”

“MAI Research Revealed as Meridian Shell Company. Axiom Customers Were Being Poached for Months”

“Meridian Stock Surges 40% in After-Hours Trading. From $9 to $12.60”

The stock that had traded flat for a decade. The “value trap” paying four percent dividends. The company Marcus had dismissed as “paying shareholders to hold a dying asset.”

Up forty percent in one day.

The timing wasn’t an accident. They’d announced on Sunday, the day before Axiom’s IPO. Maximum visibility. Minimum response time. By the time the market opened tomorrow morning, every investor would have read these headlines. Every customer who’d been approached by “MAI Research” would know who they’d really been talking to.

Marcus walked to his car. His legs felt strange, disconnected, like they belonged to someone else. Sarah would wonder where he went, but he couldn’t face people right now. Couldn’t make small talk about summer plans and kids’ sports while his entire world collapsed.

He sat in the driver’s seat with the engine off. The Florida heat was already building inside the car, sweat prickling on his forehead, but he didn’t turn on the air conditioning. He didn’t do anything. He just sat there, phone in his lap, staring at nothing.

His hands were still shaking. He looked down at them, at these hands that had typed so many confident emails, signed so many contracts, shaken so many hands at investor meetings. The same hands that had built Axiom from nothing. The same hands that would ring the bell tomorrow morning.

He felt like he might vomit.

Project Prometheus. MAI Research. It was Meridian the entire time.

They were dying, he thought. Everyone said they were dying. I said they were dying.

Fourteen months. They rebuilt everything in fourteen months. While hiding behind shell companies and NDAs.

While I was saying “after the IPO,” they were asking the right questions.

While I was protecting my trajectory, they were redefining the trajectory.

While I was dismissing “some stealth startup,” they were rebuilding everything.

Sunday, July 5, 2026 – 4:00 PM – Marcus’s Home Office

The emergency board call happened.

Marcus had driven home and locked himself in his office. Sarah found him there, staring at his laptop, and wisely left without saying anything.

Catherine Bell was first on the line, her voice controlled but tight. She’d been in crisis mode before — Helix Health’s near-collapse, the regulatory scare at NovaTech — and the pattern was always the same: the first hour determined whether the organization panicked or held. Her job right now was to keep everyone holding.

“The board is assembling. Victoria, Richard, the Blackwood partners. Everyone.”

“What’s the play?” Marcus asked.

“We go forward. We have to. The mechanics are locked.”

Victoria Hartwell joined next. “I’ve been talking to the underwriters. They’re nervous but committed. Nobody wants to be the firm that pulled an IPO at the last minute.”

“Then we ring the bell,” Catherine said. Her voice was flat, almost mechanical. Inside, she was already running scenarios. Best case: the market shrugged off Meridian’s announcement and Axiom’s fundamentals carried the day. Worst case: the IPO priced down and she’d be managing a crisis she didn’t have the tools to solve. Either way, her tenure at Axiom had an expiration date. She’d known it since she read the MeridianOne press release at 4 PM — the sick recognition that she was on the wrong side of a structural shift. “We execute the plan. Whatever happens with the stock, we stay on message. Panic is contagious. Confidence is too.”

Richard Townsend spoke for the first time. He was the newest board member, PE background, brought in six months ago to strengthen governance. “Catherine, Marcus. I need to understand what we’re facing. This isn’t a competitor making noise. This is a ground-up platform rebuild announced the day before our IPO. That’s not coincidence. That’s strategy.”

Silence on the line. Marcus could hear the weight of it: board members around the country, all of them thinking the same thing. This is going to be a disaster.

“What’s our response?” Victoria asked finally. “What do we tell investors Monday morning?”

Catherine took over. “We tell them what we’ve been telling them all along. Meridian made an announcement. We’re evaluating it. Our fundamentals are strong. Our customer retention is solid. We’re committed to our roadmap.” She paused. “The story is execution. We’re the proven platform. The safe bet.”

“Is that still true?” Richard asked.

“It has to be,” Marcus said. The words felt hollow in his mouth.

The call ended. Marcus sat alone in his office, watching the afternoon light fade through the windows.

Catherine had sounded confident on the call. But Marcus knew her well enough by now to hear what was underneath. She was already calculating. Already thinking about what came next. She’d been hired to execute an IPO. After tomorrow, that job would be done, one way or another.

Whatever happened to Axiom after the bell rang, Catherine Bell would land on her feet. She always did.

Marcus wasn’t so sure about himself.

His phone was blowing up: text messages from board members, calls from analysts, emails from the communications team. He ignored all of them.

One message caught his eye. From Prakash Venkataraman.

I’m sorry it happened this way. I tried to warn you.

Marcus stared at the message for a long time. Then he deleted it.

Sunday, July 5, 2026 – 5:00 PM – Marcus’s Home Office

Sarah found him.

She came into the office quietly, closing the door behind her, and sat in the chair across from his desk. She didn’t say anything. She just waited.

“You heard,” Marcus said.

“I heard.”

“They were building. This whole time. While I was saying they were dying, they were building.”

“I know.”

“Derek tried to tell me. Prakash tried to tell me. You tried to tell me. Edward tried to tell me.” Marcus’s voice cracked. “I didn’t listen. I was so sure I already knew the answers.”

Sarah crossed to his side of the desk and knelt beside his chair, taking his hands.

“What are you going to do?”

“I don’t know.” The admission felt like surrender. “The IPO is tomorrow. I have to ring the bell knowing that our stock is going to crater. I have to stand there and smile and pretend everything is fine while Meridian destroys everything I built.”

“You don’t have to. We could. “

“I can’t not ring the bell. We’ve told investors. The team is flying to New York tonight. The machinery is in motion. There’s no way to stop it.”

“Then you ring the bell.” Sarah’s voice was steady, certain. “You ring it because that’s what you came to do. And then you figure out what comes next.”

“What comes next is six months of lockup. Watching the stock fall while I can’t do anything about it.”

“Then you watch. And you figure out what you learned. And you decide who you want to be on the other side of this.”

Marcus looked at his wife, really looked. The woman who’d believed in him since that night at The Rusty Anchor. The woman who’d watched him disappear into this obsession for over a year, who’d asked him to be present, who’d been dismissed every time.

“I’m sorry,” he said. “You were right. About all of it.”

“I know.” She kissed his forehead. “And we’re going to get through this together.”

Sunday, July 5, 2026 – 6:00 PM – 8:00 PM – Marcus’s Home Office

The evening was the longest of Marcus’s life.

He sat in his office and read every article, every analysis, every tweet about the Meridian announcement. The coverage was brutal. Industry analysts were calling it “the most significant competitive pivot in freight tech history.” Investors were questioning whether Axiom’s IPO should proceed. Customers were demanding answers.

Sunday, July 5, 2026 – 8:00 PM – Marcus’s Home Office

Edward called.

Marcus almost didn’t answer. But this was his best friend, the man who’d tried to warn him, the man whose approach he’d been dismissing for over a year.

“I saw the news,” Edward said. “I wanted to check in.”

“It’s bad, Ed.”

“I know.”

“They were building. This whole time. They were asking the questions I should have been asking.”

There was silence on the line. Then Edward said: “What are you going to do?”

“Ring the bell. Tomorrow morning. What else can I do?”

“After that?”

“I don’t know. Six months of lockup. Watching everything fall apart.” Marcus laughed bitterly. “You warned me. At the family dinner. On the boat. Every chance you got, you tried to tell me something was wrong.”

“I wasn’t trying to be right.”

“But you were. Those questions, that’s what Meridian did. They asked what I wouldn’t ask. They built what I couldn’t see.”

“Marcus…”

“I should have listened. I should have asked. I was so confident I already had the answers.” Marcus’s voice was barely a whisper now. “And now everything I built is ash. And I still have to ring that bell tomorrow.”

“Then ring it. And then call me. Whatever happens tomorrow, we figure it out together.”

“It won’t be the same.”

“No. It won’t.” Edward paused. “But you’re still my brother. That’s not changing.”

They hung up. Marcus sat in the darkness for a long time, thinking about questions he’d never asked.

Sunday, July 5, 2026 – 8:30 PM – Live appearance on cable financial news

Marcus had been scheduled for weeks to appear on his favorite cable news financial program, part of the official IPO marketing plan, approved by legal counsel and the underwriters. It was supposed to be a victory lap the night before ringing the bell.

Instead, every question was about Meridian.

“What’s your response to MeridianOne?”

Marcus stuck to the talking points his lawyers had reviewed. “We welcome competition. Our platform is proven. We’re focused on execution.”

“Did you see this coming?”

“The competitive landscape is always evolving. Our S-1 disclosed competitive risks, and we stand by our risk factors.” The legal team had insisted on that phrase.

“How does Axiom compete with AI-native architecture?”

“We’re committed to our technology roadmap. Post-IPO, we’ll have the resources to invest appropriately.” More lawyer-approved language.

His voice sounded hollow even to himself. The host’s skeptical expression said everything the lawyers wouldn’t let Marcus say.

Sunday, July 5, 2026 – 11:00 PM – Master Bedroom

Sarah found him still at his desk.

“Come to bed. Tomorrow is going to be long.”

“I can’t sleep.”

“Try.”

She led him to the bedroom, and they lay together in the darkness, not touching, not talking. Marcus stared at the ceiling, doing math in his head.

$13 million at opening. But after today’s news…

The stock might open lower than $16. The institutional investors might bail. The retail investors might panic.

And even if it opened at target, the trajectory was clear. His equity was going to evaporate. And he couldn’t sell for 180 days.

Six months of watching my net worth collapse. Six months of answering questions I don’t have answers to. Six months of learning exactly how wrong I was.

“I keep thinking about spring break,” he said.

“Which one?”

“Last year. Sophia’s stories. Edward leaning forward, asking questions. Me thinking, ‘That’s great for school projects.’” He closed his eyes. “Edward asked the right questions. I was too focused on protecting the IPO to ask any.”

“You couldn’t have known.”

“I should have asked. That’s the whole point. I should have asked: What if I’m wrong? What if the world is changing faster than I think? What if the dying competitor isn’t dying?”

Sarah found his hand in the darkness.

“Tomorrow, you ring the bell. And then we figure out what comes next.”

“What if there’s nothing next?”

“There’s always something next. That’s what you taught me. When MJ broke his arm and we thought his basketball season was over. When Isaiah failed that test and we thought he’d given up. You said, ‘There’s always something next. You just have to find it.’“

Marcus turned to look at her. In the darkness, he could barely see her face, just the outline, the familiar shape he’d loved for twenty years.

“I don’t know who I am without this,” he admitted. “Axiom. The IPO. The trajectory. It’s been everything for so long.”

“Then you find out who you are on the other side. And I’ll be there with you.”

She squeezed his hand. He squeezed back.

The alarm was set for 4 AM. The flight to New York left at 6. The bell rang at 9:30.

Marcus stared at the ceiling until the darkness began to fade, and then he got up to face the longest day of his life.

Monday, July 6, 2026 – 4:00 AM – Webb Family Home

The alarm went off. Marcus and Sarah dressed in silence, packed in silence, rode to the airport in silence.

The private jet was waiting on the tarmac. The sun was just starting to light the eastern sky.

Marcus boarded the plane that would take him to New York, to the bell, to whatever came after.

The questions he’d never asked were finally catching up with him.

Chapter 9: The Sound of Hollow Victory

July 6, 2026

MARCUS

Monday, July 6, 2026 – 9:28 AM – New York Stock Exchange Trading Floor

The NYSE platform was smaller than he’d imagined.

Marcus stood in the center of it, surrounded by camera crews and board members and the team that had flown up from Florida. Sarah was beside him in a dress he’d bought her for this moment, navy blue, elegant, confident. She held his hand so tight it almost hurt.

The floor below was chaos: traders at terminals, screens flashing numbers, the hum of capitalism in motion. Above, the American flag hung alongside the Axiom banner. Somewhere, a bell was waiting.

This was supposed to be the greatest moment of my career.

The thought came unbidden. Marcus pushed it away.

A NYSE official handed him the mallet, heavier than expected, polished wood and brass, and explained the protocol. Ring at exactly 9:30. Ring it hard. The cameras would flash. The floor would cheer. History would be made.

History is already made. It just wasn’t the history I planned.

“Two minutes,” the official said.

Marcus looked at Sarah. Her smile was fixed, professional, but her eyes told a different story. They’d barely spoken on the flight up. What was there to say?

Catherine Bell stood at the edge of the platform, her expression unreadable. Victoria Hartwell was beside her. Both nodded. We’re here. We’re doing this. See it through.

Marcus caught Catherine’s eye. She’d been the one to approve the S-1. The one who’d said “unless it’s a major risk, don’t change what’s working.” The one who’d silenced every technology discussion with “is this going to lose us customers in the next fifteen months?”

Now they were both about to find out.

The countdown began.

Monday, July 6, 2026 – 9:30 AM – New York Stock Exchange Trading Floor

Marcus Webb rang the opening bell at the New York Stock Exchange.

The sound was deeper than he expected, a resonant tone that seemed to vibrate through the entire building. The trading floor erupted in applause. Cameras flashed. Someone cheered.

Marcus smiled. He’d practiced this smile for weeks. It felt foreign on his face now, like wearing someone else’s expression.

The first trade appeared on the screen above: $16.00. The planned price. The price they’d told investors. The price that valued Axiom at $950 million and Marcus’s stake at $13 million.

*Maybe it will be okay. Maybe the market hasn’t absorbed yesterday’s news. Maybe. *

$15.95.

$15.80.

$15.50.

Marcus watched the number drift downward, unable to look away. There was no pop. No enthusiasm. No rush of demand that typically accompanied a successful IPO. Just a slow, steady decline as the market processed what everyone had read yesterday.

Meridian’s AI Bet Pays Off as Axiom IPO Looms

Legacy Giant Leapfrogs Industry Disruptor

The headlines were everywhere. Every investor had read them. Every trader knew.

By 10 AM, the stock was at $15. By 11 AM, $14. By noon, $13.

The celebration champagne sat unopened on a table in the corner of the platform. Nobody felt like celebrating.

Monday, July 6, 2026 – 11:00 AM – NYSE Trading Floor

Marcus spent the day on the trading floor, performing confidence.

He shook hands with investors who’d bought in. He answered questions from reporters with rehearsed non-answers. He smiled for photographers who probably knew they were capturing the documentation of a disaster.

“Marcus, what’s your response to Meridian’s announcement?”

“We welcome competition. Our platform is proven. We’re focused on execution.”

“What about the capability comparison? Their metrics beat yours across the board.”

“Benchmarks can be manipulated. Real-world performance is what matters. Our customers trust us.”

“Several analysts are questioning whether the IPO should have been delayed.”

“The market decides. We’re confident in our value proposition.”

The words tasted like ash in his mouth. He kept saying them.

At 2 PM, Victoria Hartwell pulled him into a quiet corner.

“The institutional investors are nervous. Three of them have called asking about our response plan.”

“What do you want me to tell them?”

“Something. Anything. Something that isn’t ‘we welcome competition.’“

Marcus looked at her, sharp, experienced Victoria, who’d asked the hard questions at board meetings and never quite trusted his answers. She’d been right to doubt. They’d all been right.

“Where’s Catherine?”

Victoria’s expression flickered. “She had calls to make. Investor relations. Damage control.”

Marcus understood what that meant. Catherine was already working the phones, not to save Axiom, but to protect her own reputation. She’d delivered an IPO. That was the deliverable. Whatever happened to the stock afterward was a different story, a different CEO’s problem.

“We don’t have a response plan,” he admitted. “Meridian rebuilt in fourteen months. We can’t match that. We don’t have the architecture. We don’t have the tools. We don’t have the mindset.”

Victoria leaned back in her chair.

“Then we figure it out after the bell. But right now, you need to stay on message. The market is watching.”

Marcus went back to the floor. The stock was at $14.

Monday, July 6, 2026 – 4:00 PM – NYSE Trading Floor

The closing bell rang.

Final price: $12.

Marcus watched the number lock in. 25% below the opening price, 25% below what he’d told investors, 25% below everything he’d promised.

The math was brutal.

At opening: 1.4% of $950M = $13.3M
At close: 1.4% of $712M = $10M
Lost in one day: $3.3M

And the lockup hadn’t even started. For the next 180 days, until early January 2027, he couldn’t sell, couldn’t hedge, couldn’t do anything except watch.

Ten million was still a lot of money. But it wasn’t what he’d promised Sarah. It wasn’t what would let them exhale. And if the stock kept falling. if it dropped another 25%, another 50%. the numbers stopped being life-changing and started being merely okay. Or worse.

The $50,000 equity loan was still on the house. The retirement accounts were still empty. The boys’ college funds were still theoretical. And now he had 180 days to watch his paper wealth evaporate.

$3 million gone in a day. And this is just the beginning.

Sarah found him standing at the window, looking down at Wall Street. The crowd had dispersed. The cameras had packed up. The story of the day had been written: Axiom IPO Meets Muted Reception Amid Meridian Announcement.

“The celebration is starting,” Sarah said. “At the hotel. You should come.”

“Is it a celebration?”

“It’s what we scheduled. The team is there. The board is there. People need to see you.”

“See me do what? Pretend everything is fine?”

Sarah didn’t answer. She just took his hand and led him to the waiting car.

Monday, July 6, 2026 – 6:00 PM – The Langham Hotel, Manhattan

The “celebration” at the Manhattan hotel was a funeral in formal attire.

Champagne flowed; someone had insisted. But nobody seemed to be drinking it. Canapés circulated on silver trays that returned mostly full. The Axiom banner hung on one wall, a reminder of what they’d come here to celebrate.

Marcus stood at the front of the room and raised a glass.

“To Axiom,” he said. “To the team that made this possible. To our next chapter.”

The applause was polite. The champagne tasted like ash.

He circulated through the room, shaking hands, accepting congratulations that felt more like condolences. The team members who’d flown up from Florida looked shell-shocked; they’d expected triumph and gotten something else entirely.

Near the bar, Marcus spotted a face he recognized. Kevin Tanaka, a senior architect who’d left Axiom six months ago. He was standing with a group Marcus didn’t know, wearing a lanyard that caught the light.

A blue lanyard. With a logo Marcus recognized from yesterday’s news.

MeridianOne.

Kevin saw him looking and had the grace to look embarrassed. He tucked the lanyard into his jacket pocket, but the damage was done. One of Marcus’s best architects, a man who’d helped build the core platform, was now working for the company that had just destroyed Axiom’s IPO.

How many others? Marcus wondered. How many of my people are already over there, building what I should have built?

He thought about something Edward had said at spring break, over a year ago. A story about a guy named Harold. Tape libraries and mainframes. Essential to ornamental in eighteen months.

Marcus had laughed at the story. He’d told Edward it wasn’t going to happen to them. They were already the disruptors. They were already winning.

Now he was standing in a hotel ballroom, watching his equity evaporate, seeing his engineers wearing competitor lanyards. Essential to ornamental. It had taken Marcus about sixteen months from that spring dinner to this moment. Almost exactly.

He turned away before Kevin could approach him. There was nothing to say.

Then the MarketWire notification hit his phone. He read it standing alone by the window, champagne untouched.

EXCLUSIVE: MeridianOne Built by Team of Just 14 Engineers

Meridian Freight’s new platform was developed by a “tiger team” of only 14 engineers working outside the company’s traditional governance structures, according to sources familiar with the project. The team had access to “any AI tool they wanted” and reported directly to the CEO.

“They gave us unlimited tool budget and told us to build,” said one team member. “No committees. No approval processes. Just build.”

The small team rebuilt what took competitors years in just 14 months, validating what AI development advocates have been claiming: that small, empowered teams with modern tools can dramatically outperform traditional development organizations.

Marcus read it twice. Three times.

Fourteen people.

He had four hundred engineers. Axiom had spent $40 million on engineering salaries last year alone. And fourteen people with AI tools had rebuilt everything in fourteen months.

The next paragraph hit even harder:

Among the team members was Harold “Harry” Thornton, 62, a former Meridian systems engineer who had been with the company for 40 years. Thornton’s departure last year was widely reported as “Meridian’s last COBOL developer retiring,” but sources confirm he joined the Project Prometheus team specifically for his deep domain knowledge of the legacy system.

Marcus felt the floor shift beneath him.

Harry Thornton. The COBOL developer. The joke at Hartley Shipping. Margaret Sullivan had laughed about it. “Maybe their last COBOL developer finally retired.”

He hadn’t retired. He’d been recruited. His forty years of domain knowledge, every edge case, every customer workflow, every undocumented behavior in the legacy system, had become the specification for the AI tools to rebuild against.

They didn’t just build faster. They built smarter. They knew exactly what to build because they had someone who’d lived in the old system for forty years.

Marcus looked around the room at his four hundred employees. The engineering managers. The senior architects. The product managers.

Fourteen people beat all of us. Fourteen people with the right tools and the right questions.

This is the future, Marcus realized. Not four hundred engineers in committees. Not twelve-month roadmaps and steering committees. Fourteen people who know what they’re building and have the tools to build it. That’s what teams look like now. And I’m standing here with four hundred people who just got made obsolete.

He thought about Derek Huang’s resignation letter: “I want to build, with tools that actually leverage what’s possible in 2026, so I’ll still have relevant skills in 2028.”

Derek had seen this coming. He’d tried to warn them. And Marcus had said “after the IPO.”

The champagne in his hand had gone flat. He set it down on a passing tray and didn’t pick up another.

Amanda Wong, who’d stepped into Derek’s role after his departure, found Marcus near the window.

“The engineering team is asking what happens next. They want to know if their jobs are secure.”

“Their jobs are fine. The company is fine.”

“Is it?”

Marcus looked at her, young, earnest, too new to the role to have learned the art of corporate dissembling.

“Honestly? I don’t know. We need to figure out a response to Meridian. We need to rebuild our approach to AI in development. We need to convince customers that we’re not dead.” He paused. “We need to do all the things I said we’d do ‘after the IPO.’ Except now we’re doing them from a position of weakness instead of strength.”

“What should I tell the team?”

“Tell them we’re still here. Tell them we’re still building. Tell them the story isn’t over.”

Amanda nodded and left. Marcus turned back to the window, looking down at the Manhattan streets: people walking, taxis honking, life continuing as if the worst day of his career hadn’t just happened.

Sarah appeared at his side.

“You don’t have to stay. We can go back to the hotel.”

“I have to stay. These people bought our stock. I owe them my presence.”

“You don’t owe them anything. You rang the bell. You did what you came to do.”

Marcus turned to face her. In the hotel’s dim lighting, she looked tired. as tired as he felt, maybe more.

“Did I? Or did I just watch everything I built start to collapse?”

She didn’t have an answer. Neither did he.

Monday, July 6, 2026 – 11:00 PM – Hotel Suite, The Langham

The hotel room was quiet.

Marcus sat on the bed, laptop open, staring at numbers that had become his new obsession.

The math of destruction (1.4% stake):

At $16 (opening): $13.3M
At $12 (close): $10M
If it drops to $8: $6.6M
If it drops to $6: $5M
If it drops to $4: $3.3M

And he couldn’t sell until January. 180 days of watching. 180 days of calculating. 180 days of learning exactly how wrong he’d been.

Even at $3 million, he’d be okay. More than okay. But okay wasn’t what he’d promised Sarah during those years of 0% credit card rotations and no salary and watching their retirement accounts drain to nothing. Okay wasn’t what justified raiding every financial cushion they’d built over a decade of careful planning.

Okay was supposed to be the floor, not the ceiling.

Sarah emerged from the bathroom in pajamas and sat beside him.

“What do we do now?”

Marcus closed the laptop. The numbers didn’t change when he looked away, but at least he didn’t have to see them.

“We survive. We figure this out. After… after the lockup.”

Sarah caught the words. She closed her eyes.

“‘After the lockup.’ You sound like. “

“I know. I know exactly what I sound like.”

The cruelty of it hit him then. “After the IPO” had become “after the lockup.” He was still deferring. Still hoping the problem would solve itself. Still not asking the questions that might actually lead somewhere.

“Marcus.” Sarah took his hands. “This doesn’t have to break us. Even if it drops to $10, even $7. we can pay off the house, fund the boys’ college, rebuild retirement. We’ll be okay.”

“Okay.” The word tasted like ash. “I didn’t put you through two years of credit card roulette and empty retirement accounts to be okay.”

“You put us through that because you believed in something. I believed in it too.” She squeezed his hands. “Being okay is still better than where we were in 2021.”

“It’s not about the money.”

“Then what is it about?”

“It’s about everything I got wrong.” His voice cracked. “I was so confident. So sure. Meridian was dying. Our competitors were years behind. The IPO was going to prove I was right about everything.” He looked at her. “And I was wrong. About all of it. Derek saw it. Prakash saw it. Edward saw it. Everyone saw it except me.”

“So now you know. Now you can start asking the questions you should have been asking all along.”

“What questions? I don’t even know where to start.”

“I don’t know, Marcus. I don’t understand your world.” Sarah took his hands. “But I know you. The man I married asked questions. He was curious. He wanted to understand things.” She paused. “Somewhere along the way, you stopped asking. You started defending.”

“It’s too late for Axiom.”

“Maybe. But it’s not too late for you.”

They sat in silence for a long time. The Manhattan night pressed against the windows. a million lights, a million stories, a million people who didn’t know or care that Marcus Webb’s world had just collapsed.

Finally, Sarah stood and turned off the light.

“Tomorrow, we go home. And then we figure out what comes next.”

“What if there is no next?”

“There’s always a next. You just have to find it.”

She lay down beside him, and Marcus stared at the ceiling until the darkness began to fade.

The bell had rung. The stock had fallen. The lockup had begun.

Now came the hardest part: figuring out who he was without the trajectory he’d been protecting for three years.

Tuesday, July 7, 2026 – 8:00 AM – Private Jet, Teterboro to Fort Lauderdale

In the morning, they flew back to Fort Lauderdale.

Sarah held his hand during takeoff. Neither of them spoke. The plane climbed through the clouds, leaving New York and the bell and the worst day of Marcus’s life behind.

Below them, America stretched out. the same country he’d flown over a thousand times, chasing deals and customers and the dream of the IPO. It looked different now. Smaller, somehow. Or maybe he was the one who’d gotten smaller.

180 days until the lockup ended.

180 days to figure out who he was without the trajectory he’d been protecting.

Marcus closed his eyes and tried to remember the last time he’d asked a question instead of assuming an answer.

He couldn’t remember. That was the problem.

Chapter 10: The Long Decline

August – November 2026

MARCUS

Monday, August 3, 2026 – 5:00 AM – Marcus’s Home Office

August: $10.

Marcus checked two numbers every weekday morning at 5 AM, before Sarah woke up, before the boys started getting ready for school. First the pre-market stock price. $10, down from $12 at IPO close, down from $16 at opening. Then the ARR dashboard. $234 million, down from $240 million at IPO.

Both numbers moving in the same direction. Both bleeding out, week after week.

The customer losses had started the day after the Meridian announcement. Hartley Shipping, the Fortune 500 company whose CTO had warned him about feature delays, exercised their option not to renew. Two days later, a mid-sized 3PL that had been with Axiom for three years announced they were “evaluating alternatives.”

By mid-August, six more customers had given notice. The migration offers from MeridianOne were too good to ignore: free data transfer, free training, 90-day implementation guarantee. Everything Axiom had once offered to steal customers from the legacy players was now being used against them.

Marcus didn’t know which number to watch more closely: the stock price eroding his net worth, or the ARR erosion that was causing it. They fed each other in a death spiral: customers left because Axiom looked weak, and Axiom looked weak because customers were leaving.

At $10, his 1.4% stake was worth $8.3 million. Still significant money. But every week it dropped, and every week more customers announced they were “exploring options.”

He couldn’t sell. The lockup held him frozen, watching both numbers bleed away one tick at a time.

Monday, August 3, 2026 – 3:00 PM – Catherine Bell’s Office

Catherine had spent the weekend writing and rewriting the letter. Not because the words were hard. Because admitting what it meant was hard.

She’d been the best at what she did. Three companies built for exit. Three successful outcomes. A career built on one skill: taking messy organizations and making them clean enough for someone else to buy. She understood financials, governance, narrative control. She understood how to get a company from Point A to the bell.

What she didn’t understand — what she’d never needed to understand — was what happened when the ground shifted underneath you. When the playbook stopped working. When “execute the plan” stopped being the right answer because the plan itself was wrong.

She’d known since July 5th. Maybe earlier. Maybe since the day she’d issued the AI ban and watched Derek Huang’s face go flat with something she’d mistaken for compliance but now recognized as resignation. Not anger. Not rebellion. Just a young man realizing his CEO didn’t understand what she was banning.

Catherine had spent her career being the smartest person in governance rooms. The AI ban hadn’t been stupid — it had been correct for the narrow problem she was solving. Protect the IPO metrics. Minimize variance. Control the narrative. Every one of those objectives was sound. Every one of them was also irrelevant if the entire competitive landscape was shifting beneath you.

She’d been right about the tactics and wrong about the war.

Marcus knocked.

“Come in.”

He sat down across from her. She’d rehearsed this conversation too.

“I wanted you to hear it from me first.” Her voice was flat, professional — because that was who she was, and she was not going to pretend otherwise at the end. “I’m stepping down.”

Marcus stared at her. “You’re what?”

“I took this company public. That was the job Blackwood hired me for. What happens next is a turnaround, and turnarounds aren’t my expertise.” She slid a folder across the desk. “My resignation letter. Effective September 1st.”

“You’re leaving in the middle of a crisis?”

“I’m leaving because there is a crisis. The board needs different leadership now. Someone who understands technology transformation. Someone who can rebuild what needs rebuilding.” She paused. “That’s not what I do, Marcus. I build companies for exits. I don’t rebuild them after exits go wrong.”

What she didn’t say: I’m leaving because I’m the wrong person, and the longer I stay, the more damage I do. That kind of honesty was for memoirs, not resignation conversations.

Marcus wanted to be angry. He wanted to call her a coward, a mercenary, a fair-weather captain abandoning ship. But when he looked at Catherine — who had stared at the ceiling of her apartment at 3 AM the night before, running the counterfactual where she’d said “yes, let them experiment, but with guardrails” instead of “anyone caught will be terminated” — he couldn’t muster the outrage.

She’d told him. Every time Derek raised AI concerns, she’d said “is this going to lose us customers?” Every time Prakash warned about competition, she’d said “focus on execution.” She’d never claimed to understand technology. She’d only claimed to understand numbers.

And the numbers had finally caught up with both of them.

“Who’s taking over?”

“The board is bringing in Richard Townsend as interim CEO. PE background. He’s led three turnarounds. He’ll have new ideas.” She stood and offered her hand. “I wish you well, Marcus. I really do.”

He shook it. The gesture felt hollow, the end of a partnership that had never really been a partnership at all.

Catherine watched him leave. Then she sat back down and looked at the empty office she’d occupied for eighteen months. The framed photo of her daughter’s graduation. The clean desk. The whiteboard she’d never written on because the numbers lived in spreadsheets, not on walls.

She thought about Derek Huang. He’d been right. She wondered where he’d ended up.

Tuesday, August 11, 2026 – 2:00 PM – Axiom Boardroom

The August board meeting was a trial.

Victoria Hartwell led the questioning with the precision of a prosecutor. Catherine Bell was notably absent; her last day had been the previous Friday. The empty chair at the head of the table said everything about how quickly things had changed.

“Marcus, what’s our AI response?”

“We’re evaluating options. Looking at acquisitions. Talking to AI vendors. Building an internal roadmap.”

“Those are activities, not a strategy. Customers are asking concrete questions. They want to know if we can match Meridian’s capabilities.” Victoria paused. “Can we?”

Marcus hesitated. The truth was ugly, but lying to the board would only delay the inevitable.

“Not in the next twelve months. Their architecture is different. They rebuilt from scratch. We’d have to do the same thing, and we don’t have the foundation they started with.”

Richard Townsend, attending his first meeting as the incoming Chairman, leaned forward. “Let me make sure I understand the scale of what we’re facing. Meridian built their new platform with fourteen engineers. We have four hundred. They did it in fourteen months. We’ve been saying ‘after the IPO’ for over a year.” He looked around the table. “Is that an accurate summary?”

Marcus nodded. The room was silent.

“Fourteen people,” Townsend repeated. “With AI tools and clear direction. They beat four hundred people with traditional processes and delayed priorities.” He paused. “And the reports say their team included Harry Thornton, the COBOL developer everyone joked about retiring. He didn’t retire. He became their domain expert. Forty years of institutional knowledge, fed into AI tools that could build faster than any human team.”

The irony was brutal. Marcus had laughed about Meridian’s COBOL developers. Now one of them had helped destroy Axiom’s future.

“So what are we telling customers?” Victoria asked.

“That we’re committed to AI. That we have a roadmap. That we’re investing in the future.”

“Is that enough?”

“It has to be.”

But Victoria’s expression said what everyone was thinking: It’s not enough. Not anymore.

Tuesday, September 1, 2026 – 5:00 AM – Marcus’s Home Office

September: $8.

The talent exodus accelerated.

First it was a trickle: an engineering manager here, a senior architect there. People Marcus had worked with for years, people who’d believed in Axiom, walking out the door with resignation letters and farewell posts.

Then it became a flood.

One week in September, three key engineers left on the same day. All three went to Meridian.

Marcus called HR. “Can we counter-offer?”

“We’ve tried. They’re not leaving for money. They’re leaving because they don’t believe in our direction.”

Our direction. What direction? The IPO that had already happened? The AI strategy that was still being “evaluated”? The roadmap that existed only in PowerPoint slides?

Derek had been right. Prakash had been right. The best people saw the future before it arrived, and the future wasn’t Axiom.

Thursday, October 1, 2026 – 5:00 AM – Marcus’s Home Office

October: $7.

Marcus finally called Edward.

He’d been putting it off for months, dreading the conversation, dreading the admission it would require. But at 2 AM, unable to sleep, staring at the ceiling while Sarah breathed softly beside him, he picked up his phone.

Ed. I need to talk. About what you’re doing at Riverton. About how you’re approaching AI.

The reply came faster than he expected: I’ve been waiting for this call.

Saturday, October 10, 2026 – 12:00 PM – Beachside Restaurant, Fort Lauderdale

They met on a Saturday. Edward flying down from Miami, Marcus picking him up at Fort Lauderdale airport. They drove to a quiet restaurant near the beach, one they’d been to years ago, before IPOs and AI and everything that had gone wrong.

“Tell me how to catch up,” Marcus said, before the drinks even arrived. “What do I need to do?”

Edward sighed. The expression on his face was sadness, not triumph: sadness for what his friend had lost, sadness for how long it had taken him to ask.

“Marcus, I want to help. I really do. But there’s no playbook I can give you that will fix this.”

“There has to be something. You figured it out.”

“I started asking questions eighteen months ago. You’re starting now. You can’t replicate eighteen months of learning with a playbook.”

“So what do I do?”

“You start by figuring out what you’re actually trying to build. Not ‘recover the stock price.’ Not ‘fix the IPO.’ What are you trying to ship?”

Marcus opened his mouth to answer, then stopped. The question was simple. The answer wasn’t.

“I don’t know,” he admitted. “I don’t know anymore.”

“Good.” Edward leaned forward. “Sit with that. Really sit with it. Before you jump to solutions.”

Saturday, October 10, 2026 – 1:30 PM – Beachside Restaurant, Fort Lauderdale

“That’s not helpful. I need actions. I need a roadmap.”

“And that’s why you’re in trouble.” Edward set down his coffee. “You want a roadmap before you know where you’re going. You want actions before you’ve looked at what’s real.”

“So I just… wait?”

“You look. Start with the outcome. What are you actually trying to build? Not the IPO. That’s done. What’s the thing that matters?” Edward paused. “Then you figure out what’s actually stopping you. Not the story you’ve been telling yourself. The real limits. Which constraints are real and which ones did you invent?”

Marcus stared at his friend. The man who’d been his roommate, his best man, his brother for twenty-five years. The man who’d seen what Marcus couldn’t see and tried to warn him.

“And then what?”

“Then you map where work actually waits. Have you ever done that? Traced a feature from idea to deployment and counted the days?”

“No.”

“That’s the problem. You assumed you were fast because you were cloud-native. You never measured it.” Edward leaned back. “And once you see it, you figure out the smallest thing you can prove in thirty days. Not a twelve-month plan. One feature. One proof point.”

The words landed like blows. Not because they were harsh, but because they were true.

“I never mapped it,” Marcus said quietly. “I deleted the one time I tried.”

“I know. You told me.”

“I assumed I already had the answers.”

“That’s exactly the problem. You assumed the IPO was a goal. It was a milestone. You assumed board expectations were constraints. They were choices. You assumed your process was fast. You never measured it.” Edward paused. “And you never asked what you could prove in thirty days, because you were always waiting for ‘after the IPO.’“

Saturday, October 10, 2026 – 2:30 PM – Parking Lot

The conversation ended awkwardly.

Walking back to his car, Marcus thought about what Edward had said. What are you trying to build? What’s real and what’s a story? Where does work wait? What can you prove?

It sounded simple. But when he tried to apply it, tried to name an outcome, separate real constraints from invented ones, picture where Axiom’s work actually got stuck, his mind went blank.

He’d spent three years protecting a trajectory. He had no idea how to build one.

Sunday, November 1, 2026 – 5:00 AM – Marcus’s Home Office

November: $6.

At $6, Marcus’s 1.4% stake was worth $5 million. Down from $13.3 million at the opening bell. Down from the $10 million at close on day one. Every month, another chunk of his future evaporating.

Five million was still money. But after taxes it would be barely $3 million. Enough to pay off the $50,000 equity loan. Maybe fund one kid’s college. But the retirement rebuild? The cushion that would let them stop worrying? Gone. Four years of sacrifice, the equity loan, the no-salary years, the raided retirement accounts, and he’d end up no better than if he’d just stayed at Soren as a senior engineer.

The desperation moves began.

Wednesday, November 4, 2026 – 11:47 PM – Marcus’s Home Office

Marcus downloaded Claude at 11:47 PM on a Wednesday.

He’d been thinking about it for weeks, ever since the October conversation with Edward. “I’m going to learn to build again,” Edward had said. “Haven’t written production code in eight years. Maybe that’s the problem.”

If Edward could do it, Marcus could do it. He’d been a decent programmer once, back in business school, back when he’d built the first Axiom prototypes himself. The skills had to still be there somewhere.

He opened the laptop. Created an account. Stared at the blank chat window.

What do you want to build?

He typed: “I want to understand how AI coding assistants work. Show me something simple.”

The response came instantly. Pages of explanation. Code examples. Suggestions for starter projects.

Marcus tried to follow along. He copied the first code block into a text editor. Python, apparently. He hadn’t written Python since a weekend course five years ago.

The code didn’t run. Error message. Something about indentation.

He asked Claude to fix it. More code. Different error.

Two hours later, Marcus had a working script that printed “Hello World” and not much else. His eyes were burning. The screen had started to blur.

Edward did this in three hours and built something useful. I’ve been at this for two hours and I can barely make text appear.

He tried again. Something more ambitious. “Help me build a simple dashboard that shows our deployment metrics.”

Claude responded with enthusiasm. Architecture suggestions. Database schemas. Frontend frameworks. The response was three screens long.

Marcus read it twice. Understood maybe a third of it. The terms that had once been familiar, APIs, endpoints, async functions, felt like a foreign language he’d once spoken and had now forgotten.

He tried to implement the first step. Got stuck on environment setup. Spent forty-five minutes trying to install something called Node.js. Finally got it working. Then the next step failed.

At 3:17 AM, Marcus closed the laptop.

The realization was brutal and complete: he couldn’t do what Edward did. Not in a weekend. Not in a month. Edward had built things for twenty years. The eight-year gap was nothing compared to Marcus’s fifteen-year gap. Edward’s rust was surface-level. Marcus’s rust went all the way through.

I can’t catch up. I can’t even understand what catching up would look like.

He poured himself a drink. Then another. Sat in the dark living room until dawn, thinking about the gap between who he’d been and who he’d become.

Thursday, November 5, 2026 – 9:00 AM – Axiom Headquarters, Conference Room A

The next morning, Marcus hired McKinley & Associates.

If he couldn’t build it himself, he’d hire people who could. McKinley was one of the Big 4’s spin-off advisory practices. Prestigious name, $800/hour rates, a team of MBAs who came highly recommended.

“We specialize in AI transformation,” the partner said during the intake call. “Fortune 500 clients. Proven methodology. We can have a team on-site next week.”

Six weeks later, they delivered their final report. The presentation was scheduled for 2 PM in Conference Room A.

Marcus arrived early. The McKinley team had set up a projector, printed bound copies of something thick enough to be a novel, arranged water bottles with geometric precision. Professional. Polished. Expensive.

“Thank you for your partnership over the past six weeks,” the lead consultant began. “We’re excited to share our findings and recommendations.”

The first slide appeared: “Axiom AI Transformation Roadmap: Strategic Assessment and Implementation Plan.”

Marcus leaned forward. This was it. The answer he’d been looking for.

“Our assessment covered twelve dimensions of AI readiness,” the consultant continued. “Data infrastructure. Talent capabilities. Governance frameworks. Change management capacity.”

Slide after slide. Matrices with color-coded quadrants. Benchmarks against “industry leaders.” Capability gap analyses.

Marcus waited for the part that would tell him what to actually do.

“Based on our findings, we recommend a three-phase approach.”

Here it comes.

“Phase One: Assessment and Planning. Months one through six. We’ll conduct deep-dive workshops across all business units, establish baseline metrics, and develop detailed implementation roadmaps.”

“Wait.” Marcus held up a hand. “You’ve been assessing for six weeks. Now you want six more months?”

“The initial engagement was high-level discovery. Phase One is detailed planning. You can’t build a house without blueprints.”

That’s what the last consultants said. Almost word for word.

“What about Phase Two?”

“Pilot Selection and Governance Design. Months seven through twelve. We’ll identify two to three pilot use cases, establish an AI Center of Excellence, and build the governance structures needed for responsible scaling.”

“So twelve months before we build anything?”

“Transformation requires proper foundation. Companies that rush this phase typically see 60-70% failure rates.”

Marcus put down the report. “And Phase Three?”

“Controlled Implementation. Months thirteen through eighteen. Phased rollout of AI capabilities, with continuous monitoring and adjustment.”

“Eighteen months total.”

“Assuming no major blockers. Some clients take twenty-four to thirty-six months for full transformation.”

Marcus looked at the bound report in front of him. Flipped to a random page. “Cross-functional stakeholder engagement is critical to ensuring buy-in across business units.”

Another page. “A robust governance structure will mitigate implementation risks while enabling measured experimentation.”

Another. “Axiom should establish an AI Center of Excellence to drive organizational alignment around transformation objectives.”

He thought about Edward. About value stream mapping. About the question Edward kept asking: What’s stopping you from shipping?

“Let me ask you something,” Marcus said. “Our deployment pipeline. Do you know how long it takes for a feature to go from code complete to production?”

The consultants exchanged glances. “That would be covered in the Phase One deep-dives.”

“You’ve been here six weeks. Interviewed our engineers. Reviewed our architecture. And you don’t know our cycle time?”

“We focused on organizational readiness, not operational metrics. Those are different workstreams.”

Different workstreams. They spent six weeks studying the company and they never looked at where work actually gets stuck.

Marcus flipped to the budget section. $2.4 million for the full engagement. Plus technology costs. Plus hiring costs. Plus the opportunity cost of eighteen months while Meridian pulled further ahead.

He closed the report.

“Thank you for your work. We’ll need some time to evaluate internally.”

The consultants nodded professionally, started packing up their projector and their bound reports and their geometric water bottles.

Marcus sat alone in the conference room after they left, staring at the hundred pages of expensive nothing.

$2.4 million. Eighteen months. And they never once asked what’s stopping us from shipping.

Thursday, November 5, 2026 – 4:00 PM – Marcus’s Office

He tried hiring a VP of AI Transformation next, someone who could report to him and drive the change he couldn’t seem to make happen. HR posted the role. The responses were dispiriting.

The candidates with impressive titles had less hands-on experience than Marcus did. They’d managed AI initiatives, sat on steering committees, written strategy documents. But when Marcus asked what they’d actually shipped, the answers got vague. “We were in the planning phase when I transitioned.” “The implementation was handed off to another team.” One candidate had “led AI transformation” at three companies in four years, which meant he’d led nothing to completion anywhere.

The candidates who’d actually built things didn’t want to join a sinking ship. One was blunt about it: “I’ve seen your stock chart. I’d be inheriting a crisis, not an opportunity.”

The last interview haunted him. A woman from a Fortune 100 company, impressive credentials, the kind of person who could actually make things happen. She’d asked sharp questions about budget, authority, reporting structure. And then she’d asked one that stopped Marcus cold:

“Who would I be reporting to? You, or the board directly?”

Marcus had said “me” without hesitation. But afterward, walking back to his office, he realized he wasn’t sure anymore. Was he hiring someone to help him? Or was the board waiting for him to identify his own replacement?

The woman had seen it too. She’d smiled politely and said she’d be in touch. She never called back.

Marcus reached out to independent consultants, fractional CTOs who’d guided other companies through AI transitions. The good ones were booked eight months out. “Call me in Q3 2027,” one said. “I might have availability then.”

By Q3 2027, there wouldn’t be an Axiom to transform.

The rumors started that week. A PE firm was circling, one of Victoria’s contacts apparently, asking questions about a take-private deal. The board would restructure, bring in new leadership, try to rebuild what Marcus had failed to protect. It wasn’t official yet. But Marcus could read the writing on the wall.

Marcus announced an “AI roadmap” to customers, a glossy presentation full of buzzwords and timeline projections. The customers nodded politely. They didn’t believe it. Marcus could see it in their eyes: Too late. Too vague. Too desperate.

He offered retention bonuses to key engineers. Most of them had already accepted offers elsewhere. The ones who stayed didn’t seem any more confident than he was.

Tuesday, November 24, 2026 – 2:00 AM – Marcus’s Home Office

Late November, Marcus sat in his home office with his laptop open.

He’d found the articles Rachel Torres had sent Edward nearly two years ago. The same case studies Edward had mentioned at the family dinner. The same approaches Marcus had dismissed as “interesting but not urgent.”

He read them now with different eyes. Not the eyes of a confident executive protecting his trajectory, but the eyes of a man who’d lost everything and was trying to figure out why.

Start with the outcome. Map the process. Identify the constraints. Fix the bottlenecks.

Process improvement, not tool adoption.

What’s stopping you from shipping?

The phrases repeated like a drumbeat. How had he missed this? How had he spent eighteen months saying “after the IPO” while the answer was right in front of him?

Because he’d never mapped his own process. Because he’d assumed it was working. Because acknowledging uncertainty had felt like weakness.

What outcome am I trying to achieve?

Marcus typed the question into a blank document. Then he stared at the cursor blinking, waiting for an answer that wouldn’t come.

Where does work actually wait in our pipeline?

Another question. Another blank line.

What constraints are real and which ones did we invent?

He knew the numbers: stock at $6, equity at $5 million on paper, lockup ending in 40 days. He knew the business metrics: customer churn accelerating, talent departing, competitors pulling ahead.

But those were symptoms, not the actual process. The process was something deeper, something he couldn’t see yet, couldn’t name.

Sarah found him at 3 AM, hunched over the laptop, typing nothing.

“Come to bed.”

“I’m trying to figure something out.”

“What?”

“What Edward showed me. Value stream mapping. I’m trying to understand where we went wrong.”

Sarah sat down beside him and looked at the screen. A blank value stream map. Boxes with no labels.

“You can’t force it.” She put her hand on his. “This isn’t a problem you solve in one night.”

“I’ve been avoiding it for two years. I don’t have more nights to waste.”

“You’re not wasting them. You’re learning to look. That’s different.”

“Is it?”

“It’s where everyone starts.” She touched his shoulder. “The Marcus I married, the one who rebuilt himself after his knee blew out, who started a company from nothing, who climbed to the top of this one, he didn’t start with answers. He started by looking honestly at what was in front of him.”

Marcus looked at her. In the glow of the laptop screen, she looked tired, worried, still there.

“I don’t remember what not knowing felt like,” he admitted. “I’ve been so confident for so long, I forgot how to actually look.”

“Then learn again. That’s what humans do.”

She stood, leaving him with the laptop and the blank screen and the process he was finally ready to examine.

Sarah stood and turned off the light. Marcus stayed at his desk, the cursor still blinking on that blank value stream map.

Where does work wait?

What’s actually stopping us from shipping?

What does our process really look like?

He sat there until morning, not writing, not solving, just sitting with questions he was finally learning to ask.

It was a start.

Chapter 11: Christmas Eve 2026

July – December 2026

THE WEIGHT OF WINNING

Sunday, July 5, 2026 – 4:00 PM – The Dock, Edward’s House on the Intracoastal

Edward watched the Axiom IPO disaster unfold from his dock in Miami.

The day of the announcement. Sunday, July 5th. he’d been sitting on his dock when the news alert came through. Meridian. MeridianOne. The platform that destroyed everything Marcus had built.

He read the press release twice, then set down his phone and stared at the water.

I tried to warn him. At spring break. At the family dinner. Every chance I got.

He didn’t listen.

And now it’s too late.

The guilt hit him then, unexpected and sharp. He’d been right. He’d seen this coming. And what had he done about it? Mentioned it at holiday dinners? Offered vague advice about “asking questions”? Watched from a safe distance while his best friend drove toward a cliff?

I should have pushed harder. I should have been more direct.

But that wasn’t quite true either. He’d pushed. Marcus had pushed back. At some point, friendship meant respecting someone’s right to make their own mistakes.

It didn’t make the guilt go away.

Jennifer found him there an hour later, still staring at the water. She was wearing the Coast Guard sweatshirt she’d stolen from him twenty years ago, the one she always wore when she knew he needed comfort without words.

“You couldn’t have stopped him.”

“I know.”

“But you’re going to feel responsible anyway.”

“He’s my brother, Jen. Twenty-five years. Since the Academy.” Edward’s voice was rough. “We were roommates when I didn’t know what I wanted to be. We were at each other’s weddings. Our kids grew up together. And I watched him walk off a cliff.”

“You told him the cliff was there. Multiple times. He chose not to look down.” She sat beside him on the dock, the way she’d sat beside him a thousand times—on that apartment balcony in New York, on the back porch in Virginia, on this dock in Florida. Twenty years of sitting beside him while he worked through the hard things. “That’s not on you.”

“Then why does it feel like it is?”

She didn’t have an answer for that. She just sat with him, watching the water, being there the way she’d been there when he came back from Iraq and didn’t know how to talk about what he’d seen. Some things you couldn’t fix with words. You just had to be present.

Monday, July 6, 2026 – 9:30 AM – Edward’s Home Office

He watched the IPO unfold on his laptop.

Opening price: $16. Then the slide began. $15. $14. $13.

By market close, $12. A 25% drop on the first day of trading.

Edward texted Marcus: Hey. Thinking of you. Call if you need anything.

No response.

He understood. Marcus was in survival mode now. smiling for cameras, answering questions he had no good answers to, pretending everything was fine while his world collapsed.

What do you say to your best friend when the disaster you predicted has arrived?

Thursday, August 6, 2026 – 11:00 AM – Coffee Shop Near Riverton

Kevin Nakamura found Edward at the coffee shop where they’d had their difficult conversation four months ago.

“Saw the news about Axiom,” Kevin said, sliding into the booth. “Your friend Marcus. That’s got to be hard.”

Edward looked up from his laptop. He hadn’t expected Kevin to bring it up. “It is.”

“I’ve been thinking about something.” Kevin stirred his coffee. “When you pushed me too hard on the medication feature. Remember what Rachel said to you?”

“That I was good at asking questions about process but terrible at asking questions about people.”

“Right. And then you came here, bought me coffee, and asked me what I needed.” Kevin paused. “Have you asked Marcus that question?”

Edward set down his cup. “What do you mean?”

“You’ve been giving him frameworks. Value stream mapping. The questions. All the intellectual stuff.” Kevin shrugged. “But he just watched his life’s work collapse. Maybe he doesn’t need another framework right now. Maybe he needs his friend to ask how he’s actually doing.”

“When did you get so wise?”

“Around the time my boss almost drove me to quit and then had the humility to apologize.” Kevin smiled. “People surprise you when you give them room to.”

Friday, August 14, 2026 – 3:00 PM – Edward’s Office, Riverton Health Systems

August was strange.

The org-wide number hadn’t moved. Still 10%. The pilot teams were strong, the medication feature was in 127 hospitals, but the rest of Riverton had settled into an uneasy equilibrium. Industry publications were writing about “the Riverton model” based on the keynote. Edward knew the gap between the keynote and the reality.

The number that mattered most wasn’t productivity. It was 23 — the drug interactions the system had flagged in the past month alone. Twenty-three patients who might have gone home with dangerous medication combinations.

The org-wide transformation? He’d failed at that. And he was starting to understand why.

And in Fort Lauderdale, Marcus was watching his stock price fall.

$12 became $11 became $10. Every week lower. Every week worse.

Edward followed it from a distance. Marcus had refused to look at his process. Edward had looked at his and still couldn’t make the organization change.

Rachel Torres found him staring out his office window one afternoon.

“You’re thinking about Cascade again.”

“Is it that obvious?”

“You’ve been staring at their offer letter for a week.” Rachel sat down across from him. “You should take it.”

“I have teams here counting on me.”

“Your pilot teams don’t need you anymore. They’re running.” She crossed her arms. “You know that. So what are you actually staying for?”

“The teams that haven’t started yet. The ones still running serial.”

“And you’ve been here a year. How many of those teams have you converted?” She let the silence answer. “Edward, we had this conversation in May. You know why you can’t get there from here. That hasn’t changed. What’s changed is that someone’s offering you a place where it’s actually possible.”

“I have people here.”

“You have people here who will be fine. What you don’t have is a board that’s going to let you tear the building down and rebuild it.” Rachel leaned forward. “This isn’t about loyalty. You’re staying because leaving feels like admitting the ceiling is real. And it is real. That’s not failure. That’s clarity.”

“And Cascade is offering me a blank canvas.”

“A hundred-and-fifty-thousand-person blank canvas. With budget. And the mandate to start from scratch.” Rachel paused. “The medication feature will keep running. The pilot teams will keep their gains. But the thing you actually want to build — you can’t build it here. You’ve known that since May.”

“I feel like I’m abandoning the work.”

“You’re not abandoning it. You’re going where it can actually work.” She stood up. “When Marcus is ready to ask for help, you’ll be there. Until then, build the thing you’ve been thinking about. Build it right.”

Saturday, October 10, 2026 – 12:00 PM – Beachside Restaurant, Fort Lauderdale

October: The conversation at the restaurant.

Edward flew down from a conference to meet Marcus. the same restaurant they’d been to years ago, the same booth by the window. But everything else was different.

Marcus looked older. Gray at his temples. Lines around his eyes. The easy confidence he’d always projected was nowhere to be seen.

“Tell me how to catch up.”

The desperation in Marcus’s voice was painful to hear. This was his best friend. the man who’d rebuilt himself after a blown knee, who’d started companies and sold them, who’d seemed invincible for so long.

Now he was broken. And Edward didn’t have a quick fix to offer.

“This approach only works if you engage honestly. What’s your goal now? Not the IPO. that’s done. What are you actually trying to accomplish?”

“I don’t know.”

Edward waited. Marcus wasn’t ready to hear more.

But Marcus wanted answers, not questions. He wanted a roadmap, not a process. The conversation ended awkwardly.

Tuesday, November 17, 2026 – 2:00 PM – Edward’s Office, Riverton Health Systems

November: The call from Sarah.

Edward was in his office when the phone rang. Sarah’s number, not Marcus’s.

“Edward, I need to ask you something.”

“Anything.”

“Is there hope? For Marcus? For what comes next?”

The question caught him off guard. Sarah was usually the composed one, the steady presence who held the family together while Marcus worked.

But this was her husband. And she sounded scared.

“There’s always hope,” Edward said. “But it depends on him. On whether he’s ready to ask the questions.”

“He’s up at 2 AM, staring at his laptop, trying to answer them. He’s not sleeping. He’s not eating well. He’s obsessing over what went wrong.” Sarah’s voice cracked. “I don’t know how to help him.”

“You can’t. Not directly. The only thing you can do is be there when he’s ready to start over.”

There was silence on the line. Then Sarah said: “Christmas. Will you be there?”

“We’ll be there. Same as always.”

CHRISTMAS EVE

Thursday, December 24, 2026 – 5:00 PM – Edward’s House on the Intracoastal

The sun-baked 2014 Honda Odyssey pulled into the driveway as the sun set over Edward Johnson’s house. The same house. The same Christmas lights along the roofline.

Nearly two years ago, Marcus Webb had arrived here confident, sixteen months from ringing the bell at the NYSE.

Now he arrived broken.

Sarah noticed his hands tighten on the steering wheel.

“We don’t have to go in yet.”

“We have to go in eventually.”

Marcus stared at the house where everything had begun. Sophia’s stories about AI. Edward leaning forward, asking questions. Marcus dismissing it all as “great for school projects.”

If I could go back. If I could ask instead of answer.

But you couldn’t go back.

“Let’s do this,” he said.

Thursday, December 24, 2026 – 5:15 PM – Front Door

Jennifer opened the door before they could ring the bell.

Her expression flickered when she saw Marcus. shock, quickly controlled. He knew what she was seeing: the gray at his temples, the weight he’d lost. A man who’d aged ten years in six months.

“Come in, come in.”

Edward appeared in the hallway. The two men looked at each other. twenty-five years of friendship compressed into a single glance.

“Hey, brother,” Edward said.

“Hey.”

The hug was long, wordless.

“Thank you for still wanting us here,” Marcus whispered.

“Always. That’s not changing.”

Thursday, December 24, 2026 – 5:30 PM – Living Room

The kids had gathered in the living room.

Sophia was home from Georgia Tech. twenty now, a junior. Emma, seventeen, sat with her sister near the window. Lily, thirteen, was causing chaos as usual.

MJ, sixteen, slouched on one couch, earbuds in. Isaiah, thirteen, sat in a corner with a book, but his eyes kept drifting to his father.

Lily launched herself at Marcus.

“Uncle Marcus, why do you look so tired?”

“Big things happening at work, Lily-bug.” The old answer. The wrong answer. “Actually, no. Hard things happening. Things I got wrong.”

Lily nodded, as if this made sense.

“Dad says getting things wrong is how you learn. He says the questions you ask are more important than the answers you think you have.”

Marcus looked at her for a long moment.

“Your dad is right. I should have listened sooner.”

Thursday, December 24, 2026 – 6:00 PM – Dining Room

Dinner was quieter than usual.

The families sat around the same table where Sophia had told her stories nearly two years ago. Edward’s grandmother’s ham. Jennifer’s sweet potato casserole. The same food, different atmosphere.

Marcus barely ate.

When the talk turned to Sophia’s studies, he braced himself.

“The field keeps changing so fast,” Sophia said. “My professors say what we’re learning now will be obsolete in three years. But the fundamentals stay the same.”

“What kind of fundamentals?” Sarah asked.

“Knowing what you’re trying to accomplish. Understanding where work actually gets stuck. Being clear about your current process before you try to change it.” Sophia paused. “My professor calls it ‘the looking is the intervention.’“

“Uncle Marcus.” Sophia’s voice was careful. “I’m sorry about what happened with Axiom.”

“Don’t be sorry. You tried to tell me. Two years ago, at this table. I didn’t listen.”

The room went quiet.

“You’re listening now,” Sophia said.

“I’m trying to.”

Thursday, December 24, 2026 – 7:30 PM – Kitchen

After dinner, Jennifer and Sarah loaded the dishwasher.

“He looks terrible,” Jennifer said.

“Every market day, he’s up at 5 AM checking the stock price. Stays up until 2 doing research he should have done years ago.” Sarah closed a cabinet door. “The lockup ends in three weeks. He’ll be able to sell whatever’s left.”

“How much is left?”

“Stock’s at $5.60. His stake is worth about $4.6 million.” Sarah paused. “Down from $13 million at the opening bell. Sixty-five percent gone.”

“Four and a half million is still. “

“I know. We’ll be okay.” Sarah’s voice was flat. “But after taxes it’s barely $3 million. We spent two years living on 0% credit cards and raiding our retirement accounts. We still owe $50,000 on the equity loan. We emptied our retirement. And he promised me, promised himself, that this IPO would make all of that worth it.”

Sarah leaned against the counter. “He’s scared, Jennifer. He was always scared. too scared to ask questions that might threaten the IPO. Too scared to admit he might not have all the answers. And now he’s scared in a different way.”

“Scared how?”

“Paralyzed. He won’t do anything. Won’t make decisions. Won’t move forward.” Sarah’s voice cracked slightly. “It’s like he’s decided the safest thing to do is nothing. But nothing is making it worse.”

“Edward’s going to talk to him. On the dock.”

“Good. Because I can’t get through anymore. Maybe Edward can.”

Through the window, they could see the two men walking toward the dock. silhouettes against the darkening sky, fishing poles in hand.

Thursday, December 24, 2026 – 8:00 PM – Hallway

MJ found his father in the hallway.

“Dad. Are you going to be okay?”

Marcus turned. His oldest son stood there, not quite meeting his eyes.

“I don’t know,” Marcus admitted. “I made a lot of mistakes. Big ones.”

“But you’re going to try to fix them?”

“I’m going to try to learn from them. That’s not the same thing.”

MJ nodded. “You told me once, when I wanted to quit basketball after we lost by thirty points, that the best comebacks start from the bottom. You said losing teaches you things winning can’t.”

Marcus felt his throat tighten. “I said that?”

“Yeah. So maybe this is your bottom. And maybe the comeback starts now.”

MJ walked back to the living room.

The best comebacks start from the bottom.

Marcus took a breath, squared his shoulders, and walked out to the dock.

Thursday, December 24, 2026 – 8:10 PM – Living Room Window

Isaiah watched through the window as his father walked toward the water.

Sophia sat down beside him. “You okay?”

“I’m worried about Dad. He used to be so confident. Now he looks scared all the time.”

“Maybe scared is good. Maybe scared means he’s finally paying attention.”

“Do you think Uncle Edward can help him?”

Sophia thought about the spring dinner nearly two years ago. The words she’d said without knowing what they meant.

“Dad can show him where to start. But Uncle Marcus has to do the work himself.”

“You promise he’ll be okay?”

“I don’t promise. But I hope.”

They watched the two silhouettes on the dock.

Chapter 12: The Questions

December 24, 2026

THE DOCK

Fishing poles. Same dock. Two years later.

Neither of them spoke for a while. Marcus cast his line into the darkness, reeled it back, cast again. The muscle memory of twenty years of fishing together.

“I thought I was being careful,” he finally said. “That’s what kills me. I thought standing still was the safe play.”

“And now?”

“Now I’m wondering if standing still was just gambling on a different outcome.” He laughed, but there was nothing funny in it. “Fourteen engineers, Ed. Fourteen people rebuilt in fourteen months what took us four years. Four hundred engineers. Four years.”

Edward didn’t say anything. Sometimes you just had to let someone talk.

“I kept saying we had a four-year head start. Like that meant something. Like time worked the same way it always had.” Marcus shook his head. “Meridian didn’t have better people. They didn’t have more money. They just asked what was actually possible instead of assuming they already knew.”

“Yeah.”

“And the thing that kills me?” Marcus turned to face Edward. “Even if I’d started the day after Meridian launched, even if I’d dropped everything and said we’re going AI-native tomorrow, it wouldn’t have mattered. They had a year’s head start by then. A full year of shipping features while we’d still be sorting out Day One bureaucratic nightmares. Fighting over governance. Convincing the board. Restructuring teams. Losing customers the whole time.”

Edward nodded. “That’s what amazes me about all this. When an organization actually decides to go AI-native SDLC, really decides, not just talks about it, the speed is unbelievable.” He shook his head. “Meridian didn’t just catch up to you. They lapped you. In eighteen months.”

“With fourteen engineers.” Marcus’s voice was hollow. “And now they’re growing again. They just opened forty new positions. You know who’s applying? My people. The engineers I spent four years recruiting. The ones who built everything we had.” He stared at the water. “Meridian’s hiring my talent to build features that compete with what my talent already built. It’s like watching your own army switch sides.”

“Because they weren’t fighting their own process the whole time. They built the process around the outcome. You would’ve been fighting four years of accumulated decisions, every one of them made for good reasons that no longer applied.”

Marcus stared at the water. “So even if I’d woken up the morning after their launch and done everything right…”

“You’d still be a year behind. Maybe more. Because transformation isn’t just deciding to change. It’s dismantling everything that made change feel unnecessary.” Edward paused. “That’s the real lesson. The companies that move first don’t just get a head start. They get to build without the baggage. Everyone else has to renovate while the building’s on fire.”

Marcus was quiet for a long moment. Then he set down his fishing pole.

“So tell me now. Whatever you figured out. The thing that worked.”

Edward was quiet for a moment. Across the Intracoastal, someone’s Christmas lights were blinking out of sync.

“It’s embarrassingly simple,” he said. “I’m almost embarrassed to say it out loud.”

“Say it anyway.”

“Start with what you’re trying to ship. Not ‘adopt AI.’ Not ‘transform.’ One thing. The medication feature. That was our outcome.” He paused. “Then map where work actually waits. We found eleven weeks from requirement to deployment. Two weeks of work. Nine weeks of waiting in queues nobody had questioned.”

“And then you fixed it.”

“First we had to figure out which constraints were real. HIPAA review? That stays. A three-week compliance checklist because someone panicked in 2018? That goes. Once you see what’s real and what’s invented, you know what to cut.” He cast his line. “Then you bet small. Ninety days. One feature. Not a three-year roadmap. Just prove it works on something you can measure. If it works, you’ve earned the right to do it again.”

Marcus waited for more. “That’s it?”

“That’s it.” Edward reeled in some slack. “AI helped with three of the bottlenecks. The other four were just waste. Approval queues, handoffs, committees that met on fixed schedules regardless of urgency.”

“So you fixed the waste.”

“In the pilot teams, we fixed the waste. Some with AI, some without.” He paused. “The medication feature shipped in eighty-seven days. After eighteen months stuck. Twenty-three hospitals flagged drug interactions that could have killed patients.”

Marcus stared at the water. “Because you adopted AI.”

“Because we looked.” Edward turned to face him. “AI was almost beside the point. Nobody had ever mapped the actual process. We all had theories about why things were slow, but nobody had traced a feature from start to finish.”

“What did you actually change?”

“Kept the gates that mattered. HIPAA, patient safety. Cut the gates that existed because someone got nervous years ago.” He cast again. “And here’s the key: we didn’t fire the people manning those gates. We reassigned them to building things.”

“What do you mean?”

“Lisa Martinez spent eight years in QA. Now she’s one of our best developers. Turns out people who spent years finding bugs know a lot about preventing them.” Edward paused. “In the teams I was in the room for, same headcount, dramatically better output. Because we stopped using talented people to man gates that shouldn’t exist.”

Marcus was quiet for a moment, processing.

“That sounds too simple.”

“It is too simple. And here’s the part I don’t tell conference audiences.” Edward set down his pole. “At Riverton, the org-wide improvement was 10%. Ten percent. After a year of mapping sessions, training, fighting for budget, surviving near-disasters. The pilot teams were up 40%. The rest of the org was a mess. Teams trying the approach without support and making things worse. Three different versions of the methodology. Attrition up in the teams that felt left behind.”

“Ten percent.” Marcus let that sink in.

“Ten percent. I built something that works brilliantly when I’m in the room and falls apart when I’m not. You can’t transform an organization one team at a time, sequentially, with one person facilitating everything.” Edward picked up his pole again. “I went to the board. Asked them to let me restructure everything. Parallel teams, new reporting lines, the works. They said no.”

“Why?”

“Because 10% improvement doesn’t scare anyone. The stock was fine. The hospitals were happy enough. You don’t get permission to tear down a functioning building because you think the foundation could be better.” Edward shook his head. “And honestly, I’d already used up my goodwill getting the pilots approved and surviving the Infrastructure mess. I didn’t have another big ask in me.”

“So you hit a wall.”

“Yeah. The approach works. I know it works. But knowing it works and getting a twenty-year-old organization to let you rip out its wiring are two different things.” Edward reeled in some slack line. “That’s why I took the Cascade job. Not because Riverton failed. The medication feature is still saving lives. The pilot teams are still strong. But I wasn’t going to get the org where it needed to go. Not from the inside.”

“So what’s different at Cascade?”

“They’re letting me build a parallel organization. From scratch. New structure, new governance, new processes. The old org keeps running. The new one proves a different model. When it works, teams migrate voluntarily.” Edward paused. “It’s not like they recruited me because I’m brilliant. They recruited me because I’d already failed at the hard part and was honest about it. And they had something Riverton couldn’t give me — no legacy to fight. Meridian figured that out too. They didn’t fix their old company. They built a new one.”

“Why didn’t I see this?” His voice cracked a little. “Pick the outcome. Map the process. Separate real from invented. Prove it small. It’s basic.”

“Knowing isn’t doing.” Edward looked at him. “I knew it too, and I still only got 10% across the org. Everyone knows they should exercise. Doesn’t mean they do it. And even when they do, doing it one person at a time doesn’t transform the whole gym.”

“So everyone knows they should map their process and they just don’t?”

“Because it feels too simple.” Edward shrugged. “Stratton McKelvey wanted twenty-four months and three million dollars. Couldn’t tell me what we’d ship at the end of it. So I killed all of it. Every steering committee. Created one governance body. Five people. Meets weekly. Any engineer can ask for a decision and get an answer in twenty-four hours.”

“That sounds like chaos.”

“That’s accountability.” Edward paused. “If someone on the ground sees a blocker, they don’t wait for it to bubble up through three layers. They ask. We answer. In a day.”

Marcus laughed. Actually laughed. “So you transformed six teams by killing your own bureaucracy and then hit a wall with the other thirty.”

“Pretty much. The wall is why I’m in Seattle.” Edward grinned. “Turns out I’m good at the part where you figure out what’s broken. Terrible at the part where you make four hundred people change at once.”

“That’s not how the keynote made it sound.”

“Keynotes are highlight reels. I told them the pilot story. I didn’t tell them about the Slack channel called ‘value-stream-skeptics.’“

Marcus didn’t answer. They both knew the feeling.

“I’m not some genius,” Edward said. “I just got desperate enough to try something simple instead of something complicated. And then honest enough to admit when simple wasn’t enough.”

“And now you’re trying the hard version. Parallel org.”

“Now I’m trying the hard version. We’ll see if it works.”

Marcus picked up his pole again. Cast the line out. “Will you help me?”

“Yeah.”

“Just yeah?”

“We’re family. Our kids are basically siblings. What did you think I was gonna say?”

“I don’t know. Maybe remind me that I ignored you for two years.”

“You did ignore me for two years.” Edward grinned. “I’m still gonna help. We can do it right here. Dock sessions. Fishing poles. Value stream maps.”

“I don’t even know where to start.”

“Start with what you’re trying to build. Then map where work waits. Figure out which constraints are real and which ones you invented. Then pick the smallest thing you can prove in thirty days. Once you see the picture, the fixes are usually obvious.”

Marcus opened his mouth. Closed it. Opened it again.

“I don’t know,” he finally said. “I actually don’t know.”

“That’s the beginning. Admitting you don’t know.”

Edward reached into his pocket. Pulled out something small and metal.

“My grandfather gave me this when I left for the Academy. I took it to Iraq. Kept it in my pocket the whole deployment.” He turned it over in his hands. “Two years on the Boutwell, watching the horizon, waiting for threats that might never come. Jennifer was teaching English in Istanbul so we could see each other when I got leave. Stolen weekends in Cyprus, Athens, wherever my ship docked. I used to hold this compass and think about where I was going next.”

He pressed it into Marcus’s hand. “My grandfather said it was useless to someone who already knew where they were going. Valuable to someone willing to admit they might be lost.”

Marcus looked down. A compass. Old, scratched, clearly used.

“I can’t take this.”

“You’re not taking it. I’m giving it to you.” Edward stood up, stretched. “Come on. The families are waiting. Sarah’s probably wondering if we drowned.”

They walked back toward the house. Through the windows, Marcus could see Jennifer and Sarah in the kitchen, the kids sprawled across the living room.

“I’m sorry,” Marcus said. “For not listening.”

“I know.”

“I thought you were the one taking risks.”

“I know that too.”

“And the whole time…”

Marcus trailed off. He stopped walking.

“Harold,” he said. “That story you told me two years ago. The tape library guy.”

“What about him?”

“Essential to ornamental in eighteen months. That’s exactly what happened to me. Almost exactly eighteen months from that dinner to the IPO. I became Harold.”

Edward was quiet for a moment. “No. You didn’t.”

“How is that different?”

“Harold waited. He saw the change coming and he sat at his desk and watched his skills become irrelevant. He never asked what was next. Never mapped a new path.” Edward looked at him. “You’re asking now. You’re lost, but you’re asking. Harold never asked. That’s the difference.”

Marcus turned the compass over in his hand. The brass was warm from his pocket.

“Marcus.” Edward stopped walking. “You can apologize all night. Or you can start mapping your process. You can’t do both.”

Marcus looked at the compass in his hand. Then at the house. Then back at his oldest friend.

“What’s the outcome I’m trying to achieve?” He paused. “And where is work getting stuck?”

Edward smiled. “Now you’re ready.”

They went inside.

Chapter 13: The Looking Begins

December 25–28, 2026

CHRISTMAS DAY

Friday, December 25, 2026 (Christmas Day) – 7:30 AM – Guest Room, Edward’s House

Marcus woke to sunlight streaming through the windows.

He hadn’t reached for his phone at 5 AM. Hadn’t checked futures or overnight news. The ceiling fan turned slowly above him, and he just watched it.

He reached into his pocket and found the compass. Turned it over in his hands.

Sarah stirred beside him.

“You’re awake. And you didn’t check your phone.”

“I didn’t need to.”

“What happened last night?”

“Ed showed me where I went wrong. I never looked at my own process. I assumed it was working because I was too busy protecting it to look.”

Sarah looked at him for a long time. Then she got out of bed and started the coffee maker.

Friday, December 25, 2026 (Christmas Day) – 10:00 AM – Kitchen

Marcus found Sophia near the coffee maker.

“Can I tell you something?”

She looked up, surprised.

“Two years ago, at this table, you told stories about hackathons and AI. I dismissed them. ‘That’s great for school projects.’” He paused. “I wasn’t just wrong. I was dismissive. You showed me the future, and I refused to see it.”

Sophia set down her mug.

“Uncle Marcus, you taught me something important.”

“What?”

“When I was little, you told me the best comebacks start from the bottom.” She smiled. “You’re at the bottom now. So start the way Dad started. Map it. Be honest about what you find.”

Marcus laughed. “You sound like your father.”

“I sound like you. Two years ago. Before you got too busy to look.”

Friday, December 25, 2026 (Christmas Day) – 1:00 PM – Living Room

Christmas lunch. The families gathered.

Marcus stood up.

“I want to say something.”

The room quieted.

“Two years ago, Sophia told us stories. I dismissed them. Edward listened. He asked questions. I assumed I had answers.” He took a breath. “I lost a lot this year. Money. Reputation. Certainty. But I gained something too. Humility. And a best friend willing to teach me what he learned.”

He raised his glass.

“To asking the right questions.”

The room raised glasses in response.

Friday, December 25, 2026 (Christmas Day) – 7:00 PM – Back Patio

Edward found Marcus on the patio, looking at the Intracoastal.

“You’re going to be okay,” Edward said.

“You really think so?”

“I do. Not because you have answers. because you’re finally asking questions.”

Marcus was quiet for a moment. Then: “Ed, when you get to Seattle… do you need an unpaid intern?”

Edward laughed. “What?”

“I’m serious. I need to learn how to build with AI. Really learn. Not read about it, not hire consultants. actually do it. Hands on keyboard. The way you learned.”

“You want to be my intern?”

“I want to be a student. I spent three years thinking I was too important to learn. Look where that got me.” Marcus turned to face his friend. “I have twelve months minimum before anyone will hire me for anything real. Might as well spend it learning from the best.”

Edward turned it over. “You know what that would look like? Starting from scratch. Writing code again. Making beginner mistakes.”

“Good. I need to remember what it feels like to not know.”

“Unpaid intern.” Edward shook his head, smiling. “The former CIO of a public company wants to be my unpaid intern.”

“Former CIO of a company that tanked on day one. Not exactly a resume highlight.”

“We’ll figure something out. Maybe not ‘intern.’ But I can get you access to our training programs. Our tools. Our processes.” Edward paused. “The parallel org I’m building in Seattle — it needs people who understand what happens when you try to transform from the inside and hit the wall. Real stories about why sequential transformation fails. About what happens when you don’t look at your process, and what happens when you do look but can’t make the whole org absorb it.”

“You want me to be a cautionary tale?”

“I want you to be a teacher. The lessons you learned the hard way. other people can learn them the easy way. Through your story.”

Marcus straightened in his chair. He uncapped a pen.

“Process First,” he said. “That’s what I want to build. Help people ask the questions before they have to learn the hard way.”

“Now you’re thinking like someone who understands.”

THE CALL

Monday, December 28, 2026 – 6:30 AM – Master Bedroom

The argument happened at dawn.

Marcus had been awake since 4 AM, checking the stock price ($6.28, down another two cents), reading about Meridian’s latest customer wins, spiraling into the same dark thoughts that had consumed him for six months.

Sarah found him pacing in the bedroom, phone in hand.

“You need to stop,” she said. “The obsessing. The 3 AM research sessions. The constant checking.”

“I’m trying to figure out what went wrong. “

“You know what went wrong. You’ve known for months. What you’re doing now isn’t figuring anything out. It’s self-flagellation.”

Marcus felt heat rise in his chest. “Easy for you to say. You didn’t lose $10 million in six months.”

Sarah went still.

“I didn’t lose it?” Sarah’s voice cracked. “I lived on 0% credit cards for two years. I watched you raid our retirement accounts. I explained to the boys why Daddy couldn’t come to their games because he was saving his company. I sat in that kitchen at 2 AM listening to you tell me it would all be worth it.”

She stood up, arms crossed.

“MJ’s college fund? Gone. Isaiah’s braces? We put them on a credit card we couldn’t pay. Our tenth anniversary trip? Cancelled. I haven’t bought myself new clothes in three years because every dollar went into your dream.”

Her voice was low now, controlled, and that was worse than shouting.

“I lost it too, Marcus. I just didn’t spend six months making it everyone else’s problem.”

“That’s not fair.”

“Neither was promising me we’d finally be okay and then watching you throw it all away because you were too afraid of the board to ask questions.” She sat on the edge of the bed. “I told you. In May 2025. I said I’d watched three companies do exactly what you were doing. You told me I didn’t understand IPO mechanics.”

Marcus opened his mouth to respond, then closed it. She was right. She’d warned him. Like Derek had warned him. Like Prakash had warned him. Like Edward had warned him.

Everyone had warned him. He just hadn’t listened.

“What do you want me to do?” he asked.

“I want you to stop punishing yourself and start rebuilding. I want you to use that framework Edward taught you. actually use it, not just talk about it. I want you to figure out what you’re going to do next instead of obsessing over what you did wrong.” She stood up. “We have $3 million after taxes. Three million dollars, Marcus. We’re not broke. We’re not desperate. But we’re not rich either. Four years of sacrifice, and we ended up exactly where we would have been if you’d just stayed at Soren.” She paused. “That’s the real lesson, isn’t it? You bet everything on being right. And you were wrong.”

“It feels like one.”

“Then change how it feels. You’re the only one who can.”

She left the room. Marcus stood alone, the early morning light filtering through the blinds, thinking about the process he still hadn’t mapped. the bottlenecks he still hadn’t identified.

Monday, December 28, 2026 – 9:17 AM – Marcus’s Home Office

The phone rang. Unknown number with a New York area code.

Marcus almost didn’t answer. Then he did.

“Marcus? It’s Richard Townsend.”

Marcus sat up straight. Richard Townsend. The Chairman of the Board. he’d taken over in August when Catherine Bell resigned, and had been consolidating control ever since. Victoria Hartwell had stepped down from the board two weeks ago, exhausted by the endless crisis management. Now Townsend was the man who would decide Axiom’s future.

“Richard. I wasn’t expecting. “

“I know. That’s why I’m calling now. Before the lawyers get involved.” Townsend’s voice was calm, measured. “I want to discuss your transition.”

Marcus’s stomach tightened. Here it comes. The termination. The public statement about “new leadership” and “fresh direction.”

“I’m listening.”

“The board met on Christmas Eve. We’ve decided to offer you a package.” Townsend paused. “Chief Strategy Officer. Twelve months of garden leave. Full salary. Your options continue to vest.”

Marcus blinked. “I’m sorry. did you say garden leave?”

“Paid leave. You stay on the books, keep your title, keep your benefits. You just don’t come to the office. Don’t talk to customers. Don’t represent the company publicly.” Another pause. “There’s an NDA. Comprehensive. You don’t discuss the transition, the board’s decisions, or the company’s strategic direction.”

“You’re paying me to stay home and keep quiet.”

“I’m paying you for your years of service and your discretion during a difficult transition.” Townsend’s voice hardened slightly. “The alternative is a standard termination. Sixty days severance. Immediate vesting stop. Public announcement that the founder is being removed.”

Marcus understood. They were buying his silence. His cooperation. His willingness to fade quietly into the background while they brought in new leadership and told a different story about Axiom’s future.

A year ago, he would have been furious. Would have fought. Would have demanded his seat at the table.

Now?

“I have one condition,” Marcus said.

“What’s that?”

“I want access to everything. All the transformation materials. The AI training programs. The SDLC documentation.” He paused. “Not to compete. To learn. I want to understand what I should have built.”

Silence on the line.

“That’s… unusual.”

“I spent three years protecting a trajectory instead of asking questions. I’d like to spend the next twelve months learning what those questions should have been.”

More silence. Then: “I’ll have legal draw up the papers. You’ll have access to the technical documentation. Not the financials, not the strategic plans. but the engineering materials. The training resources.” Townsend’s voice shifted, almost curious. “Why does this matter to you?”

“Because I want to help other people avoid my mistakes. And I can’t do that if I don’t understand what I got wrong.”

“Fair enough. Papers will be in your inbox by end of week. Take a few days to review. Let me know if you have questions.”

“Richard. thank you.”

“Don’t thank me yet. You’re still losing your company. We’re just making it less painful.”

The line went dead.

Marcus sat in his home office, phone in hand, processing what had just happened.

Twelve months. Full salary. Options vesting. Access to learn.

He’d been prepared for destruction. Instead, he’d been given time.

Monday, December 28, 2026 – 10:30 AM – Kitchen

Sarah found him making coffee, a strange expression on his face.

“What happened?”

“The new Chairman called. They’re giving me garden leave. Twelve months. Full salary. Options keep vesting. I just have to sign an NDA and stay quiet.”

Sarah set down her mug. “They’re paying you to leave gracefully.”

“They’re paying me to not make noise while they rebuild.” Marcus poured coffee into his cup. “But here’s the thing. I asked for access to all their training materials. The AI programs. The SDLC documentation. Everything I should have been learning for the past three years.”

“And?”

“He said yes.”

Sarah stared at him. “So you have twelve months of paid time to learn everything you missed?”

“Twelve months to become a student again. To actually understand the tools. To ask the questions I was too confident to ask.” Marcus set down the coffee pot. “Edward offered to get me into their training programs in Seattle. Between that and Axiom’s materials… I can spend a full year doing nothing but learning.”

“And then?”

Marcus looked out the window. A boat was heading south on the Intracoastal, dragging a low wake.

“I’ll take 2027 to become relevant in 2028.” He turned back to face her. “That’s the timeline. One year to learn what I should have learned. One year to understand the questions I should have been asking. And then I help other people avoid my mistakes. Process First. That’s what I want to build.”

Sarah was quiet for a moment. Then she crossed the kitchen and hugged him.

“This is the best possible outcome,” she said. “You know that, right?”

“I know. I thought I was going to get destroyed. Instead, I got a second chance.”

“To do what?”

“To learn how to ask the right questions. And then to teach everyone else.”

Monday, December 28, 2026 – 2:00 PM – Phone Call

“Ed, you’re not going to believe this.”

Marcus told him everything. The call. The garden leave. The access to training materials.

Edward was quiet for a long moment.

“Marcus, do you understand what just happened?”

“They bought my silence.”

“No. You negotiated your education.” Edward’s voice was warm. “You asked for learning instead of money. For understanding instead of revenge. That’s the first good question you’ve asked in three years.”

“I want to do this right. The training programs, the processes, the tools. all of it. Hands on keyboard. Starting from scratch.”

“Then we start in February. When I’m settled in Seattle.” Edward paused. “First dock session. Fishing poles. And homework.”

“Homework?”

“By the time I see you, I want you to have answered those questions. Really answered them. For whatever you’re going to build next.”

Marcus looked at the compass on his desk.

“I’ll be ready.”

“I know you will. That’s why I’ve been waiting.”

Monday, December 28, 2026 – 9:00 PM – Phone Call

Edward called from Seattle that evening.

“I heard about the garden leave,” he said. “That’s actually a good outcome.”

“Better than I deserved.”

“Stop that.” Edward paused. “You’re not a cautionary tale. You’re someone who learned something expensive and is choosing to do something with it.”

“How’s the new job?”

“Different.” Edward paused. “I had my first value stream mapping session with the DevTools team today. Same questions. Different whiteboard. Different problems. But the same pattern: they didn’t know where work was waiting because nobody had ever asked.”

“And?”

“Eleven weeks from feature request to deployment. Sound familiar?” Edward laughed. “Different company. Different industry. Same waste. But this time I’m not trying to retrofit. The parallel org is clean. No legacy process to fight. No twenty-year-old governance structures. We’re designing it right from the start.”

“You sound happy.”

“I am. But I’m also aware that the parallel model is unproven. Riverton taught me what works in a room. Seattle is where I find out if it works across an organization.”

Marcus heard something in his friend’s voice. A heaviness that hadn’t been there before.

“Everything okay?”

“Jennifer and I had a conversation in November. About what this career was costing. About becoming someone I didn’t want to be.” Edward was quiet for a moment. “I was so focused on proving the approach worked that I almost lost the things the approach was supposed to protect. I’m still figuring out the balance.”

“That sounds hard.”

“It is. But it’s the right kind of hard.” Edward paused. “You’re going to be okay, Marcus. It’s a beginning.”

“I know.”

“February. Dock sessions. Value stream maps. The Process First curriculum you’re going to build. We’ll figure it out together.”

“Thank you. For everything.”

“That’s what brothers do.”

Monday, December 28, 2026 – 11:30 PM – Home Office

After Sarah went to bed, Marcus sat alone with a notebook and a pen.

What am I trying to build?

He wrote slowly, carefully:

Be relevant in 2028. Help others be relevant. Help one company ship one thing that’s been stuck long enough for everyone to call it normal.

He stopped. Drew a line through the first sentence. Too vague. Wrote again.

Then do it again. And again. Until it becomes a method instead of a story.

What’s actually stopping me?

Fear. Ego. Twelve months of momentum in the wrong direction. I told Derek his questions were noise. I told Sarah she didn’t understand IPO mechanics. I let governance structures make me feel safe instead of keeping anyone safe. Those weren’t constraints. Those were choices I made because looking honestly felt like weakness.

What does my situation actually look like?

Starting from zero. No legacy to protect. No trajectory to defend. No process to map because there is no process yet. He stared at that for a long time. That’s actually freedom. Edward spent a year fighting Riverton’s accumulated decisions. I don’t have any accumulated decisions to fight.

What can I prove in thirty days?

The compass sat on his desk. The notebook lay open before him.

At the bottom of the page, he wrote one more line and boxed it twice.

First engagement: one stuck feature, one whiteboard, one decision room, thirty days to prove the approach.

I’ll take 2027 to become relevant in 2028.

Epilogue: The Looking Never Stops

December 2027

ONE YEAR LATER

Thursday, November 18, 2027 – 2:10 PM – Plainsight Field Services, Dallas

The feature had been stuck for eleven months.

Marcus wrote the number in the top-left corner of the whiteboard and stepped back so the room could stare at it.

11 MONTHS

On one side of the table sat the product lead, a woman named Denise with a legal pad full of escalations. On the other sat the VP of Engineering, two managers, a staff engineer, and the COO who’d hired Process First after hearing Marcus speak at a manufacturing conference in September.

“All right,” Marcus said. “What outcome are we actually trying to achieve?”

The engineering manager answered first. “Complete the mobile dispatch rewrite.”

Marcus shook his head. “That’s work. What’s the outcome?”

Denise didn’t look up from the pad. “Our field techs close jobs on paper because the app takes ninety seconds to load with weak signal. In West Texas they lose connection half the time. The dispatch feature isn’t the problem. The problem is trucks sitting in parking lots while people wait for a spinner to stop.”

Marcus circled her sentence.

Close a job from the truck in under ten seconds on bad signal.

“Good,” he said. “Now walk me from code complete to a technician actually using it in the field. Not the pretty version. The real one.”

For three hours they mapped the process.

Security review waiting for a weekly slot.
QA waiting on a shared environment.
Operations requiring a CAB sign-off for pilot installs.
Product holding release notes until training approved them.
Training waiting on screenshots because the build kept changing.

By the time Marcus capped the marker, the board was a mess of arrows, timestamps, and red boxes.

“That’s forty-three days,” Denise said.

“For something your lead engineer says takes five days to build,” Marcus said.

Nobody argued.

The COO leaned forward. “What’s the move?”

Marcus pointed at the board. “One decision room. One pilot market. No CAB for a feature flag serving forty technicians in Odessa. Security in the build room, not a week later. QA on the same branch the engineers are testing. Training writes from live builds, not screenshots.” He paused. “And if any of that feels reckless, good. It means you’re looking at the delay instead of calling it normal.”

Denise stared at the board, then laughed once. Not because it was funny. Because it was obvious now and had not been obvious yesterday.

“Eleven months,” she said. “We’ve been saying rewrite when the thing we needed was one damn release path.”

Three weeks later, Plainsight rolled the feature to forty technicians in Odessa.

Median closeout time on weak signal dropped from seventy-six seconds to eight.

On December 3, Denise texted Marcus a photo from a truck cab: a gloved hand holding a phone, job closed, green banner across the screen.

No spinner. Eight seconds. The COO just approved phase two. You were right about the decision room.

Marcus looked at the photo for a long time before forwarding it to Edward with one line.

First one shipped.

Friday, December 24, 2027 (Christmas Eve) – 6:00 PM – Edward’s House on the Intracoastal

Two years and nine months since that spring break dinner when Sophia told her stories and Edward started asking questions.

Both families were around the table again. Turkey and stuffing and too many side dishes. The Johnson and Webb kids arguing over some video nobody over thirty could follow. Jennifer and Sarah in the kitchen, talking over the sound of the dishwasher.

A lot had changed.

Edward had left Riverton in the spring. Cascade Technologies, the cloud infrastructure giant, had recruited him to build a parallel organization alongside the existing 150,000-person company. A year in, forty-one teams had moved voluntarily. The first major proof point had come in October, when the new platform organization shipped an internal developer environment feature in twelve days after the legacy structure had let it sit for ninety-three. After that, the waiting list started. But Edward knew what he’d learned at Riverton: early results in a parallel org were the easy part. The hard part came later, when the parallel org got big enough to develop its own legacy, its own politics, its own reasons to resist change. He wasn’t celebrating yet.

The medication tracking feature he’d shipped at Riverton was now in more than 400 hospitals. The FDA was studying it as a model for drug interaction prevention.

Marcus had built something smaller and more stubborn. Process First Consulting had started with one paid diagnostic, then Plainsight, then five more clients who’d heard about Odessa and wanted the same question asked in their own conference rooms. It was not a rocket ship. It was better than that. It was profitable. Small on purpose. A business built around one rule: no transformation roadmap without a feature, workflow, or release path attached to it.

He’d sold his Axiom shares the day the lockup ended. Three million after taxes. Enough to pay off the equity loan, refill part of the college accounts, and buy time to start over without pretending it had all been worth it.

The book he’d written with Edward, The Process You’re Not Looking At, was coming out in the spring. Pre-orders were strong enough that his publisher had asked for a second printing before launch.

Sophia stood up during dessert.

“I have an announcement.”

The room quieted.

“Cascade offered me a job. Full-time after graduation. Product rotation first, then platform.”

Edward grinned. “I may have put in a word.”

Sophia pointed her fork at him. “Did you tell them I was the one who started all this?”

“I told them you were the first person in this family to ask the right question without turning it into a speech.”

Marcus raised his glass. “To the catalyst.”

Sophia raised hers back. “To people finally listening.”

Friday, December 24, 2027 (Christmas Eve) – 8:00 PM – The Dock

The stars were out. Edward and Marcus stood at the edge of the water, fishing poles in hand.

“Three years ago, you were eighteen months from ringing the bell,” Edward said.

“And you were trying to figure out why a feature that could save lives was still in a backlog.”

Edward reeled in slack line. “Plainsight. Eight seconds in bad signal. That’s real.”

Marcus nodded. “It felt real when Denise sent the photo. First time in a long time I looked at a result and didn’t immediately start converting it into narrative. It was just a thing in the world that worked.”

“How many clients now?”

“Six. Seventh starts in January.” Marcus smiled. “I keep saying no more than that until I know who I’d have to become to manage twelve.”

“That sounds healthier than Axiom.”

“That’s the idea. Sarah likes this version of me better.” He cast into the dark. “So do I.”

Edward was quiet for a moment. “Cascade approved the second migration wave yesterday. Twenty more teams. Nobody made a speech. They just looked at the numbers and moved.”

Marcus glanced over. “Sounds like you figured it out.”

“I figured out the first part. Building from scratch is easier than retrofitting. But we’re forty-one teams now. Big enough to have politics.” Edward reeled in some slack and cast again. “I’ve already seen two directors argue about migration priority like it was turf, not outcomes. Give it another year and we’ll have our own version of the committees I dissolved at Riverton.”

They stood there listening to the water slap against the dock.

Marcus took the compass from his pocket and turned it in his hand.

“I still carry this,” he said.

“I noticed.”

“You know what changed?” Marcus asked. “I used to think clarity was a thing you got before you moved. Like certainty was the ticket price. Now I think you move, you look, and the clarity shows up in pieces if you’re honest enough to keep looking.”

Edward nodded. “That’s closer.”

“And expensive lessons are only expensive if you waste them.” Marcus slipped the compass back into his pocket. “A year ago I was asking how to become relevant again. Now I’m asking how to keep success from turning into a new kind of blindness. That’s a better problem.”

Edward smiled. “Took you long enough.”

“Some of us need public humiliation to improve.”

“Merry Christmas, Marcus.”

“Merry Christmas, Ed.”

They walked back toward the house.

THE END

The process you never examine becomes the bottleneck you can’t fix.