Design Taste

Design taste is the pattern recognition and judgment that lets you make decisive calls when data conflicts, AI options multiply, and the right path is not obvious. It is knowing which of the twelve generated interfaces will actually respect the users attention in real usage rather than just looking clean in a screenshot. The article shows that this is what survived the 2025 AI wave that ate research synthesis, spec writing, mock polishing, design critique, and handoffs. Linear AI handles synthesis. Claude turns Figma frames into specs. v0 and Figma AI plus Lovable handle polish. The handoff dies when the designer ships the PR. Taste judgment and decision making in ambiguity is the human layer that remains. The issue is it was always ten percent of the old senior role. Now it is one hundred percent of it and must be paired with shipping to command the new compensation bands at Stripe Anthropic and Vercel.

It is not your personal aesthetic or coolness factor. It is not the ability to make things look nice in Figma or run impressive critique sessions. It is not defending your opinion in meetings without shipping data to back it. The old senior who lived in the handoff and directed juniors on polish discovered their taste was not as scarce as they believed once generation became free. When every junior can prompt their way to polished mocks the value of the director drops. Taste without the context of shipping and owning the outcome is just decoration. It is not the skill that lets you survive as a traditional senior product designer in 2026 unless you sit in one of the four narrow remaining seats.

A concrete example played out at Anthropic in 2025 during the claude.ai artifacts update. The team generated over fifty variants using their internal tools and v0. All passed accessibility checks. All respected the calm intelligent brand. The design engineer exercised taste by selecting the version that minimized visual noise during complex interactions. Their experience told them that overwhelming the user with options at the wrong moment would break the flow even if the animations looked impressive. They rejected the flashy versions. They then switched to Cursor, loaded their prompt library tied to the Anthropic design system, adjusted the React code for perfect behavior, ran it against real usage data, opened the PR with their decision framework included, resolved the engineering discussion in comments, and shipped it. The feature felt like magic rather than technology. Users responded with immediate praise in feedback. This replaced what used to be a six week senior PD process of synthesis polishing spec and handoff with a four day cycle. The taste was the same. The delivery mechanism and velocity were entirely new. Four other seniors the author knew followed this exact path from Big Tech L5 roles and freelance leads into higher paid shipping positions inside eighteen months by replacing case studies with live GitHub repos.

A second concrete example sits with the redesign at Linear of their AI powered ticket system. The designer faced conflicting signals from user interviews. Some wanted more visibility into the AI reasoning. Others wanted it invisible. AI tools generated options for both. Taste guided the call to make the AI reasoning available but collapsed behind a subtle toggle that respected the primary flow. The choice required understanding the product at a deep level that no prompt could fully capture. They implemented it directly as a shipped component that became the new default. The measurable drop in ticket resolution time proved the taste call correct. This is the new senior. They read the codebase. They own the surface. The Figma file is a temporary thinking tool not the deliverable.

Use design taste when you have cleared the generation layer and sit in the decision layer. Use it when founding designer roles at Cursor or Lovable require setting an entire aesthetic from day one that AI cannot fake. Use it in the audit you run on your own role before the company runs it on you. The five question audit reveals whether your taste has a chair left or whether you are riding the old title into the reorg. Deploy it in regulated spaces like financial compliance at Stripe or accessibility critical surfaces where liability demands human judgment. These plus design leadership at scale and pure research roles form the four narrow places where the old senior still sits.

Do not use design taste from within the old senior PD role that owns the Figma file but never the production codebase. Those jobs are not coming back. The public openings at the pace setting companies prove it. Do not use it as your defense when the math shows one shipping designer replaces three traditional ones. The contractor path or founder designer path beats staying in the dying chair. Never treat taste as static. It evolves with the tools. The senior who does not update their taste for AI native interfaces and AI workflows will find their judgment outdated faster than they expect. The workflow of the new senior includes Cursor as the editor, prompt libraries, Skill packs for consistency, and Figma integration. Taste sits on top of that stack as the accelerator not the entire job.

Taste is the last moat but it shrinks every quarter you spend without shipping.