Decision Map Skill

Helps teams move from a user problem to a measurable outcome. The Decision Map covers four areas in sequence: Define, Measure, Focus, and Lead. Each area has its own set of skills. Together they give teams a complete system for turning user research into product decisions.Download these skills and drop into a LLM chat along with this prompt:Extract the zip and save each SKILL.md file with a .skill extension. Present all of them in the chat as installable skill files so I can install each one with one click.What you getDefine— figure out who you're designing for and what they needMeasure— turn guesses into real findings you can trustFocus— pick the best direction from your optionsLead— connect design work to business goalsExample outputWhat the Decision Map DoesThe Decision Map is a four-area framework. Each area answers a different question about the work.AreaQuestion it answersSkills insideDefineWhat is the real problem, and is it credible?User Needs, Audience, Collecting, SituationsMeasureDoes this design do what we intended for people?Concepts, Hunches, Testing, FindingsFocusOf the options, which is worth committing to?Initiatives, Variables, Comparing, BetsLeadDid the bet move the business enough to keep funding it?Business Goals, Workflows, Mapping, ResultsThe areas are designed to run in sequence. Define names a credible situation. Measure tests one hunch and calls it. Focus repeats the test across options and makes a bet. Lead ties the bet to a business goal and checks whether it held. Each area ends in an output block that judges one quality: Situations (credibility), Findings (usefulness), Bets (desirability), and Results (viability). UX Metrics is a shared system used by all four areas, with its own skill.The Four AreasDefineGets the team clear on the real problem before any building or testing begins.Skills:User Needs: names what users are actually trying to do, across five layers and 20 needs, and checks what they say against what they doAudience: names the source of every signal, rates its credibility, and defines people by behavior instead of labelsCollecting: gathers evidence openly, before anyone has a hunch, and maps how far to trust each sourceSituations: names the recurring conditions behind what users do and checks that they are credibleWhat it produces:A needs brief with the need, the evidence, and the UX metrics that would show it improvingAn Audience Definition Card with the source, behavioral attributes, and a credibility ratingA Source Map: what was gathered, how far to trust it, and the gapsA named situation on the confidence ladder; at Recurring, it goes to MeasureMeasureTurns a credible situation into a tested hunch, with a verdict and a Use signal.Skills:Concepts: names the design effort and ties it to a user need and a business goalHunches: turns a belief into a falsifiable hypothesis and writes the questions that would prove itTesting (skill: glare-measure-questioning): picks the technique, Stack, and tool, rates the evidence, and names leading and lagging metricsFindings: calls the hunch, writes the Use signal, and picks one of five decision types: Implement, Refine Design, Test Iteration, Revisit Later, or Do Not PursueWhat it produces:A concept brief with the user need, business goal, and the signal to measureA hunch ready to test: we believe this change for this group will have this impact because of this reason, with its type, perspective, and questionsA Test Plan with the technique, evidence rating, and leading and lagging metricsA finding: a verdict (Supported, Challenged, Refuted, or No call), a Use signal, and a next moveFocusRepeats the measurement across options and commits to the one worth backing.Skills:Initiatives: organizes scattered requests into one focused area of work with a shared goalVariables (skill: glare-focus-methods): names the one thing that changes between measurements, from 12 variablesComparing: repeats the same measurement across the variable and reads a Use line and a Prefer lineBets (skill: glare-focus-decisions): commits to one option by the winner rule, with a predicted outcome and a check dateWhat it produces:An initiative brief that answers six framing questionsA variable choice with what stays fixedA comparison readout with a Use line, a Prefer line, and the tradeoffA bet record: the call, the cost, the bet size, the predicted outcome, and the ownerLeadConnects design work to business outcomes and makes the impact visible to leadership.Skills:Business Goals: anchors the work to one of five pressures and 20 goals, with Design, Product, and Business KPIsWorkflows: names the function that owns each KPI and translates findings into its languageMapping: builds the Chain of Proof and names a link type for every step: Causal, Correlated, Sequential, or LinkedResults: checks each bet's predicted outcome against a baseline over its window and gives a verdictWhat it produces:A goal anchor with KPIs at three layersA workflow map with an owner for every numberA Chain of Proof with the weakest link namedA verdict (Held, Partly held, Didn't hold, or Too early) that re-ranks the next roundHow the Areas ConnectEach area passes its output to the next.Define names a credible situation that Measure writes hunches aboutMeasure produces a finding and a Test Plan that Focus can repeat across optionsFocus produces a bet with a predicted outcome that Lead checksLead's verdict re-ranks the next bets, and gaps go back to Measure as new hunchesTeams can also enter at any point depending on where they are stuck:Cannot agree on the problem → start with DefineHave a credible situation but nothing testable → start with MeasureHave options to choose between → start with FocusHave a bet but no proof it paid off → start with Lead

Related links

Gerie Owen

Gerie Owen shows how to apply impact mapping to software projects with examples. Useful when a software team wants a worked example before trying it themselves.

They Make Design

TheyMakeDesign explains how to turn UX insights into shipped actions, not just reports. Useful when a team gathers data but rarely changes the product.

Cezara Moisuc

Cezara Moisuc combines the product trio with the opportunity solution tree as a discovery duo. Useful when a team wants a clear playbook for ongoing discovery work.

Identify where decision quality breaks down

The Glare Design Assessment helps teams spot weak validation, stakeholder friction, alignment gaps, and assumptions that scale without measurable learning—so you have a clearer starting point for improvement.

About 5 minutes · Team-based · Diagnostic snapshot you can act on

Take the Design Assessment