The Problem Framing Kernel: Why Most Design Strategies Fail and How to Fix Them

A recent dialogue between design strategist Morteza Pourmohamadi and industry peer Lucas Mara has ignited a renewed debate within the design community regarding the efficacy of modern problem-solving methodologies. At the heart of this discourse is the application of Richard Rumelt’s seminal business text, Good Strategy Bad Strategy, to the discipline of design. The core thesis emerging from this analysis suggests that many organizations conflate high-level ambition with functional strategy, leading to a systemic failure in project execution. This misalignment is not merely a matter of semantics; it represents a fundamental breakdown in the way organizations approach complex, ill-defined challenges in an era increasingly dominated by rapid, AI-driven digital transformation.

The Historical Context of Strategic Failure

Richard Rumelt’s 2011 publication, Good Strategy Bad Strategy, challenged the prevailing corporate culture that often mistakes "fluff"—inspiring but empty statements—for strategic direction. Rumelt argued that a robust strategy must contain a "kernel" consisting of three distinct components: a diagnosis of the challenge, a guiding policy to address it, and a set of coherent, coordinated actions.

When Pourmohamadi revisited this framework after fifteen years of professional experience, he identified a parallel crisis in the design industry. Despite the ubiquity of "design thinking" workshops and innovation briefs, many design teams produce frameworks that lack this essential kernel. The result, according to the analysis, is not a strategy, but a collection of wishes. This realization has prompted a broader investigation into why professional design teams, despite access to sophisticated toolkits and extensive resources, frequently fail to produce actionable problem frames.

Chronology of the Modern Design Crisis

The trajectory of problem framing in professional environments has followed a distinct path over the last two decades:

• 2005–2010: The rise of design thinking in corporate settings, popularized by consultancies like IDEO. During this period, the focus was on empathy and user-centricity.
• 2011–2015: The institutionalization of "design sprints." Problem framing became a standard phase in the agile product development cycle.
• 2016–2020: The scaling of design systems. As design departments grew, the process became commodified, often leading to the "template-first" approach where the rigor of framing was sacrificed for the speed of output.
• 2021–Present: The AI inflection point. The arrival of generative AI has accelerated the production of design artifacts, but without a clear strategic kernel, many organizations are producing vast quantities of output that fail to address the underlying business or user challenges.

The Three-Part Kernel: A New Taxonomy

To address the lack of rigor in problem framing, experts have proposed a simplified, three-pillar model: Collect, Connect, and Commit. This framework is designed to serve as a diagnostic tool for teams whose projects have stalled or lost their way.

1. The Collect Phase: Disciplined Divergence
The initial stage of problem framing requires an exhaustive gathering of inputs. This includes technical requirements, user needs, market precedents, constraints, and identified unknowns. Unlike traditional brainstorming, which often prioritizes volume, this stage is characterized by "disciplined divergence." It involves mapping the full scope of the landscape. Data from industry studies suggests that projects which skip this phase—moving immediately to solutioning—experience a 40% higher rate of rework during the development lifecycle.

2. The Connect Phase: Mapping Tension
The second phase is the analytical heart of the process. In this stage, designers examine the relationships between the collected elements. Insights are rarely found in isolation; they are discovered in the friction between competing variables. For instance, the tension between user privacy and data-driven personalization is where the most effective problem frames are built. Teams that fail to map these contradictions often produce solutions that are "tidy" but ultimately toothless, as they ignore the inherent complexities of the ecosystem.

3. The Commit Phase: The Editorial Act
The final, and most neglected, phase is the commitment to a specific perspective. Framing is, by definition, an act of exclusion. By choosing to focus on specific elements and deliberately setting others aside, a design team asserts its strategic intent. This mirrors the process of a film director or a book editor—decisions are made not because other data points are incorrect, but because they do not serve the specific problem being addressed.

Data and Implications

The impact of poor problem framing is quantifiable. According to research from the Project Management Institute (PMI) and various design effectiveness audits, "misalignment on project goals" consistently ranks as a top-three cause of project failure, cited in approximately 37% of failed digital initiatives.

From an institutional perspective, the implications are clear:

• Resource Allocation: Teams that skip the "Commit" phase often spread resources too thin, attempting to solve too many facets of a problem simultaneously.
• Innovation Velocity: Organizations that utilize the kernel approach report higher success rates in early-stage validation, as the "guiding policy" (as defined by Rumelt) provides clear criteria for what to test and what to discard.
• Strategic Cohesion: The kernel serves as a common language between product, engineering, and design, ensuring that all stakeholders understand the "why" behind the "what."

Expert Responses and Peer Perspectives

The perspective shared by Pourmohamadi has resonated with many in the design leadership community, who have long observed a disconnect between the "workshop culture" of design and the cold reality of business metrics.

"The temptation in large organizations is to make the frame inclusive to avoid internal friction," says one anonymous design director at a Fortune 500 firm. "But a frame that includes everything is essentially a frame that excludes nothing. That’s not a strategy; that’s just a list of features. The discipline to say ‘no’ is where the real value of design resides."

Conversely, some argue that in highly volatile markets, rigid problem frames can become a liability. However, proponents of the kernel approach argue that the framework is not meant to be static. Instead, it acts as a "live" document that must be revisited as the diagnosis of the challenge evolves.

Broader Impact on the Industry

As generative AI lowers the barrier to entry for content and interface creation, the role of the designer is shifting away from execution and toward synthesis. In this new landscape, the ability to frame a problem becomes the primary competitive advantage. If AI can generate a thousand variations of a screen, the designer’s value lies in determining which problem is worth solving in the first place.

The "kernel" model provides a robust defense against the "feature-factory" mentality that currently plagues many tech-forward organizations. By forcing teams to diagnose the challenge, identify tensions through connection, and exercise the editorial judgment required to commit, organizations can ensure that their design outputs are not just visually or functionally competent, but strategically sound.

Ultimately, the argument presented is that the "scaffolding" of design—the workshops, the canvases, and the collaborative software—is useful only if the foundation is solid. Without the kernel of diagnosis, policy, and action, the design process remains a form of wishful thinking. In an increasingly complex global market, the organizations that survive will be those that possess the courage to frame their challenges with precision, selecting what to exclude as carefully as what to include.