taste-skills

Build taste through volume of output, deliberate failure, and speed. Taste cannot be developed by watching. It's sharpened by making, failing, and making again. Use when designing practice routines, breaking through creative blocks, or helping someone move from analysis to execution.

Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.

Navigate the gap between what you can see and what you can make. The Ira Glass gap. Use when a designer is frustrated by the distance between their taste and their output, when mentoring someone through a creative plateau, or when someone is considering quitting because their work doesn't match their vision.

Structured exposure habits for building taste through relentless, intentional consumption. Not passive scrolling. Active intake across design, architecture, film, music, food, and culture. Use when building a taste practice, advising on professional development, or diagnosing why someone's design range feels narrow.

Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.

Reverse-engineer why a design decision was made. Move from observation to inference. Use when studying products you admire, learning from competitors, or building analytical design thinking.

Break a design system into its constituent decisions and evaluate each one. Use when auditing design systems, evaluating consistency, or understanding how a product maintains quality at scale.

Study how products evolve over time using archived versions. The decisions that survive redesigns are the taste decisions. Use when understanding what's essential vs. cosmetic in a design, or learning from product evolution.

Explain the same design observation to a designer, a developer, and a non-technical stakeholder. Same insight, three languages. Use when working cross-functionally or presenting design decisions to mixed audiences.

Precise language for design feedback. Ban vague words. Name what you actually see. Use when giving design feedback, running critiques, or training teams to communicate about quality.

Defend a design decision to skeptical stakeholders with structure and evidence. Use when presenting design work, writing design documentation, or pushing back on requests to change something.

Write a structured design review that someone can act on without follow-up questions. Use when giving async design feedback, writing portfolio case studies, or documenting design decisions.

Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.

Systematic design quality evaluation. Hierarchy, type, color, space, craft, system. Use when evaluating whether a design is ready to ship, running quality audits, or setting quality standards.

Diagnose your taste gaps across six skill areas. Know what to practice. Use when starting a taste development program, checking progress, or identifying specific areas to improve.

Task sequences, progressive disclosure, and the pacing of an experience over time. Use when designing multi-step flows, evaluating onboarding, or diagnosing why users get lost.

Animation as communication. Feedback, orientation, emphasis, delight. If motion doesn't serve one of these four purposes, it shouldn't exist. Use when evaluating animation quality, designing transitions, or deciding whether motion adds or subtracts.

Response timing, acknowledgment, and making the interface feel alive. Every action deserves a response at the right speed. Use when designing interactions, evaluating responsiveness, or diagnosing why a product feels sluggish or dead.

Understand the constraints a design was built under and evaluate quality within that context. Use when reviewing work that had limited time, budget, or team size, or when assessing whether constraints were handled well.

Rank multiple design solutions and explain why. Separate personal preference from quality judgment. Use when comparing design options, evaluating competing approaches, or making design decisions with clear reasoning.

Tell the difference between design decisions that age well and decisions that follow the crowd. Use when evaluating whether a design choice is principled or fashionable, or when a client asks to 'make it look modern.'

Name what was prioritized, what was sacrificed, and whether the tradeoff was right. Every design decision trades something. Use when evaluating design decisions, defending choices, or helping teams understand what they're giving up.

Pull design principles from architecture, fashion, film, industrial design, and physical spaces into screen-based design. Use when seeking inspiration beyond digital, expanding creative range, or building cross-disciplinary design vocabulary.

Micro-decision analysis. Catalog the border radii, spacing scales, type sizes, and state coverage that most people miss. Use when auditing design systems, evaluating craft quality, or training granular perception.

Annotate and map the anatomy of any design. Identify visual hierarchy, spacing systems, color roles, and tension points through clinical analysis. Use when doing formal design audits, teaching design analysis, or building structured observation skills.

The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.

Draw from architecture, fashion, music, food, and industrial design to expand your design taste range. Use when seeking inspiration beyond digital, building diverse reference sets, or expanding creative vocabulary.

Build a reference system that returns the right reference in under 60 seconds. Use when setting up a design reference library, reorganizing existing collections, or helping teams build shared reference systems.

Tag design references by principle, not aesthetic. Build a library you can actually search. Use when saving references, organizing inspiration, or building a design library that returns useful results.

15-minute daily taste exercises. Monday through Friday. Compound effect over time. Use when building personal practice habits, training a team's design eye, or adding structure to professional development.

Run taste-informed design reviews using Observation > Principle > Question. Use when facilitating design critiques, improving feedback quality on a team, or building a shared vocabulary for quality.

Help other designers develop judgment without imposing your style. Use when mentoring designers, running design education, or building team-wide quality standards.

Read a designer's taste through their typography decisions alone. Type is the fastest taste signal in any design. Use when evaluating design maturity, assessing portfolio quality, or understanding what typography reveals about design thinking.

Choose typefaces based on voice and context, not trends. Use when selecting fonts for a project, evaluating type choices, or understanding what a typeface communicates before anyone reads a word.

Scale, weight, line height, and tracking as a coherent system. Use when building type scales, auditing typography consistency, or diagnosing why text feels off.

Palette roles, restraint, semantic consistency, and when fewer colors means better design. Use when building color palettes, evaluating color usage, or diagnosing color-related design problems.

Consistent radii, pixel-perfect alignment, state coverage, and the details that signal design quality. Use when polishing designs, auditing quality, or evaluating whether a design is ready to ship.

Visual weight, attention order, and the decisions that guide the eye. Use when building layouts, evaluating information architecture, or diagnosing why a design feels confusing.

Density, whitespace, rhythm, and how space communicates relationships between elements. Use when building layouts, evaluating spacing consistency, or diagnosing why a design feels cramped or empty.