# Mapping AI Skill Lead Area · Mapping Block · Decision Map · Oct 23, 2026 (v1.1) --- ## 1. What the Skill Does The Mapping skill helps teams trace how user success turns into business results. It is the third block in the Lead area of Glare's Decision Map, after Business Goals and Workflows and before Results. Mapping traces each bet's expected outcome chain from Focus. The skill builds the Chain of Proof: five rungs from what users need to what the business values. | Rung | Question it answers | Example | |---|---|---| | User Need | What are users trying to achieve? | "I want to finish onboarding quickly." | | User Outcome (Design KPI) | Did users succeed in the moment? | 85% completed setup without error | | Product Outcome (Product KPI) | Did that lead to adoption or return use? | Trial-to-paid conversion doubled | | Business Outcome (Business KPI) | Did the company benefit? | Pipeline revenue grew | | Business Goal | Which pressure did this support? | Growth | Each link between rungs gets a link type. The link type decides how strongly the team can claim the business moved. | Link type | What it means | What you can claim | |---|---|---| | Causal | A tested change moved the KPI (experiment, holdout, or staged rollout) | The change caused the move | | Correlated | The KPIs move together across users, accounts, or periods | They move together; cause not proven | | Sequential | A before-and-after read | The KPI moved after the change; other things may have too | | Linked: Defined | True by formula, such as pay rate as part of revenue | Certain, but says nothing about whether design moved it | | Linked: Stated or Planned | Someone says so, or a plan assumes it | Unproven; never report it as causal | ### The Link Rule Every link in the chain names its type, and the claim never goes past it. A Sequential link can say the KPI moved after the change; only a Causal link can say the change moved it. A Stated or Planned link is a hunch about the business, not proof. When a link is weak and the decision is big, the skill suggests a holdout or staged rollout to make it Causal. ## 2. Business Benefit Without mapping, progress stops at screens and features. With it, a single usability signal becomes part of a story leaders can trust, and the team is honest about how strong that story is. This helps teams: - show how a design change reaches a business goal - say exactly how strong each claim is - find the weak link before leadership does - give Results the links it needs to read an outcome ## 3. Skill Output When used correctly, the skill produces a Chain of Proof with a link type on every step. The example below shows how this works for a mobile banking dashboard. | Field | Example Output (Mobile Banking Dashboard) | |---|---| | User Need | Findable: see my balance at a glance | | Design KPI | First-click success on balance (79% in test) | | Design → Product link | Sequential now; Causal if the launch is staged to half of users first | | Product KPI | Sessions ending without an action (baseline 38%) | | Product → Business link | Correlated: accounts with more abandoned sessions churn more, across past cohorts | | Business KPI | Account churn; support calls about balance | | Business → Goal link | Linked: Defined: churn is part of the Retention goal by definition | | Business Goal | Retention: keep customers | | Weakest Links | Design → Product is only Sequential until the staged launch; Product → Business is only Correlated | | Failure Mode to Watch | Reporting "the redesign cut churn." No link in this chain is Causal yet. | | Next Step Handoff | → glare-lead-results to check the bet's outcome against this chain | ## 4. Prompt Strategies The prompts below show different ways to use this skill. Each example uses a mobile banking dashboard update. ### Prompt 1: Chain Entry: Build the Chain of Proof *"We're backing the redesigned mobile banking home screen to keep customers. Using the glare-lead-mapping skill, build the five-rung Chain of Proof and name the link type for each step."* **Why this works:** It shows the whole path from user need to business goal, and how strong each step is. **Best for:** - preparing a bet for leadership - quarterly impact reviews ### Prompt 2: Claim Entry: Check what we can say *"Our mobile banking team wants to report that the redesign reduced churn. Using glare-lead-mapping, check each link and tell us the strongest claim we can honestly make."* **Why this works:** It keeps the claim no stronger than the weakest link. **Best for:** - launch reports - board or exec updates ### Prompt 3: Upgrade Entry: Strengthen a weak link *"The link between abandoned sessions and churn in our mobile banking chain is only correlated. Using glare-lead-mapping, suggest how to make it causal before our next big bet."* **Why this works:** A holdout or staged rollout turns a correlation into proof when the stakes justify it. **Best for:** - high-stakes bets - teams whose impact claims get challenged --- *Glare Framework · glare-lead-mapping · Lead Area. Handoffs: glare-lead-business-goals · glare-lead-workflows · glare-lead-results · glare-focus-decisions (Bets) · glare-ux-metrics*