# Initiatives AI Skill Focus Area · Initiatives Block · Decision Map · Oct 23, 2026 (v1.1) --- ## 1. What the Skill Does The Initiatives skill helps teams name the area of work that deserves attention before anything is varied or compared. It is the first block in the Focus area of Glare's Decision Map. This is where scattered requests (redesign this page, fix this flow, test this feature) become one focused effort with a clear goal. Without a clear initiative, everything feels equally important. Tests run without a shared target, and results come back that don't connect to a decision. An initiative gives the team a container for signals, variables, comparisons, and bets. A strong initiative connects three things. | Part | What it names | |---|---| | User Need | What users are trying to do and where they get stuck | | Business Goal | What outcome the business is trying to move | | Measurable Part of the Experience | The specific area that needs to improve | All three must be present. An initiative with no user need is a roadmap item. One with no business goal is a design exercise. One with no measurable part of the experience is a direction without a target. ### The Framing Rule Don't choose a variable until the initiative answers six questions: - What part of the experience needs attention? - Who is affected by it? - What user need is involved? - What business goal does it connect to? - What signal would show progress? - What decision needs to be made? If any answer is missing, the initiative isn't ready. Frame it before moving on. The skill uses ten common initiative types as starting points: Simplify Identity & Access, Accelerate Onboarding & First-Use Success, Optimize Navigation & Discovery, Streamline Checkout & Payment, Increase Engagement & Retention, Personalize User Experiences, Strengthen Collaboration & Communication, Elevate Marketing & Growth Pages, Improve Content & Support, and Expand Device & Context Reach. Each points to a different kind of friction, business pressure, and signal pattern. ## 2. Business Benefit A clear initiative keeps design work on the problems that matter most to users and the business, and stops tests that produce results nobody can act on. This helps teams: - connect scattered requests to one shared goal - choose the right variable and metric for the work - group many concepts under one outcome without losing scope - explain findings to product and leadership - give each bet a goal it can be checked against later ## 3. Skill Output When used correctly, the skill produces an initiative brief that answers the six framing questions. The example below shows how this works for a mobile banking dashboard. | Field | Example Output (Mobile Banking Dashboard) | |---|---| | Initiative Type | Optimize Navigation & Discovery | | Area of Experience | Mobile banking dashboard home screen | | Audience | Habitual users who log in three or more times a week | | User Need | Findable: users need to see their balance and recent transactions without extra taps | | Business Goal | Reduce session abandonment | | Signal of Progress | First-click success on balance (Use), likely to choose (Prefer), and sessions that end without an action | | Concepts in Scope | Redesigned home screen, summary card, pinned transactions | | Decision Needed | Which home screen to take into the next release | | Failure Mode to Watch | Running two initiatives at once. If the team can't pick one, the work hasn't been scoped yet. | | Next Step Handoff | → glare-focus-methods (Variables) to name the one thing that changes between measurements | The output connects to the other Focus blocks: - Variables uses the decision to name what changes - Comparing uses the need and metric to measure every option the same way - Bets uses the business goal to write a predicted outcome ## 4. Prompt Strategies The prompts below show different ways to use this skill. Each example uses a mobile banking dashboard update. ### Prompt 1: Diagnostic Entry: Start from scattered requests *"We've been asked to redesign the mobile banking home screen, fix the transaction history flow, and test a new summary card, all at once. Using the glare-focus-initiatives skill, map these requests to one initiative with one user need, one business goal, and one signal of progress."* **Why this works:** Three requests with no shared frame is the exact symptom this skill fixes. It pulls them toward one area of improvement the team can test and decide on. **Best for:** - sprint planning with too many directions - connecting a list of requests to a business outcome ### Prompt 2: Typing Entry: Name the initiative type *"We're improving the mobile banking dashboard and can't tell if this is a Navigation, Engagement, or Personalization initiative. Using glare-focus-initiatives, pick the type that fits, explain what it is built to improve, and tell us which signals that type usually needs."* **Why this works:** The wrong type leads to the wrong metrics and comparisons that don't support the real decision. **Best for:** - new Focus efforts without a clear category - projects where scope keeps growing ### Prompt 3: Readiness Entry: Check before choosing a variable *"Our initiative: help habitual users find their balance faster on the mobile banking home screen, to reduce session abandonment, tracked by first-click success. Using glare-focus-initiatives, check it against the six framing questions and tell us whether it's ready for Variables."* **Why this works:** Teams often leave out the decision or the audience. Here the decision is missing, and the skill catches it before a round of testing that can't support one. **Best for:** - checking an initiative before a research sprint - preparing an initiative brief for product or leadership --- *Glare Framework · glare-focus-initiatives · Focus Area. Handoffs: glare-focus-methods (Variables) · glare-focus-comparing · glare-focus-decisions (Bets) · glare-define · glare-measure*