# Hartnett’s Consensus-Oriented Decision-Making Model
Executive summary
Consensus-Oriented Decision-Making (CODM) is Tim Hartnett’s seven-step facilitation model: frame the topic; open discussion; identify underlying concerns; develop proposals collaboratively; choose a direction; synthesize a final proposal; and close by testing for consensus and deciding. It aims for widespread agreement and commitment while recognizing that groups need explicit fallback rules when unanimity is unavailable or inappropriate. Hartnett’s Consensus-Oriented Decision-Making model is strongest when consensus means widespread support plus transparent treatment of remaining concerns, not unanimous enthusiasm or veto by exhaustion; its seven-step facilitation process must sit inside clear authority, evidence, accessibility, and implementation safeguards. 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 Hartnett consensus-oriented decision making 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
Consensus-Oriented Decision-Making (CODM) is Tim Hartnett’s seven-step facilitation model: frame the topic; open discussion; identify underlying concerns; develop proposals collaboratively; choose a direction; synthesize a final proposal; and close by testing for consensus and deciding. It aims for widespread agreement and commitment while recognizing that groups need explicit fallback rules when unanimity is unavailable or inappropriate.
Foundation 1
Consensus is not identical preference. Members may strongly support, support with reservations, stand aside, or raise an objection they believe identifies material harm. Terms, thresholds, and consequences must be defined before pressure rises. 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
Concerns are information about needs, risks, values, constraints, or implementation. They should be understood before premature solution bargaining. A concern deserves response but does not automatically grant one person unlimited veto over an accountable body. 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
Facilitation shapes power. Agenda, framing, speaking order, summaries, proposal wording, time allocation, and what counts as resolution can privilege interests invisibly. Neutrality means procedural accountability and disclosed roles, not absence of influence. 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
Consensus can increase understanding, legitimacy, and implementation ownership when interdependence is high. It is poorly suited to urgent command decisions, adjudication of rights, matters requiring independent expertise, or settings where retaliation makes apparent agreement unreliable. 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. Frame the topic
State the decision, purpose, scope, constraints, affected people, authority, evidence, timeline, consensus definition, fallback rule, facilitator role, and conditions that require another process. Confirm shared understanding, not agreement with an answer. 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. Open discussion and identify concerns
Invite hopes, evidence, experience, questions, risks, and alternatives using accessible formats. Cluster underlying concerns without attaching them permanently to individuals or letting the first proposal dominate. 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. Develop proposals collaboratively
Generate options that address the concern map, identify non-negotiable protections, combine compatible mechanisms, investigate facts, test feasibility, and keep status quo and minority alternatives visible. 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. Choose direction and synthesize
Use transparent criteria and a temperature check to select a promising direction without declaring final consensus. Draft a complete proposal with responsibilities, resources, safeguards, tests, timing, and unresolved tensions. 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. Close, decide, and implement
Read the proposal, clarify, test levels of support and objections, modify where warranted, apply the declared consensus or fallback rule, record dissent, assign action, and review outcomes and participation. 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 codm seven-step pathway shows an animated pathway compresses framing, discussion, concerns, proposals, synthesis, and consensus closure. 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: A composite worker cooperative revising weekend schedules
Situation
Members wanted a fair schedule but differed over customer service, caregiving, religious observance, income, health, seniority, and whether one objection could block any change. 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
The facilitator clarified legal and safety constraints, formal board authority, membership scope, decision deadline, accessible participation, consensus categories, and a supermajority fallback after two properly facilitated sessions. 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
Open discussion separated positions from concerns: predictable income, service coverage, recovery, caregiving, observance, equal opportunity, and protection from manager retaliation. Anonymous input surfaced needs absent from the room. 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
Working groups developed rotation, voluntary premiums, shift exchange, and minimum-rest proposals. Operational data and a trial schedule tested assumptions instead of asking vulnerable members to negotiate only from personal disclosure. 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
A direction gained broad support; synthesis added predictable notice, protected exemptions, fair premium access, appeal, review, and staffing triggers. Two members stood aside and one objection about recovery produced a material revision. 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 final decision used the declared rule, recorded unresolved concerns without names, and assigned a six-week review of coverage, income, fatigue, fairness, swaps, and complaints. Consensus was judged by transparent support and responsible response, not silence. 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–12: charter the decision
Define the decision, authority, affected stakeholders, deadline, evidence needs, feasible alternatives, confidentiality, participation rules, and what would show that Hartnett consensus-oriented decision making is the wrong method. 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 13–28: prepare evidence and participation
Synthesize existing evidence, recruit for relevant knowledge and lived consequences, provide accessible materials, disclose conflicts, protect dissent, and pilot questions and facilitation before formal deliberation. 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 29–45: run structured inquiry
Separate independent judgment from social influence, surface assumptions and minority evidence, compare alternatives against explicit criteria, record uncertainty, and prevent status or facilitation choices from silently determining the result. 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 46–70: decide and test
State agreement and unresolved disagreement, use the declared decision rule, assign owners and safeguards, and test the decision at a proportionate scale with outcome, quality, risk, equity, and participation counter-measures. 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: verify and learn
Share a decision record, close the loop with participants, compare results with premises, protect those who raised concerns, correct harms, and review whether the group process should be repeated, changed, or retired. 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 Understanding the Decision Cycle, Monte Carlo Analysis, 10 Common Decision-Making Mistakes, Organizing Team Decision Making, The Delphi Method, Avoiding Groupthink 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. Participation integrity
Relevant groups reached, accessibility, independent routes, contribution distribution, facilitator interventions, and confidentiality. 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. Concern coverage
Underlying needs and risks identified, evidence gathered, proposal response, and unresolved concerns preserved. 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. Support profile
Levels of support, reservations, stand-asides, objections, changes across stages, and sensitivity to decision rule. 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. Decision quality
Feasibility, value, safety, fairness, resources, risk, implementation clarity, and comparison with alternatives. 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. Follow-through
Commitments completed, outcome and burden distribution, complaints and remedies, learning, and legitimacy after implementation. 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 second infographic presents consensus as a transparent support profile with qualified support, reservations, stand-asides, and objections rather than a binary and potentially coerced declaration of unanimity.
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. Unanimity trap
Every discomfort becomes veto. Define consensus and fallback. 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. Exhaustion consent
Meetings continue until opponents leave. Limit sessions and preserve dissent. 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. Premature proposal
Positions arrive before concerns. Explore needs and evidence first. 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. Facilitator capture
Summaries steer the answer. Use visible records and participant checks. 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. Consensus outside authority
The group promises what it cannot decide. Map authority and escalation. 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
Apparent consensus is invalid where retaliation, dependency, intimidation, or inaccessible participation prevents refusal. 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
A consensus process must not bargain away legal rights, safety requirements, or protections of absent and marginalized people. 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
Personal stories shared to explain concerns require consent, minimization, and protection from later employment or social use. 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
Facilitators should disclose conflicts, sponsor expectations, authority limits, compensation, records, and any circumstances requiring them to stop the 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.
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
Reconstruct one recent Hartnett consensus-oriented decision making decision. Mark when each option entered, who spoke before whom, what evidence changed, where dissent appeared, and how the final rule operated. 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
Collect independent written judgments from four relevant people before discussion. Compare unique information, confidence, assumptions, and how views change after evidence is shared. 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 one procedural safeguard for authority influence, conformity, information cascades, confidentiality, accessibility, and minority evidence; name evidence that the safeguard actually works. 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
Complete the checklist and draft a public-facing decision record stating participants, evidence, alternatives, agreement, disagreement, authority, safeguards, owner, and review date. 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
- Define consensus, authority, and fallback before deliberation. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Explore underlying concerns before proposals harden. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Design facilitation for evidence and power, not politeness alone. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Synthesize complete testable proposals. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Preserve reservations, stand-asides, and objections accurately. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Review both outcomes and process legitimacy after action. 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] Tim Hartnett. “Consensus-Oriented Decision-Making.” 2011. https://www.newsociety.com/Books/C/Consensus-Oriented-Decision-Making
[s2] Mindtools Content Team. “Hartnett’s Consensus-Oriented Decision-Making Model.” 2024. https://www.mindtools.com/ao6r70v/hartnetts-codm-model/
[s3] Sam Kaner et al.. “Facilitator’s Guide to Participatory Decision-Making, Third Edition.” 2014. https://www.wiley.com/en-us/Facilitator%27s+Guide+to+Participatory+Decision-Making%2C+3rd+Edition-p-9781118404959
[s4] Michel Avery, Brian Auvine, Barbara Streibel, and Lonnie Weiss. “Building United Judgment.” 1981. https://search.worldcat.org/title/8410334
[s5] Larry Dressler. “Consensus Through Conversation.” 2006. https://search.worldcat.org/title/62741444
[s6] Patrick Lencioni. “The Five Dysfunctions of a Team.” 2002. https://search.worldcat.org/title/49225717
