UX Collective: Product design in 2026 — the three walls that fell

Kike Peña, Chief Design Officer, published this piece in April 2026 as a diagnosis of structural change in the design profession. The article does not focus on AI tools or specific workflows; instead, it argues that the economic and organizational conditions that historically constrained designers have changed, and that the profession needs to respond deliberately rather than just adopt new tools.

The central argument is organized around three barriers Peña calls “walls” — each representing a category of constraint that historically prevented designers from influencing strategy, engineering, or innovation at their companies.

The first is the product conversation wall. For most of design’s history, product decisions were centralized in separate product management teams, with designers operating in isolated execution cycles. The industry shift toward cross-functional triads — where design, product, and engineering share decision-making — has given designers direct access to business context, customer data, and strategic discussions they were previously excluded from.

The second is the code wall. The argument here is familiar but stated directly: AI-assisted coding tools have made it possible for designers to prototype and deliver functional code without depending on an engineering handoff. Peña frames this as elimination of the “not engineered” excuse — the default reason a design idea was deprioritized or never built. Whether through Figma Make, Claude Design, or other tools, designers can now move a concept through to something running in a browser.

The third wall is the innovation wall. With access to both the product conversation and the technical stack, designers are no longer limited to interface aesthetics. They can influence internal processes, operational decisions, and the direction of product strategy alongside business stakeholders.

Peña’s prescription for working designers follows from this analysis. He argues that imagination and business judgment — not tool proficiency — will differentiate designers going forward. A colleague’s observation anchors this: “New designers should be measured on how big their imagination is, instead of how much they know about tools.” The implication is that expanding one’s range of thinking about what is possible matters more than staying current with software updates.

The article is most useful for mid-to-senior designers who feel their influence plateauing despite adopting AI tools, and for design leaders thinking about how to frame the profession’s value inside organizations that are still uncertain about where design fits in an era of faster iteration cycles. It does not offer a workflow guide or tool comparison; it makes a structural argument about conditions and responsibility.