Updated June 2026
Most organizations want design to succeed. Yet their operating models can unintentionally limit its contribution.
Design rarely struggles because of the work itself. More often, it is constrained by inherited assumptions about how decisions should be made, what success looks like, and where valuable insights come from.
The result is a self-reinforcing pattern I call the Design Cycle of Doom.
Design succeeds when it changes customer behavior in ways that improve business outcomes. When organizations treat design as a tactical service, deliverables are planned before problems are understood, opportunities to engage users are reduced, and teams converge on solutions before enough evidence has been gathered. In practice, the signal I watch for isn’t the quality of the design work—it’s how late in the process design is invited to participate.
When design is viewed primarily as a function for making things visual, teams involve it after key product decisions have already been made. Design is asked to refine predetermined solutions, not define them.
Assumptions go unchallenged, opportunities to learn from users are reduced, and customer evidence arrives too late to meaningfully shape product decisions. Products become far less likely to deliver the value organizations expect.
When outcomes disappoint, organizations may interpret the issue as a limitation of design rather than of the surrounding operating model. Design receives less investment, less influence, and more micromanagement. Customer learning declines, and organizations grow increasingly confident in decisions supported by assumptions rather than evidence.
Breaking the cycle doesn’t begin by changing designers. It begins by changing how organizations understand design.
Design is a strategic capability
Design informs product strategy through learning and evidence. By engaging customers, uncovering unmet needs, challenging assumptions, and validating ideas before organizations commit to solutions, it helps shape better product decisions. When design enters after product strategy and product definition are complete, its influence is largely limited to execution.
Design reduces uncertainty before it creates solutions
Design’s greatest contribution isn’t producing artifacts. It’s helping organizations understand problems, challenge assumptions, and make better decisions before committing to solutions.
Design changes behavior, not just interfaces
Successful design isn’t measured by the quality of its artifacts. It’s measured by whether customer behavior changes in ways that improve business outcomes.
Outputs serve outcomes
Wireframes, prototypes, research reports, and design systems are valuable only insofar as they help create better customer and business outcomes.
Shared beliefs become meaningful when they are reflected in how teams work.
Give design a seat where strategic decisions are made
Design is better positioned to contribute strategically when it participates in the conversations where priorities and outcomes are defined.
Involve design before solutions are chosen
Invite design into problem framing, customer discovery, and roadmap conversations—not just implementation.
Validate problems before optimizing solutions
Research, experimentation, prototyping, and testing should reduce uncertainty before organizations invest in delivery.
Measure learning as progress
Reward research, testing, and evidence generation alongside delivery milestones. Learning is not overhead; it is risk reduction.
Measure customer outcomes, not design outputs
Implementation metrics—whether screens produced, AI tokens consumed, features shipped, or deliverables completed—can help teams improve efficiency. They should not be mistaken for measures of customer or business outcomes.
When I encounter this pattern, my first step is not to make the case for design. It’s to understand why the current arrangement makes sense to the people inside it. Design is usually treated as a downstream function because it entered the organization that way—through a hiring decision, an org chart, a project intake process—and nobody ever restructured how it connects to upstream work. The cycle persists not because leaders dislike design, but because the operating model was never built to use it differently.
The most effective entry point I’ve found is the product planning process itself. When I can get into roadmap conversations, discovery reviews, or early initiative framing sessions, I can begin shifting design from a delivery function to a shaping function. That doesn’t require a reorganization. It requires being in the room when problems are still being defined, and asking the questions that surface which assumptions are carrying the most risk.
I often work with product and engineering partners to introduce a lightweight problem-framing step before solution definition begins. This isn’t a research embargo—it’s a short, structured conversation: What problem are we solving? Who experiences it? What would we need to see to know we’ve solved it? These questions take thirty minutes. They frequently prevent months of rework.
On the measurement side, I help teams distinguish between progress signals and outcome signals. Delivery milestones tell you what shipped. Customer behavior data tells you whether it mattered. I’ve helped organizations build both into their operating rhythms—not as competing priorities, but as complementary views of the same work.
The cycle breaks when design is visibly useful to product strategy, not just to implementation. Getting there is a coordination problem as much as a craft problem. It starts with showing up early, asking the right questions, and making the evidence legible to the people who make the decisions.
When organizations understand design as a means of transforming insight into better decisions, innovation, and measurable value, the cycle begins to break. Doing so requires resisting the pursuit of premature certainty and recognizing that meaningful design outcomes emerge from influence, not activity alone.
The first step toward breaking the Design Cycle of Doom is redefining design as a means of learning, influencing decisions, and creating better outcomes—not simply producing visual outputs.