There’s a great story David Pogue tells about writing the original iPhone manual in 2007.
The iPhone had just launched. Pogue was writing iPhone: The Missing Manual. The book needed roughly 400 full-color screenshots. There was just one problem.
The iPhone had no way to take a screenshot.
No keystroke. No gesture. Nothing.
Pogue knew Apple had a way — their marketing materials were full of them. So he called PR. They said yes, there’s an internal tool, but it’s an ugly command-line thing and we don’t let it out.
He pushed. Could he just borrow it for the book?
Apple’s answer: no, but fly to Cupertino and we’ll put you in a conference room under observation, you can generate the screenshots on our equipment, and go home with the JPEGs.
He booked the flight.
Right before he flew out, Apple PR called back. Steve Jobs had heard about the arrangement and killed it. No journalist was going to sit in an Apple conference room using Apple’s ugly internal tools.
The new plan: send us a spreadsheet of every screenshot you need — what’s on screen, where the windows are, what the data shows — and we’ll assign an engineer to spend the summer building them for you.
That actually happened. One engineer. Entire summer. Four hundred screenshots.
A year later, Apple was launching a new iPhone, Pogue needed to update the book, and he came back asking for screenshots again. This time Apple said no. Instead they said: we’ll just build the feature. Press two buttons at the same time and the phone will screenshot itself.
That is the gesture you have used every single time you’ve taken a screenshot on an iPhone, for almost two decades.
It exists because one journalist made it more annoying for Apple to not ship the feature than to ship it.
What this story is actually about
It’s tempting to read this as a cute origin story. It isn’t. It’s a clean lesson in how good product decisions actually get made.
For two years, Apple had a workaround. A clunky internal tool. A summer-long engineering project. A flight to Cupertino. Each one was just barely good enough to avoid building the real thing.
It took a second request — the same problem returning — to force the answer that should have existed from day one.
The screenshot feature didn’t ship because someone had a vision. It shipped because a workaround stopped being cheaper than a solution.
Why this matters for your AI strategy
Every enterprise I walk into has its own version of the Cupertino conference room.
A senior leader needs a report, so an analyst spends two days pulling it together every month. A customer service team can’t search its own knowledge base, so they maintain a private Slack channel of “things we figured out.” Finance reconciles three systems by hand because integrating them was deprioritized in 2022. Legal reviews the same five contract clauses on every deal because nobody’s templated them.
These are screenshot moments. Workarounds that became permanent because the workaround was just barely cheaper than the fix.
AI is doing something interesting to these workarounds. It’s changing the math.
The cost of building the real solution — the templated contract review, the self-serve report, the searchable knowledge base, the reconciled system of record — used to be high enough that the workaround won. With AI in the toolkit, the cost has collapsed. The summer-long engineering project is now a two-week sprint. The flight to Cupertino is a well-designed prompt.
But — and this is the part most leaders miss — the workarounds don’t disappear on their own.
Somebody has to point at them.
The diagnostic question
Walk through your organization this week and ask one question in every function:
“What’s the thing we’ve been working around for so long that we stopped noticing it?”
That’s your screenshot list.
It’s not the strategic AI initiative your steering committee is debating. It’s not the big platform decision. It’s the boring, embarrassing, decade-old workaround that everyone has quietly accommodated because the cost of fixing it always seemed higher than the cost of living with it.
AI changes that math. And the organizations that win the next 18 months aren’t the ones with the boldest AI vision. They’re the ones who systematically hunt down their workarounds and replace them.
The closing thought
The screenshot feature on your phone exists because one persistent person made the workaround more expensive than the fix.
Inside your organization, nobody is calling Apple PR. Nobody is booking a flight to Cupertino. The workarounds just sit there, year after year, costing real money and real time, hidden behind the phrase “that’s just how we do it.”
AI-Native organizations aren’t defined by how many bold initiatives they launch.
They’re defined by how aggressively they hunt down the things that should have been built years ago.
Find your screenshots.
