A strategy makes choices

 
 

BuzzAnalysis suggests that for AI concerns, it's vital to acknowledge that a plan is not a strategy, as AI reshapes organizational roles, capabilities, and competitive landscapes. Below, tips for AI start-ups to manage the difference.

At its core, a plan is a list of controllable actions—focusing on what you can manage internally, like resources, timelines, and budgets. It's reassuring because it deals with certainties: "We'll do X, Y, and Z."

A strategy, however, is an integrated set of choices that positions your organization to win on a specific playing field. It involves a coherent theory about customers and competitors, embracing risks since outcomes depend on external factors you can't fully control.

Plans feel safe—they're about "playing to participate"—while strategies demand discomfort, hypothesizing why your approach will succeed where others fail. As  architects and analysts, we often excel at planning through capability maps and roadmaps, but strategy requires us to link these to a bigger picture: What must be true for this to work? It's a humble reminder that not everything is under our control.

In our field, business architecture is about alignment—connecting vision to capabilities, initiatives, and requirements. But without a strategy underpinning it, our work can just be incremental improvements rather than transformative impact.

A plan might detail enhancing a capability like "customer management," but a strategy asks: How does this help us win customers in a
competitive landscape?

Here are some key reasons this matters, in bullet points for clarity:

  • Alignment with Uncertainty: Strategies embrace market dynamics, while plans assume predictability—crucial in volatile areas like AI.

  • Avoiding Silos: Plans can lead to disconnected efforts; strategies ensure coherence across the organization.

  • Facilitating Iteration: Strategies allow for testing assumptions, using tools like knowledge bases to refine approaches.

  • Humility in Practice: We must admit that strategies involve bets, not guarantees, encouraging adaptive architectures.

From my observations, teams often call detailed roadmaps "strategic" when they're just comfortable checklists. Strategy requires stepping
into the angst of customer-driven outcomes.

Real-World Examples

To illustrate, let's look at industries where this plays out. Airline Industry: Major carriers planned expansions (e.g., more routes, bigger hubs)—controllable actions that kept them in the game. Southwest's strategy? Target short-haul, low-cost travel as an alternative to buses:

Standardized on Boeing 737s for efficiency. Point-to-point flights, no meals, online bookings. Theory: Simplify to offer lower prices, winning price-sensitive customers. Outcome: Southwest gained market share; others shared a shrinking pie.

Retail Sector: Walmart didn't just plan store openings; their strategy integrated cost-leadership:

Leverage scale for supply chain dominance. Everyday low prices to attract budget shoppers. Theory: Be the cheapest and most accessible, outpacing competitors on efficiency. Smaller chains with growth plans often fail to compete without this coherence.

Disruptive Cases:

Netflix: Strategized convenient streaming over physical rentals, betting on anytime access. Uber: Empowered gig drivers and users via app, disrupting taxis with flexibility.

These examples highlight that plans ensure activity, but strategies create winning theories. In architecture terms, map these to capabilities tied to value propositions.

In AI, where disruption is accelerating, confusing plans with strategies is especially common. Many organizations plan AI adoption (e.g., "Buy tools, train teams") without a theory of victory. For architects and analysts, this means shifting from tactical roadmaps to integrative choices across key dimensions, with a strong emphasis on business architecture capabilities. These capabilities represent the high-level, stable abilities of the organization—what it does to deliver value, such as "Customer Management" (as defined in frameworks like BIZBOK). In an AI context, strategies should align AI initiatives to enhance, automate, or disrupt these capabilities, ensuring they support competitive positioning rather than isolated tech implementations.

Here's five critical dimensions for AI strategiest:

Capabilities: High-level business abilities enhanced by AI systems to solve problems and deliver value (e.g.,  "Customer Management" capability,  aligning to strategic goals like market expansion).

Infrastructure: Scalable tech foundations that support capability execution, such as vector databases and data pipelines, enabling secure processing at scale without disrupting core business abilities. Talent: Human capital, including architects and analysts, upskilled to map and refine AI-enhanced capabilities (e.g., training teams to integrate AI into capability models for better requirement elicitation).

Governance: Oversight mechanisms to ensure AI aligns with ethical standards and risk mitigation, protecting capability integrity (e.g.,
bias checks and performance metrics tied to capability KPIs). Tools: Third-party accelerators that speed up capability development
and deployment (e.g., chat interfaces or decision dashboards to prototype AI within existing capability maps).

A plan addresses these in isolation; a strategy integrates them with a hypothesis:

"How will this combination enhance our business capabilities to win customers?"

Read the whole thing here.

Follow Opportunity Now on Twitter @svopportunity

We prize letters from our thoughtful readers. Typed on a Smith Corona. Written in longhand on fine stationery. Scribbled on a napkin. Hey, even composed on email. Feel free to send your comments to us at opportunitynowsv@gmail.com or (snail mail) 1590 Calaveras Ave., SJ, CA 95126. Remember to be thoughtful and polite. We will post letters on an irregular basis on the main Opp Now site.

christopher escher