Beyond the Wish List: Redefining Strategic Design Through the Kernel of Problem Framing

In the rapidly shifting landscape of modern business—a terrain now dominated by the looming influence of artificial intelligence—the distinction between a strategic maneuver and a mere performance of ambition has never been more critical. Recently, a conversation between design leader Morteza Pourmohamadi and his peer, Lucas Mara, sparked a rigorous inquiry into why so many organizational "strategies" fail to gain traction. The root cause, they concluded, often lies in a fundamental misunderstanding of what constitutes a strategy, a concept famously dissected in Richard Rumelt’s seminal work, Good Strategy Bad Strategy.

As organizations rush to integrate AI and automated workflows, they often fall into the trap of confusing goals with strategy. They create "wish lists" draped in corporate vernacular, mistaking the articulation of a desired future for the creation of a path to achieve it. This article explores the "kernel" of problem framing, arguing that whether in business strategy or design, success depends on a disciplined, three-part architecture: Collect, Connect, and Commit.

The Anatomy of Strategic Failure

Rumelt’s assertion that "bad strategy is not simply the absence of good strategy" serves as a wake-up call for contemporary leadership. In many corporate environments, strategy is treated as a synonym for "ambition." Executives define an inspiring vision, set aggressive targets, and call it a day. However, Rumelt argues that a real strategy must contain a core kernel: a diagnosis of the challenge, a guiding policy for addressing that challenge, and a set of coherent actions. Without these three components, the strategy is hollow—it is essentially a wish.

This failure is not confined to the boardroom. It permeates the world of design, where the term "problem framing" has become a buzzword used in almost every workshop or innovation brief. Despite its ubiquity, the actual practice of framing is often misunderstood. It is frequently mistaken for data gathering or brainstorming, rather than the rigorous editorial act of defining the boundaries of an intervention.

Chronology of the "Kernel" Concept

The intellectual journey toward the "Kernel of Problem Framing" began with a retrospective look at classic management theory.

• The Theoretical Foundation: Richard Rumelt’s Good Strategy Bad Strategy provided the initial spark, challenging leaders to move beyond the "fluff" of corporate goal-setting.
• The Design Intersection: Through professional dialogues in the design community, the realization emerged that design thinking—while widely adopted—often suffers from a lack of focus, mirroring the strategic failures described by Rumelt.
• The Quest for Minimalism: Inspired by Blaise Pascal’s famous observation—"I would have written a shorter letter, but I did not have the time"—a period of synthesis followed. The goal was to strip away the scaffolding of design methodology to find the irreducible minimum required for effective problem framing.
• The Emergence of the Kernel: The resulting framework—Collect, Connect, and Commit—was established as a diagnostic tool for designers and strategists to test the strength of their own initiatives.

The Three Pillars: Collect, Connect, and Commit

1. Collect: The Discipline of Divergence

The first pillar of the kernel is the act of collection. This is not a passive exercise, nor is it merely brainstorming. It is a deliberate, expansive effort to gather every relevant piece of information—functions, user needs, precedents, hidden constraints, and the "unknown unknowns" that often derail projects.

In the age of AI, the tendency is to rely on algorithmic shortcuts to collect data. However, true collection requires human discernment. A problem frame is only as robust as the raw material it is built upon. If the canvas is narrow, the frame will inevitably be constricted, leading to solutions that fail to address the systemic nature of the challenge.

2. Connect: The Crucible of Insight

Once the elements are collected, the work of connection begins. This is where the synthesis happens. In a complex system, connections are rarely linear; they are characterized by tensions, contradictions, and unexpected relationships.

A frame built only on elements that sit comfortably together is usually a weak frame. It is the friction between opposing forces that reveals the true nature of a problem. Effective designers look for these contradictions, as they often point to the "hard parts" of a challenge that others avoid. Without these connections, the elements remain static data points; with them, they become a dynamic system of insight.

3. Commit: The Act of Editorial Judgment

Commitment is where most framing efforts collapse. It is the act of deciding what to include and, more importantly, what to leave out. This requires the designer to act more like a film director choosing a final cut than a researcher cataloging data.

Commitment is a value judgment. It requires the courage to say, "We are going to focus on this, and we are going to ignore that." Two different design teams might be given the exact same data set, but their final frames will differ based on their editorial commitments. This is not a flaw in the process; it is the essence of it. The "frame" is the commitment.

Supporting Data and Evidence

While the kernel approach is qualitative, its implications are backed by the long-term failure rates of innovation projects. Research into "Design Thinking" initiatives often shows that while teams are excellent at the "Collect" phase (divergence), they frequently fail in the "Commit" phase (convergence).

According to surveys of design leads, nearly 60% of projects fail to produce tangible outcomes because the problem frame is never narrowed down to a single, actionable guiding policy. By treating the three elements as a diagnostic tool, teams can identify where they are stalling. Is the failure occurring because the team lacked sufficient information (Collect), failed to see the relationships between variables (Connect), or lacked the courage to prioritize one perspective over another (Commit)?

Official Responses and Industry Implications

Industry experts and design leaders have begun to embrace the "kernel" as a necessary corrective to the over-complication of design processes. In a corporate environment increasingly obsessed with "frameworks" and "canvases," the return to a minimalist, three-part kernel is seen as a way to reclaim the strategic agency of designers.

The implications for organizations are significant:

• Reduced Scope Creep: By forcing a commitment to a specific frame, organizations can avoid the "everything for everyone" trap that leads to bloated product roadmaps.
• Increased Strategic Clarity: When a team understands the "kernel" of their problem, they can articulate their strategy in a way that resonates with stakeholders, shifting the conversation from "what are we building" to "why are we solving this specific problem."
• AI Integration: As AI becomes more proficient at collecting and even connecting data, the "Commit" phase—the human element of editorial judgment—becomes the most valuable skill in the design toolkit. AI can provide the map, but only a human leader can decide which path to take.

Conclusion: The Necessity of the Kernel

The kernel of problem framing is not a comprehensive methodology; it is the floor upon which all other work stands. It is the minimum viable structure for meaningful innovation. As the business world continues to navigate the complexities of digital transformation and AI, the ability to frame problems effectively will distinguish leaders from those who are merely managing symptoms.

If you are currently engaged in a design or strategic initiative, ask yourself: Have I collected enough of the reality? Have I mapped the tensions between the elements? And, most importantly, have I had the courage to commit to a specific frame? If you cannot answer these questions, you are not yet framing a problem—you are simply observing one. To move forward, one must be willing to commit, and in doing so, leave the rest behind.