UX Research

UX Magazine Outlines a Three-Part Kernel for Design Problem Framing

A UX Magazine column names Collect, Connect, and Commit as the minimum conditions for any usable problem frame, adapting Richard Rumelt's 2011 strategy kernel to design practice.

  • AuthorTom Whitfield
  • ChannelUX Research
  • Filed
  • Read3 min
A Problem Framing Kernel
A Problem Framing KernelAI-generated
  • UX Magazine column 'A Problem Framing Kernel' names three components: Collect, Connect, Commit
  • Framework adapts Richard Rumelt's three-part strategy kernel from his 2011 book 'Good Strategy Bad Strategy'
  • Triggered by a recent conversation between the author and design leader Lucas Mara on design in the age of AI
  • Rumelt quoted directly: 'bad strategy is not simply the absence of good strategy'
  • Closing claim: framing without the kernel may be useful work but is not yet framing

A column published in UX Magazine names three steps — Collect, Connect, Commit — as the minimum conditions for any usable problem frame. The framework adapts a structure that Richard Rumelt set out in his 2011 book Good Strategy Bad Strategy, restating his three-part strategy kernel for design work.

The origin is conversational. The author re-read the book after a recent discussion with Lucas Mara, a design leader, about the value of design in the age of AI. One line, underlined years ago without full use, prompted the adaptation: "bad strategy is not simply the absence of good strategy." That claim — that most organizations mistake ambition for strategy — anchors the design-side argument that follows.

What does this change for working designers?

The piece treats the kernel as a diagnostic rather than a methodology. A designer who has collected inputs and mapped their relations, yet still produced a weak frame, can locate the failure by walking back through the three steps. The author frames the kernel as a guard against two recurring failure modes: framing too early, and describing a landscape without ever committing to a frame.

Rumelt supplies the source analogy, quoted directly: "A real strategy has a kernel with three components: a diagnosis of the challenge, a guiding policy for dealing with it, and a set of coherent actions. Without all three, you don't have a strategy. You have a wish." The column applies the same structural test to design.

What does "Collect" require?

The first step expands the raw material available to the frame. The author enumerates concepts, functions, needs, requirements, precedents, stakeholders, constraints, assumptions, and known unknowns. The intent is to widen both the size and resolution of the canvas before any synthesis begins.

The piece contrasts this with brainstorming. Collect, it argues, is disciplined divergence rather than ideation. A narrow collection produces a narrow frame, regardless of how sharp the later thinking becomes.

How does "Connect" produce insight?

The second step maps the relationships between collected elements. Some connections are obvious; others are weak, surprising, or contradictory. The column argues that contradiction tends to produce better frames than tidy agreement, on the grounds that a frame built only from comfortable elements has avoided the harder parts of the problem.

Without connections, the author writes, a designer has no defensible basis for deciding what to include in a frame and what to leave out. The tensions between elements reveal where the actual problem sits.

Why does "Commit" carry the weight?

The third step is where framing diverges from landscape-making. Most collected work, the column argues, never becomes a frame because the editorial choice to foreground certain elements and set others aside is never made. Commit is described as closer to a film director's final cut than a researcher's catalogue.

A second quotation states the choice plainly: "What you leave out of the frame is as important as what you keep in, and the discipline of framing lives precisely in that choice." Two designers working from identical collection and connection maps can land on different frames without either being wrong, because judgment about what matters most is part of the work, not a flaw in the process.

What does the framework leave out?

The piece is explicit that a kernel is not a method. Discovery workshops, framing canvases, and innovation briefs sit on top of the three steps as scaffolding, sometimes essential scaffolding, but not the minimum. The author invites designers to use the kernel as a test: if a frame reads as weak or unactionable, the cause traces back to a narrow Collect, an unworked Connect, or an avoided Commit.

The column closes with a final provocation: "If you're framing problems without this kernel, you might be doing something useful. But you're not framing yet." Whether that diagnosis holds up at the scale of larger product organizations is the question its first adopters will now answer.

Original: linkedin.com

Share this article:

More from Tom Whitfield

Tom Whitfield

Show full bio

Correspondent covering companies, deals and strategy in Product and interaction design, design systems at Interface Wire.

65 articles

Related articles

  1. Figma's Field: design matters more as AI lowers the cost of code

  2. Agentic AI Systems Turn Fragile as Non-Engineers Build Big Balls of Mud

  3. MIT Sloan Management Review Calls for a Responsibility Reboot in Design Thinking

  4. Microsoft Design on Using AI to Activate Research Insights

« Previous articleNext article »