Decisions

Decisions turn signals into action.By the time a team reaches Decisions, the work should no longer be floating in opinion. The initiative is clear. The method has framed the data. Comparing has shown what is stronger, weaker, or worth changing.Now the team needs to choose. A decision is where Focus becomes movement. It takes the signal, names the tradeoff, and gives the business a clear next step. Without a decision, findings stay in decks. Concepts stay open. Meetings keep circling the same questions.Decisions cut through that. They help teams say what should happen next, why it should happen, and what evidence supports the move.Why Decisions MatterMost teams do not struggle because they lack ideas. They struggle because they do not know when to commit.A team may have strong findings, useful comparisons, and clear user feedback, but still hesitate. One stakeholder wants to ship. Another wants another round. Someone else wants to protect scope. The team keeps talking, but the work does not move.That is how momentum slips. Decisions help teams:turn evidence into a clear directionexplain tradeoffs without reopening the whole debatereduce second-guessingconnect design choices to business movementshow what should happen nextkeep meetings from turning into opinion loopsA strong decision gives the team permission to move.Two types of decisionsDecisions happen at two levels.There is a broader strategic view, where leaders decide what kind of direction the business should support. Then there is the tactical meeting view, where teams decide what to do next with a specific concept, design, or signal.Both matter. The strategic view helps leadership understand how design choices shape business outcomes. The tactical view helps teams leave the meeting with a clear next move.Strategic decisionsStrategic decisions look across the larger direction of the work.This is where the team asks whether an initiative, concept, or product direction deserves more investment. The decision is not only about one screen or one test result. It is about whether the evidence supports a bigger move.A strategic decision might answer:Should we invest in this direction?Should this initiative become a priority?Should this concept move into the roadmap?Should we shift resources toward this opportunity?Should this work shape a larger business workflow?The strategic view often works like a triangle.At the top, decisions are broad and directional. They shape priorities, investment, and business confidence. At the bottom, decisions are more tactical. They shape screens, flows, messages, and iterations.Both are connected. A tactical signal can support a strategic direction. A strategic direction can shape which tactical decisions matter most.Tactical decisionsTactical decisions happen closer to the work. These are the choices teams make in reviews, working sessions, product discussions, or research readouts. The decision should be clear enough that the team knows what happens next.A tactical decision might answer:Should we implement this?Should we refine the design?Should we test another iteration?Should we revisit this later?Should we stop pursuing this direction?This is where decisions become practical.The team should be able to leave the meeting knowing what was chosen, why it was chosen, and what action follows.Tactical Decision MakingA decision should not be vague. Teams need clear decision types so the evidence leads to action. These types help the team move without over-explaining every time.ImplementUse this when the signal is strong enough to move forward.The team has enough evidence to act. The direction supports the user need, connects to the initiative, and gives the business confidence to invest.Implement means:the signal is strongthe tradeoff is acceptablethe next step is clearthe team should move into production, planning, or rolloutRefine DesignUse this when the direction is right, but the design needs improvement.The signal shows potential, but something needs to be clarified, simplified, or strengthened before the team commits fully.Refine Design means:the concept has valuethe current version is not strong enough yetthe team knows what needs to changeanother pass should improve the signalTest IterationUse this when the team needs another signal before deciding.The evidence is useful, but not strong enough to act on yet. The team may need to compare a new version, test a different audience, or reduce uncertainty around a specific risk.Test Iteration means:the direction is still openthe current signal is incompletea sharper comparison is neededanother round will help the team decideRevisit LaterUse this when the idea has potential, but is not the right move right now.The signal may be mixed, the timing may be wrong, or the initiative may not be ready. Revisit Later keeps the idea alive without letting it distract the team.Revisit Later means:the idea is not deadthe timing or context is not rightthe team should capture the rationalethe work may return when priorities shiftDo Not PursueUse this when the signal shows the direction is not worth more investment.This is not failure. It is a useful decision. It protects the team from spending time on work that does not create enough value.Do Not Pursue means:the signal is weakthe tradeoff is not worth itthe direction does not support the initiativethe team should stop or remove it from considerationWhat goes into a decisionA decision starts with evidence. The team should not make a decision from a feeling alone. It should come from a signal that has been framed and compared clearly enough to support action.A strong decision usually includes:the initiative being supportedthe concept, flow, feature, message, or direction being consideredthe UX metric that mattersthe signal that shaped the choicethe comparison that gave the signal contextthe tradeoff the team is acceptingthe next step the team should takeWithout those pieces, the decision can feel like an opinion. With them, the decision becomes easier to trust.How to make a decisionStart with the signal, then make the choice explicit.Use five steps.1. Name what is being decidedStart by naming the exact choice in front of the team. This might be a concept, feature, design direction, CTA, flow, message, or journey moment.Ask:What are we deciding?Is this a strategic direction or a tactical next step?What initiative does this support?What happens if we do not decide?This keeps the team from turning one decision into five different debates.2. Ground the decision in the signalBring the strongest evidence into the conversation. The signal should show what users did, felt, understood, preferred, or struggled with. It should connect back to the UX metric that matters for the initiative.Ask:What signal matters most?What metric supports it?What user feedback explains it?What comparison gives it context?This keeps the decision from drifting back into preference.3. Explain the tradeoffEvery decision gives something up. A direction might improve clarity but take more effort to build. It might create more trust but reduce speed. It might serve one audience better than another.Name the tradeoff clearly.Ask:What gets stronger if we choose this?What might get weaker?What risk are we accepting?What are we choosing not to do?This helps stakeholders support the decision without pretending it is perfect.4. Choose the decision typeUse a clear decision type so the team knows what happens next.Choose one:ImplementRefine DesignTest IterationRevisit LaterDo Not PursueThis turns the discussion into action. The team should not leave with a vague “let’s keep exploring” unless the decision is actually to test another iteration.5. Lock the next moveEnd by naming the next action. A decision is not complete until someone knows what to do with it.Define:who owns the next stepwhat needs to happen nextwhat evidence should be carried forwardwhen the decision should be reviewed again, if neededThis keeps the decision from getting lost after the meeting.What comes out of a decisionThe output of a decision is a clear next move. A strong decision gives the team:a named choicethe signal behind the choicethe tradeoff being acceptedthe decision typethe owner or workflow affectedthe next stepThis is what helps the business move forward.Product knows what to prioritize.Design knows what to refine.Research knows what still needs evidence.Marketing knows what message to sharpen.Leadership knows what direction to back.A decision should make the work easier to act on, not just easier to talk about.Where Decisions work bestDecisions work best when the team has enough signal to choose.Use Decisions when the team has compared concepts, reviewed signals, and needs to move the work into action. They are especially useful in design reviews, roadmap discussions, research readouts, sprint planning, and leadership updates.Decisions work less well when the signal is too weak or the initiative is unclear. If the team does not know what matters, what was compared, or what the tradeoff means, go back to Methods or Comparing before forcing the choice.A decision should create confidence, not hide uncertainty.Where Decisions fit in GlareDecisions sit at the end of the Focus facet. Initiatives define the area of work that needs attention. Methods frame the data. Comparing shows what is stronger. Decisions turn that evidence into action.In the Focus flow:Initiatives define what needs attention.Methods frame the data.Comparing shows what is stronger.Decisions move the work forward.Decisions are where Focus creates momentum. They turn signals into choices, choices into action, and action into business movement.AI PromptThis prompt helps you turn a comparison finding into a named decision your team can act on.Start with a finding from a completed comparison, review, or research readout. It guides you to:Ground the decision in the strongest signal from the comparisonName the tradeoff the team is acceptingChoose exactly one of the five decision types: Implement, Refine Design, Test Iteration, Revisit Later, or Do Not PursueLock the next move so someone owns what happens after the meetingYou'll end with a clear decision backed by signal, with a tradeoff named and a next step recorded.Use this in any design review, sprint, or stakeholder readout where the team has evidence but keeps circling the same questions without committing.AI SkillThe Decisions skill file teaches your AI the full five-move taxonomy and decision-making process so it can help you convert any comparison finding into a named, recorded decision that downstream teams can act on.Load it when you need to go deeper on the criteria for each decision type, writing tradeoffs explicitly, or distinguishing strategic decisions about direction from tactical decisions about the next move on a specific concept. It gives your AI:The five tactical decision types with the criteria for choosing between themThe five-step process from naming what is being decided through locking the next moveThe guidance for grounding every decision in a signal rather than a preferenceThe decision record structure including the initiative, signal, tradeoff, type, and next stepDownload the skill file below to use the full Decisions framework with your AI assistant.