The Ninety-Day Test

The deck was beautiful. The roadmap was ambitious. Every word was correct: platform, ecosystem, enterprise, AI, expansion. Every slide looked like strategy.

I asked one question.

What ships in the next ninety days?

Not what might ship. Not what the theme implies.

• What will a customer touch?
• What job gets better?
• Who owns the outcome?
• What number tells us it worked?

The room went quiet. Someone reached for a dependency. Someone reached for a caveat. Someone reached for the vision. Nobody reached for a date, an owner, or a metric.

That silence is the tell. Most product strategy is theatre.

What theatre is

Strategy theatre is the production of strategy artifacts whose real function is performance rather than execution. It has all the props: market maps, vision statements, strategic pillars, three-year roadmaps, TAM slides. It looks exactly like the work.

It is missing one thing. A choice that could have gone another way.

• No customer is chosen over another.
• No workflow was selected as the wedge.
• No feature killed to fund the bet.
• No metric that could prove the team wrong.

Strategy is a choice under constraint. No constraint, no choice. No choice, no strategy.

A strategy that does not tell you what will not happen is a narrative. Narratives are useful. They are not a strategy. Real strategy reallocates time, talent, capital, and sequence. It closes doors. It is uncomfortable by design.

Theatre avoids the discomfort. It keeps every door open and every stakeholder seen. Everyone leaves the room aligned. Nothing changes on Monday.

Why theatre survives

Theatre is not a conspiracy. It is an equilibrium. It protects people from exposure.

Propose a sharp strategy, with a named customer and a written list of what you will abandon, and you become measurable. People can argue with you. Leadership can hold you accountable when the bet fails.

Produce a broad, well-written narrative, and you are safe. Sales see expansion. Marketing sees the category story. Engineering sees platform architecture. The board sees TAM. Nobody loses. Nobody decides.

One thing in theatre’s defense. The grand narrative has a legitimate job. A CPO needs air cover to raise money, brief a board, and align a global go-to-market team. You cannot walk into a boardroom with nothing but a ninety-day delivery schedule.

The crime is not the narrative. The crime is failing to translate the narrative into a sequence of hard choices on the floor. That is where most organizations stop. The document gets written for the most senior audience, alignment becomes the goal, and the review becomes a ceremony where approval replaces improvement. The deck ships. The strategy does not.

I have made this mistake. I have shipped the deck that created universal agreement and changed nothing on Monday morning. Comfort is not clarity.

The test

Pick any item labeled a strategic priority and ask: what ships in the next ninety days because of this, and who owns it? Keep asking until the answer lands or collapses.

Ninety days does not require landing on Mars. It requires the rocket to leave the atmosphere. Something must become more true.

• A customer touches a working workflow.
• A critical technical risk is retired.
• A pricing signal is tested with real buyers.

“Ships” does not have to mean a GA release. It can be a workflow proof, an instrumented experiment, or a design partner in production. But it must be inspectable. It must change reality.

If nothing can change in ninety days, you may have a vision or a thesis. You do not yet have a strategy.

What theatre sounds like

“We are building an enterprise-grade AI platform that helps organizations manage risk across all digital touchpoints. It serves Legal, Marketing, and Operations. The roadmap covers every channel and every segment, with a land-and-expand motion. Q2 is trust, Q3 is scale, Q4 is monetization. The market is enormous and we are uniquely positioned to win.”

It sounds familiar because most decks say a version of it. It is directionally correct, unfalsifiable, and useless to an engineer.

What a real answer sounds like

Here is the version I can defend because I live it.

Straker spent over two decades in the translation and localization business. AI collapsed the price of raw translation. Defending the old category was a losing bet, so we made a different one: arbitr, the trust layer between AI and live systems.

The wedge is not translation. The wedge is governed review. AI drafts the output. Humans verify it. The system records the source, the changes, and the approval.

The ninety-day proof was not a slide. We shipped a human-in-the-loop release internally in 30 days. We shipped a comprehensive vendor selection, management, and review 20 days later. The second date mattered more than the first because it started the sunset clock on two legacy products with real revenue attached. That is the tradeoff in writing, with consequences.

The metric is three (3) existing enterprise customers running Multilingual Risk Triage in production on live multilingual content workflows in the first 30 days, with each customer showing repeat weekly reviewer action and one quantified value signal, owned by the GM for the Trust & Intelligence transition. The kill rule is written down: if the workflow does not prove repeatable value with the first cohort, we halt expansion and re-evaluate before the sunsets complete.

The two most common disguises

The platform story. Companies tell a platform story early because it implies scale and defensibility. Platform language must be earned. Customers do not trust a platform because you announce one. They trust it because you solved one painful workflow, built operational confidence, and expanded from earned credibility. Wedge first. Trust second. Platform third.

The all-customers strategy. Targeting everyone feels safe because it broadens the commercial reach. It is a political compromise dressed as market expansion, and usually the easy way out of a hard fight with the head of sales. When every customer matters, no customer teaches you anything. Feedback fragments. The roadmap becomes a negotiation between anecdotes.

The rules that collapse theatre

Theatre lives in ambiguity. Remove the ambiguity, and the props stop working.

• No roadmap item without a specific customer, a specific job, and a validation metric.
• No strategic priority without a named tradeoff.
• No owner without the authority to allocate and cut.
• No platform initiative funded without a proven workflow wedge.
• No quarterly plan approved without a stop-doing decision.
• No launch celebrated until the customer outcome is verified by data.

A roadmap without evidence is an inventory. Bets need kill rules before they need budgets. The list of things you will not build is a strategy asset, not an admission of weakness.

The only question that matters

The next time someone hands you a beautiful strategy deck, look past the polish and ask: what ships in the next ninety days, for whom, and who owns the outcome?

If nobody can answer, stop pretending. Call it a vision. Call it a pitch. Call it a board narrative. Do not call it strategy.

Strategy is not a slide. It is a sequence of decisions. The work is to make choices that change what ships.