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 how do we measure it?User Needs, Audience, UX Metrics, CollectingMeasureWhat are we testing and what do we expect to find?Concepts, Hunches, Questioning, FindingsFocusWhat does the evidence say and what should we do next?Initiatives, Methods, Comparing, DecisionsLeadHow does this work connect to business outcomes?Business Goals, Mapping, Workflows, ResultsThe areas are designed to run in sequence. Define sets up the problem. Measure builds the evidence. Focus interprets it. Lead connects it to the business. Each area produces outputs the next one depends on.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 and separates real needs from stated preferencesAudience: decides whose feedback counts and how much weight to give each voiceUX Metrics: chooses the right numbers to prove the work is making a differenceCollecting: builds a research plan that produces evidence the team can act onWhat it produces:A needs brief with active need types validated against observed behaviorAn audience brief with the right voices, segments, and participant typesA metric plan with one attitudinal, one behavioral, and one performance metricA collection plan with the research mode, techniques, tools, and sharing approachMeasureTurns the problem into a testable effort with a hypothesis, research questions, and findings.Skills:Concepts: frames the design effort by connecting a user need to a business goalHunches: turns instinct into a falsifiable hypothesis the team can confirm or disproveQuestioning: writes specific, unbiased research questions tied to a metric and techniqueFindings: translates raw data into signals that connect to user needs and business outcomesWhat it produces:A concept brief with the user need, business goal, and signal that would prove it workedA hypothesis using the template: we believe this change for this group will have this impact because of this reasonA question set covering People, Process, Product, and Problem, each tied to a metricA signal for each finding: raw data, user need, business result, and recommendationFocusInterprets the evidence and produces a clear decision about what moves forward.Skills:Initiatives: organizes scattered requests into one focused area of work with a shared goalMethods: chooses the right frame for bringing data into the initiativeComparing: places signals side by side using a shared metric to find the strongest resultDecisions: names what happens next - Implement, Refine, Test Iteration, Revisit, or Do Not PursueWhat it produces:An initiative brief with the user need, business goal, audience, and UX metricA method plan that matches the frame to the decision the team needs to makeA comparison finding with the strongest signal and the tradeoff the team acceptedA decision record with the signal, tradeoff, decision type, next step, and ownerLeadConnects design work to business outcomes and makes the impact visible to leadership.Skills:Business Goals: maps Design KPIs to Product KPIs to Business KPIs in a connected chainMapping: builds the full Chain of Proof from user need to business goal across five rungsWorkflows: translates design findings into the language of eight business functionsResults: closes the loop between Initiatives, Findings, Decisions, and OutcomesWhat it produces:A three-layer KPI chain: Design KPI, Product KPI, Business KPIA Chain of Proof with all five rungs named and connectedA translated finding for each business function in their own metrics and vocabularyA project loop that connects every initiative to a visible business outcomeHow the Areas ConnectEach area passes its output to the next.Define names the user need that Measure will frame as a conceptDefine names the metrics that Measure will track in its hypothesisMeasure produces the findings that Focus will compare and decide onFocus produces the decision that Lead will connect to a business outcomeLead produces the chain that proves the whole loop moved somethingTeams can also enter at any point depending on where they are stuck:Cannot agree on the problem → start with DefineHave a problem but no testing plan → start with MeasureHave evidence but no decision → start with FocusHave a decision but cannot explain its business value → start with Lead