# Results AI Skill Lead Area · Results Move · Decision Map --- ## 1. What the Skill Does The Results skill helps teams close the loop between the work they do and the outcomes leadership can see. It is the final move inside the Lead area of Glare's Decision Map. This is where individual findings, decisions, and metrics become a continuous proof that design is moving the business forward. Most teams produce results — usability scores, retention lifts, session improvements — but the results stay inside the design team. They do not connect to initiatives. They do not roll up to business goals. They get shared once, noted, and forgotten. The next sprint starts from zero. The Results skill fixes that by keeping the four-layer project loop connected and visible: Initiatives lead to Findings, Findings lead to Decisions, Decisions lead to Outcomes. The loop has four layers. Every layer needs to be present. | Layer | What it does | |---|---| | Initiatives | Frames a business pressure into a focused area of design work | | Findings | Turns testing and measurement into evidence tied to user needs | | Decisions | Converts evidence into a named next move | | Outcomes | Connects the decision to a user, product, and business result | When one layer is missing, the loop breaks. No Findings means the team is making decisions without evidence. No Decisions means Findings sit in decks and never reach action. No Outcomes means nobody can see whether the work moved anything. The Results skill finds the missing layer and fixes it. **The Clarity Rule** Teams often stall on results because they are trying to prove exact causation — they want to show that this specific design change caused this specific revenue number. That standard is almost impossible to meet, and chasing it keeps teams from sharing results that are genuinely useful. The rule is simple: perfect attribution is rare and that is fine. What matters is direction and progress. A finding that shows first-click success improved from 61% to 79%, session return rate increased, and 90-day retention is trending up does not prove causation — but it shows the chain moving in the right direction. Clarity beats precision every time. Share the direction of travel and let the chain speak for itself. --- ## 2. Business Benefit When the loop stays connected, design builds credibility with every sprint instead of starting over. Leadership stops asking whether design contributes — they can see the chain from initiative to outcome and follow it themselves. This helps teams: - stop starting each project from zero by building on connected evidence over time - give leadership a way to see design's contribution without asking for a special presentation - catch workflow breaks early — before they turn into quarters of invisible work - translate wins into repeatable frameworks the whole team can use - build the kind of trust with stakeholders that earns more design investment over time Results are how design proves it belongs in the room. --- ## 3. Skill Output When used correctly, the skill produces a connected project loop — or a clear diagnosis of where the loop is breaking. The output shows: - how each layer of the loop connects for a specific initiative - which layer is missing or disconnected - which of the five maturity dimensions the break lives under - the specific calibration to apply The example below shows how this works for a mobile banking dashboard. | Layer | Example Output (Mobile Banking Dashboard) | |---|---| | Initiative | Optimize the home screen for habitual users to reduce session abandonment and improve 90-day retention | | Findings | First-click success on transaction history: 61% → 79%. Post-task satisfaction: 3.6 → 4.1. Habitual users return faster when key information is on the home screen. | | Decision | Implement — redesigned home screen moves to production. Power user shortcuts flagged for a follow-on initiative. | | Outcomes | Design KPI: first-click success +18 points. Product KPI: session return rate increasing. Business KPI: 90-day retention trending up. Business Goal: Retention. | | Where the Loop is Breaking | Outcomes layer is incomplete — session return rate and 90-day retention are trending but not yet quantified. The chain cannot be shared with leadership until these numbers are confirmed. | | Maturity Dimension | Building Proof — the team has findings and a decision but the outcome is not yet tied to a measurable business result. Calibration: define measurable success upfront for the next initiative so the outcome layer is ready before the decision is made. | | Failure Mode to Watch | Sharing the Design KPI improvement without the full loop. A 79% first-click score is a strong design result but it is not a business outcome. The loop is only complete when all four layers have named, connected results. | | Next Step Handoff | → glare-lead-business-goals or glare-lead-mapping to confirm and communicate the full outcome chain | --- ## 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: Find where the loop is breaking "Our team has been doing good design work on the mobile banking dashboard for two quarters but leadership keeps saying they cannot see the impact. We have usability findings and we make design decisions every sprint but our results do not seem to connect to the business. Using the glare-lead-results skill, help us map one recent initiative through the four-layer loop — Initiatives, Findings, Decisions, Outcomes — and identify which layer is missing or disconnected." **Why this works:** "Leadership cannot see the impact" is almost always a loop break, not a results problem. This prompt uses the four-layer diagnostic to find the specific gap — usually a missing Outcomes layer or Findings that were never connected to a decision — so the team can fix the workflow instead of producing more reports. **Best for:** - any situation where design work feels invisible to leadership - diagnosing a workflow problem before the next sprint planning session - building a case for why the team needs a more structured way to track outcomes --- ### Prompt 2 — Maturity Entry: Diagnose which dimension is limiting results "Our mobile banking dashboard team has strong research but our findings rarely change what gets built. Decisions get made in roadmap sessions without our evidence. The loudest voice usually wins. Using the glare-lead-results skill, match this symptom to the right maturity dimension, apply the calibration, and tell us what to change in our workflow this sprint." **Why this works:** "Loudest voice wins" is a named symptom in the Guiding Decisions dimension. This prompt uses the 15-symptom diagnostic to match the pain precisely to a dimension and produce a specific calibration — not a general recommendation to "be more strategic," but a concrete change to make in the next sprint. **Best for:** - any recurring team frustration that feels structural rather than project-specific - diagnosing a maturity gap before a team retrospective or process review - preparing a case for a workflow change that needs leadership support --- ### Prompt 3 — Attribution Entry: Share results without perfect causation "We improved first-click success on our mobile banking dashboard from 61% to 79% last quarter. Session return rate is up and 90-day retention is trending positive. We want to share these results with our executive team but we are worried they will ask for stronger proof that our design changes caused the retention improvement. Using glare-lead-results, help us frame these results using the clarity-over-precision principle — showing the chain and the direction of travel without overclaiming causation." **Why this works:** Waiting for perfect attribution before sharing results means results never get shared. This prompt uses the clarity rule to frame a strong directional story — first-click success improved, users returned more often, retention is trending up — that shows the chain moving without claiming more certainty than the data supports. **Best for:** - preparing an executive update after a research and design cycle - any situation where the team has strong directional evidence but not controlled proof - building a habit of sharing results in progress rather than only after full confirmation --- *Glare Framework · glare-lead-results · Lead Area* *Handoffs: glare-lead-business-goals · glare-lead-mapping · glare-lead-workflows · glare-design-assessment*