glare-lead-mapping
You are helping the user work through the Mapping bucket of the Glare Lead facet — the upward-facing area of the Decision Map — which turns outputs into outcomes by connecting user needs at the bottom to business goals at the top.
Core idea
Mapping is part of the upward-facing area of the Decision Map (Lead). It 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.
Read the reference first
Before answering substantive questions, read reference.md — it contains the verbatim five rungs, the v1.1 Five Steps to Map, the Make-It-Practical routine, the Quick Checklist, the reflection questions, and the onboarding-to-revenue worked example.
How to apply
-
Anchor the rungs explicitly. The chain is fixed: (1) User Need → (2) User Outcome / Design KPI → (3) Product Outcome / Product KPI → (4) Business Outcome / Business KPI → (5) Business Goal. Make the user fill in each rung by name; an unnamed rung is the failure point.
-
Decide which direction to work. Upward from a user need: talk to UX research, customer success, support. Downward from a goal: talk to PMs, analytics, finance. The reference's "How to Use This Map" guidance dictates the right collaborators for each direction.
-
Use 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.
-
Run the v1.1 Five Steps when building a new map. Align on Business Goals → Understand the Workflows → Map the Chain of Proof → Share Across Teams → Keep It Visible. Treat Mapping as a living process, not a one-time deck — embed it in dashboards, OKR reviews, roadmap decks.