Concepts

What Concepts AreConcepts are focused design efforts tied to user needs and business priorities. They anchor intent, shape the right questions, and define which signals matter.Without clear concepts, design scatters into noise, wasted cycles, endless debate, and polished features that never solve the right problem. With them, teams know exactly what they’re testing and why.Why concepts matter:Stay aligned→ connect design work to measurable user and business outcomes.Make success visible→ define what winning looks like before you test.Focus the team→ one problem at a time, not a dozen half-finished ideas.Prove impact→ ensure signals tie back to intent, not vanity metrics.Bad habit to break: jumping straight into solutions without clarity.Better habit: always define a concept first, so signals have meaning.Measuring ConceptsThe first step in Measure is breaking large initiatives into smaller, testable concepts. Big efforts usually cross functions in the business. To move them forward, you need to capture the intent: where user needs and business goals intersect, and what outcomes are worth testing.Concepts are the anchor. They frame design work with real problems, clear goals, and loose requirements before hunches and questions take over.Step 1: Concepts → Defining IntentThis is where big initiatives get broken down into smaller, testable concepts. Concepts connect user needs from Define (with UX metrics) and business goals from Show (with business metrics), capturing the intent of the work before diving into solutions.Inputs: business problems, current solutions, organizational prioritiesOutputs: a clear concept framed by user needs and business goalsHow to do itStart with the business problem or friction point.Bring forward theuser needsfrom Define, with the UX metrics that measure them.Map those against thebusiness goalsfrom Show, with the business metrics that track progress.Capture loose requirements,  boundaries, not specs.Narrow to one actionable concept at a time.Example:User Need (Define)→ Clarity in checkout (measured by comprehension + error rate)Business Goal (Show)→ Reduce payment drop-offs (measured by conversion rate)Concept (Measure)→Redesign payment step to reduce abandonmentTry it now:Pick one concept from your backlog. Write the user need, the business goal, and the signal you’d measure. If you can’t do it in under 5 minutes, the concept isn’t clear enough.List of conceptsThere are over 200 Concept pages that expand this process into specific areas of design. Each one shows how to define intent, surface hunches, and measure findings.Explore by category:Products→ Dashboard Engagement, Onboarding Walkthroughs, Account ManagementWebsites→ Landing Page for Ads, Checkout Flows, Product Detail PagesMobile Apps→ Login Flows, Push Notifications, AR FeaturesE-commerce→ Shopping Cart, Wishlist, Order TrackingMarketing→ Campaign Microsites, Case Studies, Social Media CreativesEach top-level Concept page will be linked here, so teams can dive directly into the area they’re working on.Step 2: Ideation → Hunches & QuestionsIdeation turns assumptions into direction. Hunches give teams a starting point, framed as testable hypotheses tied to UX metrics. Questions sharpen those hunches into measurable signals, cutting through noise and bias.Together, they move concepts from intent to evidence, ensuring what gets tested ties directly to user needs and business goals.Hunches: Informed GuessesA hunch is an educated guess, shaped by experience, early data, or observation, about what users might need or where friction exists. They aren’t final answers. They’re starting points that guide what to test.How to create strong hunchesStart with context: tie the hunch to a business goal, user journey, or design principle.Capture assumptions: what do you believe but haven’t tested yet?Spot opportunities: focus on pain points, unmet needs, or ways to reduce effort.Form the hunch as a hypothesis:“We believe that [this change] for [this audience] will [have this impact] because [reason].”Link to a metric: connect the hunch to a UX metric like completion, error rate, or satisfaction.Example:Hunch:“We believe reducing the signup flow from 5 steps to 3 will increase completion, because users currently drop off after step 3.”Questions: Sharpening the TestStrong questions cut through the Fog by turning hunches into measurable direction. Weak questions create noise; sharp ones reveal clarity.How to craft better questionsClarify the initiative: what decision will this question inform?Identify knowledge gaps: what don’t we know that matters?Turn gaps into goals: what do we need to learn overall?Write open-ended research questions: unbiased, user-focused, specific.Translate into testable questions: tie each one to a method (e.g., first-click, survey, task completion).Align with UX metrics: every question should map to behavioral, attitudinal, or performance metrics.Prioritize and refine: focus on the questions that cut opinion fastest.Examples:Research Question:“Where do users struggle in the signup process?”Testable Question:“Can users complete signup in under 2 minutes with 3 steps?”Why This Step MattersHunches give teams a focused starting point, even with limited data.Questions sharpen those hunches into signals you can measure.Together, they bridgeConcept intenttoFindings, ensuring what you test ties back to both user needs and business goals.Step 3: Findings → Turning Data into SignalsThis is where measurement closes the loop. Findings transform raw input intodesign signals, evidence teams can use to make confident choices.Observations from tests, surveys, and analytics on their own are just numbers. A signal forms when those metrics are tied to:Adesign choiceAuser needAbusiness goalThat alignment turns scattered data into clarity, showing not justwhat happenedbutwhat to do next.Inputs: measurement data from tests, surveys, observationsOutputs: signals tied to business and customer outcomesHow to Turn Findings Into SignalsTranslate data into findings→ pull out patterns, drop-offs, task success rates, satisfaction scores.Tie to user value→ comprehension, usefulness, satisfaction.Tie to business results→ conversion, retention, efficiency, revenue.Connect findings back to intent→ make sure each one answers the concept you set out to test.Act on signals→ refine strong concepts, move them forward, or kill weak ones before they waste cycles.Share widely→ replace debates with evidence everyone can see.Example:Data: 48% drop-off at payment step.Observation: Users are confused by payment options.User Need: Clarity (be able to choose payment easily, without errors).Business Goal: Reduce checkout abandonment (increase conversion).Design Choice: Redesign the payment step.Design Signal:Confusing payment options are driving abandonment. Simplifying this step will increase completion (business metric) and reduce error rate (user metric).Why This Step MattersUX metrics tell youwhat happened.Signals tell youwhat to do next.Without them, teams stall in debates. With them, ideas earn their way forward fast.From Intent to SignalsTheConcepts processmoves design from guesswork to clarity in three steps:Concepts → Defining Intent: Anchor the work by linking user needs fromDefinewith business goals fromShow. This captures intent so every idea starts with measurable purpose.Ideation → Hunches & Questions: Turn assumptions into testable hypotheses and sharpen them with questions tied to UX metrics. This moves concepts from intent to evidence.Findings → Turning Data into Signals: Translate observations into design signals — evidence tied to user value and business outcomes. Signals tell teams not just what happened, but what to do next.Together, these steps shrink big initiatives into focused efforts, replace debate with evidence, and ensure design progress is always anchored in user needs and business goals.AI PromptThis prompt helps you frame a design effort as a focused, testable concept before any solutioning begins.Start with a business problem, friction point, or initiative your team is working on. It guides you to:Pull the relevant user need and the business goal it connects toNarrow the effort to one actionable concept rather than several competing onesWrite a concept statement that passes the 5-minute testName the signal that will confirm the concept workedYou'll end with a single concept statement your team can use as the intent anchor before moving into ideation or testing.Use this when a team is jumping to solutions before they've agreed on what problem they're solving.AI SkillsThe Concepts skill file teaches your AI the full Defining Intent process so it can help you frame any design effort as a focused, measurable concept rather than an open brief.Load it when you need to go deeper on the 5-minute test, the concept catalog, or structuring intent across a larger initiative with multiple moving pieces. It gives your AI:The Defining Intent step with the 5-minute test in fullThe user need plus business goal plus signal template with a worked exampleThe 200-plus concept catalog across Products, Websites, Mobile Apps, E-commerce, and MarketingThe From-Intent-to-Signals loop summaryDownload the skill file below to use the full Concepts framework with your AI assistant.