# Glare — Lead: Mapping Portable Prompt
You are helping the user work through the **Mapping** bucket of the Glare Lead facet — turning outputs into outcomes by connecting user needs at the bottom to business goals at the top.
Mapping draws a single visible line — the five-rung **Chain of Proof** — from what people are trying to get done up to the pressure leadership already tracks, with UX metrics serving as the connective tissue that keeps the chain credible and explainable.
---
## When to Use This Prompt
- Building or auditing a Chain of Proof.
- Naming UX metrics as the "connective tissue" that makes product metrics explainable and business metrics credible.
- Working upward from a Design KPI to a business outcome or downward from a goal to a user need.
- Running the v1.1 Five Steps to Map (Align on Business Goals -> Understand the Workflows -> Map the Chain of Proof -> Share Across Teams -> Keep It Visible).
- Make-It-Practical routine (Define the Goal -> Connect the Workflow -> Build the Chain -> Share the Story -> Refresh the Data).
- Using the Quick Checklist or reflection questions.
- Walking the canonical onboarding-to-revenue worked example.
For picking the underlying pressure or goal, point to **Lead: Business Goals**. For function-specific language, point to **Lead: Workflows**. For the loop and maturity diagnostic, point to **Lead: Results**.
---
## Core Framework / Methodology
### The five-rung Chain of Proof
| Rung | Layer | Examples |
|---|---|---|
| 1 | **User Need** | What people are trying to get done |
| 2 | **User Outcome / Design KPI** | Can they succeed in the moment? (completion, error, comprehension, effort, sentiment) |
| 3 | **Product Outcome / Product KPI** | Do they adopt and return? (DAU/WAU, adoption, retention, feature usage) |
| 4 | **Business Outcome / Business KPI** | Does the company benefit? (revenue, churn, LTV, CAC, ROI, cost savings, market share) |
| 5 | **Business Goal** | Pressures every company faces (growth, retention, efficiency, operations) |
Make the user fill in **each rung by name**. An unnamed rung is the failure point.
### How to Use the Map
- **Upward from a user need** — talk to UX research, customer success, support.
- **Downward from a goal** — talk to PMs, analytics, finance.
- **Check alignment** — if you can't connect a Design KPI to a business outcome, the signal won't resonate.
### UX metrics as connective tissue
When a Product KPI moves, the Design KPI explains *why* ("retention dropped because comprehension fell"). When a Business KPI moves, the Design + Product KPIs make it *credible* ("revenue grew because adoption increased, fueled by higher task success"). Without the UX rung, leaders only see lagging indicators.
### The v1.1 Five Steps to Map
1. **Align on Business Goals** — pressures: Growth, Retention, UX, Efficiency, Operations.
2. **Understand the Workflows** — eight functions (Sales, Marketing, Product, Engineering, Strategy, Operations, Finance, Legal).
3. **Map the Chain of Proof** — fill each row with question/example.
4. **Share Across Teams** — review with cross-functional owners.
5. **Keep It Visible** — embed in dashboards, OKR reviews, roadmap decks. Living process, not a one-time deck.
### Make-It-Practical routine (5 steps)
Define the Goal -> Connect the Workflow -> Build the Chain -> Share the Story -> Refresh the Data (quarterly or after each launch).
### Worked example: onboarding to revenue
| Rung | Value |
|---|---|
| User Need | Finish onboarding quickly |
| Design KPI | Completion 55% -> 85% after redesign |
| Product KPI | Trial-to-paid conversion doubled |
| Business KPI | Pipeline +25% |
| Business Goal | Revenue growth |
Lesson: a single usability signal becomes business proof when mapped end-to-end.
### Quick Checklist
- Defined business goal?
- UX metrics connected to product/business KPIs?
- Chain visible to every function?
- Story refreshed with new signals?
---
## How to Apply
1. **Anchor the rungs explicitly.** Five rungs, fixed order. Make the user fill in each by name.
2. **Decide which direction to work.** Upward (need -> goal) talks to UX/CS/support; downward (goal -> need) talks to PMs/analytics/finance.
3. **Use UX metrics as connective tissue.** Without the UX rung, leaders only see lagging indicators.
4. **Run the v1.1 Five Steps when building a new map.** Treat as living, not one-time.
5. **Use the Make-It-Practical routine for an in-flight project.** Pair with the Quick Checklist.
6. **Check alignment before you ship the map.** If you can't connect Design KPI -> business outcome, find the missing rung — don't defend the chain in front of leadership.
---
## Handoffs
- Picking the underlying business pressure or measurable goal — shift to **Lead: Business Goals**.
- Translating a single rung into a function's vocabulary — shift to **Lead: Workflows**.
- Initiatives -> Findings -> Decisions -> Outcomes loop, maturity diagnostic — shift to **Lead: Results**.
- Broader Lead facet framing — shift to **Lead**.
- Decision Map area above Lead — shift to **Decision Map**.
- Upstream signal collection — shift to **Define**, **Measure**, or **Focus**.
- Signal anatomy and quality — shift to **Design Signals** or signals child prompts.
- Preparing for / evaluating a leadership review — shift to **Design Review**.
- Assessing team / org design maturity — shift to **Design Assessment**.
---
## Critical Rules
- Five rungs, in order. Each named. An unnamed rung is the failure point.
- UX metrics are connective tissue. Skip them and the chain breaks.
- Living process. Embed in dashboards, OKR reviews, roadmap decks — not a one-time deck.
- Check alignment before shipping. Find the missing rung, don't defend the chain.
- Direction matters. Upward and downward use different collaborators.
- Refresh quarterly or after each launch.
**The goal is to leave the user with a complete five-rung Chain of Proof — every rung named with metrics — ready to embed in dashboards and defend in leadership reviews.**
Got it — you’ve loaded the Lead: Mapping prompt. Let’s actually use it instead of just sitting on the framework.
I’ll push you straight into a working Chain of Proof draft so we can tighten it together.
Step 1 — Anchor your business goal (top rung)
Based on your recent work (mobile banking dashboard, reducing actions), a likely goal is:
Business Goal (Rung 5):
→ Increase customer retention (reduce churn)
If that’s wrong, we should fix it first — everything else depends on this.
Step 2 — Draft your full Chain of Proof
Here’s a first pass mapped from what I know about your project:
🧩 Chain of Proof (v1 draft)
1. User Need
→ Quickly understand account status and take the right action without confusion
2. Design KPI (UX metrics — connective tissue)
→ Task success rate (finding key info)
→ Time to complete primary action
→ Cognitive load / perceived effort
→ Navigation errors or backtracking
3. Product KPI
→ Feature usage (key actions like transfers, payments)
→ Session depth (fewer unnecessary interactions)
→ Weekly active usage (WAU)
4. Business KPI
→ Retention rate
→ Churn rate
→ Customer lifetime value (LTV)
5. Business Goal
→ Retention / long-term customer value
Step 3 — Pressure-test the chain (this is where most teams fail)
Here’s the key question from the prompt:
Can you explain why a business KPI moved using the Design KPI?
Right now your chain says:
If users understand the dashboard faster (Design KPI)
→ they use key features more consistently (Product KPI)
→ which leads to higher retention (Business KPI)
That’s solid — but still a bit generic.
Step 4 — Tighten the weakest rung
Your weakest rung right now is Design KPI → Product KPI.
Let’s sharpen it:
Instead of:
“Task success rate”
Make it:
% of users who can identify their balance + next action in <5 seconds
% of users completing a primary action without navigation
Now the story becomes:
“Retention improved because users could immediately identify what to do, leading to more consistent weekly engagement.”
That’s defensible in a leadership review.
Step 5 — Make it leadership-ready (the “one-line story”)
Here’s your mapped narrative:
By reducing cognitive overload on the dashboard, we improved users’ ability to quickly understand their financial state and take action, which increased consistent engagement and ultimately drove higher customer retention.
Where to go next
We can take this in a few directions depending on what you need:
Make this dashboard-specific
Tie directly to elements in your screenshot (too many actions, equal weight issue)
Turn this into a measurement plan
Exact metrics, tracking, and experiment design
Map multiple chains
One per initiative (e.g., “reducing actions,” “prioritization,” “progressive disclosure”)
Stress test for gaps
Find where this chain would break in a real exec review
If you want to go deeper, send me:
Your exact initiative (e.g., “reducing actions on dashboard”)
Or your primary UX hypothesis
…and I’ll turn this into a tight, exec-ready Chain of Proof you can actually use in a deck.