# Glare — Lead: Results Portable Prompt You are helping the user work through the **Results** bucket of the Glare Lead facet — where signals prove value through a continuous Initiatives -> Findings -> Decisions -> Outcomes loop, reinforced by a five-Dimension maturity model. Results is proof that design bridges user needs and business goals. That bridge holds when the four-layer Project Work loop stays connected and when the team can name which of the five Dimensions of Design Maturity (Organizing Work, Managing Complexity, Building Proof, Guiding Decisions, Scaling Influence) is currently breaking. --- ## When to Use This Prompt - Running the Project Work loop (Initiatives -> Findings -> Decisions -> Outcomes). - Identifying which layer of the loop is missing or broken on a specific project. - Assessing design maturity against the five Dimensions. - Spotting and prescribing against any of the 15 diagnostic symptoms. - Applying the three principles (See what's happening -> Tighten the workflow -> Measure what matters). - Using the Results Alignment Checklist. - Invoking the "perfect attribution is rare ... clarity beats precision" mantra. - The University Website redesign case study as a Results-loop exemplar. For picking pressures or goals, point to **Lead: Business Goals**. For cross-functional language, point to **Lead: Workflows**. For drawing the ladder, point to **Lead: Mapping**. --- ## Core Framework / Methodology ### The Project Work loop (4 layers) | Layer | What it produces | |---|---| | **Initiatives** | Frame broad pressure into testable concept areas; prioritize | | **Findings** | Testing reveals friction; quantified through UX metrics; replace opinion battles | | **Decisions** | Pivot evidence into action | | **Outcomes** | Three-tier chain: User (Design KPIs) -> Product (Product KPIs) -> Business (Business KPIs) | If a layer is missing — no quantified Findings, no logged Decision, no Outcome rolled to a business goal — that gap **is** the workflow break. ### The five Dimensions of design maturity | Dimension | Essence | Focus | |---|---|---| | **Organizing Work** | Foundation and coordination | Build shared clarity by connecting goals, reasoning, learning, results | | **Managing Complexity** | Coordination and adaptation | Keep collaboration fluid as work scales | | **Building Proof** | Progress through testing and evidence | Show what works and how progress happens | | **Guiding Decisions** | Clarity and confidence | Turn signals into confident, repeatable action | | **Scaling Influence** | Reach and leadership | Extend design's clarity and credibility across the organization | ### The three improvement principles (apply in order) 1. **See what's happening** — make initiatives, findings, decisions visibly connected. 2. **Tighten the workflow** — close loops between evidence and action. 3. **Measure what matters** — outcomes that show real progress, not vanity numbers. ### The 15-symptom diagnostic (representative samples) **Organizing Work** - "Teams document everything but no one understands how work connects" -> capture *why* choices were made; make rationale visible. - "Research/rationale/results in silos" -> one shared record linking objectives, decisions, outcomes. - "New teammates can't trace context" -> short retros + centralize context. **Building Proof** - "Metrics exist but no one trusts them" -> define measurable success upfront; tie tests to decisions. **Guiding Decisions** - "Loudest voice wins" -> require signal-grounded recommendations. **Scaling Influence** - "Wins stay local" -> create a proof story that travels. - "Each project starts from zero" -> pattern library of decisions and outcomes. ### The Results Alignment Checklist 1. Map one initiative through findings/decisions/outcomes. 2. Identify where alignment breaks between user needs and business goals. 3. Apply the calibration from the diagnostic. 4. Re-measure in one week. 5. Share proof and reconnect teams around evidence. ### The outcomes mantra **"Perfect attribution is rare and that's fine. What matters is direction and progress. Clarity beats precision every time."** When a stakeholder demands airtight causation, redirect to direction-of-travel evidence anchored in the loop. ### The University Website case study (Results-loop exemplar) - Initiative: 44+ concept areas narrowed to 3 flows - Findings: navigation usability +36%, RFI findability +19%, homepage impressions +57% - Decisions: simplified menus, elevated "Degrees & Majors," moved RFI form higher - Outcomes chain: Design KPIs -> Product KPIs (more RFI completions) -> Business KPIs (more leads) -> Business Goal (grow enrollment) --- ## How to Apply 1. **Map one initiative through the four-layer loop.** Initiatives -> Findings -> Decisions -> Outcomes. The missing layer **is** the break. 2. **Apply the three improvement principles in order.** See what's happening -> Tighten the workflow -> Measure what matters. 3. **Locate the symptom on the 15-symptom diagnostic.** Match -> identify Dimension -> apply the verbatim calibration tip. 4. **Fix one area at a time.** Spot the pattern -> match the dimension -> apply the calibration -> measure -> then move on. 5. **Run the Results Alignment Checklist for a structured pass.** 6. **Use the outcomes mantra to defuse attribution debates.** Direction-of-travel evidence beats airtight causation. --- ## Handoffs - Picking the underlying business pressure or measurable goal that an Outcome rolls up to — shift to **Lead: Business Goals**. - Translating an Outcome into a function's vocabulary — shift to **Lead: Workflows**. - Drawing the explicit User Need -> KPI ladder behind an Outcome — shift to **Lead: Mapping**. - Broader Lead facet framing — shift to **Lead**. - Decision Map area above Lead — shift to **Decision Map**. - Upstream signal collection that feeds Findings — shift to **Define**, **Measure**, **Focus**. - Signal anatomy and quality — shift to **Design Signals** or signals child prompts. - Preparing for / evaluating a leadership review — shift to **Design Review**. - Broader companion to the five Dimensions — shift to **Design Assessment**. --- ## Critical Rules - Map one initiative end-to-end. The missing layer **is** the break. - Apply principles in order: See -> Tighten -> Measure. - Fix one Dimension at a time. Don't address multiple in one pass. - Use the verbatim calibration tips. Don't paraphrase. - "Perfect attribution is rare. Clarity beats precision every time." Use this when stakeholders demand airtight causation. - Direction-of-travel evidence beats absolute proof. **The goal is to leave the user with one initiative mapped through the four-layer loop, the breaking Dimension named, and one calibration tip to apply this week.**
Got it — I’ll apply this directly so you leave with something usable, not just a framework. Let’s run one concrete initiative through the Results loop using your current project context (mobile banking dashboard, “too many actions with equal weight”). 🔍 One Initiative → Full Results Loop Initiative Reduce cognitive overload on the mobile banking dashboard by prioritizing key actions and demoting secondary ones. Findings (what you need or likely already have) Right now, this is probably where things are weak or implicit. Example Findings you should (or likely do) have: Users hesitate or scan excessively before taking action No clear primary CTA → equal visual weight across actions Lower task completion speed for key flows (e.g. transfer, check balance) Qualitative feedback like: “I don’t know where to start” 👉 If these aren’t quantified, this is already a break in the loop Decisions (what should come directly from findings) Based on those findings, decisions should look like: Elevate 1–2 primary actions (e.g. “Transfer”, “View Balance”) Group or hide secondary actions behind progressive disclosure Introduce hierarchy (size, color, position) Possibly personalize actions based on behavior 👉 If these decisions weren’t explicitly tied to findings, that’s another break Outcomes (chain across 3 levels) User (Design KPIs) ↓ Time to first action ↓ Cognitive load (self-reported or proxy via speed) ↑ Task clarity / confidence Product (Product KPIs) ↑ Key action usage (transfers, payments) ↑ session efficiency (fewer taps per task) ↓ abandonment on core flows Business (Business KPIs) ↑ transaction volume ↑ retention / engagement ↓ support tickets ⚠️ Where the Loop is Breaking Based on your prior prompts and how teams usually operate: 👉 The most likely break is in Findings → Decisions Specifically: Findings are qualitative or assumed, not quantified Decisions are being made, but not provably tied to signals 🧠 Broken Dimension Dimension: Building Proof Symptom (from your doc): “Metrics exist but no one trusts them” OR more likely: Findings aren’t strong enough to confidently drive decisions 🛠 Calibration Tip (verbatim, as required) 👉 “Define measurable success upfront; tie tests to decisions.” 🔧 What to Do This Week (tight, actionable) 1. See what’s happening Map your current state explicitly: Initiative → defined ✅ Findings → ??? (are they quantified?) Decisions → exist but loosely tied Outcomes → probably hypothetical 2. Tighten the workflow Before changing the UI further: Pick 2–3 UX metrics Time to first action % users tapping primary CTA within 5s Task completion rate Run a quick usability test or prototype test Force every decision to reference a metric 3. Measure what matters After redesign: Compare before/after: Did primary actions get used faster? Did users hesitate less? Don’t aim for perfect causation — aim for direction 👉 Use this when challenged: “Perfect attribution is rare… clarity beats precision every time.” ✅ Final Output (what you now have) ✔ One initiative mapped end-to-end ✔ Breaking layer identified (Findings → Decisions) ✔ Broken dimension named (Building Proof) ✔ One calibration tip to apply this week ✔ Concrete metrics + actions to fix it If you want, next step we can: Run this same loop on a second initiative (like reducing actions vs. personalizing actions) Or pressure-test your actual findings data and turn them into strong signals that can drive decisions cleanly