Why Data Alone Won't Save Your Strategy

Picture a manager in the disk-drive business, watching a smaller, cheaper drive land in the market and deciding, quite rationally, to ignore it. His best customers didn't want it. His margins looked better without it. And yet, in Clayton Christensen's famous study of that industry, that reasonable choice is exactly how established firms kept missing the technologies that eventually displaced them. Christensen, a Harvard Business School researcher, dug into the disk-drive industry to understand why established firms could miss what entrants saw as promising. What he found changed how we think about strategy. And Wesam, this is the puzzle we'll sit with: the problem wasn't laziness or bad data. It was the absence of a strategic lens, the habit of seeing every decision as connected to a long-term position.

So what actually separates strategy from just reacting well? Michael Porter, arguably the most influential voice in strategy, drew a hard line here. Strategy, he argued, means creating a unique and valuable position through a different set of activities, not merely doing the same work more efficiently. That distinction matters because operational improvements, things like quality, speed, productivity, can be copied. Rivals imitate them, and your advantage evaporates. Porter went further: real strategy requires trade-offs. Choosing what not to do is how a company preserves a distinctive position instead of trying to serve every customer in every way. His airline example makes it concrete. Serving meals on flights sounds like a small service choice, but it adds cost and slows gate turnaround. You cannot just bolt on features without consequences. And the strongest advantage, in his view, comes from activities that reinforce one another, so the whole system is harder to copy than any single practice.

Now, here's where I want to bring in the lens itself, the tool that turns ordinary observations into strategy. Consider Porter's five forces framework. It asks you to assess rivalry, new entrants, substitutes, and the bargaining power of both buyers and suppliers. Notice what that does. It forces you to look past your direct competitors, because substitutes and the negotiating power of customers and suppliers can constrain your profitability just as much. It also separates two questions people constantly blur: whether an industry is attractive, and whether your position within it is strong. A strong position can matter even in a challenging industry. For example, suppose you run a coffee shop against giant chains. Instead of asking how to make coffee faster, the five forces push you to ask who has leverage over you, what customers could substitute for you, and where a new entrant might sneak in. Same street corner, completely different conversation.

Which brings us back to Christensen, because his disk-drive findings reveal something uncomfortable about listening to customers. In his account, entrants often started with products more suitable or affordable for an underserved segment, while incumbents focused on their most demanding, most profitable customers. Smaller drive architectures, like the 3.5-inch, initially followed performance trajectories the incumbent customers didn't value, so established firms rationally looked away. The counterintuitive lesson is that listening closely to current customers can still leave you exposed. One number from that research stuck with me: roughly six percent of entrants pursuing a sustaining strategy, meaning matching incumbents on their own performance dimensions, succeeded. Six percent. That's, that's like betting your savings on a horse that almost never comes in. And disruption, in this research, isn't a synonym for any successful innovation. It describes a particular path, starting from a low-end or new-market foothold and moving toward broader competition with established firms.

So how do you actually use this, starting today? Treat your routine observations as raw material. An unserved customer, a frustrating workaround, a shifting industry pressure, these are hypotheses to test, not proof an opportunity exists. Run three questions through your business each month. Who is underserved right now, and overserved by what we already offer? What trade-offs are we willing to make, and I mean genuinely willing, to protect our position? And what would we never do, even if a competitor did it first? Strategy is choosing what not to do, before circumstances choose for you. That's the lens. The manager in the disk-drive business wasn't foolish, Wesam. He just never looked up from this quarter's best customers long enough to ask what position he was drifting toward. Now you can.

A plan that was working perfectly on paper bled quietly for months, and the company never felt it. That's what breaks when execution runs without feedback, Wesam. Not a dramatic collapse, just a slow leak nobody notices until the numbers dip. Take a tech firm I want to tell you about, Orion Devices. They shipped a flagship smartwatch with a bold health-tracking promise, watched early sales jump, and then waited for the hockey-stick curve that never came. What they didn't have was any systematic way to hear what the market was telling them, in real time, while they could still act on it. [fact:none]

Orion's launch ran on an internal belief: a compelling product, well marketed, sells itself. Which sounds reasonable, right? You build the thing, you announce the thing, buyers come. And because they trusted that belief, the launch plan had no systematic feedback mechanism at all. No listening posts. No structured way for user behavior to travel back to the people making decisions. So when the sales curve went flat, they were steering by a map drawn before the trip started. Think of it like driving a long highway at night with your headlights off, convinced the road can't have changed since you last looked. [fact:none]

Now, the puzzle. A senior executive, the CEO, stared at the plateau and asked the question that should have saved them: why aren't customers adopting the product as expected? From there, the wrong turn. They tried three tactics, marketing pushes, partnership deals, retail incentives, and measured all of them by a single metric, sales volume. That's like judging a patient's health by weight alone. Their diagnosis assumed low adoption meant weak demand. But early adopters, the people who'd already bought, were complaining about something else entirely. The product experience itself. The demand was there. The product was pushing it away. [fact:none]

And what convinced me this story is about feedback, not luck? After three months, a field-service engineer, out on routine calls, discovered a real-world defect. A software glitch, linked directly to product returns, that no dashboard in the building had caught. The evidence was literally sitting in customers' homes. By the time anyone connected the returns to the glitch, the company had spent a quarter of its launch budget solving a problem it didn't have. A week of listening to support calls might have surfaced it. Instead, the information existed and simply had no path back to the decision-makers. [fact:none]

So the VP of product development authorized a rapid-feedback loop, and the design of it is worth remembering. Three components: telemetry dashboards delivering real-time user data, and not just to analysts, directly to the product development team; automated alerts flagging issues the moment they appeared; and a standing process for folding what came back into the roadmap. Within one quarter they shipped a software patch and a refined interface targeting the actual complaints. Real-time is the operative word here. Feedback that arrives after the decision is just a postmortem. The loop has to close faster than the market changes, or it's decoration. [fact:none]

The result, and this is the number worth carrying around: adoption surged twenty-seven percent in the quarter after the patch landed. Same product. Same market. Different listening. I'll admit, when I first read that kind of turnaround, I assumed the fix must have been some brilliant new feature. It wasn't. It was the absence of noise, the, the defect and friction, removed once someone finally knew it was there. Which tells you something uncomfortable, Wesam. Execution isn't a phase where the plan gets carried out. It's a phase where the plan keeps getting rewritten, and rewritten fast. [fact:none]

Scale that up and the cost compounds. Suppose you run a team shipping anything, software, services, a product line. Every week without a feedback loop is a week of small decisions compounding on bad information. A quarter of wasted budget is what it cost Orion; for a smaller firm, that's not a bruise, that's survival. And here's the part strategists still argue about. Some hold that strong upfront analysis makes feedback loops unnecessary overhead, that a great plan shouldn't need mid-course corrections. Others answer that no plan survives contact with users, so the loop is the plan. [fact:none]

I sit closer to the second camp, but the disagreement is genuinely live, because building loops costs money and discipline, and some companies do over-correct into chasing every complaint. Where the argument will settle, nobody quite knows yet. What I'd leave you with is this tension: Orion didn't fail at planning, and they didn't fail at building. They failed at the space between, where reality is supposed to flow back in and reshape the work. Strategy dies quietly when nobody's listening. Keep a channel open, and it stays alive. [fact:none]