The Conversation That Did Not Move

I was running product at a midsize white-label content portal company right as the iPhone and iPad were rewriting how people used the web. People were moving from desktop to mobile almost overnight, and the company had built its entire business around optimizing the desktop experience, on a tech stack that was falling behind and losing support. Something had to change. I tried to convince the executives with data, charts, and usage trends. They nodded, agreed there was an issue, and resisted any real change. They had a cash cow. They had steady service revenue from business customers. They had no appetite to risk it.

Why Data-Driven Pitches Lose

Most strategic failures result from beliefs that were never examined. Most people leading this kind of work report chronic difficulty getting buy-in. Leaders can read a chart. A chart of a future trend just does not feel like a future they have to do anything about today. Reactive cycles are expensive, because the moment to move usually arrives wrapped in the comfort of the current quarter being fine.

You are constantly investigating the quantitative insights... and also the qualitative insights.

The job is data-informed, not data-driven. Quantitative work tells you what is happening. Qualitative work tells you whether what is happening is what matters. The executives I was pitching had the quantitative work. What they were missing was the qualitative experience of the future, which is what a prototype provides and what a chart cannot.

The Move That Changed the Room

I built interactive prototypes. I ran scenarios that showed how things looked fine today and how the underlying forces were pulling us toward a bad outcome. And I enlisted allies. I worked with engineering by showing them that a portal rebuild was their chance to adopt a more flexible, supported stack. I worked with our head of business development to take prototypes out to customers and let them see the future they were going to face. When I came back to the executives with prototypes, scenarios, and an engineering leadership team explaining it was all doable, the conversation changed completely. We rebuilt the product, expanded into new verticals, and gave the business a new lease on life.

Support a few crackpots, heretics, and dreamers, especially if they are wildly optimistic about their ideas.

The new CTO who wanted to bring modern thinking into a change-resistant culture was, in the executives' eyes, a heretic. The business development lead willing to walk a half-built prototype into a customer meeting was a crackpot. Both were right. Adaptive moves get made by the people the existing leadership has not yet learned to take seriously. Stakeholder Empowerment, the second step, is the practice of finding those people deliberately and giving them a real voice in the cycle.

A Brief Note on Apple Pie Positions

Shreyas Doshi has a useful name for the kind of language that gets a leader nodded along to without committing to anything: the Apple Pie Position, a statement that instantly elevates the person who is saying it and is simultaneously hard for anyone else to push back on. Leadership conversations are full of them. "We need to be more customer-centric." "We have to be willing to change." "Strategy has to be adaptive." Each one is true. None of them produces a decision. The framework's Safe Space Reset is built specifically to convert apple-pie agreement into a real choice with a real owner and a real timeline.

How to Evaluate a Change Pitch

• Replace the chart with a prototype whenever you can. A working artifact is something an executive can feel.
• Run two scenarios in parallel rather than a single recommendation. One that assumes the current strategy holds, one that assumes the trend lands. Let the executives compare the futures side by side.
• Find your engineering ally before your executive meeting. Resistance to change shrinks when the technical leader in the room is explaining how it gets done.
• Bring a customer into the conversation. Internal data can be argued with. A customer naming the future they expect from you cannot be argued with as easily.
• Frame the move as protecting the cash cow, not threatening it. Adaptation extends the runway of the existing business; it does not abandon it.

SharedForesight's Stakeholder Empowerment and Radical Voice steps exist because of this experience. Bringing data is necessary and it is not sufficient. Bringing people into the prototype, the scenario, and the conversation with whoever you serve is what changes a direction.