Define: Audience

# Audience AI Skill Define Area · Audience Block · Decision Map · Oct 23, 2026 (v1.1) --- ## 1. What the Skill Does The Audience skill helps teams decide who they are learning from, and how much to trust each source. It is the second block in the Define area of Glare's Decision Map, after User Needs and before Collecting. Teams have personas, ad segments, CRM lists, and panels, and they don't all mean the same thing. The skill asks one question first: **where did this signal come from, and what kind of decision can it support?** | Source | How it's built | Credibility for design | |---|---|---| | Helio Audience Groups | Poll questions that group people by behavior and motivation | High | | CRM / Lifecycle Segments | Purchase history, tenure, activation milestones | Medium | | Advertising Segments | Demographic and interest targeting | Low | | Internal Assumptions | Team expertise and stakeholder belief | Lowest: a starting point only | The skill also places each voice in one of four audience types, built in this order: Project Team (intent), Stakeholders (alignment), Participants (validation before launch), Customers (proof in real use). Internal voices guide; external voices validate. ### The Behavior-Over-Label Rule Define people by what they do, not by a title. "Manager" says little. "Approves budgets for a team of ten or more" says how that person works and what they need. If the source can't be named, the skill can't rate it, and it stops to ask. ## 2. Business Benefit When every source is weighted the same, work drifts toward whoever speaks loudest. Naming the source keeps a targeting segment from passing as user proof. This helps teams: - know which evidence can support a design decision - recruit the right people for Collecting and Testing - avoid averaging groups into a finding that fits none of them - carry the right level of confidence into Measure ## 3. Skill Output When used correctly, the skill produces an Audience Definition Card. The example below shows how this works for a mobile banking dashboard. | Field | Example Output (Mobile Banking Dashboard) | |---|---| | Name | Habitual mobile bankers | | Type | Participants now; Customers after launch | | Source | Helio Audience Group, checked against a CRM segment | | Defining Attributes | Log in three or more times a week; mostly check balance and recent transactions; use the app, not the website | | User Need | Findable (from User Needs) | | Connected UX Metrics | Success, Comprehension | | Credibility | High: behavioral attributes from a named source | | Gaps | No data yet on users who rely on shortcuts | | Failure Mode to Watch | Using the ad team's "young professionals" segment as the design audience. It was built for reach, not for how people use the app. | | Next Step Handoff | → glare-define-collecting to gather evidence from this audience | ## 4. Prompt Strategies The prompts below show different ways to use this skill. Each example uses a mobile banking dashboard update. ### Prompt 1: Source Entry: Rate what you have *"We have a marketing persona, a CRM export, and last month's Helio panel for our mobile banking app. Using the glare-define-audience skill, name the source type of each, rate its credibility for a home screen redesign, and tell us which to use."* **Why this works:** It names each source before anyone treats it as proof. **Best for:** - teams with many overlapping segments - kicking off Define ### Prompt 2: Attribute Entry: Swap labels for behavior *"Our audience for the mobile banking dashboard is 'millennials who bank on mobile.' Using glare-define-audience, rewrite this with behavioral attributes and write the Audience Definition Card."* **Why this works:** Behavioral attributes make the audience testable and comparable. **Best for:** - personas built on demographics - recruiting for a study ### Prompt 3: Conflict Entry: Settle whose input counts *"Our stakeholders want a promotions-first home screen, but participant feedback points the other way. Using glare-define-audience, place each voice in the four audience types and tell us how much weight each should carry for this decision."* **Why this works:** It separates intent and alignment from validation, so the team knows which input settles the question. **Best for:** - stakeholder disagreements - conflicting feedback --- *Glare Framework · glare-define-audience · Define Area. Handoffs: glare-define-user-needs · glare-define-collecting · glare-define-situations · glare-measure-hunches (who to recruit)*

Open skill ↗⬇ Download glare-define-audience-v1-2.zip