AI Reflex OS
Decision Clarity Reflex Area
2026-09-21
Table of Contents
- Recognizing When Work Is Relying on a Decision
- Distinguishing Decisions From Intent, Assumption, Preference, and Open Questions
- Distinguishing Decisions From Situation, Assessment, and Consequence
- Identifying Implicit Decisions in Meetings, Documents, and Work
- Reconstructing Candidate Decisions From Messy Material
- Testing Whether a Reconstructed Decision Is Supported by the Material
- Making Decisions Explicit, Concrete, and Actionable
- Making Decisions Atomic
- Clarifying the Concrete Benefit of the Choice
- Identifying the Rejected Alternative
- Identifying the Accepted Downside
- Clarifying Decision Ownership and Authority
- Surfacing Hidden Assumptions and Undecided Dependencies
- Challenging Decisions Against Constraints and Reality
- Correcting, Narrowing, or Rejecting Candidate Decisions
- Checking Decisions for Internal Consistency
- Checking Whether the Decision Set Is Complete Enough
- Testing Whether Decisions Can Carry Commitment
- Distinguishing Decision Problems From Execution Problems
- Preserving Decision Integrity During Execution
- Changing, Reversing, and Replacing Decisions Explicitly
Recognizing When Work Is Relying on a Decision
Identifying Next Steps That Depend on an Unstated Choice
- Which planned next steps assume that a choice has already been made?
- What specific choice would have to be settled for those steps to make sense?
- Which planned actions would change or stop if another option were chosen?
- What evidence shows that the underlying choice is actually settled?
- Are people acting on an explicit commitment or on a shared assumption?
- What becomes harder to reverse if work continues before the choice is made explicit?
- What decision needs to be made or confirmed before these next steps proceed?
Clarifying Whether Silence Is Being Treated as Agreement
- What exactly is being treated as agreed because nobody objected?
- Was there an established rule that silence would count as agreement?
- Who needed to agree, and did each of them have a real opportunity to do so?
- What else could the silence reasonably mean in this situation?
- Is anyone now relying on a commitment they never explicitly accepted?
- What evidence other than silence supports the claimed agreement?
- What needs explicit confirmation before the organization treats this as decided?
Checking What Was Actually Decided in a Meeting
- What specific choice was the meeting expected to resolve?
- What exact commitment, if any, did the meeting actually produce?
- Who had authority to close the choice, and what did they say or do?
- Which statements were recommendations, preferences, or discussion rather than decisions?
- What scope, conditions, or exceptions were part of the agreement?
- Do the notes, actions, and participants' recollections support the same interpretation?
- What remained open when the meeting ended?
Determining Whether a Topic Is Ready for a Decision
- What exact choice needs to be made?
- Are the alternatives developed enough to make that choice meaningful?
- What information could still reasonably change which option should be chosen?
- Which assumptions or uncertainties are material to the choice?
- Is the relevant decision owner or decision-making body clear?
- Does the choice depend on another unresolved decision that should come first?
- What can legitimately remain uncertain without preventing a responsible decision now?
Recognizing Commitments That Are Becoming Difficult to Reverse
- What action or commitment is beginning to close off other options?
- Which decision is supposed to justify crossing that point?
- What would become financially, operationally, contractually, or politically difficult to undo?
- Is the underlying choice explicit enough for others to rely on it?
- Which important assumptions or dependencies remain unresolved?
- How much flexibility remains if circumstances change after this step?
- What needs to be confirmed before the organization crosses the point of difficult reversal?
Comparing Different Interpretations Across Teams
- What does each team believe has actually been decided?
- Which part of the commitment do their interpretations differ on?
- What source or wording is each interpretation based on?
- Are the different interpretations genuinely plausible from the available decision record?
- What would each team do differently if it followed its own interpretation?
- Does the disagreement reveal ambiguity in the decision or failure to follow a clear commitment?
- What needs to be clarified or explicitly decided so the teams can rely on the same basis?
Identifying Topics That Keep Returning Without Closure
- What choice was supposedly settled the last time this topic was discussed?
- What evidence shows that a real decision was made?
- Which part of the issue keeps returning despite that supposed decision?
- Are people reopening the choice, disputing its meaning, or simply not following it?
- What material question remains unresolved beneath the recurring discussion?
- Is there a legitimate owner or decision-making mechanism capable of closing it?
- What explicit commitment would stop the topic from returning for the same reason?
Distinguishing Approval of Material From Approval of a Decision
- What exactly was approved: the document, the analysis, the recommendation, or a specific course of action?
- What does approval mean under the process being used here?
- Which proposed decisions are contained inside the approved material?
- Did the approver have authority to make those decisions as well as approve the material?
- Which statements in the material remain assumptions, recommendations, or analysis?
- Is there separate evidence that the substantive choice itself was adopted?
- How should the approved decision be stated so nobody has to infer it from the document?
Clarifying Internal Choices Before Making External Commitments
- What external promise or obligation is about to be created?
- Which internal choices must already be settled for that commitment to be credible?
- Who has authority to make those internal choices?
- What scope, resources, or responsibilities are still being assumed rather than committed?
- Which dependencies could prevent the organization from fulfilling the external promise?
- What alternative would the external commitment effectively close?
- What must be made explicit internally before the organization commits externally?
Checking the Decision Basis Before Execution Begins
- What decisions does the planned execution already rely on?
- Can those decisions be stated clearly enough for the people doing the work?
- Do the people involved share the same understanding of scope and expected outcome?
- Are ownership and authority clear for the decisions execution depends on?
- Which assumptions, resources, or dependencies are still carrying part of the commitment?
- Which open matters are legitimate implementation details rather than missing decisions?
- Is the decision basis stable enough for execution to begin without teams inventing substantive choices themselves?
Distinguishing Decisions From Intent, Assumption, Preference, and Open Questions
Separating Intent From Commitment
- What does the organization currently intend to do?
- Which part of that intent has actually been committed to?
- Could the intended direction still change without reversing a decision?
- What authority, approval, or choice would convert the intent into a commitment?
- Are people already acting as though the intention were binding?
- What conditions or unresolved choices still separate the intention from a decision?
- How should the current state be described so others do not mistake intent for commitment?
Identifying Assumptions Embedded in Apparent Decisions
- Which parts of the apparent decision are stated as facts but have not actually been confirmed?
- What must be true for the commitment to mean what people currently think it means?
- Which assumed facts could materially change the decision if they proved false?
- Are any future approvals, resources, or stakeholder actions being treated as though they were already secured?
- Does any assumption actually conceal another decision that has not yet been made?
- Which elements are supported by evidence, and which are being inferred?
- What needs to be confirmed or separated before the actual decision can be stated cleanly?
Distinguishing Preferences From Decisions
- What option is currently preferred?
- Has anyone with the relevant authority actually selected that option?
- Are other options still legitimately open?
- What would have to happen before the preference becomes a commitment?
- Are plans or communications already treating the preferred option as settled?
- Could the preference change without anyone needing to reverse a decision?
- How should the current position be expressed so preference is not mistaken for choice?
Clarifying Which Questions Are Still Open
- What has actually been settled so far?
- Which material questions still have more than one live answer?
- Which open questions could change the meaning or scope of the existing commitment?
- Who owns each unresolved choice?
- Which questions can remain open until execution without weakening the decision?
- Are people already assuming answers to questions that have not been decided?
- What must be resolved before the decision can be treated as complete enough for its next use?
Separating Recommendations From Commitments
- What course of action is being recommended?
- Who made the recommendation, and what authority do they have?
- Has the legitimate decision owner or decision-making body accepted it?
- Which parts of the recommendation remain optional or subject to further choice?
- Are downstream teams treating the recommendation as though it were already binding?
- What evidence distinguishes endorsement of the recommendation from adoption of the proposed action?
- What decision, if any, should now be recorded separately from the recommendation?
Distinguishing Direction of Travel From a Decision
- What broad direction has been established?
- Which concrete choices remain open within that direction?
- What does the direction rule out, if anything?
- Could several materially different decisions still be consistent with it?
- Are teams making specific commitments that the broad direction did not actually authorize?
- What future choices are deliberately being preserved?
- What should be stated explicitly so the direction guides work without being mistaken for a completed decision?
Testing Whether a Proposal Has Actually Been Approved
- What exact proposal was submitted for approval?
- What evidence shows that an authorized person or body approved it?
- Was the approval final, conditional, partial, or limited to a particular scope?
- Were any elements excluded, deferred, or sent back for further work?
- Does the approval cover the substantive commitment or only permission to proceed to another stage?
- Are implementation activities assuming more than the approval actually grants?
- What is the strongest decision statement the approval genuinely supports?
Clarifying What Agreement in Principle Does and Does Not Decide
- What part of the proposed direction has genuinely been agreed in principle?
- Which details or conditions remain explicitly unresolved?
- What further decision or approval is still required before commitment becomes final?
- Which alternatives have actually been closed and which remain available?
- Are people treating agreement in principle as permission to begin irreversible work?
- What could still change without reversing what has already been agreed?
- How should the current commitment be stated so its limits are unmistakable?
Separating Document Approval From Decision Approval
- What did approving the document authorize or confirm?
- Which substantive decisions are described or recommended inside the document?
- Did the approval process explicitly adopt those decisions?
- Could someone approve the document while disagreeing with one of its proposed choices?
- Which assumptions or analytical conclusions remain merely part of the document?
- What evidence shows that a particular commitment moved from proposed to decided?
- Which decisions need to be recorded separately from the document approval?
Determining Whether a Discussion Produced a Real Decision
- What choice was the discussion trying to resolve?
- Did someone with legitimate authority actually close that choice?
- What option was selected, and what alternatives remained open afterward?
- Was the apparent agreement explicit or inferred from the direction of the conversation?
- What scope, conditions, or qualifications accompanied the conclusion?
- Would different participants describe the resulting commitment the same way?
- If no clear commitment emerged, what remains to be decided?
Distinguishing Decisions From Situation, Assessment, and Consequence
Separating Observable Conditions From Decisions
- Which statements describe what is currently happening?
- Which of those statements are observations rather than choices?
- What evidence supports the description of the current condition?
- Has anyone moved from describing the condition to committing to a response?
- Are people treating an observed fact as though it dictates only one possible action?
- What alternative responses remain available given the same condition?
- What decision, if any, still needs to be made about how to respond?
Distinguishing Problem Statements From Choices
- What problem or gap is being described?
- Does the statement identify what is wrong, or does it actually choose what to do about it?
- Could several different responses address the same problem?
- Is a preferred solution being hidden inside the way the problem is framed?
- What evidence supports the problem statement independently of the proposed response?
- Has an authorized decision-maker selected among the available responses?
- How should the problem and the resulting choice be stated separately?
Separating Causal Analysis From Commitment
- What explanation is being offered for why the situation exists?
- How strongly is that causal explanation supported?
- Does accepting the explanation necessarily imply a particular response?
- What different actions could follow from the same causal assessment?
- Are people treating an analytical conclusion as though it were already a commitment?
- Has anyone with authority chosen what to do in light of the analysis?
- What should remain analysis, and what decision still needs to be stated separately?
Distinguishing Constraints From Decisions
- What condition is being treated as a constraint?
- Is it genuinely fixed, or could someone with appropriate authority change it?
- What options does the constraint rule out without selecting among the remaining ones?
- Are people presenting a preferred choice as though the constraint made it inevitable?
- Does the constraint apply to the full scope of the decision?
- What choices remain available within the constraint?
- What actual decision still needs to be made once the constraint is acknowledged?
Separating Risk Assessment From Choice
- What uncertain event or outcome is being assessed?
- What does the assessment say about likelihood, consequence, or exposure?
- Does the risk assessment itself commit the organization to any response?
- What different choices could reasonably follow from the same risk assessment?
- Who has authority to decide what level of risk to accept or mitigate?
- Are people confusing recognition of a serious risk with agreement on how to respond?
- What decision is still required after the risk has been understood?
Distinguishing Option Comparison From Selection
- Which alternatives are being compared?
- What criteria or tradeoffs does the comparison reveal?
- Does the analysis identify a preferred option or an actually selected one?
- Who has authority to turn the comparison into a decision?
- Are any viable alternatives still open despite one option scoring better?
- What assumptions materially affect the comparison?
- What evidence shows that selection has occurred rather than analysis merely pointing toward one option?
Separating Consequences of Inaction From Chosen Action
- What is expected to happen if no decision or action is taken?
- How well supported is that consequence?
- Does recognizing the cost of inaction establish what the organization should do instead?
- What different responses could avoid or reduce the consequence?
- Are people treating urgency as though it eliminates the need to choose among alternatives?
- Has a specific response actually been selected?
- What decision remains after the consequences of inaction are made clear?
Identifying Analytical Conclusions Presented as Commitments
- What conclusion does the analysis reach?
- Does that conclusion describe what appears true or what the organization has committed to do?
- Who produced the analysis, and do they have authority to make the resulting decision?
- What alternatives remain possible even if the analytical conclusion is accepted?
- Are downstream documents or plans treating the conclusion as binding?
- What additional act of decision would be needed to create commitment?
- How should the analytical conclusion be restated so it cannot be mistaken for a decision?
Clarifying Whether a Consequence Has Been Mistaken for a Response
- What consequence or effect is being described?
- Is that consequence something expected to happen or something the organization has chosen to make happen?
- What action would actually be required to produce, avoid, or manage the consequence?
- Has that action been explicitly selected?
- Could different responses lead to the same desired consequence?
- Are people assuming the response from the outcome they want?
- What choice must be stated separately from the consequence?
Reclassifying Statements That Mix Situation, Assessment, Consequence, and Choice
- Which part of the statement describes the current situation?
- Which part interprets or explains that situation?
- Which part describes an expected consequence?
- Which part, if any, actually commits the organization to a choice?
- Are assumptions or recommendations being blended into the same statement?
- What becomes clearer if the different elements are separated?
- After separating them, what genuine decision remains to be stated or confirmed?
Identifying Implicit Decisions in Meetings, Documents, and Work
Tracing Agreed Next Steps Back to the Decisions They Imply
- What agreed next step would be difficult to explain unless some prior choice had been made?
- What minimum commitment is required for that next step to make sense?
- Could the same action occur under another plausible decision?
- Who authorized the action, and does that authorization reveal a decision?
- Does the action imply a narrow local choice or a broader organizational commitment?
- What evidence independently supports the implied decision?
- What candidate decision should be made explicit rather than left embedded in the next step?
- Which meeting conclusions actually close a choice rather than summarize discussion?
- What commitments are implied by the actions or conclusions recorded at the end of the meeting?
- Which conclusion could still be interpreted in more than one decision-relevant way?
- Who had authority to make each implied choice?
- What scope or conditions can be supported from the meeting material?
- Which apparent decisions depend on inference rather than explicit wording?
- What candidate decisions should be extracted for separate confirmation or recording?
Identifying Decisions Embedded in Plans and Roadmaps
- Which parts of the plan assume that one option has already been selected?
- What scope, timing, technology, operating model, or resource choices are embedded in the roadmap?
- Which of those choices are necessary for the plan to work as written?
- Could the plan still make sense if another option were chosen?
- What evidence shows that the embedded choices were actually authorized?
- Which items are planning assumptions rather than decisions?
- What candidate decisions should be separated from the plan before others rely on them?
Identifying Commitments Embedded in Draft Contracts or Terms
- Which clauses assume that an internal choice has already been made?
- What obligations would become real if the draft were signed in its current form?
- Which scope, pricing, service, liability, or responsibility choices are embedded in the terms?
- Were those choices explicitly decided internally or introduced during drafting?
- Who has authority to commit the organization to each material term?
- Which provisions remain negotiation positions rather than accepted commitments?
- What internal decisions need to be made explicit before the contract progresses?
Inferring Decisions From Budget and Resource Commitments
- What choice appears to be reflected in the way money or resources have been allocated?
- Is the allocation specific enough to distinguish one option from the alternatives?
- Could the same budget or staffing decision support several different courses of action?
- Who authorized the commitment of those resources?
- Does the resource commitment reveal a final choice, a pilot, or only preparation?
- What broader decision would be overclaimed if inferred from this allocation?
- What is the narrowest candidate decision the resource evidence actually supports?
Clarifying Choices Implied by Scope Boundaries
- What has been included and excluded from the current scope?
- Which underlying choices would explain those boundaries?
- Were the boundaries explicitly decided or simply inherited from planning assumptions?
- Could different decision rationales produce the same scope?
- Who had authority to define the boundary?
- What work is already relying on the implied inclusion or exclusion?
- What candidate scope decision should be made explicit before the boundary is treated as settled?
Tracing Ownership Assignments Back to Unstated Commitments
- What does the ownership assignment assume has already been decided?
- Does assigning this role imply a choice about structure, responsibility, scope, or operating model?
- Could the same ownership assignment exist under another plausible decision?
- Who made the assignment, and did they have authority over the implied commitment?
- Is the assigned owner being asked to execute a decision that was never explicitly made?
- What other responsibilities or authorities are being inferred from the assignment?
- What candidate decision should be separated from the ownership assignment and confirmed directly?
Identifying Decisions Revealed by Work Already Underway
- What course of action does the work already underway appear to assume?
- Could this work reasonably have begun while the underlying choice remained open?
- Who authorized the work, and what exactly did that authorization cover?
- Is the activity exploratory, reversible, or already committing the organization to one path?
- What alternative explanations could account for the work without a real decision having been made?
- What part of the apparent commitment is supported only retrospectively by the fact that work started?
- What candidate decision can be reconstructed without treating the activity itself as proof of legitimate closure?
Inferring Choices From Explicitly Ruled-Out Options
- Which alternatives have been explicitly ruled out?
- Who had authority to close those alternatives?
- Does eliminating them leave one genuinely available option or several?
- Is the option set complete enough for elimination to imply a positive choice?
- Could an undocumented alternative still remain open?
- What exactly has been closed even if no final selection can yet be established?
- What candidate decision, if any, can be inferred without confusing elimination with selection?
Separating Multiple Implicit Decisions Within One Passage or Discussion
- How many independently meaningful choices are embedded in the material?
- Which parts could change without requiring the others to change?
- Do different parts have different owners, scopes, tradeoffs, or conditions?
- Is one apparent commitment actually dependent on another hidden choice?
- What evidence supports each implied decision separately?
- Which parts are genuine commitments and which are assumptions or implementation detail?
- How should the implied choices be separated so each can be tested on its own?
Reconstructing Candidate Decisions From Messy Material
Reconstructing Decisions From Fragmented Meeting Notes
- Which notes contain direct evidence of a choice rather than discussion around it?
- What decision question appears to have been under consideration?
- Which fragments consistently point toward the same commitment?
- What scope, conditions, or qualifications can be recovered from the notes?
- Which elements remain inferred because no note states them directly?
- Do any fragments contradict the candidate decision?
- What is the narrowest candidate decision the meeting notes support without filling the gaps?
Reconstructing Candidate Decisions From Conflicting Notes
- What does each set of notes claim was decided?
- Are the apparent conflicts about the same time, scope, and decision?
- Which record is closer to the decision event or carries greater authority?
- Could chronology, provisional status, or later supersession explain the difference?
- Which parts of the candidate are supported despite the disagreement?
- What competing reconstructions remain plausible if the conflict cannot be resolved?
- What should remain explicitly uncertain rather than being reconciled into a cleaner story?
Reconstructing Decisions From Slide Decks
- Which slides describe facts, analysis, recommendations, or options rather than decisions?
- Where does the deck indicate that an option has actually been selected?
- What decision status can be established from the deck itself?
- Which scope, timing, or ownership details are explicit and which are inferred?
- Was the deck merely presented, or was any part of it formally adopted?
- What supporting evidence outside the slides would be needed to confirm the commitment?
- What candidate decision can be reconstructed without treating presentation material as automatic approval?
Reconstructing Decisions From Email or Message Threads
- Which message contains the strongest evidence that a choice was actually closed?
- Who sent it, and what authority did they have over the decision?
- How did the available options change over the course of the thread?
- Which statements are proposals, objections, conditions, or acknowledgments rather than commitments?
- Did later messages alter, qualify, or contradict the apparent decision?
- Are people relying on silence, reactions, or informal wording as evidence of agreement?
- What candidate decision best fits the thread while preserving unresolved ambiguity?
- Which parts of the evidence describe what people said, and which show what they actually did?
- What commitment would best explain both the commentary and the observed actions?
- Where do the actions support the stated position, and where do they diverge?
- Could the behavior result from assumption, workaround, or premature execution rather than a decision?
- Which evidence is contemporaneous with the supposed decision and which is retrospective?
- What elements of the candidate depend mainly on interpreting behavior?
- What is the smallest reconstruction that explains the evidence without turning action into proof of intention?
Reconstructing a Decision Across Several Documents
- Which documents contain evidence about the same underlying choice?
- What chronology links the proposal, discussion, approval, and later implementation?
- Which source provides the strongest evidence for the actual commitment?
- Are later documents independently corroborating the decision or merely repeating an earlier statement?
- Where do the documents differ on scope, status, timing, or conditions?
- Which elements can be supported across sources and which remain source-specific?
- What candidate decision best preserves the combined evidence without smoothing over genuine differences?
Working With Incomplete Material When Reconstructing Decisions
- What can be established directly from the material that is available?
- Which decision elements are missing rather than merely unclear?
- What assumptions would be required to produce a complete-looking decision?
- Which of those assumptions would materially affect the commitment?
- Are there several plausible reconstructions that fit the surviving evidence?
- What additional source or human confirmation would most reduce the uncertainty?
- How should the candidate be stated so the missing evidence remains visible?
Reconstructing Choices That Were Narrowed but Never Stated
- Which options were explicitly removed from consideration?
- What options remained after each narrowing step?
- Did the remaining option set ever become genuinely singular?
- Who had authority to eliminate the options that were closed?
- Could additional unrecorded alternatives still have remained available?
- Does the evidence show final selection or only progressive narrowing?
- What candidate decision, if any, can be stated without treating a narrowed field as a completed choice?
Separating Several Candidate Decisions Hidden Inside One Topic
- What distinct choices are being discussed under the same topic?
- Which choices could have different answers without contradicting one another?
- Do the candidates differ in owner, scope, timing, tradeoff, or dependency?
- Which parts of the material support each candidate separately?
- Is one apparent candidate actually a prerequisite for another?
- Which statements combine several choices only because they were discussed together?
- How should the candidates be separated so none claims evidence that belongs to another?
Reconstructing Decisions From Actions Already Being Taken
- What decision would most naturally explain the actions currently underway?
- Could those actions have occurred without that decision being made?
- Who authorized the actions, and what did that authorization actually cover?
- Are the actions exploratory and reversible or already committing the organization to one path?
- What evidence predating the actions supports the reconstructed choice?
- Which parts of the supposed decision are being inferred only from hindsight?
- What candidate decision can be stated without using current implementation to invent the original commitment?
Testing Whether a Reconstructed Decision Is Supported by the Material
Checking Whether the Chosen Path Is Supported by the Material
- Where does the material explicitly indicate that this path was selected?
- Which sources support the choice directly, and which only imply it?
- Does the evidence support the full scope of the reconstructed choice or only a narrower commitment?
- Are the sources describing the same decision, time, and organizational scope?
- What evidence would we expect to see if another path had actually remained open?
- Is there credible material that contradicts or qualifies the apparent selection?
- How confidently can we state the chosen path without claiming more than the evidence supports?
Checking Whether the Stated Benefit Is Supported by the Material
- Where does the material connect this decision to the stated benefit?
- Was the benefit identified when the decision was made or inferred afterward from what happened?
- Does the material describe this as a reason for the choice, an expected outcome, or a broader objective?
- Is the benefit specific to the chosen path rather than something several alternatives could provide?
- Are we filling a missing rationale because the reconstructed decision seems more coherent with one?
- Does any source point to a different primary benefit?
- What benefit can be stated without going beyond the evidence?
Verifying Whether the Rejected Alternative Appears in the Material
- What evidence shows that this alternative was actually considered or available?
- Where does the material indicate that the alternative was rejected rather than simply not selected?
- Was the alternative still viable when the decision was made?
- Does the evidence support rejection of the whole alternative or only part of it?
- Are side agreements, exceptions, or later statements keeping any part of the alternative open?
- Could another unrecorded alternative have remained available?
- What can we safely say was closed based on the material?
Distinguishing Supported Downsides From Explicitly Inferred Downsides
- Which downside is explicitly recognized in the source material?
- Was it understood as a consequence of the chosen path when the decision was made?
- Which stated downside is instead being inferred from later events or general knowledge?
- Does the material show that the downside was knowingly tolerated rather than merely possible?
- Would the same downside also have existed under the rejected alternative?
- Are we interpreting an unforeseen negative outcome as though it had been consciously accepted?
- Which downside can be attributed to the original decision with confidence, and which should remain marked as inference?
Separating Reconstruction From Invention
- Which parts of the candidate decision are directly supported by identifiable evidence?
- Where have we added scope, rationale, conditions, ownership, or tradeoffs that the material does not state?
- Is each inferred element necessary to explain the evidence, or merely useful for completing the story?
- Could a narrower reconstruction explain the same material with fewer assumptions?
- Are we resolving genuine ambiguity instead of preserving it?
- What parts of the candidate would disappear if we removed everything supported only by plausibility?
- What is the strongest reconstruction we can make without inventing missing content?
Assessing Candidate Decisions Supported Only Indirectly
- What indirect evidence points toward this candidate decision?
- How difficult would that evidence be to explain if the candidate were false?
- Could the same actions, plans, or resource commitments result from another plausible choice?
- Are several independent sources converging, or are they all derived from the same underlying assumption?
- How much of the candidate depends on interpreting behavior rather than explicit commitment?
- What material contradiction or missing evidence limits confidence?
- Should the candidate be treated as plausible, tentative, or too weak to rely on?
Assessing Contradictory Evidence Behind a Candidate Decision
- Which pieces of evidence materially conflict with the candidate decision?
- Do the conflicting sources actually concern the same time, scope, and decision?
- Could provisional status, later change, or supersession explain the contradiction?
- Which source has stronger authority, proximity, specificity, or provenance?
- Would resolving the conflict require us to invent a compromise that neither source supports?
- What parts of the candidate remain reliable despite the contradiction?
- How should the unresolved conflict change the confidence or wording of the reconstructed decision?
Comparing Several Plausible Reconstructions
- What are the materially different reconstructions that fit the available evidence?
- Which evidence supports each reconstruction directly?
- Which candidate requires the fewest unsupported assumptions?
- What important evidence is difficult for each reconstruction to explain?
- Does one candidate claim broader scope or stronger commitment than the material warrants?
- What additional evidence would most clearly distinguish between the competing reconstructions?
- Can one reconstruction be preferred, or should several remain explicitly plausible?
Recognizing When the Material Does Not Support a Reliable Decision
- Is there direct evidence that the relevant choice was ever closed?
- Do the available sources support one reconstruction clearly enough to distinguish it from credible alternatives?
- Are core elements such as scope, status, or authority dependent on unsupported assumptions?
- Does material contradictory evidence remain unresolved?
- Are apparently independent sources actually repeating the same ambiguous account?
- Would relying on the reconstruction require downstream users to treat uncertainty as fact?
- Is the most defensible conclusion that the available material cannot establish a reliable decision?
Flagging Inferred Elements for Human Confirmation
- Which parts of the reconstructed decision are inferred rather than directly supported?
- Which inferred elements would materially affect what people do if they were wrong?
- Does the scope, status, owner, condition, alternative, or downside require confirmation?
- Who is in the best position and has sufficient authority to confirm each material inference?
- Can confirmation establish what the current organization should rely on even if the historical record remains uncertain?
- Which elements can safely remain inferred because they do not affect the commitment?
- What should be presented for confirmation without implying that the inference is already established?
Making Decisions Explicit, Concrete, and Actionable
Turning Vague Direction Into Concrete Commitment
- What concrete choice is hidden inside the broad direction?
- What will actually happen differently because of this decision?
- Which parts of the direction remain intentionally open?
- Who or what organizational scope is being committed?
- What boundaries or conditions materially limit the commitment?
- Could two reasonable readers turn the current wording into different actions?
- What is the narrowest concrete statement that captures what has genuinely been decided?
Replacing Aspirational Language With Commitment Language
- Which words describe what the organization hopes to achieve rather than what it has decided to do?
- What specific action or boundary sits underneath the aspiration?
- Is the organization committing to an outcome, an action, or merely an ambition?
- Who is actually bound by the commitment?
- What remains uncertain even after the aspiration is made concrete?
- Would stronger wording overstate what has really been agreed?
- How can the decision be stated as a commitment without converting ambition into a promise nobody made?
Clarifying What Will Actually Happen
- What concrete action, change, or non-action follows from the decision?
- Who will behave differently once the decision takes effect?
- Which current practice will continue, stop, or change?
- What part of the intended outcome is still dependent on later choices?
- Could someone follow the decision correctly while doing something materially different from what was intended?
- What implementation freedom can remain without changing the commitment?
- What needs to be stated so affected people know what they can legitimately rely on?
Naming the Relevant Actor or Organizational Scope
- Who or what part of the organization is actually covered by this commitment?
- Is the current use of words such as "we", "the business", or "the organization" unambiguous?
- Does the decision apply to one team, several functions, a legal entity, or the entire organization?
- Who is affected without being part of the committed scope?
- Does the named actor have authority over everything the statement appears to commit?
- Would the decision mean something materially different if another organizational scope were assumed?
- What scope needs to be named explicitly to prevent overreach or underinterpretation?
Defining the Scope of the Commitment
- What exactly is included in this decision?
- Which products, teams, customers, systems, locations, or activities fall within its boundary?
- What is clearly outside the scope?
- Are any boundary cases likely to produce competing interpretations?
- Does the stated scope match what was actually authorized?
- What would materially expand the commitment beyond the current decision?
- How can the boundary be stated precisely without turning implementation detail into decision content?
Clarifying What the Decision Does Not Commit To
- What could a reasonable reader mistakenly assume this decision also settles?
- Which adjacent choices deliberately remain open?
- Does the decision apply only to a pilot, phase, scope, or time period rather than the broader issue?
- Which alternatives remain available outside the chosen scope?
- Are there future decisions that should not be prejudged by the current commitment?
- Would stating a non-commitment prevent a likely and material overinterpretation?
- What should be explicitly left outside the decision so its true boundary remains clear?
Removing Wording That Allows Conflicting Interpretations
- Which words or phrases could reasonably support more than one commitment?
- Are vague qualifiers such as "where appropriate", "as needed", or "generally" carrying substantive meaning?
- Do pronouns or broad labels make the actor or scope unclear?
- Are timing, conditions, or exceptions left open to interpretation?
- Could different teams follow the sentence faithfully and still take incompatible actions?
- Which ambiguity reflects a genuinely unresolved choice rather than poor wording?
- What wording removes the ambiguity without pretending that unresolved matters have been decided?
Translating Verbal Agreement Into a Written Decision
- What did the participants explicitly agree to?
- Which parts of the verbal discussion were conditions, qualifications, or unresolved points?
- What can be written directly from the agreement without interpretation?
- Which apparent details would have to be inferred to create a complete-looking statement?
- Would any proposed wording make the agreement broader, stronger, or more permanent than it was?
- What needs confirmation before it can appear as part of the written decision?
- What written statement preserves the actual agreement while leaving genuine uncertainty visible?
Comparing Written Decisions With Verbal Agreement
- What does the written decision say was committed to?
- What did participants actually agree to verbally?
- Has the written version added scope, certainty, conditions, or obligations that were not agreed?
- Has it omitted an important qualification or exception from the verbal agreement?
- Are differences merely improvements in wording, or do they change the substance?
- Which version are downstream teams already relying on?
- What needs to be corrected or confirmed so the written record accurately reflects the commitment?
Making Decisions Precise Enough for Downstream Work
- What downstream action will rely on this decision?
- Which parts of the commitment must be unambiguous for that work to proceed correctly?
- What choices should downstream teams still be free to make themselves?
- Are any critical scope, ownership, condition, or timing questions still being left to interpretation?
- Could two competent teams implement materially different commitments from the same statement?
- What additional precision would prevent rework without over-specifying execution?
- Is the decision now clear enough to survive handoff without verbal reconstruction?
Making Decisions Atomic
Identifying Multiple Decisions Hidden in One Sentence
- How many independently meaningful choices are contained in this sentence?
- Which parts could change without requiring the rest to change?
- Does the sentence commit different actors or scopes to different things?
- Are separate tradeoffs being compressed into one statement?
- Does one clause depend on a choice that has not yet been made?
- Could someone reasonably accept one part while rejecting another?
- Which distinct decisions should be separated before the commitment is recorded?
Splitting Bundled Choices Into Separate Decisions
- Which choices in the bundle can be governed independently?
- What is the smallest meaningful commitment in each part?
- Do the separate choices have different owners, scopes, conditions, or effective dates?
- Which choice logically depends on another?
- Would separating them expose a decision that is still unresolved?
- What context must remain shared so the separate decisions are not misunderstood?
- How should the bundle be split so each decision can be accepted, changed, or reversed on its own?
Separating Decisions With Different Owners
- Which parts of the current statement belong to different legitimate decision owners?
- What authority does each owner have over their part?
- Is anyone being treated as owner of a choice outside their mandate?
- Does one person's decision depend on another owner's separate commitment?
- Could one part be changed without the other owner's approval?
- Is apparent shared ownership really evidence that several decisions have been bundled together?
- What separate decisions would align each commitment with the authority that can actually make it?
Separating Decisions With Different Tradeoffs
- Which parts of the compound decision create different benefits or disadvantages?
- Would someone reasonably accept one tradeoff while rejecting another?
- Are different stakeholder groups bearing different costs under different parts of the decision?
- Does each component close a different meaningful alternative?
- Could one tradeoff later become unacceptable without affecting the others?
- Are we hiding a controversial choice inside a broader attractive package?
- Which decisions should be separated so each tradeoff can be considered and accepted explicitly?
Separating Decisions That May Need to Change Independently
- Which parts of the current commitment are likely to face different future conditions?
- Could one component need revision while the others remain valid?
- Do the parts have different assumptions, dependencies, or review triggers?
- Would changing one component currently force an unnecessary reopening of the whole statement?
- Which elements are more reversible than others?
- What relationships between the parts still need to be preserved after separation?
- How should the decisions be split so later change can be explicit and targeted?
Unpacking Conditions That Hide Additional Choices
- What condition is attached to the decision?
- Does the condition simply determine when the commitment applies, or does someone still need to choose what happens?
- Who determines whether the condition has been satisfied?
- Are the criteria for that determination already settled?
- Could different interpretations of the condition lead to different commitments?
- Is a future decision being disguised as an automatic trigger?
- What separate choice needs to be stated if the condition does more than qualify the existing decision?
Separating a Core Decision From Its Exceptions
- What is the general commitment that applies by default?
- Which exceptions are already part of that commitment?
- Does each exception merely define the boundary, or require a separate discretionary choice?
- Who has authority to approve an exception?
- Could exceptions become broad enough to undermine the core decision?
- Are any side agreements functioning as unrecorded exceptions?
- What should remain in the core decision, and what needs separate treatment as an exception decision?
Testing Whether a Compound Statement Can Be Accepted or Rejected as One
- Could a legitimate decision-maker reasonably agree with one part and disagree with another?
- Do all parts have the same owner and authority?
- Do they share the same scope, timing, conditions, and tradeoff?
- Would rejecting one component necessarily invalidate the others?
- Are the components operationally inseparable or merely discussed together?
- Could the statement be changed later only as a whole without creating unnecessary rigidity?
- Is there a genuine reason to keep the commitment atomic as one decision?
Checking Whether One Part of a Decision Can Stand Independently
- What exactly would this part commit the organization to on its own?
- Does it have a complete enough scope and owner to stand independently?
- Does it rely on another part for its meaning rather than merely for implementation?
- Would its benefit and downside still make sense if the other components changed?
- Can this part be accepted, implemented, or reversed independently?
- What dependency must remain explicit if it is separated?
- Should this become its own decision or remain inseparable from the larger commitment?
Preserving Necessary Relationships After Splitting Decisions
- Which of the separated decisions depend on one another?
- Does one need to occur before another can take effect?
- Are any decisions mutually exclusive or conditional on another choice?
- Do several decisions share a critical assumption or constraint?
- Which decision supersedes, qualifies, or creates an exception to another?
- What relationship would downstream users lose if the decisions were stored separately without links?
- How should the connections be recorded so atomicity does not create a false impression of independence?
Clarifying the Concrete Benefit of the Choice
Identifying the Operational Benefit Created by a Choice
- What practical improvement is expected because this particular option was chosen?
- What will become easier, faster, cheaper, safer, more reliable, or otherwise better in actual work?
- How does that improvement address the situation that required a decision?
- Would the same benefit arise under the most relevant alternative?
- What mechanism connects the chosen action to the expected improvement?
- Is the benefit concrete enough to observe or recognize later?
- What is the clearest operational benefit that explains why this choice matters?
Separating Concrete Benefits From General Aspirations
- Which claimed benefits describe broad ambitions rather than effects of this specific choice?
- What concrete change is expected to move the organization toward the aspiration?
- Could the same aspiration be used to justify several competing options?
- Which benefit differentiates this decision from those alternatives?
- Are words such as "agility", "alignment", "innovation", or "efficiency" hiding a more specific effect?
- What would actually be different in practice if the benefit materialized?
- How can the benefit be stated without relying on generic positive language?
Connecting the Benefit to the Situation Being Addressed
- What specific condition or problem made this decision necessary?
- Which part of that situation does the chosen option improve?
- How directly does the claimed benefit address the original need?
- Is the benefit attractive but unrelated to the actual decision problem?
- What evidence supports the link between the choice and the expected improvement?
- Would solving the stated problem still matter if this benefit did not materialize?
- What benefit best explains the connection between the situation and the chosen response?
Separating Concrete Benefit From Broader Decision Rationale
- What concrete benefit does the choice create?
- What other considerations form part of the broader rationale?
- Which constraints, risks, assumptions, or strategic considerations explain the decision without themselves being benefits?
- Is the current benefit statement trying to summarize the entire case for the decision?
- What useful effect would remain if the wider rationale were removed?
- Does the benefit identify what the organization gains rather than why every other option was rejected?
- How should the benefit and broader rationale be stated separately?
Selecting the Primary Benefit Among Several Benefits
- What different benefits are expected from the decision?
- Which benefit most directly addresses the situation that required the choice?
- Which benefit most clearly distinguishes the chosen option from the rejected alternative?
- If one benefit failed to materialize, which loss would most seriously weaken the case for the decision?
- Are some benefits secondary consequences rather than reasons for choosing this path?
- Do different stakeholders consider different benefits primary?
- Which benefit should be treated as primary without hiding the material secondary benefits?
- What benefit should appear directly after implementing the decision?
- Which claimed benefits depend on later changes, adoption, scale, or additional decisions?
- What causal steps connect the immediate effect to the longer-term outcome?
- Which longer-term effects remain uncertain rather than inherent in the choice?
- Could the decision succeed operationally without producing the broader long-term benefit?
- Are people using distant aspirations to justify a choice whose immediate benefit is unclear?
- Which benefit belongs to the decision itself, and which should be treated as a later expected effect?
Sharpening Benefits That Are Too Vague to Explain the Choice
- What does the current benefit statement actually mean in practical terms?
- Who experiences the improvement, and in what activity or outcome?
- What changes relative to the current situation?
- What changes relative to the rejected alternative?
- Which vague words could be replaced by observable effects?
- Is the benefit still meaningful once generic positive language is removed?
- What more precise wording captures the useful difference this choice is expected to create?
Testing Whether the Benefit Distinguishes the Chosen Option
- Would the rejected alternative provide the same benefit?
- If so, what benefit actually differentiates the chosen path?
- Is the claimed benefit merely a property of solving the problem at all?
- Which option produces more of the benefit, produces it sooner, or produces it with fewer sacrifices?
- What evidence supports the claimed difference between the options?
- Would the decision still make sense if the distinguishing benefit disappeared?
- What benefit best explains why this option was selected rather than the meaningful alternative?
Removing Benefit Language That Merely Restates the Decision
- Does the benefit describe an improvement, or simply repeat what the organization has chosen to do?
- What useful consequence follows from the chosen action?
- Why does the action matter to the situation being addressed?
- Could the current benefit statement be true even if the decision produced no improvement?
- What comparison with the rejected alternative reveals the real value of the choice?
- Are we confusing completion of the chosen action with realization of a benefit?
- What benefit can be stated without using the decision itself as its own justification?
Recognizing When No Concrete Operational Benefit Is Stated
- What benefit is currently claimed for the decision?
- Does that claim identify a concrete improvement or only a strategic aspiration?
- Is any source material clear about what useful difference the choice is expected to create?
- Could the decision have been made primarily because of a constraint rather than a positive benefit?
- Are several possible benefits being inferred because none was actually stated?
- Does the absence of a clear benefit weaken the decision or merely leave its rationale incomplete?
- What needs to be confirmed before a concrete benefit can be attributed to the choice?
Identifying the Rejected Alternative
Identifying the Most Meaningful Rejected Alternative
- What viable course of action did the chosen option displace?
- Which alternative best reveals the real tradeoff involved in the decision?
- Was that alternative genuinely available when the choice was made?
- Did it address substantially the same decision problem?
- What advantage did the rejected alternative offer that the chosen path gave up?
- Were other rejected options less relevant because they were clearly inferior or infeasible?
- Which alternative should be named if the goal is to understand what the decision actually closed?
Separating Rejected Alternatives From Simple Negations of the Choice
- Is the stated alternative an executable course of action or merely "not doing" the chosen option?
- What would the organization actually have done under the alternative?
- Does the alternative specify enough to compare its benefits and downsides with the chosen path?
- Could several materially different actions all fit the current negation?
- Was one of those actions genuinely under consideration?
- Does the supposed alternative create a fair comparison or make the chosen path look artificially inevitable?
- What concrete alternative best represents the path that was really available?
Writing Alternatives as Concrete Executable Options
- What would the organization actually do if this alternative were selected?
- Who would act differently under the alternative?
- What scope would it cover?
- What resources, timing, or operating model would it require?
- Is the alternative specific enough to assess against the same criteria as the chosen path?
- Are important choices still hidden inside the alternative itself?
- How can the alternative be stated as a real course of action rather than a vague category?
Selecting the Relevant Rejected Alternative Among Several Options
- Which alternatives were genuinely viable at the time of decision?
- Which one represented the strongest competing path?
- Which rejected option most clearly exposes the tradeoff behind the chosen decision?
- Did different alternatives address different parts of the problem rather than the same choice?
- Were some options already eliminated by constraints before the final choice?
- Does focusing on one alternative hide another path that remained materially relevant?
- Which rejected alternative is primary for understanding the decision, and which secondary alternatives should still remain visible?
Checking Whether an Alternative Has Actually Been Closed
- What evidence shows that the alternative is no longer available under the current decision?
- Was it explicitly rejected, or merely not selected at the time?
- Does the closure apply to the full organizational scope or only part of it?
- Is the alternative closed permanently, for a period, or only for the current phase?
- Can local exceptions or later choices still restore part of it?
- Are teams continuing to behave as though the alternative remains available?
- What exactly has the decision closed, and what remains open?
Identifying Side Agreements That Keep Rejected Alternatives Alive
- What informal agreements or local arrangements preserve parts of the rejected path?
- Who authorized those arrangements?
- Are they legitimate exceptions within the decision or unrecorded changes to it?
- How much of the rejected alternative remains operational through those agreements?
- Do the side agreements affect the same scope the original decision was meant to settle?
- Would removing the side agreements make actual practice match the stated decision?
- Does the decision need an explicit exception or change to reflect how the organization is really expected to operate?
Distinguishing Alternative Actions From Unwanted Outcomes
- Is the stated alternative something the organization could deliberately choose to do?
- Or is it an outcome the organization wants to avoid?
- What executable action would actually produce or risk that outcome?
- Could several different alternatives lead to the same unwanted consequence?
- Are people comparing the chosen option with a bad outcome rather than a credible competing course of action?
- What real alternative should be compared with the chosen path?
- How does the decision look once the unwanted outcome is separated from the alternative itself?
Testing Whether a Rejected Alternative Was Genuinely Available
- Could the alternative actually have been implemented at the time?
- Was it within the relevant decision-maker's authority?
- Was it legally, technically, operationally, and financially viable enough to matter?
- Could it have met the required timeframe?
- Was it excluded by a real constraint or merely never seriously considered?
- What evidence shows that decision-makers regarded it as a live option?
- Should it be described as rejected, unavailable, or simply unexamined?
Surfacing Meaningful Alternatives Left Implicit
- What credible path could have addressed the same decision problem but is missing from the recorded options?
- Did existing objectives or constraints unnecessarily narrow the option set?
- What would continuing the current approach have looked like as an explicit alternative?
- Were there less ambitious, more ambitious, staged, or reversible options that remained possible?
- Did organizational habit or early framing make one alternative effectively invisible?
- Would introducing this alternative materially change the understanding of the chosen tradeoff?
- Which implicit alternatives deserve recognition without pretending they were historically considered?
Clarifying Decisions That Avoid Choosing Between Competing Paths
- Which competing paths are still being kept open?
- Does the current decision genuinely resolve anything between them?
- Is preserving both options a deliberate choice with its own benefit and downside?
- What commitment has actually been made while the main alternative remains unresolved?
- Are downstream teams being forced to choose one path informally?
- When and by whom must the remaining choice eventually be made?
- Should the current decision be stated as a deliberate deferral rather than as selection of a path?
Identifying the Accepted Downside
Identifying the Concrete Cost Created by a Choice
- What disadvantage, sacrifice, or limitation follows directly from choosing this option?
- What will the organization have less of, pay more for, delay, constrain, or make harder?
- Does this cost arise specifically from the chosen path rather than from the situation generally?
- Who or what part of the organization will actually bear the cost?
- Is the cost temporary, recurring, or effectively permanent?
- Would the meaningful rejected alternative avoid or materially reduce it?
- What is the clearest concrete downside the organization is accepting in exchange for the benefit of the choice?
Separating Accepted Downsides From General Risks
- Which negative effects are expected consequences of the choice rather than uncertain possibilities?
- What adverse event could occur but is not inherent in the decision itself?
- Has the supposed downside been treated as certain, likely, or merely possible?
- Would the decision still create this disadvantage even if every identified risk were successfully managed?
- Which risks require mitigation rather than acceptance as part of the tradeoff?
- Are people calling something an accepted downside simply because it appeared on a risk register?
- What known disadvantage should be separated from the uncertain risks surrounding the decision?
- What negative outcome is being attributed to the decision?
- What causal connection links that outcome to the chosen path?
- Could the same outcome have occurred regardless of which option was selected?
- Did another event, later decision, or execution failure contribute materially to the outcome?
- Was the outcome foreseeable from the decision when it was made?
- Are we using hindsight to convert every subsequent problem into a downside of the original choice?
- Which negative consequence genuinely belongs to the tradeoff created by this decision?
Testing Whether the Downside Actually Follows From the Choice
- What mechanism causes the claimed downside to result from this option?
- Would the downside still occur if another viable alternative were chosen?
- Does the decision create the disadvantage directly or only make it more likely?
- What assumptions connect the choice to the claimed cost?
- Is there evidence that the downside is inherent enough to treat as part of the decision tradeoff?
- Could implementation choices eliminate the downside without changing the underlying decision?
- What downside remains once effects that are avoidable, uncertain, or unrelated are removed?
Checking Whether the Same Downside Exists Under the Rejected Alternative
- Would the rejected alternative create the same disadvantage?
- If so, would it create it to the same degree, duration, or for the same people?
- What part of the downside is genuinely incremental to the chosen option?
- Are we attributing a cost to the decision that actually comes from the wider situation?
- Does another alternative shift the downside rather than eliminate it?
- How does comparing the options change the significance of the stated downside?
- What disadvantage best captures what is specifically being sacrificed by choosing this path?
Selecting the Primary Downside Among Several Costs
- What material downsides does the chosen option create?
- Which one most clearly represents the tradeoff being made for the primary benefit?
- Which downside would most seriously weaken the decision if it became worse than expected?
- Who bears each downside, and does that affect which one is most significant?
- Are some costs implementation burdens rather than consequences of the choice itself?
- What important secondary downsides should remain visible even if one is treated as primary?
- Which downside should be named first to give an accurate picture of what the organization is accepting?
Surfacing Downsides Hidden Inside Assumptions
- Which assumptions make the chosen option appear less costly or difficult than it may actually be?
- What disadvantage emerges if a favorable assumption proves false?
- Are assumed resources, stakeholder behavior, or future capabilities masking a real sacrifice?
- Does the decision depend on mitigation working exactly as expected to keep the downside tolerable?
- What cost has been shifted to another team, future period, or external party without being recognized?
- Which downside becomes visible when the assumptions are stated explicitly?
- Does that newly visible downside change the tradeoff that was supposedly accepted?
Replacing Abstract Downside Language With Concrete Consequences
- What does the current downside language mean in practical terms?
- Who experiences the consequence and what changes for them?
- What becomes slower, more expensive, less flexible, less capable, or otherwise worse?
- Over what scope and time period will the consequence occur?
- Are terms such as "complexity", "friction", or "reduced flexibility" hiding materially different effects?
- Could affected people recognize when this downside has actually materialized?
- How can the downside be stated concretely enough for someone to decide whether it is acceptable?
Testing Whether Anyone Is Willing to Accept the Stated Downside
- Who is expected to bear the downside?
- Who has authority to accept that consequence for the affected scope?
- Was the downside actually visible when the decision was made?
- Did the relevant decision owner explicitly or implicitly accept it as part of the tradeoff?
- Are people saying the downside is acceptable because they expect somebody else to absorb it?
- What happens if the downside materializes exactly as currently described?
- Would the authorized decision-maker still stand behind the choice under those conditions?
Revising Decisions When the Real Downside Differs From the Stated One
- What downside was originally understood and accepted?
- What disadvantage has actually emerged or is now expected?
- How does the real downside differ in magnitude, duration, distribution, or kind?
- Would the original decision still have been made if this downside had been understood correctly?
- Can the new downside be mitigated without changing the underlying commitment?
- Has the tradeoff changed enough to require explicit reconsideration?
- What part of the decision should be revised if the original accepted downside no longer describes reality?
Clarifying Decision Ownership and Authority
Identifying the Decision Owner or Decision-Making Body
- What specific choice needs an identifiable owner or decision-making body?
- Who can legitimately close that choice for the scope affected?
- Is the authority held by one person, a board, a committee, a vote, or another defined mechanism?
- What evidence shows that this person or body actually owns the decision?
- Does the authority cover the full organizational scope of the commitment?
- Are other participants being mistaken for owners because they are more visible or influential?
- Who or what body should be named as the source of the final commitment?
Separating Decision Ownership From Participation and Advice
- Who is participating in the decision without having final authority?
- Who provides expertise, recommendation, challenge, or consultation?
- Which participants must be heard but do not have a veto?
- Is anyone's strong influence being mistaken for formal ownership?
- What does each person's involvement actually allow them to decide?
- Could the decision still be made if one adviser disagreed?
- Who ultimately converts the participants' input into a binding choice?
Separating Decision Ownership From Execution Ownership
- Who owns the decision itself?
- Who is responsible for carrying the decision out?
- Does the execution owner have authority to change the underlying commitment?
- Is the decision owner being assumed to manage implementation simply because they made the choice?
- Is an executor being forced to make substantive choices that the decision owner never settled?
- What escalation is required when execution reveals a need to change the commitment?
- How should decision ownership and execution responsibility be stated so neither is mistaken for the other?
Checking Whether the Named Owner Has Authority to Commit
- What organizational scope does the named owner actually have authority over?
- What policy, delegation, role mandate, governance rule, or established practice supports that authority?
- Are there financial, legal, geographic, functional, or other limits on it?
- Does the decision commit people, resources, or obligations outside the owner's remit?
- Is another person's approval or consent required before the commitment becomes valid?
- Are people relying on seniority or job title instead of actual decision rights?
- What part of the decision, if any, exceeds the named owner's authority?
Identifying Shared Ownership That Leaves No Single Decision Owner
- What does "shared ownership" mean in this case?
- How does the group actually convert differing views into one binding commitment?
- Must everyone agree, does a majority decide, or does one member have final authority?
- What happens if the supposed co-owners disagree?
- Does each person own the whole decision or only a distinct part of it?
- Is shared ownership concealing the absence of a real closure mechanism?
- What decision rule or separation of ownership is needed before the choice can be relied on?
Identifying Responsibility Without Sufficient Authority
- What outcome is this person or team being held responsible for?
- Which decisions materially determine whether they can deliver that outcome?
- Which of those decisions can they actually make?
- What resources, scope changes, priorities, or tradeoffs require someone else's approval?
- Are delays or failures being attributed to execution when necessary authority sits elsewhere?
- Is there an effective escalation path for decisions outside their authority?
- What authority or decision ownership needs to change for the assigned responsibility to be workable?
Identifying Authority Without Clear Responsibility
- What decisions can this person or body make?
- Who remains responsible for the consequences of those choices?
- Can the authority holder intervene without owning the resulting impact?
- Are executors accountable for outcomes they could not influence?
- Does the authority holder have any obligation to monitor, revisit, or defend the decision after it is made?
- Is formal decision power separated from accountability in a deliberate and workable way?
- What responsibility needs to be clarified around the exercise of this authority?
Clarifying Decision Ownership in Cross-Functional Work
- What distinct choices cut across the functions involved?
- Which function or role has legitimate authority over each one?
- Where does one function's authority stop and another's begin?
- Are consultation rights or specialist approvals being mistaken for ownership of the whole decision?
- Which parts require genuine joint governance rather than one function deciding for others?
- What happens if two legitimate authorities make incompatible choices?
- How should the decision structure be divided so each cross-functional commitment has a clear and legitimate owner?
Determining Whether a Multi-Owner Decision Contains Several Decisions
- What part of the supposed decision does each owner actually control?
- Could those parts be decided differently without making the others impossible?
- Do the owners have different authority, scope, tradeoffs, or conditions?
- Is one collective choice really a sequence of separate commitments?
- Would splitting the decision reduce conflict about who can decide what?
- What dependencies would need to remain visible after separation?
- Is genuine joint ownership still necessary once the distinct choices are made explicit?
Recognizing When No Legitimate Decision Owner Exists
- What choice needs to be made?
- Who appears to own it now, and what authority do they actually have?
- Does the decision cross organizational boundaries that no single role can legitimately commit?
- Has responsibility been assigned without creating corresponding decision authority?
- Is everyone waiting for someone else because the governance structure has no clear owner?
- Can the decision be split into smaller choices that existing authorities can legitimately make?
- What governance or delegation decision is required before the original choice can be made legitimately?
Surfacing Hidden Assumptions and Undecided Dependencies
Identifying Assumptions a Decision Depends On
- What must be true for this decision to work as intended?
- Which of those conditions are confirmed facts and which are assumptions?
- Which assumption would most materially affect the commitment if it proved false?
- Are any assumptions carrying part of the scope, benefit, downside, or feasibility of the choice?
- What evidence supports the most important assumptions?
- Which assumptions should be tested or monitored rather than simply accepted?
- Does any assumption conceal a choice that someone still needs to make?
Making Hidden Prerequisites Explicit
- What has to exist or happen before this decision can take effect?
- Which prerequisites are external conditions and which require deliberate action?
- Who is responsible for establishing each prerequisite?
- Has anyone actually committed the resources, approvals, or capabilities required?
- What happens to the decision if a prerequisite is not met?
- Are people already proceeding as though all prerequisites were guaranteed?
- Which prerequisites need to be stated explicitly as conditions of the commitment?
Tracing Decisions That Depend on Other Unresolved Decisions
- What other decision must be resolved for this commitment to operate as intended?
- Who owns that dependent choice?
- What materially different outcomes could that unresolved decision produce?
- Would all of those outcomes leave the current decision intact?
- Is one future outcome already being assumed in current planning?
- What work can safely proceed before the dependent decision is made?
- Should the current decision remain conditional until the dependency is resolved?
Clarifying Commitments That Depend on Future Explanation
- What part of the commitment is expected to be explained later?
- Does later explanation merely add context, or will it determine what people are actually required to do?
- Could different explanations materially change scope, exceptions, or responsibilities?
- Are downstream teams able to act correctly before the explanation exists?
- Who has authority to issue the later interpretation?
- Is "we will explain it later" concealing a choice that has not yet been made?
- What needs to be decided now so future explanation does not become an informal decision process?
Identifying Dependencies on Future Governance or Approval
- What future governance decision or approval does the current commitment depend on?
- Is that future step a genuine condition or being treated as a guaranteed formality?
- Who has authority to give the approval or establish the governance arrangement?
- What different outcomes could that future decision produce?
- Would an unfavorable outcome invalidate, narrow, or delay the current commitment?
- Are people already making irreversible commitments before the future authority has acted?
- How should the current decision be qualified until the governance or approval dependency is resolved?
Checking Assumed Availability of Resources or Capability
- What people, money, systems, skills, capacity, or facilities does the decision require?
- Which of those resources are actually committed?
- Which are merely expected to become available?
- Who controls each unconfirmed resource or capability?
- Would the decision remain viable if availability were lower or later than assumed?
- Is an unresolved resource allocation being treated as an implementation detail?
- What resource commitment needs confirmation before the decision can be relied on?
Surfacing Assumed Behavior From Other Teams or Stakeholders
- What does the decision assume another team or stakeholder will do?
- Have they explicitly committed to doing it?
- Did the person making that commitment have authority over the required behavior or resource?
- What incentives, responsibilities, or constraints might make the assumed behavior unrealistic?
- When must their contribution occur for the decision to work?
- What happens if they act differently from what is assumed?
- Is their cooperation an operational dependency or another unresolved decision that needs explicit ownership?
Clarifying Cross-Functional Dependencies That Remain Undecided
- What cross-functional dependency is essential to the decision?
- Which function controls the unresolved part?
- What specific choice still needs to be made across the organizational boundary?
- Are both sides assuming different outcomes without realizing it?
- What part of execution cannot proceed until the dependency is settled?
- Does the current decision overstate how much has actually been committed across functions?
- What separate decision or agreement is needed to resolve the dependency explicitly?
Identifying Where Interpretation Is Carrying Part of the Commitment
- What must people infer because the decision does not state it directly?
- Are different teams filling the gap in different ways?
- Does the missing interpretation affect scope, obligations, exceptions, or tradeoffs?
- Could someone follow the written decision faithfully while reaching a materially different conclusion?
- Are original participants relying on shared verbal context that newer participants do not have?
- Is the required interpretation ordinary implementation judgment or a substantive decision left unstated?
- What should be made explicit so the commitment no longer depends on unwritten interpretation?
Identifying Where Future Follow-Up Is Standing In for a Decision
- What issue has been deferred to follow-up?
- Would different answers materially change the commitment?
- Is execution already assuming one answer before the follow-up occurs?
- Who is supposed to resolve the deferred choice, and by when?
- Has the same issue been postponed repeatedly as though it were merely detail?
- Could work continue safely without prejudging the deferred choice?
- Should the issue be recognized as an unresolved decision rather than another follow-up item?
Challenging Decisions Against Constraints and Reality
Checking Whether a Decision Fits Available Authority
- What authority is required to make this commitment valid?
- Does the identified owner or decision-making body possess that authority?
- Which part of the decision reaches beyond their organizational, financial, legal, or functional remit?
- Are other parties being committed without their own legitimate authority acting?
- Could the decision be narrowed to fit the authority that actually exists?
- Is another approval or decision required before the broader commitment can stand?
- What is the largest version of this decision that can legitimately be made now?
Stress-Testing a Decision Against Budget and Resources
- What budget, people, capacity, systems, and skills does the decision require?
- Which of those resources are actually committed rather than assumed?
- What happens if available resources are materially lower than expected?
- Does the decision still make sense if delivery takes longer or costs more?
- Which resource constraint would force a narrower or different commitment?
- Are competing decisions already claiming the same scarce resources?
- What part of the decision survives under the resources the organization can realistically provide?
Comparing a Decision With Operational Reality
- What would the organization actually have to do differently to implement this decision?
- Which existing processes, responsibilities, interfaces, or constraints conflict with it?
- Does the operating model possess the capability the decision assumes?
- What current behavior would have to stop for the commitment to become real?
- Are informal workarounds already revealing that the stated decision does not fit practice?
- Which difficulties are manageable execution problems and which undermine the decision itself?
- What needs to change in the decision if operational reality cannot support it as written?
Checking Whether Timing Makes the Decision Viable
- What must happen before this decision can take effect?
- Which dependencies control the earliest realistic timing?
- Are any external deadlines genuinely fixed?
- What capability, approval, or resource cannot be available by the stated date?
- What becomes irreversible if work begins before the necessary conditions are ready?
- Would changing the timing preserve the decision or alter its substantive tradeoff?
- What timing commitment is actually viable given the sequence of work and dependencies?
Testing a Decision Against External Obligations
- What laws, regulations, contracts, standards, policies, or external commitments constrain this decision?
- Which of those obligations genuinely bind the scope involved?
- Does any part of the decision conflict directly with an existing obligation?
- Could compliance be achieved through implementation, or would the decision itself need to change?
- Are supposed obligations actually internal preferences being treated as fixed constraints?
- Who is qualified or authorized to determine whether the conflict is real?
- What part of the commitment remains viable once the binding obligations are applied?
Testing Critical Dependencies Behind a Decision
- Which dependency could most seriously undermine the decision if it fails?
- Who controls that dependency?
- How secure is the required contribution, approval, capability, or event?
- What happens if it arrives late, changes, or does not occur?
- Does the decision contain a fallback, or is one branch being silently assumed?
- Would dependency failure require implementation adjustment or a new decision?
- Is the commitment robust enough to stand given the uncertainty around its critical dependencies?
Examining Conflicts With Existing Incentives and Responsibilities
- What behavior does the decision require from the people affected?
- How does that behavior align with their current incentives and responsibilities?
- Are people being asked to sacrifice outcomes for which they remain accountable?
- Could existing rewards or performance measures encourage behavior that undermines the decision?
- Does anyone face conflicting obligations that cannot simply be managed through better communication?
- Which conflicts make execution harder and which make the commitment structurally unrealistic?
- What must change in the decision, incentives, or responsibilities for the expected behavior to be credible?
Testing a Decision Against Known Political Constraints
- Which stakeholders have enough influence to materially affect whether this decision can operate?
- What interests or commitments make the decision difficult for them to support?
- Are these political constraints binding, negotiable, or simply sources of resistance?
- Does implementation depend on cooperation from someone who has not committed to provide it?
- Which part of the decision is vulnerable to informal veto or later reversal?
- Would a narrower or differently sequenced commitment preserve the core choice without ignoring political reality?
- What political difficulty changes the viability of the decision rather than merely making execution uncomfortable?
Testing Whether the Accepted Downside Is Actually Tolerable
- What downside has the decision supposedly accepted?
- Who will bear it, and for how long?
- What level of that downside was actually understood when the choice was made?
- At what point would the disadvantage become unacceptable?
- Does the person or body accepting it have authority over the affected scope?
- Is the decision relying on mitigation to make an otherwise unacceptable downside tolerable?
- If the downside occurs exactly as described, would the organization still stand behind the decision?
Subjecting the Decision to Skeptical Review
- What is the strongest evidence-based argument that this decision will not work as intended?
- Which assumption is most vulnerable to being wrong?
- What fact or constraint may have been minimized because it weakens the preferred option?
- What would a knowledgeable critic say the decision fails to account for?
- Which plausible failure scenario would most seriously challenge the commitment?
- What evidence would cause us to narrow, change, or reject the decision?
- After serious challenge, what part of the decision still stands confidently and what part needs revision?
Correcting, Narrowing, or Rejecting Candidate Decisions
Correcting Candidate Decisions That Misstate the Commitment
- What does the candidate claim was decided?
- What does the strongest available evidence actually support?
- Is the problem in scope, status, actor, timing, condition, or wording?
- Does an identifiable underlying commitment remain once the error is removed?
- What part of the candidate is stronger or different from what was actually chosen?
- Can the candidate be corrected without creating a new decision?
- What wording most accurately represents the real commitment?
Narrowing Decisions That Claim More Than Was Chosen
- What part of the candidate extends beyond the evidence of commitment?
- Which organizational, geographic, temporal, product, or functional scope was actually chosen?
- Does the candidate turn a pilot, phase, or local decision into a broader commitment?
- What narrower version remains fully supported?
- Would narrowing preserve the substantive choice while removing overclaim?
- Are downstream actors already relying on the broader interpretation?
- What is the smallest complete decision that reflects what was genuinely chosen?
Removing Unsupported Content From Candidate Decisions
- Which elements of the candidate lack identifiable support?
- Are unsupported benefits, alternatives, downsides, conditions, or rationale being presented as though they were part of the decision?
- Does removing them change the core commitment?
- Are any elements being included simply because a complete decision template appears to require them?
- What information should remain explicitly unknown rather than be filled in?
- Does the remaining candidate still make sense as an actual decision?
- What should be removed so clarity does not exceed the evidence?
Revising Rejected Alternatives After Challenge
- What alternative was originally reconstructed as rejected?
- Does the evidence show that it was genuinely available and actually closed?
- Was only part of the alternative rejected?
- Did challenge reveal that another alternative better represents the path the decision displaced?
- Are exceptions or side agreements keeping the supposedly rejected option alive?
- Would correcting the alternative materially change the understood tradeoff?
- What rejected alternative can now be stated without overclaiming what was closed?
Revising Accepted Downsides After Challenge
- What downside was originally attributed to the decision?
- Does that downside genuinely follow from the chosen path?
- Would the rejected alternative have created the same disadvantage?
- Was the downside actually known and accepted when the decision was made?
- Has challenge revealed a more material downside that was previously hidden?
- Does the new downside remain tolerable to the authorized decision owner?
- How should the accepted downside be revised so it reflects the real tradeoff?
Replacing Overbroad Candidates With Smaller Real Commitments
- What smaller commitment is clearly supported inside the overbroad candidate?
- Which parts fail because of evidence, authority, resources, or unresolved choices?
- Can those unsupported parts be removed without destroying the core decision?
- Does the smaller commitment have a legitimate owner and workable scope?
- What remains deliberately open after narrowing?
- Would the reduced commitment still justify the work currently relying on it?
- What smaller decision should replace the broader candidate as the authoritative statement?
Rejecting Candidate Decisions That No One Will Own
- Who would need to own this candidate for it to be a real organizational commitment?
- Does any person or decision-making body actually accept that ownership?
- Is the candidate assigning responsibility to someone without authority?
- Is "shared ownership" concealing the absence of a real closure mechanism?
- Could the candidate be split into smaller decisions with legitimate owners?
- Is the lack of ownership an evidence gap or evidence that no commitment exists?
- Should the candidate be rejected until a legitimate owner or decision mechanism exists?
Rejecting Candidate Decisions That Depend on Unresolved Choices
- What unresolved choice does the candidate assume has already been settled?
- Would different answers to that choice materially change the candidate?
- Who owns the unresolved decision?
- Is current work already prejudging one outcome?
- Could the candidate be made legitimately conditional instead of pretending the dependency is resolved?
- Does any meaningful commitment remain once the unresolved choice is separated?
- Should the candidate be rejected because the core choice itself is not yet closed?
Reclassifying Candidates That Are Still Open Questions
- What choice does the candidate appear to claim has been made?
- What evidence shows that multiple answers remain live?
- Is the current statement actually a proposal, recommendation, preference, assumption, or question?
- Who still needs to decide among the remaining options?
- Are people acting as though a favored answer were already settled?
- What would have to happen before this could legitimately become a decision?
- How should the candidate be reclassified so its unresolved status is clear?
Concluding That No Decision Exists Yet
- What decision would need to exist for the current work to have a clear commitment basis?
- What evidence shows that the relevant choice remains open?
- Has the authorized owner explicitly deferred or declined to decide?
- Are multiple alternatives still genuinely under consideration?
- Is the apparent decision only an inference from activity, preference, or momentum?
- Could a historical decision have existed even though the available evidence cannot establish it reliably?
- Is the defensible conclusion that no decision has yet been made, or only that no reliable decision can currently be reconstructed?
Checking Decisions for Internal Consistency
Identifying Direct Contradictions Between Decisions
- Which active decisions make commitments about the same underlying issue?
- Can all of those commitments be true or followed at the same time?
- What specific actions, boundaries, or obligations conflict?
- Do the apparent contradictions apply to the same scope and time period?
- Could one decision have superseded another without that change being recorded?
- Which decision has current authority if the conflict cannot be reconciled?
- What needs to be changed or superseded so the active decision set no longer contains incompatible commitments?
Identifying Decisions That Assign Incompatible Responsibilities
- What responsibilities does each decision assign?
- Are the same people or teams expected to fulfill commitments that conflict with one another?
- Does one responsibility prevent another from being carried out as required?
- Are different decisions assigning control and accountability for the same work to different owners?
- Could the conflict be resolved through execution, or does one of the underlying commitments need to change?
- Which authority established each responsibility?
- What explicit decision is needed to remove the incompatible assignment?
Finding Dependencies on Options Rejected Elsewhere
- Which active decision depends on a method, capability, structure, or option rejected by another decision?
- What exactly was closed by the earlier rejection?
- Is the current dependency genuinely incompatible with that rejection or only superficially similar?
- Has an exception or later decision legitimately reopened part of the option?
- Are people relying on the rejected option without realizing the conflict?
- What would break if the rejection were enforced exactly as originally decided?
- Which decision needs clarification, modification, or replacement to restore consistency?
Comparing Scope Boundaries Across Decisions
- What scope does each relevant decision claim to cover?
- Where do those scopes overlap?
- Do overlapping decisions impose different commitments on the same people, systems, products, or activities?
- Are gaps between scopes leaving important work without a clear decision basis?
- Do terms that sound similar actually refer to different boundaries?
- Has a later scope change made an earlier decision inaccurate?
- What scope relationship needs to be made explicit so the decisions can coexist coherently?
Checking Ownership and Authority Across the Decision Set
- Who owns each related decision?
- Do any decisions assign overlapping authority over the same choice?
- Is someone being committed by a decision made outside the decision-maker's legitimate scope?
- Do different decisions rely on inconsistent assumptions about who can approve, change, or override what?
- Are decision rights aligned with the responsibilities created by the set?
- What happens when two legitimate authorities reach incompatible decisions?
- What ownership or governance change is needed to make authority across the set coherent?
Identifying Competing Commitments for the Same Resources
- Which decisions depend on the same scarce people, budget, capacity, systems, or management attention?
- How much of each resource has actually been committed?
- Can all active decisions be fulfilled simultaneously with the resources available?
- Are different decisions relying on the same resource without recognizing the competing claim?
- Which commitments have priority if the resource cannot satisfy all of them?
- Would additional resources solve the conflict, or does the decision set itself need to change?
- What explicit choice is required to resolve the competition between commitments?
Tracing Rejected Alternatives That Reappear Elsewhere
- What alternative was previously rejected?
- Where does that alternative reappear in another decision, plan, exception, or assumption?
- Is it being reintroduced intentionally or only through downstream implementation?
- Does the later use fall outside the scope of the original rejection?
- Who authorized the reintroduction, if anyone?
- Does allowing it undermine the benefit or tradeoff of the original decision?
- Should the later decision be changed, or should the earlier rejection be explicitly reconsidered?
Checking Accepted Downsides Against Other Commitments
- What downside has one decision explicitly accepted?
- Which other commitments assume that downside will not occur or must be prevented?
- Can both commitments remain valid if the accepted downside materializes?
- Are different teams being held to expectations that contradict the tradeoff already chosen?
- Has the downside changed in magnitude since the other commitment was made?
- Does one decision need to acknowledge or absorb the consequence accepted elsewhere?
- What change would make the commitments compatible with the tradeoffs the organization has actually chosen?
Assessing Which Decisions Break When Another Changes
- Which decisions depend directly on the decision that is changing?
- What assumptions, scope boundaries, responsibilities, or rejected alternatives were built around it?
- Which dependent decisions remain valid under the new commitment?
- Which become inconsistent, infeasible, or meaningless?
- Are any downstream decisions still relying on the superseded version?
- What needs to be reviewed before the changed decision becomes the new active basis?
- Which dependent decisions must be confirmed, revised, or replaced as part of the change?
Surfacing Contradictions Hidden Behind Different Terminology
- Which different terms may refer to the same underlying role, system, scope, or activity?
- What does each decision actually require beneath the terminology it uses?
- Do apparently different concepts create conflicting commitments in practice?
- Are identical terms being used with different meanings in different decisions?
- What real-world object or behavior should the decisions be compared against?
- Would people implementing both decisions encounter an actual conflict despite the different wording?
- What terminology or commitment needs clarification so the contradiction becomes explicit and resolvable?
Checking Whether the Decision Set Is Complete Enough
Identifying Decisions an Upcoming Commitment Depends On
- What commitment is the organization about to make?
- Which choices must already be settled for that commitment to be responsible?
- Which of those decisions can be identified explicitly?
- What is still being assumed rather than decided?
- Which unresolved choice could materially change the commitment after it is made?
- What can safely remain open until later?
- Which decisions must be confirmed before the upcoming commitment proceeds?
Finding Fundamental Decisions That Are Still Missing
- What major part of the work lacks a clear commitment basis?
- What choice are people repeatedly having to make for themselves?
- Which missing decision affects multiple downstream plans or teams?
- Has the issue been left open deliberately or simply overlooked?
- Who has authority to close the missing choice?
- What work is currently compensating for the absence of that decision?
- Which missing decision would most materially strengthen the overall decision basis?
Surfacing Deferred Choices That Execution Already Depends On
- What choice has officially been deferred?
- What current work nevertheless depends on one particular answer?
- Are teams already selecting provisional branches that could become difficult to reverse?
- Who owns the deferred decision, and when is it supposed to be made?
- What rework would occur if the eventual choice differs from the assumption being used now?
- Can dependent work remain neutral until the choice is resolved?
- Should the decision be made now, or should the dependent work be explicitly limited until it can be?
Checking Decision Coverage Across Several Workstreams
- What decisions does each workstream rely on?
- Which commitments need to be shared across several workstreams?
- Are different workstreams making their own versions of the same underlying decision?
- Where do gaps between workstreams leave ownership, scope, or interfaces undecided?
- Are any cross-workstream dependencies based only on assumptions?
- Which local decisions could create conflicts for the wider effort?
- What additional decision coverage is needed so the workstreams can proceed on a coherent basis?
Testing Whether a Detailed Plan Rests on a Complete Decision Basis
- Which substantive choices does the plan assume are already settled?
- Can each of those choices be traced to an actual decision?
- Are detailed tasks masking unresolved questions about scope, ownership, timing, or approach?
- Which parts of the plan would change materially if an open decision went another way?
- Are teams mistaking planning detail for evidence that the underlying choices have been made?
- What planning can proceed safely despite remaining open decisions?
- Is the decision basis complete enough to justify the level of detail and commitment in the plan?
Identifying Missing Decisions Required for a Primary Choice to Operate
- What additional choices must be settled for the primary decision to work in practice?
- Which of those choices determine essential scope, ownership, resources, interfaces, or conditions?
- Are they genuine subordinate decisions or ordinary implementation details?
- Who owns each missing choice?
- Can the primary decision operate meaningfully before they are resolved?
- Is current execution silently deciding them by default?
- Which subordinate decisions need explicit closure before the primary choice can function as intended?
Separating Missing Decisions From Ordinary Implementation Details
- What unresolved issue is currently being treated as a possible missing decision?
- Would different answers materially change the underlying commitment?
- Does the issue affect scope, authority, tradeoffs, dependencies, or what others may rely on?
- Can competent executors resolve it within the authority already delegated to them?
- Would resolving it one way or another require reopening the original decision?
- Is the issue simply about how to implement a settled choice?
- Should it remain with execution, or does it require an explicit decision?
Finding Decision Gaps Created by Changes in Scope or Responsibility
- What scope or responsibility has changed?
- Which earlier decisions were built around the previous arrangement?
- What new choices does the changed boundary create?
- Are existing owners still authorized to make decisions for the new scope?
- Has work moved to a team that lacks a clear decision basis for it?
- Which responsibilities or interfaces now fall between existing decisions?
- What new or revised decisions are required to close the gaps created by the change?
Checking Whether Irreversible Consequences Have an Explicit Decision Basis
- What consequence is about to become difficult or costly to reverse?
- Which decision explicitly authorizes crossing that point?
- Does the decision cover the full scope of what will become committed?
- What assumptions or unresolved dependencies still affect the consequence?
- Who has authority to accept the loss of flexibility involved?
- Are people relying on momentum or execution rather than an explicit decision?
- Is the decision basis strong enough to justify making the consequence irreversible?
Determining Whether the Decision Set Is Sufficient to Proceed
- Proceed to what specific next commitment or stage?
- Which decisions does that step materially depend on?
- Are those decisions clear, compatible, and owned by legitimate authorities?
- Which open issues can genuinely remain open without changing the commitment?
- Would downstream actors have to invent any substantive choices themselves?
- What uncertainty or dependency could still invalidate the basis for proceeding?
- Is there enough closure for this next step without pretending that every future decision has already been made?
Testing Whether Decisions Can Carry Commitment
Reviewing Decisions Before Contract Signature
- What commitments will become legally or commercially binding once the contract is signed?
- Which internal decisions support those commitments?
- Are scope, requirements, responsibilities, and material conditions clear enough to survive the contract?
- Who has authority to make the underlying business decisions and to sign the agreement?
- Which dependencies or approvals are still being assumed?
- Does the contract introduce choices that were never explicitly decided internally?
- Is the decision basis strong enough to justify creating the external obligation?
Reviewing Decisions Before Budget Release
- What exactly is the released budget authorizing?
- Which decisions establish the scope and purpose of the spend?
- Are the expected benefit and accepted downside clear enough to justify the commitment of funds?
- What resources or later decisions does the funded work still depend on?
- Could the budget release unintentionally lock the organization into one path before that path is decided?
- Who has authority both to approve the spend and to make the substantive choices it depends on?
- Is the decision basis stable enough for the money to be committed now?
Checking Decision Clarity Before Scope Freeze
- What boundaries are about to become difficult to change?
- Are inclusion and exclusion decisions explicit?
- Do all affected teams interpret those boundaries the same way?
- Which alternatives or future choices will the freeze close?
- Are unresolved dependencies being hidden inside the frozen scope?
- What later changes would count as genuine scope change rather than clarification?
- Is the decision basis clear enough that the organization can responsibly treat this scope as fixed?
Confirming the Decision Basis Before External Commitment
- What promise, representation, or obligation is about to be made externally?
- Which internal decisions must already be settled to support it?
- Does the person making the external commitment have authority to bind the relevant scope?
- Are resources, capabilities, and dependencies sufficient to make the promise credible?
- What internal uncertainty is being concealed by the external certainty of the commitment?
- What alternatives will become harder to pursue once the promise is made?
- Is the internal decision basis strong enough to justify what the organization is about to tell others they can rely on?
Reviewing Decisions Before Operational Rollout
- What decisions define what is actually being put into operation?
- Are scope, responsibilities, authority, and operating conditions sufficiently clear?
- Has the organization confirmed that the chosen model can work under real operational conditions?
- Which assumptions or dependencies remain critical at the point of rollout?
- What fallback or reversion options exist if operation reveals a material problem?
- Are teams prepared to distinguish implementation issues from reasons to reopen the decision?
- Is the decision basis mature enough for the organization to rely on the new operating state?
- What responsibility is being transferred?
- What authority accompanies it?
- Does the receiving party understand the decisions that define the responsibility?
- Are resources, obligations, interfaces, and unresolved risks visible?
- Is anything being transferred that the receiving party cannot legitimately control?
- What decisions remain with the previous owner despite the transfer?
- Is the decision basis clear enough that accountability will not become ambiguous after the handover?
Reviewing Decisions Before Dependent Teams Begin Irreversible Work
- Which decision is the dependent team about to rely on?
- What work will become difficult or costly to undo?
- Is the underlying commitment explicit enough for another team to rely on without reinterpretation?
- Which assumptions or dependencies could still change the required direction?
- Has the dependent team confirmed that it interprets the decision as intended?
- What would happen if the decision changed after this work began?
- Is the decision stable enough to justify transferring the cost of irreversibility to another team?
Testing Decisions Before Reversal Becomes Politically Difficult
- What will make reversal politically or organizationally harder after this point?
- Who will become publicly, professionally, or institutionally committed to the choice?
- Is the decision basis strong enough to justify creating that commitment?
- Which uncertainties or disagreements remain unresolved before positions harden?
- Are people treating political momentum as evidence that the decision itself is sound?
- What information would still justify reconsideration before reversal becomes costly?
- Should the organization proceed, narrow the commitment, or preserve more room to change?
Testing Whether Decisions Stand Without Verbal Context
- Can someone who was not present for the original discussion determine what was decided?
- What essential meaning currently exists only in participants' memories?
- Are scope, conditions, exclusions, and ownership clear from the authoritative record?
- Could two competent readers derive materially different commitments from it?
- Which contextual information is useful for understanding why the decision was made but not necessary to know what it is?
- Are new participants repeatedly dependent on original participants to explain what was "really meant"?
- What needs to be made explicit so the commitment stands without verbal reconstruction?
Determining Whether the Decision Basis Is Stable Enough to Rely On
- What parts of the decision are settled and what remains conditional?
- Which uncertainties could still materially change the commitment?
- Are the assumptions most likely to trigger reconsideration visible?
- Would plausible changes in surrounding facts leave the core decision intact?
- Do dependent teams know which parts they can safely rely on now?
- Is there a clear trigger and mechanism for explicit change if conditions move beyond the current basis?
- Is the decision stable enough for the next consequence without requiring false certainty?
Distinguishing Decision Problems From Execution Problems
Distinguishing Missing Decisions From Delivery Problems
- What decision would execution have needed in order to proceed correctly?
- Did that decision actually exist before the delivery problem appeared?
- Were executors forced to make a substantive choice that should have been settled earlier?
- Could the same delivery failure have occurred even with a complete decision basis?
- Were responsibilities, resources, or plans clear enough after the decision was made?
- Is the current problem caused by absence of commitment or failure to carry out an existing one?
- What needs fixing first: the decision basis or the delivery mechanism?
Tracing Rework Back to Decision Ambiguity
- What work had to be redone?
- Which earlier interpretation or assumption led to the original work?
- Could the decision reasonably have supported more than one interpretation?
- Did different teams act consistently with different readings of the same commitment?
- Was the ambiguity present from the beginning or introduced by later documents or plans?
- Would clearer execution planning have prevented the rework without changing the decision?
- What specific ambiguity, if any, should be corrected to prevent the same rework recurring?
Separating Conflicting Interpretations From Failure to Follow a Clear Decision
- What does each party say the decision requires?
- What does the authoritative decision record actually say?
- Are both interpretations genuinely plausible from the wording?
- Did one party have access to clarification or context that the other did not?
- Is someone knowingly departing from a clear commitment rather than misunderstanding it?
- Would rewriting the decision materially change what the parties are expected to do?
- Is the appropriate response clarification, explicit change, or enforcement of the existing decision?
Distinguishing Scope Ambiguity From Ordinary Scope Change
- What scope was originally decided?
- Can the original boundary be established clearly from the decision record?
- What is now being treated as newly included, excluded, or uncertain?
- Could that issue reasonably have been interpreted either way from the beginning?
- Did circumstances or requirements change after the original decision?
- Has an authorized person explicitly approved a new boundary?
- Is the current issue clarification of an ambiguous scope or a genuine change that should be recorded as a new decision?
Separating Missing Decision Ownership From Execution Responsibility Problems
- Who was supposed to own the underlying decision?
- Who was responsible for executing it?
- Did the executor have a clear and legitimate commitment to act on?
- Were they forced to decide issues outside their authority?
- Is the current failure caused by nobody owning the decision or by weak execution after a valid decision was made?
- Would clearer task ownership solve the problem without changing decision rights?
- What ownership needs correction: authority over the choice, responsibility for execution, or both?
Distinguishing Decision Dependencies From Operational Coordination Problems
- What dependency is causing the difficulty?
- Does resolving it require another substantive choice or only coordination of an existing commitment?
- Have the relevant teams already committed to what each must provide?
- Is the problem about timing, handoffs, sequencing, or information exchange?
- Could improved coordination solve the issue without anyone making a new decision?
- Is one team assuming an outcome that another team has never decided to provide?
- Should the issue be managed as execution coordination or elevated as an unresolved decision dependency?
Separating Reopened Decisions From Planning Failure
- What issue has returned during execution?
- Are people reconsidering the underlying commitment or only how to deliver it?
- Did the plan fail because it translated the decision poorly?
- Has new information made the original choice genuinely questionable?
- Are implementation difficulties being used as a reason to reopen a decision unnecessarily?
- Would a new plan solve the problem while keeping the commitment intact?
- Does the organization need better planning or an explicit new decision?
Distinguishing Decision Ambiguity From Capability Problems
- What does the decision require people to do?
- Is that requirement clear to the people responsible for carrying it out?
- Do they possess the skills, systems, knowledge, or capacity needed?
- Are different outcomes arising from different interpretations or from inability to execute the same interpretation?
- Would clearer wording materially improve performance?
- Would additional capability solve the problem without changing the decision?
- Is the root problem uncertainty about what was decided or inability to deliver what was clearly decided?
Comparing Weak Decision Basis With Poor Implementation
- What weaknesses existed in the decision basis before execution began?
- What implementation failures occurred independently of those weaknesses?
- Which problems can be causally traced to ambiguity, missing choices, or unrealistic commitments?
- Which problems resulted from planning, coordination, capability, discipline, or resource execution?
- Did implementation compensate for decision weakness or amplify it?
- If execution had been excellent, which problems would still have remained?
- What should be corrected in the decision basis and what should be corrected in execution?
Recognizing Execution Failure Despite a Clear Decision Basis
- Was the decision explicit, coherent, authorized, and sufficiently complete?
- Did the people executing it understand the commitment consistently?
- Were the necessary resources and dependencies reasonably available?
- Where did actual execution depart from the decision or agreed plan?
- What capability, coordination, discipline, or performance problem caused the departure?
- Is anyone blaming decision ambiguity for a failure that occurred despite clear direction?
- What execution problem now needs attention without unnecessarily reopening the underlying decision?
Preserving Decision Integrity During Execution
Referencing Explicit Decisions When Questions Resurface
- Which active decision originally settled the issue now being questioned?
- What exactly does that decision say?
- Does the current question fall inside its scope?
- Has any later decision superseded or modified it?
- Are people reopening the choice or simply asking how to implement it?
- What new information, if any, justifies reconsideration?
- Should the existing decision be reaffirmed, clarified, or explicitly reopened?
Keeping Narrative and Explanation Separate From the Decision
- What part of the material is the actual commitment?
- What part explains the context, reasoning, history, or expected consequences?
- Could later changes to the explanation accidentally be read as changes to the decision?
- Is rationale being used to impose obligations that the decision itself never created?
- Can someone identify the active commitment without reading the entire surrounding narrative?
- Does the explanation still accurately reflect the decision without becoming part of its operative wording?
- What should remain clearly separated so context can evolve without silently changing the commitment?
Preventing Plans and Documents From Quietly Changing Commitments
- What does the authoritative decision currently require?
- Where does the new plan or document describe something materially different?
- Is the difference an implementation detail or a change to scope, timing, ownership, conditions, or tradeoffs?
- Who introduced the difference, and did they have authority to change the commitment?
- Are downstream teams already treating the new wording as authoritative?
- Should the document be corrected, or does the underlying decision now need explicit change?
- How can the authoritative decision remain visible when derivative documents evolve?
Bringing New Participants Back to the Existing Decision Basis
- What active decisions do new participants need in order to understand the work?
- Are they learning those decisions from authoritative records or from current behavior and hearsay?
- Which historical explanations are useful without obscuring the present commitment?
- Are any old or superseded decisions still influencing how newcomers interpret the work?
- What assumptions might new participants reasonably make if the decision basis is not shown explicitly?
- Do they understand what remains open as well as what is settled?
- What decision record should serve as their reference point when questions arise?
Checking Materialized Downsides Against What Was Accepted
- What downside was originally accepted as part of the decision?
- What downside has actually materialized?
- Is it the same type and scale of consequence that was anticipated?
- Who is bearing the downside in practice?
- Has it crossed the threshold the decision owner was willing to tolerate?
- Does the changed downside require mitigation, implementation adjustment, or reconsideration of the decision itself?
- Can the organization still stand behind the original tradeoff as it is now unfolding?
Recognizing Rejected Alternatives Being Quietly Reintroduced
- What alternative did the original decision close?
- Where is that alternative now reappearing in practice?
- Is it returning through exceptions, local workarounds, planning choices, or informal agreements?
- Does the reintroduction fall within a legitimate exception to the original decision?
- Who authorized the return of the rejected approach?
- Is current practice undermining the benefit or tradeoff the original decision was meant to establish?
- Should the behavior stop, or should the decision be explicitly reconsidered?
- What informal agreement has been made alongside the official decision?
- Does it alter scope, responsibility, exceptions, timing, or available alternatives?
- Who made the side agreement, and what authority did they have?
- Is the arrangement simply coordinating implementation within the existing decision?
- Would people following the official decision act differently from people following the side agreement?
- Has the operative commitment already changed in practice even though the formal record has not?
- Should the side agreement be removed, formalized as an exception, or reflected in a new decision?
Tracing Later Disagreement Back to Specific Decisions
- What are people currently disagreeing about?
- Which earlier decision should govern the disputed issue?
- Can the disagreement be traced to a specific wording, boundary, condition, or tradeoff?
- Did the disagreement exist when the decision was made or arise only after circumstances changed?
- Are participants relying on different decisions or different versions of the same decision?
- Has a later plan or interpretation displaced the authoritative commitment?
- What decision needs clarification, reaffirmation, or explicit change to resolve the disagreement?
Maintaining a Reliable Record of Active Decisions
- Where can people determine which decisions currently govern the work?
- Are active, proposed, rejected, and superseded decisions clearly distinguishable?
- Can each active decision be traced to its owner, date, scope, and supporting context?
- Are later changes recorded without rewriting the historical decision?
- Do plans and other documents point back to the authoritative decision rather than becoming competing sources?
- Can someone identify the current commitment without reconstructing it from several inconsistent records?
- What needs to change so the decision record remains a trustworthy source of current truth?
Distinguishing Decision Clarification From Decision Change
- What did the original decision already commit the organization to?
- What does the proposed clarification add or alter?
- Could a reasonable reader have reached the clarified interpretation from the original wording?
- Does the clarification change scope, obligations, ownership, conditions, alternatives, or accepted tradeoffs?
- Would someone acting correctly under the original decision now have to behave differently?
- Is ambiguity being resolved or is a previously open choice being closed?
- Should this be recorded as clarification of the existing decision or as an explicit new decision?
Changing, Reversing, and Replacing Decisions Explicitly
Reassessing Decisions When Facts Change
- What fact has changed since the decision was made?
- Was the original decision materially dependent on the previous fact being true?
- How does the new information affect the expected benefit, feasibility, or tradeoff?
- Would the same decision still be reasonable under the facts now known?
- Can the changed reality be handled through execution without altering the commitment?
- Which part of the existing decision, if any, no longer fits the situation?
- Should the current decision remain in force, be narrowed, or be replaced explicitly?
Reconsidering Decisions After Assumptions Break
- Which assumption supporting the decision has proved false?
- How important was that assumption to the original commitment?
- What part of the decision depended on it being true?
- Does the failed assumption undermine the chosen path, its benefit, or its accepted downside?
- Can the decision still operate under a different assumption without changing what was committed?
- What new evidence or choice is needed before deciding whether to continue?
- Does the broken assumption justify keeping, modifying, or replacing the existing decision?
Revising Decisions When External Constraints Change
- What external constraint has changed?
- Did the previous constraint rule out options that may now be available?
- Does the new constraint make any part of the current decision infeasible or impermissible?
- Which scope, timing, obligations, or alternatives are affected?
- Can the existing commitment be preserved through implementation changes alone?
- What previously rejected alternatives should now be reconsidered?
- What explicit revision is needed so the decision reflects the constraints that now actually apply?
Reconsidering Decisions When Accepted Downsides Become Unacceptable
- What downside did the organization originally agree to accept?
- How does the downside now differ from what was understood at the time?
- Has its magnitude, duration, distribution, or consequence crossed a meaningful threshold?
- Who has authority to decide whether the downside remains tolerable?
- Can mitigation restore the original tradeoff without changing the decision?
- Does the expected benefit still justify accepting the downside as it now exists?
- What new decision is required if the organization is no longer willing to bear that cost?
- How is the organization currently behaving differently from the recorded decision?
- What informal reinterpretation is being used to justify that difference?
- Does the new interpretation merely clarify the original commitment or contradict it?
- Who introduced the reinterpretation, and did they have authority to reverse the decision?
- Is the original decision still being presented as active even though practice has abandoned it?
- What would need to be stated explicitly if the organization genuinely intends to reverse course?
- How should the reversal be recorded so actual practice and the authoritative decision basis match again?
Replacing Existing Decisions With New Commitments
- What existing decision is no longer intended to govern the work?
- What new commitment should replace it?
- What changed enough to justify replacing rather than merely clarifying the previous decision?
- Which parts of the old decision remain valid, if any?
- Who has authority to make the replacement decision?
- When should the new commitment take effect?
- What dependent work or decisions need to be updated once the replacement becomes active?
Narrowing Decisions After Circumstances Change
- What part of the existing commitment is no longer viable or desirable?
- What smaller scope can still be supported under the changed circumstances?
- Does narrowing preserve the core purpose of the original decision?
- Which people, products, locations, activities, or time periods would fall outside the revised commitment?
- What previously accepted benefit or downside changes when the scope is reduced?
- Would anyone currently relying on the broader decision be affected by the narrowing?
- What explicit narrower decision should replace the existing scope?
Identifying Which Previous Decision a New Decision Supersedes
- What earlier commitment governs the same issue as the new decision?
- Does the new decision replace that commitment completely or only within part of its scope?
- Are there several earlier decisions that the new commitment affects?
- From what point should the previous decision stop governing work?
- Which parts of the earlier decision remain active outside the superseded scope?
- Could people reasonably continue relying on the old decision if supersession is not made explicit?
- How should the relationship between the old and new decisions be recorded so the current commitment is unmistakable?
Updating Tradeoffs When Decisions Change
- What concrete benefit justified the previous decision?
- Which meaningful alternative did it reject?
- What downside did the organization knowingly accept?
- Which of those elements has changed enough to support the new decision?
- What benefit does the new commitment now prioritize?
- What alternative is newly rejected and what downside is newly accepted?
- How should the changed tradeoff be recorded so the new decision is understood on its own terms rather than as an unexplained reversal?
Preserving Decision History Across Reversals and Replacements
- What should remain recorded about the previous decision after it is no longer active?
- Why was the previous commitment reasonable or defensible when it was made?
- What facts, assumptions, constraints, benefits, or downsides later changed?
- Which decision formally replaced or reversed it, and when did that happen?
- Can someone distinguish the current commitment from the historical decisions that preceded it?
- Are earlier records being preserved without allowing superseded decisions to remain operationally ambiguous?
- What history is necessary so future users can understand both what is decided now and how the organization arrived there?