# Improving solutions by arguing for and against your options
Executive summary
Arguing for and against options is a structured decision method in which participants develop the strongest evidence-based case supporting an option and the strongest case opposing it, compare both against explicit criteria, and synthesize implications before commitment. It differs from unstructured debate because roles, evidence standards, decision rights, and interpersonal safeguards are designed in advance. Arguing for and against options improves solutions only when advocacy is structured as evidence-seeking role separation: teams must construct the strongest affirmative and negative cases, compare common criteria, expose assumptions, and then synthesize rather than reward the loudest advocate. The managerial task is to turn the concept into an evidence system: clarify the decision, expose assumptions, observe outcomes, compare alternatives, and revise action when results disagree. This chapter treats the method as a disciplined operating capability rather than a workshop artifact. It integrates theory, implementation, measurement, failure analysis, ethics, and a field exercise so a reader can use the model while respecting its limits.[s1][s2][s3][s4][s5][s6]
Learning objectives
By the end of this lesson, you will be able to:
- Diagnose when arguing for and against options can materially improve a business decision.
- Design a defensible evidence and implementation process rather than a presentation-only exercise.
- Select leading, lagging, economic, and quality measures that reveal whether the intervention works.
- Identify analytical, organizational, and ethical failure modes before they cause stakeholder harm.
- Translate an insight into a time-bounded test with ownership, thresholds, and a learning loop.
Foundations: what the concept means
Arguing for and against options is a structured decision method in which participants develop the strongest evidence-based case supporting an option and the strongest case opposing it, compare both against explicit criteria, and synthesize implications before commitment. It differs from unstructured debate because roles, evidence standards, decision rights, and interpersonal safeguards are designed in advance.
Foundation 1
Confirmation bias makes people seek, interpret, and remember evidence consistent with an initial preference. Explicitly considering the opposite can reduce some forms of overconfidence, but the instruction must change the search process; ceremonial objections after commitment merely legitimize the preferred choice. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 2
Devil’s advocacy assigns a person or group to criticize a proposed course. Dialectical inquiry goes further by constructing competing plans from different assumptions and seeking a synthesis. Both can improve assumption visibility, yet effects depend on task, facilitation, power, and whether dissent carries interpersonal cost. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 3
Task conflict concerns ideas, evidence, and choices; relationship conflict concerns identity, respect, or motive. Structured challenge can slide into relationship conflict when advocates are permanently identified with positions, senior people retaliate, or rhetorical dominance replaces shared inquiry. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 4
Decision quality and acceptance are separate outcomes. Intensive argument may improve analysis but reduce commitment if people experience the process as manipulative or cannot understand why a final choice followed. A decision record should show how objections affected design, safeguards, or rejection. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
The literature provides complementary rather than interchangeable lenses.[s1][s2][s3][s4][s5][s6] A rigorous practitioner uses those lenses to sharpen observation and decision quality, not to borrow academic authority for a conclusion already chosen. Definitions, samples, methods, and boundary conditions should travel with every important claim.
A decision-ready operating framework
A useful framework must specify inputs, transformation, outputs, ownership, and feedback. The following five-stage system creates that chain while leaving room for the method to be adapted to category, organization, and evidence quality.
1. Define the decision and common criteria
State options, constraints, decision owner, deadline, baseline, and weighted criteria before assigning advocacy. Include stakeholder harm, reversibility, information value, and strategic fit alongside financial return. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Build independent affirmative and negative cases
Separate teams or roles, provide equal access to evidence, and require causal claims, assumptions, base rates, failure conditions, and uncertainty rather than lists of agreeable adjectives. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Cross-examine claims, not people
Ask what evidence supports each link, what would falsify it, which stakeholder sees a different reality, and how outcomes change under alternative assumptions. Rotate or depersonalize roles. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Synthesize options and safeguards
Identify claims that survive challenge, uncertainties that require a test, design features that mitigate risk, and hybrid or staged options that neither original case contained. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Decide, document, and revisit
The authorized owner explains criterion trade-offs, records unresolved objections and review triggers, protects dissenters, and schedules a premortem or post-decision review before commitment bias hardens. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
This animated structured option challenge shows five stages connect shared criteria, affirmative case, negative case, cross-examination, and synthesis into a decision that preserves evidence and dissent. The sequence remains fully understandable when motion is disabled.
The stages are iterative. New evidence may change the original question, expose a missing stakeholder, or show that an apparently attractive option is infeasible. Governance should allow the team to return to an earlier stage without describing learning as failure.
Worked example: ArthaGrid, a composite B2B payments platform
Situation
The company considered launching instant settlement for small merchants. Sales forecast rapid adoption, while risk leaders feared fraud and liquidity exposure. Previous meetings repeated departmental positions without producing a testable decision. The case is hypothetical and composite; it illustrates a reasoning process rather than reporting facts about any real organization. Management agreed to separate observations, interpretations, choices, and measured outcomes so hindsight could not erase uncertainty.
Case movement 1
A facilitator defined six criteria before debate: merchant cash-flow value, fraud loss, liquidity need, service reliability, compliance effort, and reversibility. The chief product officer retained decision authority but could not join either advocacy team. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 2
The affirmative team modelled reduced working-capital delay and retention; the negative team modelled account takeover, settlement irreversibility, and peak liquidity. Each disclosed data gaps and constructed the other side’s strongest case before presenting its own. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 3
Cross-examination exposed a shared hidden assumption: every merchant would receive the same limit from day one. The negative case did not invalidate instant settlement; it invalidated an undifferentiated rollout. The affirmative case showed that waiting for zero risk would erase most customer value. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 4
The synthesis introduced earned limits, device-change holds, merchant confirmation, reserve rules, manual escalation, and a randomized staged launch. Stop thresholds covered fraud, delayed reversals, support burden, vulnerable-merchant complaints, and liquidity stress. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 5
The decision record credited objections that changed the design. After six weeks, value improved for eligible merchants while one fraud pattern triggered a temporary segment pause. Because disagreement had become a test architecture, correction did not require anyone to “lose” the debate. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Interpretation
The case matters because action followed the diagnosed mechanism, not the fashionable label. It also preserved a comparison and a boundary statement. A result in one setting changed the next decision; it did not become a universal law.
90-Day Action Plan
Implementation needs an executive sponsor, a working owner, protected access to evidence, and explicit decision dates. The plan below can be compressed for a small reversible choice or expanded for a regulated, capital-intensive, or high-harm decision.
1. Days 1–15: establish the decision charter
Name the decision, sponsor, working owner, affected stakeholders, current state, desired outcome, constraints, evidence sources, and the date on which action is required. Record what is assumed rather than observed. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Days 16–30: build the evidence baseline
Triangulate process data, direct observation, documents, and stakeholder accounts. Define units and denominators, examine variation and exceptions, and document missing or unreliable evidence before proposing causes. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Days 31–50: create and challenge explanations
Develop multiple causal or systemic accounts, identify the prediction each makes, search for disconfirming cases, and involve people close to the work. Select tests by information value as well as cost and speed. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Days 51–70: run a bounded intervention
Choose a reversible option, specify owner, resources, safeguards, comparison, leading indicators, counter-metrics, stop rules, and escalation thresholds. Preserve the old process where rollback may be necessary. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Days 71–90: decide and institutionalize learning
Compare results with the baseline and rival explanation, review stakeholder effects, decide whether to scale, adapt, stop, or reframe, and archive a decision record that distinguishes evidence from interpretation. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
The plan should connect with What is problem solving, The problem definition process, How good is your problem solving, Creative Problem Solving, The Four-Step Innovation Process and the Strategy learning hub. These links are complementary tools, not substitutes for the evidence required by this decision. At day ninety, write a one-page decision record covering the original premise, evidence obtained, decision taken, result, unresolved risk, and next review.
Measurement and review
Measurement should serve learning and accountability. Establish a baseline, define the unit and denominator, segment outcomes where averages can conceal harm, and choose a review interval that matches how quickly the underlying mechanism can change.
1. Problem-definition stability
Track how often the stated problem changes after evidence review and whether revisions clarify mechanism, boundary, stakeholder, and desired outcome rather than merely changing language. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Evidence quality
Rate coverage, provenance, recency, reliability, missingness, triangulation, and the number of serious rival explanations that have been tested rather than dismissed. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Decision-cycle performance
Measure elapsed time from signal to framed decision, time spent waiting for information or authority, experiment cost, rework, and the proportion of decisions revisited on schedule. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Outcome and mechanism
Measure the operational result and the nearer mechanism expected to produce it. Report baseline, denominator, variation, comparison, confidence, and whether the effect persisted beyond the test. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Stakeholder and resilience counter-metrics
Monitor safety, workload, fairness, privacy, accessibility, customer harm, supplier burden, reversibility, unintended consequences, and recurrence after apparent resolution. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
The audit traces each option claim to evidence, a visible assumption, a possible falsifier, and the resulting decision implication rather than tallying superficial pros and cons.
Avoid a dashboard in which every number rises when activity rises. Include outcome, quality, economic, and counter-metrics. Predefine a threshold that triggers investigation or stopping, and retain qualitative evidence that explains why the number moved.
Failure modes and corrective action
The most dangerous errors are often organizational rather than technical: incentives reward certainty, a senior sponsor prefers one explanation, or presentation deadlines arrive before evidence. Treat the following patterns as control failures with observable warning signs.
1. Solving the presented symptom
Urgency makes the first description feel authoritative. The warning sign is a solution embedded in the problem statement; correct it by separating observation, consequence, suspected mechanism, and proposed response. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Single-story certainty
A coherent explanation crowds out alternatives. Watch for evidence collected only to confirm one cause; require rival hypotheses, disconfirming evidence, and an explicit confidence level. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Workshop without decision rights
Teams generate maps and ideas but no authorized owner can alter the system. Define authority, resources, decision dates, escalation routes, and the artifact that commits action before convening. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Activity mistaken for outcome
Meetings, ideas, tickets, and training completions rise while the underlying failure persists. Pair activity indicators with mechanism, outcome, recurrence, and harm measures. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Premature standardization
A promising local result is converted into a universal procedure. Test transfer conditions, preserve local feedback, stage the rollout, and specify circumstances that require adaptation or rollback. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
Run a pre-mortem before launch and an after-action review after the first decision cycle. Record near misses, not only visible failures. A healthy team can say that an attractive hypothesis was not supported and redirect resources without reputational punishment.
Ethics, limits, and responsible use
Business usefulness does not excuse deception, avoidable harm, or unsupported inference. The method should be proportionate to the decision and reviewed more carefully when it affects employment, credit, health, safety, privacy, or access to essential services.
Responsibility 1
A problem-solving process must not turn uncertainty into a pretext for surveillance, retaliation, or blame. Protect confidential reporting, separate learning from discipline, and give people affected by a decision a safe route to challenge the evidence and proposed remedy. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 2
Analytical elegance does not justify shifting costs onto workers, customers, suppliers, or communities with less power. Map who receives the benefit, who bears risk, whose knowledge is excluded, and what accessible remedy exists when the intervention causes harm. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 3
Collect only data proportionate to the decision, document purpose and retention, restrict access, and test whether proxies reproduce structural disadvantage. When employment, health, safety, credit, or legal rights are involved, obtain qualified review and preserve due process. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 4
Models simplify reality and therefore create blind spots. State assumptions, uncertainty, scope, and reversibility; distinguish a test from a settled conclusion; and stop when evidence of harm, invalid measurement, or an unrepresented stakeholder makes the original design unsafe. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Limits should be written into the decision record: population, context, time, method, uncertainty, and the conditions under which the conclusion should be revisited. Do not imply individualized legal, medical, financial, or employment advice.
Practice Checklist and Laboratory
Implementation Checklist
- [ ] The audience, decision, accountable owner, and intended value are explicit.
- [ ] Material claims have traceable evidence, sources, limits, and correction ownership.
- [ ] The plan includes a baseline, comparison, primary outcome, cost, and stakeholder counter-metric.
- [ ] Consent, privacy, accessibility, safety, legal, and platform obligations have been reviewed.
- [ ] Stop, escalation, remedy, and after-action review rules are documented before launch.
Complete the exercises with a live but reversible decision. Preserve artifacts so another reviewer can inspect how you moved from evidence to recommendation.
Exercise 1
Take one current operational complaint and write four separate statements: observed condition, consequence, plausible mechanism, and proposed solution. Ask a colleague to mark every word that assumes a cause not yet demonstrated. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 2
Construct an evidence ledger for the decision with columns for claim, source, method, date, scope, reliability, disconfirming observation, and responsible reviewer. Remove any claim that cannot support the decision being asked of it. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 3
Design the smallest safe test that distinguishes the two most credible explanations. Specify comparison, duration, sample or cases, expected signal, counter-metric, stop rule, owner, and what each possible result would mean. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 4
Facilitate a thirty-minute red-team review with someone affected by the proposed change. Record the strongest objection, hidden cost, missing stakeholder, and condition under which the intervention should not proceed. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Finish with a decision memo: “We believed… We observed… We now infer… We will test… We will stop or revise if…” This format makes uncertainty actionable and creates an organizational memory stronger than a polished retrospective.
Key takeaways
- Structured advocacy is an evidence process, not permission for louder meetings. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Define decision criteria and authority before teams become attached to positions. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Construct the strongest version of both cases and expose assumptions, base rates, and falsifiers. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Protect task conflict from becoming relationship conflict through role rotation and psychological safety. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- The goal is synthesis: a better option, safeguard, staged test, or justified rejection. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Record how dissent changed the decision and preserve triggers for revisiting it. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
Mastery means choosing the method for the decision it can improve, using evidence at the level it supports, and changing course when the world contradicts the model.
References and further reading
The sources below establish the conceptual and methodological foundation. Publication details and locators have been retained so editors can verify every material attribution before publication.
[s1] Charles R. Schwenk. “Effects of Devil’s Advocacy and Dialectical Inquiry on Decision Making: A Meta-Analysis.” 1990. https://doi.org/10.1016/0749-5978(90)90051-A
[s2] David M. Schweiger, William R. Sandberg, and James W. Ragan. “Effects of Devil’s Advocacy and Dialectical Inquiry on Decision Making: A Field Study.” 1986. https://doi.org/10.2307/256403
[s3] Charles G. Lord, Mark R. Lepper, and Elizabeth Preston. “Considering the Opposite: A Corrective Strategy for Social Judgment.” 1984. https://doi.org/10.1037/0022-3514.47.6.1231
[s4] Irving L. Janis and Leon Mann. “Managing Intraindividual Conflict in Decision Making.” 1977. https://archive.org/details/decisionmakingps0000jani
[s5] Kathleen M. Eisenhardt, Jean L. Kahwajy, and L. J. Bourgeois III. “The Effects of Conflict on Strategic Decision Making Effectiveness and Organizational Performance.” 1997. https://doi.org/10.1287/mnsc.43.1.42
[s6] Gary Klein. “The PreMortem Method.” 2007. https://hbr.org/2007/09/performing-a-project-premortem
