Measure: Concepts

# Concepts AI Skill Measure Area · Concepts Block · Decision Map · Oct 23, 2026 (v1.1) --- ## 1. What the Skill Does The Concepts skill helps teams name what is being designed and why, before anyone writes a hunch. It is the first block in the Measure area of Glare's Decision Map, followed by Hunches, Testing, and Findings. A concept is a focused design effort, such as a page, flow, feature, or message, tied to a user need and a business goal. Big initiatives cross many teams. The skill breaks them into concepts small enough to test one at a time. Every concept connects two things. | Part | Where it comes from | How it is measured | |---|---|---| | User Need | Define | UX metrics, such as Comprehension or Error Rate | | Business Goal | Lead | Business metrics, such as conversion or retention | The skill also captures loose requirements: boundaries, not specs. It uses the concept catalog, grouped by Design Area (Products, Websites, Mobile Apps, E-commerce, Marketing), as a starting point. ### The Five-Minute Rule If the team can't write the user need, the business goal, and the signal it would measure in under five minutes, the concept isn't clear enough to test. Narrow it until it is, and work on one concept at a time. ## 2. Business Benefit Teams that jump straight to solutions end up with polished features that solve the wrong problem. A concept says what winning looks like before the test, so every signal that follows has a meaning. This helps teams: - break big initiatives into pieces they can test - connect design work to a user need and a business goal - agree on what is being judged before testing - avoid vanity metrics by naming the signal up front ## 3. Skill Output When used correctly, the skill produces a concept brief. The example below shows how this works for a mobile banking dashboard. | Field | Example Output (Mobile Banking Dashboard) | |---|---| | Concept | Redesign the dashboard home screen so balance and recent transactions are the first thing users see | | Design Area | Mobile Apps | | User Need (Define) | Findable: habitual users need their balance without extra taps, measured by Success and Comprehension | | Business Goal (Lead) | Reduce session abandonment, measured by sessions that end without an action | | Loose Requirements | Keep quick actions on the home screen; no new navigation patterns this release | | Signal to Measure | First-click success on balance | | Failure Mode to Watch | Writing the solution as the concept ("add a balance card") before naming the need it serves | | Next Step Handoff | → glare-measure-hunches to state the belief about this concept and the questions that would prove it | ## 4. Prompt Strategies The prompts below show different ways to use this skill. Each example uses a mobile banking dashboard update. ### Prompt 1: Breakdown Entry: Split a big initiative *"Our initiative is to make the mobile banking dashboard easier to navigate. Using the glare-measure-concepts skill, break it into three or four concepts we could test one at a time, each with a user need, a business goal, and the signal we would measure."* **Why this works:** It turns a broad goal into concepts the team can test, without picking a solution too early. **Best for:** - kicking off Measure after a Focus initiative - backlogs full of large, vague efforts ### Prompt 2: Clarity Entry: Check a concept *"Our concept is 'add a balance card to the mobile banking home screen.' Using glare-measure-concepts, tell us whether this is a concept or a solution, and rewrite it with the user need, business goal, loose requirements, and signal."* **Why this works:** It catches a concept written as a fix and reframes it around the need, so the hunches that follow can test more than one answer. **Best for:** - concepts that arrive as feature requests - reviewing a concept before writing hunches ### Prompt 3: Catalog Entry: Find a starting point *"We are designing the mobile banking dashboard home screen. Using glare-measure-concepts, find the closest concepts in the Mobile Apps area of the catalog and show us how they define intent and what they usually measure."* **Why this works:** The catalog gives the team a proven starting frame instead of a blank page. **Best for:** - teams new to Glare - common design areas like dashboards, onboarding, or checkout --- *Glare Framework · glare-measure-concepts · Measure Area. Handoffs: glare-measure-hunches · glare-define-user-needs · glare-lead-business-goals · glare-focus-initiatives*

⬇ Download SKILL.md