The Architecture of Intent: Why "Problem Framing" Requires More Than Just Ambition

In the fast-paced world of modern business, leaders often conflate movement with progress. We hold endless workshops, fill digital whiteboards with sticky notes, and draft strategic decks that look impressive on screen. Yet, when the dust settles, many organizations find themselves running in place.

A recent dialogue between design leader Lucas Mara and industry peers has reignited a critical conversation regarding the intersection of strategy and design. At the center of this discourse is Richard Rumelt’s seminal work, Good Strategy Bad Strategy. While the book is over a decade old, its central thesis—that “bad strategy is not simply the absence of good strategy”—has become a clarion call for designers and executives alike.

As the digital landscape evolves under the pressure of AI and rapid market shifts, the ability to accurately define a problem has become the most valuable currency in business. This article explores the "kernel" of problem framing, arguing that without a rigorous, three-part architecture, most design efforts are merely wishful thinking.

The Strategic Fallacy: Ambition vs. Reality

For many organizations, strategy is often mistaken for a collection of goals. We see mission statements that promise “industry-leading innovation” or “customer-centric growth.” These are not strategies; they are desires. Rumelt’s core argument is that a functional strategy requires a “kernel”: a diagnosis of the challenge, a guiding policy for addressing it, and a set of coherent actions.

When we apply this lens to the field of design, a troubling trend emerges. Designers and product teams talk incessantly about “problem framing.” It is the bedrock of design thinking, yet it is frequently treated as a superficial exercise. We collect data, we observe users, and we create personas—but do we have a frame? Or are we simply cataloging the landscape?

Chronology of the "Kernel" Concept

The evolution of problem framing from a vague design practice to a disciplined methodology has been a gradual process, marked by several key shifts in professional philosophy:

• The Era of Divergence (2000–2010): Following the popularization of IDEO’s design thinking, the focus was almost entirely on "Collect." Teams were encouraged to gather as much data as possible. The belief was that more information would naturally lead to better solutions.
• The Era of Mapping (2010–2020): As design systems matured, the emphasis shifted toward "Connect." Organizations began utilizing complex mapping exercises—customer journeys, empathy maps, and system diagrams—to visualize relationships between data points.
• The Era of Intent (2020–Present): In the current climate, where AI can synthesize data in seconds, the role of the designer has shifted from researcher to editor. The focus has moved to "Commit"—the act of making high-stakes editorial decisions about what not to do.

The Three Pillars of Problem Framing

If we are to move beyond the superficial, we must distill problem framing to its absolute essentials. Drawing on the principle that the most profound insights are often the most concise, the kernel of any successful problem frame can be reduced to three distinct, non-negotiable phases: Collect, Connect, and Commit.

1. The Art of Disciplined Collection

The first phase is not brainstorming; it is a systematic gathering of the problem space. This involves identifying functions, needs, stakeholders, constraints, and the often-ignored “unknowns.”

This phase is about expanding the canvas. Many teams fail here by starting with a preconceived notion of the solution, which inevitably leads to "confirmation bias" in the collection process. True collection is expansive and exhaustive. Without a rich, high-resolution dataset, the subsequent steps of the process will inherently lack the depth required to solve complex, ill-defined problems.

2. Mapping the Interconnected Landscape

Once the data is collected, the designer must transition from an observer to a synthesizer. This is the "Connect" phase. The objective is to identify the relationships between the gathered elements.

In a robust problem frame, everything is linked. Isolated, free-floating data points are usually symptoms of a lack of depth. Designers should specifically look for tensions and contradictions. If two data points pull in opposite directions, you have found the friction where the real problem resides. Tidy, harmonious frames are often the result of ignoring the difficult realities of the market; truly innovative frames are built from the friction of opposing requirements.

3. The Necessity of Commitment

The final, and perhaps most difficult, pillar is "Commit." This is the editorial act. To frame a problem is, by definition, to exclude.

In a world of infinite data, the designer’s primary value is their ability to decide what to ignore. This is where most organizations stumble. They attempt to solve for everyone and everything, resulting in a diluted, ineffective strategy. A strong frame requires the courage to say, “This is the specific challenge we are solving, and these are the factors we are choosing to deprioritize.” This is not a failure of research; it is the pinnacle of design leadership.

Supporting Data: Why Framing Matters

Industry performance data suggests a direct correlation between early-stage framing and project success. According to various innovation benchmarks, projects that spend more time in the "Problem Framing" stage exhibit a 30–40% higher rate of market adoption compared to projects that rush to the "Solutioning" phase.

Furthermore, teams that engage in explicit "Commit" sessions—where stakeholders are forced to vote on the exclusion of certain features or problem areas—report higher levels of alignment throughout the development lifecycle. When the team understands not just what they are building, but why they have chosen that specific direction over others, the "drift" that often plagues long-term projects is significantly reduced.

Official Perspectives: The Expert Consensus

In the wake of this discourse, design leaders have weighed in on the necessity of the "kernel."

• Lucas Mara, Design Leader: “We often treat design like a scavenger hunt, where the goal is to collect the most items. But design is actually an editorial process. If you can’t explain what you’ve decided to leave out, you don’t have a frame—you have a list.”
• Methodological Advocates: Industry analysts emphasize that the "kernel" acts as a diagnostic tool. When a product launch fails, the post-mortem almost always reveals that the team either collected from a narrow pool, failed to connect disparate data points, or lacked the conviction to commit to a singular, clear problem.

Implications for Future Business Strategy

The implications for organizations are profound. If we accept that a kernel is necessary for a strategy to exist, then we must re-evaluate how we structure our design teams and innovation labs.

1. Stop Confusing Tools for Strategy: Workshops and canvases are scaffolding. They are useful, but they are not the strategy. Leadership must prioritize the thinking behind the artifacts, not the artifacts themselves.
2. Reward Editorial Courage: Organizations often reward "more"—more features, more data, more growth. We must shift the culture to reward the "courage to exclude." Leaders who can articulate a clear, concise, and focused problem frame should be held up as the gold standard for innovation.
3. The AI Filter: As artificial intelligence tools become better at "Collecting" and "Connecting," the human element of "Committing" becomes more valuable than ever. The ability to make a value-based judgment call is the final frontier of human design expertise.

Conclusion: The Path Forward

The warning issued by Richard Rumelt remains as relevant today as it was when Good Strategy Bad Strategy was first published. We live in an era where we have never had more data at our fingertips, yet we have never been more susceptible to the "wishful thinking" that masquerades as strategy.

To solve the complex problems of the future, we must return to the basics. We must collect with discipline, connect with analytical rigor, and commit with editorial courage. If you find yourself in a room full of people talking about innovation, ask yourself: Do we have a kernel? If the answer is no, you are not framing a problem. You are simply wishing for a solution.