Gate Delay 3270 Chapter Two: The Marketing Problem

The airport lighting had shifted subtly, from harsh white to that late-afternoon honeyed hue that
made everything look vaguely nostalgic. The screens still showed the same red DELAYED
message, and the terminal speakers had fallen into an awkward silence, as if even the announcement system was unsure what came next.

Jamie closed their laptop with a sigh. “You know,” they said, staring into the middle distance, “it’s
weird. I’ve been through onboarding at two different companies, sat through three architecture
bootcamps, and not once did anyone mention the word mainframe. Not even in the ‘legacy we don’t talk about’ slides.”

Frank chuckled. “That’s because no one wants to admit how much they depend on something they don’t understand.”

Dana raised an eyebrow. “Or how much it costs.”

Alex leaned forward, hands steepled like a podcast host ready to stir debate. “That’s the real issue, isn’t it? It’s not that mainframes don’t work—it’s that they’re expensive, exclusive, and come with a culture that hasn’t adapted to the modern developer.”

Frank tilted his head. “And yet, when you need to process a billion transactions in a day without
losing a single record, who you gonna call?”

“No one,” Sam said, looking up from their book. “Because nobody knows it’s even happening.”

That drew a pause.

Dana, still calm but clearly reflecting, folded her arms. “You’re not wrong. At the board level, we
never see the mainframe. It’s buried in infrastructure budgets. It doesn’t show up in digital
transformation dashboards. You don’t pitch it to investors. It's a black box.”

“Exactly,” Alex said. “It’s got no narrative.”

Jamie grinned. “You mean it needs a personal brand?”

Frank actually laughed. “You joke, but maybe it does.”

Sam gestured vaguely around them. “If this delay teaches us anything, it’s that even the invisible
stuff matters. Especially the invisible stuff.”

Dana’s gaze dropped to her tablet. “We spend millions trying to modernize what’s on the surface. UX, customer apps, dashboards. All the glitter. But the foundation is never part of the story. The story is always ‘replace the old thing’—never ‘understand what the old thing actually does.’”

“You don’t rebuild the Eiffel Tower because the elevator buttons are outdated,” Frank said.

Jamie’s brow furrowed. “So how do we fix that? How do we make it... relevant again?”

Alex leaned back. “Tell better stories. Make it approachable. Bring it into the light. You can’t keep
calling something 'critical' and then treating it like a dirty secret.”

Frank nodded. “And maybe stop pretending that everything new is automatically better. Hybrid
isn’t a compromise—it’s a strategy.”

Dana’s fingers tapped against the tablet. Slowly. Thoughtfully. “If I’m honest, I’ve only ever seen
the mainframe show up during budget reviews. Usually as a cost center. Never as a value driver.
And certainly never as a source of innovation.”

“Then maybe that’s where we start,” Jamie said, surprising even themself. “Don’t pitch it as
infrastructure. Pitch it as opportunity. Talk less COBOL, more capability.”

Alex smiled. “We don’t need to modernize the mainframe. We need to modernize the conversation.”

Another pause. This one quieter. More grounded.

In the distance, a fresh update blipped on the screen. The flight now had an estimated departure
time—four hours from now.

Frank glanced at it and then looked back at the group. “Looks like we’ve got time to save the world after all.”