Beyond Wishful Thinking: Why Modern Design and Strategy Fail Without a Core Framework

SAN FRANCISCO — In an era dominated by rapid technological disruption, artificial intelligence integration, and the constant demand for organizational agility, corporate leaders and innovation experts face a persistent paradox. Despite having access to more data, advanced design frameworks, and strategic tools than ever before, companies continually misinterpret their core challenges.

According to a recent industry analysis sparked by discussions among design leaders, the root of this failure is not a lack of effort or ambition, but a fundamental misunderstanding of what constitutes a real strategy and an effective problem frame.

Drawing parallels from Richard Rumelt’s seminal business text, Good Strategy Bad Strategy, industry veterans argue that organizations routinely mistake high-level goals and inspiring rhetoric for actionable strategy. This shortfall, experts warn, has bled directly into modern design thinking, leading to widespread superficial problem framing that stalls innovation before it even begins.

Chronology of a Paradigm Shift: From Business Strategy to Design Framing

To understand how modern organizations arrived at this methodological crossroads, it helps to examine the evolution of strategic thinking over the past two decades:

• The Early 2000s (The Rise of Ambition): Corporations increasingly adopted mission statements, vision boards, and innovation workshops. Strategic plans frequently ballooned into massive, multi-page slide decks laden with corporate jargon, often functioning more as motivational posters than actionable blueprints.
• The Mid-2010s (The Proliferation of Design Thinking): As design thinking gained corporate dominance, "problem framing" became a standard buzzword in innovation briefs and agile sprints. However, the practice often devolved into endless brainstorming sessions and expansive canvases that captured endless data without driving focus.
• Recent Years (The AI Disruption and Search for Essentials): With generative AI accelerating the production of content, code, and design assets, the volume of available information has exploded. Leaders like Lucas Mara and academic researchers began revisiting classic strategic foundations—such as Rumelt’s core strategic kernel—to filter out the noise.
• Present Day (The Hunt for the Problem Kernel): Industry leaders are actively pushing back against bloated methodologies, seeking minimalist, high-impact frameworks that strip away corporate theater and return to the bare essentials of defining and solving complex problems.

Main Facts: The Anatomy of a Bad Strategy

The modern critique of strategic planning begins with a foundational premise popularized by Rumelt: bad strategy is not simply the absence of good strategy.

Most organizations fail because they mistake goals for strategy. A company might state, "Our strategy is to grow market share by 20% through AI-driven personalization." While clear and ambitious, this is merely a statement of desire. It lacks the structural mechanics required to navigate obstacles.

According to Rumelt, a genuine strategy requires a precise kernel consisting of three inseparable components:

1. A diagnosis of the specific challenge at hand.
2. A guiding policy for dealing with that challenge.
3. A set of coherent actions executed in alignment with the policy.

Without all three elements present, an organization does not possess a strategy—it possesses a wish.

This exact diagnostic failure manifests daily within the design industry. "Designers and organizations talk about ‘problem framing’ constantly," notes design leader Morteza Pourmohamadi. "It appears in every design thinking workshop, every strategy deck, and every innovation brief. But what is actually at the heart of a problem frame? What are the bare minimum elements without which you simply don’t have one?"

Supporting Data and the Cost of Ambiguity

The corporate penchant for unstructured problem framing carries a steep price. Industry data surrounding digital transformation and product development highlights a systemic disconnect between initial planning and execution:

• The Scope Creep Penalty: Studies in agile product management indicate that up to 45% of feature development time is spent on items that deliver little to no user value, frequently traced back to poorly defined initial problem statements.
• The Alignment Gap: According to organizational surveys by leading management consultancies, fewer than 30% of employees can clearly articulate their company’s overarching strategic priorities, pointing to a failure in strategic communication and editorial focus.
• The Proliferation of Tools vs. Outcomes: Despite the introduction of hundreds of proprietary design toolkits and digital whiteboarding templates over the last decade, failure rates for major corporate innovation initiatives remain stubbornly high, hovering near 70%—largely attributed to teams jumping straight to ideation without rigorous problem scoping.

Echoing the famous observation by Blaise Pascal—"I would have written a shorter letter, but I did not have the time"—experts emphasize that true rigor lies in reduction, not expansion.

The Solution: The Three-Step Problem-Framing Kernel

To combat the tendency toward bloated, unactionable problem spaces, design leaders have distilled effective problem framing down to its absolute minimum viable components. Referred to as the Collect, Connect, Commit kernel, this framework serves as both a operational guide and a diagnostic tool.

1. Collect: Embracing Disciplined Divergence

The initial phase of problem framing requires gathering everything potentially relevant: concepts, functions, user needs, regulatory requirements, stakeholder expectations, underlying assumptions, and known unknowns.

Design challenges are inherently ill-defined; a complete picture never exists at the outset. Consequently, the work begins by deliberately expanding the canvas. However, experts stress that this is distinct from casual brainstorming. It is a systematic assembly of raw materials. A narrow initial collection inevitably yields a narrow frame, regardless of how sophisticated the subsequent analysis might be.

2. Connect: Unearthing Tension and Insight

Once the raw elements populate the table, the analytical work commences. Connections represent the relationships between collected items, forming the bedrock of genuine insight.

While some connections are expected, the most valuable insights often stem from surprising, weak, or contradictory relationships. Tensions and opposing forces within a data set are vital; a problem frame built exclusively from comfortable, harmonious elements usually indicates that a team has skirted the hardest parts of the challenge. Real problems are tightly interconnected, leaving little room for elements that float freely without relation to the whole.

3. Commit: The Act of Editorial Judgment

Commitment is where the majority of problem-framing efforts collapse. A team may meticulously collect elements and map complex connections, but until they deliberately choose which factors to foreground and which to set aside, they lack a frame—they merely possess a landscape.

Committing is an act of editorial curation, akin to a film director executing a final cut. There is always more data that could be included, but the discipline of framing lives entirely within the exclusion. Two separate teams can ingest identical data and map identical connections yet arrive at completely different frames based on their distinct judgments of what matters most. Far from a process flaw, this subjective editorial judgment is the core of design practice.

Implications for the Future of Design and Strategy

The implications of adopting a strict problem-framing kernel extend far beyond individual workshops or design studios. As artificial intelligence automates routine ideation, data collection, and rapid prototyping, the human value in product development shifts decisively toward framing and judgment.

Operational Diagnostics

The three-element kernel functions as a diagnostic tool for stalled projects. When a design sprint or strategic initiative feels sluggish, unactionable, or uninspired, teams can audit their process against the kernel:

• Did we collect data too narrowly?
• Are the connections between our insights underexplored?
• Have we avoided the discomfort of making a definitive commitment?

The Death of Scaffolding as Substance

In contemporary corporate environments, methodologies, software licenses, agile certifications, and elaborate canvas templates often masquerade as strategy. The kernel highlights a sobering reality: all external tools are merely scaffolding. They are useful, and at times essential, but they are not the structure itself.

Organizations that rely on the ceremony of design thinking without mastering the underlying cognitive acts of collecting, connecting, and committing will continue to produce elegant wishes rather than robust strategies.

As the lines between business strategy and design execution continue to blur in a tech-driven economy, mastering the fundamental kernel of problem framing will separate organizations that merely generate activity from those that drive actual, meaningful transformation.