Chapter 12: Decision-Making and Voting

How a standards body reaches decisions is as important as what it decides. The decision-making structure determines who has power, how disagreements get resolved, and whether the resulting specification will actually be implemented. A standard that passes a vote but doesn't reflect genuine consensus is a standard that sits on a shelf.

One thing to understand from the outset: every organization has its own rules, processes, and culture around decision-making. There is no universal standard for standards governance. What constitutes a quorum at W3C is different from what constitutes a quorum at OASIS. How IETF gauges rough consensus is nothing like how ISO/IEC conducts a national body ballot. The voting thresholds, the role of the chair, the treatment of abstentions, and even the definition of "consensus" vary from organization to organization. When you engage with a new standards body, read the governance rules before you attend your first meeting. The assumptions you bring from your last engagement may not apply.

This chapter covers the mindset required for multi-party decision-making, the mechanics of consensus and voting, the group dynamics that shape outcomes, and what happens when consensus fails. The governance rules discussed here exist within an antitrust framework — standards bodies are fundamentally a creature of antitrust law, and the openness, balance, and due process requirements that shape governance design are what keep these competitor collaborations legal. That framework is covered in depth in Chapter 4.

12.1 The Mindset Shift

Multi-party negotiations require a fundamentally different approach than bilateral ones, and standards are multi-party negotiations at their most complex. The adversarial instincts, the advocacy skills, the habit of framing everything as win-or-lose — none of it works when the "other side" is fifteen companies that all need to agree and then voluntarily build to the result.

The core problem is structural. In litigation, a judge decides. In bilateral negotiation, you and a counterpart hammer it out, and if you can't agree, you walk away. In both contexts, there's a resolution mechanism that doesn't require the other side's voluntary cooperation after the fact.

Standards have no such mechanism. There's no judge. There's no binding resolution. And the output is voluntary — nobody is required to implement. You can win every vote and still lose if the companies that matter choose not to adopt the result. This changes the entire calculation. The goal isn't to prevail over the other side. It's to produce an outcome that enough participants will voluntarily implement to make the standard successful.

This requires a fundamentally different toolkit. Instead of advocacy, you need coalition-building. Instead of clever arguments, you need an understanding of what every participant needs and what they can live with. Instead of going for the win, you need to find the compromise that keeps enough parties at the table. The participants you're working with today are the same ones you'll encounter next quarter in a different working group and next year in a different organization. The relationships compound — for good or for bad.

In some international settings, the dynamic is literally diplomatic. UN-chartered organizations like ITU-T begin meetings with formal acknowledgments of national delegations. The pace is deliberate. The language is careful. The back-channel conversations are where the real work happens. Even in less formal settings — a consortium working group, a JDF project — the underlying dynamic is the same. You're building coalitions, managing relationships, and trading concessions across multiple dimensions simultaneously.

12.2 Consensus-Based Decision Making

What Consensus Actually Means

Consensus doesn't mean unanimity. This is one of the most common misunderstandings in standards governance.

Unanimity means everyone agrees. Consensus means the group has reached a position that everyone can live with — even if not everyone loves it. There may be participants who would have preferred a different outcome but aren't willing to block progress over it. Consensus is often best understood as the absence of sustained and vigorous objection, not the presence of universal enthusiasm.

This distinction is more subtle than it appears. Consider a room of ten people. If six support a proposal and four are ambivalent — they don't love it but they're not going to fight it — you likely have consensus. But if eight people enthusiastically support the proposal and two are vigorously and persistently opposed, you may not have consensus, even though you have a clear numerical majority. The intensity of the objection matters as much as the count.

In practice, the chair of a working group typically gauges consensus by asking whether anyone objects to a proposed direction. If no one objects, consensus is declared. If someone does object, the chair evaluates whether the objection is substantive, whether it represents a broader concern or an isolated position, and whether the objector is willing to stand aside or intends to sustain the objection. A single objection doesn't necessarily break consensus — but a sustained, vigorous one from even a small minority can.

The Difference Between Unanimity, Consensus, and Majority Rule

These three decision-making models exist on a spectrum, and different organizations use different models for different types of decisions.

Unanimity is rare in standards because it gives every participant a veto. It doesn't scale — in a large group, a single holdout can paralyze the process. But for small groups of five companies or fewer, you should generally strive for unanimous agreement even if the governance rules provide otherwise. In a group that small, every participant matters for adoption. Forcing a decision over the objection of one out of five participants is a hollow victory — because the "losing" party doesn't have to implement, and without their implementation, the standard may not achieve the critical mass it needs.

Consensus is used by many standards bodies, particularly in the technology space. It allows progress without requiring every participant to affirmatively agree, while still ensuring that serious objections are heard and addressed. The challenge is that consensus is inherently subjective — reasonable people can disagree about whether consensus has been reached, and the chair's judgment call is sometimes contested.

Majority voting is the default decision-making mechanism in many standards organizations, particularly incorporated entities with formal bylaws. It's clean and unambiguous — you count the votes, and the result is the result. The risk is that a majority can push through a decision over the objection of a significant minority, which may undermine the legitimacy of the standard and discourage implementation by the dissenting parties.

Some governance structures combine both approaches. The JDF model, for instance, uses consensus as the primary mechanism with a supermajority vote as a backstop, as discussed below. Other organizations use majority voting for most decisions but require supermajority or consensus for specific categories like IP policy changes.

The Consensus-Then-Supermajority Model

The JDF model illustrates a particularly effective approach: decisions are made by consensus, but if consensus can't be reached, the matter escalates to a supermajority vote.

The design is intentional. The supermajority threshold is high enough that neither side is likely to achieve it unless they have overwhelming support. This means that in most cases, the threat of a vote that nobody can win drives the parties back to the consensus process. The supermajority vote isn't really designed to produce a winner — it's designed to make both sides realize that they need to compromise, because neither can force the outcome through voting alone.

This is a governance structure that uses its own impracticality as a feature. The harder it is to win a vote, the stronger the incentive to find consensus. The supermajority backstop exists not to be used, but to make the consensus process work better.

Rough Consensus and Running Code

IETF's formulation — "rough consensus and running code" — deserves specific mention because it captures a philosophy that extends well beyond IETF.

Rough consensus acknowledges that perfect agreement is neither achievable nor necessary. What matters is that the group has broadly converged, that dissenting views have been heard, and that the remaining disagreements aren't fundamental. "Running code" means that the consensus is validated by implementation — a standard that works in practice is more valuable than one that's theoretically perfect but unimplemented.

This philosophy is specific to IETF's standards development approach and reflects its engineering culture. It is not how open source development works, and it is not the decision-making model used by most other standards bodies. But the underlying principle — that practical convergence matters more than theoretical perfection — is applicable broadly.

12.3 Voting Structures

When formal voting is required, the design of the voting structure shapes the outcome as much as the substance of the proposal.

One Vote Per Company

The most common structure in industry consortia is one vote per company, regardless of size. This prevents dominance by large companies — a startup's vote counts the same as the largest technology company in the world. It rewards persuasion and coalition-building over market power.

This principle typically extends to corporate families: a parent company and its affiliates collectively get one vote, not one vote per subsidiary. The rationale is straightforward — without this rule, a company could multiply its voting power by participating through multiple subsidiaries. The same logic that prevents one company from dominating through market size prevents it from dominating through corporate structure.

The limitation is that one-vote-per-company can also give disproportionate influence to small companies with narrow interests. A company with minimal implementation stake can cast a vote with the same weight as a company that will spend millions implementing the result.

Weighted Voting and Qualified Majority

Some organizations use weighted voting, where votes are allocated based on membership tier, contribution level, or other criteria. International organizations sometimes weight by national delegation. ETSI historically gave votes by national delegation, which — as discussed in Chapter 1 — led to companies joining multiple national delegations to multiply their voting power.

Qualified majority thresholds — requiring more than a simple majority to pass — are used for significant decisions like approving final specifications or amending governance documents. Common thresholds include two-thirds and three-quarters, though the specific number varies by organization and by the type of decision.

The Details Matter: Supermajority Precision

Supermajority thresholds sound straightforward until you try to apply them. A "two-thirds majority" can mean different things depending on the denominator.

Is it two-thirds of all members? Two-thirds of those present? Two-thirds of those who actually cast a vote — excluding abstentions? Each definition produces a different number, and the difference can determine the outcome on a close vote.

Even the arithmetic can become a question. Is two-thirds 66.6% or 66.7%? If you have 10 members voting and need a two-thirds majority, is that 7 votes or 6.67 (rounded to 7)? What if the answer changes with one abstention? These seem like pedantic questions until they decide a contentious vote, at which point the party that lost will scrutinize every decimal.

Different organizations answer these questions differently, and some don't answer them at all — they have thresholds defined in their governance documents without specifying the calculation methodology. When you're drafting governance rules, be precise. Specify the denominator. Specify how abstentions are treated. Specify the rounding. If the rules are ambiguous, the ambiguity will surface at the moment of maximum contention, which is the worst time to resolve it.

Organizations also vary in what decisions require a supermajority. Some require a supermajority only for governance changes (amending bylaws, admitting new membership classes) while using simple majority for technical decisions. Others require a supermajority for approving final specifications, on the theory that a standard that passes over significant opposition is unlikely to achieve broad implementation. A few require consensus for everything, with voting only as a last resort. The design choices here reflect the organization's priorities — speed versus inclusiveness, efficiency versus legitimacy.

Provisions That Require Unanimity — Or Can't Change at All

Some matters are so fundamental that they require unanimous agreement to change — or are designed not to change at all.

Patent policies are the primary example. In most well-designed organizations, changes to the IPR policy require unanimous consent of the affected members, or are simply prohibited. The rationale is that participants joined the organization based on the IP terms in effect at the time. Changing those terms after the fact — even by a supermajority — could alter the patent commitments participants have already made or alter the rights implementers are relying on.

This is why getting the patent policy right from the beginning matters so much. You can usually amend bylaws, adjust membership criteria, restructure working groups, and change decision-making thresholds through the governance process. But the patent policy is, for practical purposes, permanent. Treat it accordingly.

Voting Order and Visibility

Whether votes are cast simultaneously or sequentially, and whether they're visible or secret, creates different strategic dynamics.

Simultaneous, secret voting minimizes strategic behavior. Everyone votes based on their own assessment without being influenced by others' positions. This is cleanest but can produce surprising results when the outcome doesn't reflect the back-channel conversations.

Sequential, visible voting — as seen in the DVD-CCA structure discussed in Chapter 11 — creates signaling dynamics. Early voters set the tone. Later voters can adjust their positions based on what they've seen. This can facilitate coalition-building, but it can also enable manipulation, strategic abstention, and games around who gets stuck being the "bad guy."

Recorded votes with public minutes fall somewhere in between. The vote happens simultaneously, but the individual positions are recorded and published — meaning participants know their vote will be visible after the fact, even if they don't know how others voted at the moment they cast their own.

The choice between these models depends on the trust level among participants, the contentiousness of the issues, and whether the goal is to reveal true preferences or to build consensus through visible alignment.

Abstention and Quorum

Two mechanical issues that trip up organizations more often than you'd expect: abstention rules and quorum requirements.

Can a participant abstain? Does an abstention count toward quorum? Does it count as a "no" vote for purposes of calculating thresholds? Does it count as a vote at all for purposes of the denominator? Organizations answer these questions differently, and the answers can determine outcomes. An abstention that counts toward quorum but not toward the vote threshold lowers the effective bar for passage. An abstention that doesn't count toward quorum can prevent the vote from happening at all.

Quorum requirements — the minimum number of participants who must be present for a vote to be valid — prevent a small subgroup from making decisions for the whole. But they can also be used tactically: if you want to block a vote, simply don't show up and hope enough others don't either. Some organizations address this by allowing proxy voting or mail ballots to make quorum easier to achieve.

12.4 Group Dynamics at Scale

Small Groups vs. Large Organizations

Decision-making dynamics change fundamentally as groups grow.

In a group of three to five companies, you can work things out conversationally. Everyone knows everyone. Trust is personal. Consensus is reached through discussion, and formal voting is rarely needed.

At ten to fifteen companies, you start needing structure — formal agendas, defined decision-making rules, roles like chairs and editors. The personal dynamics still matter, but they're supplemented by process.

At fifty companies or more, the dynamics shift again. You can no longer negotiate with everyone individually. Coalition management becomes essential. The formal rules matter more because not everyone has a personal relationship with the chair. And paradoxically, it can be easier to drive decisions through a large group than a small one — because in a large group, most participants are deferential to the process and will go along with a well-presented proposal, while in a small group, every participant feels entitled to litigate every point.

Who Shows Up Matters

Standards decisions are made by the people who show up. This sounds obvious, but its implications are significant.

Attendance at working group meetings fluctuates. Some companies send the same representative every time. Others rotate, losing institutional context with each change. Some stop showing up when the work gets boring or the timeline slips.

The result is that the composition of the room can differ significantly from meeting to meeting, and the direction of the work can shift based on who happens to be present when a key decision is made. Companies that show up consistently — even when the agenda seems routine — have disproportionate influence on the outcome.

Persistent Objectors

Every standards body eventually encounters a participant who objects to everything. Sometimes the objections are substantive — the participant has a genuinely different technical vision. Sometimes they're strategic — the participant is trying to slow progress. Sometimes they're just temperamental.

The governance structure needs a way to handle persistent objection without either capitulating to it or ignoring it. Most organizations allow the chair to override a persistent objection after documented attempts to address the concern, subject to an appeal process. The appeal provides a safety valve — the persistent objector isn't silenced, but they can't hold the entire group hostage indefinitely.

12.5 Organizational Culture and Who's in the Room

The Evolution from Engineers to Governance Professionals

When organizations are small — five or ten companies in a working group — the people writing the specs are the same people making governance decisions. The chair is usually the most technically engaged person. The culture is engineering-driven. Governance is informal because everyone knows the rules, or there aren't many rules to know.

As organizations grow, a division emerges. The technical work stays with the engineers who build the specs. But the governance — the bylaws, the membership rules, the voting procedures, the IP policy — increasingly attracts a different type of participant: the standards professional. These are people whose job is governance, process, and organizational management. They may have engineering backgrounds, but their day-to-day work is running the organization rather than writing specifications.

This creates a cultural tension. The engineers want to build things. The governance professionals want to refine the rules. And governance professionals, in particular, have a tendency to want to "fix" governance — to propose amendments, restructure committees, and optimize processes. This can be productive when the governance genuinely needs improvement. It can also become self-referential work that consumes time and attention without advancing the technical mission. Be aware of this dynamic. Not every governance improvement proposal deserves the working group's time, and sometimes the best governance is the governance that stays out of the way.

Which Department Shows Up

Beyond the individual, pay attention to which department within a company sends the representative. The department's mission shapes what that representative optimizes for, and the results can be dramatically different.

In one content protection standards group, the major studios initially sent their content protection teams — the people whose job was to prevent piracy. These teams designed a system that was technically robust and extraordinarily complex. It maximized security. It addressed every conceivable piracy vector. Support costs, consumer experience, implementation burden — none of these were their problem. Their metric was content protection, and by that metric, the system was a success.

Later, the studios replaced their content protection representatives with people from their home video divisions — the people whose job was to sell movies to consumers through online channels. The home video teams walked into the working group and couldn't understand why the system was so difficult to implement, why the consumer experience was so poor, and why support costs were so high. After all, when a customer called because the movie they bought wouldn't play, it was the home video division that fielded the call and absorbed the cost.

Same companies. Same standards body. Entirely different priorities, because the representatives came from different departments with different success metrics. The lesson for practitioners: when you're evaluating the dynamics of a working group, don't just look at which companies are at the table. Look at who within those companies is sitting in the chair. Their department's mission will shape the standard.

12.6 When Consensus Fails

Sometimes the group can't agree. The technical visions are incompatible. The commercial interests diverge. The trust breaks down. What happens next depends on the governance structure and the stakes.

Appeals and Escalation

Most formal organizations have an appeal process — a participant who believes the chair declared consensus incorrectly, or that the process was unfair, can escalate to a higher body. The appeal mechanism is important because it provides legitimacy. Even if the appeal is denied, the fact that it was heard and considered gives the dissenter a path that doesn't require blowing up the process.

Fork Threats

The ultimate escalation in standards — as in open source — is the fork. If a group of participants is sufficiently unhappy with the direction, they can take the work (subject to copyright and IP terms) and start a competing effort elsewhere.

Fork threats are sometimes explicit and sometimes implicit. The HTML5/WHATWG story discussed in Chapter 1 is the canonical example — participants who disagreed with W3C's direction formed a competing group and ultimately won. The threat of a fork is what keeps standards bodies responsive to their participants. If the governance is too rigid, the process too slow, or the outcome too dominated by a single interest, the dissatisfied parties will leave.

This is why, as a governance design principle, the best way to avoid a fork is to make one unnecessary. Flexible governance, fair process, and genuine responsiveness to minority concerns reduce the incentive to walk away. The organizations that thrive long-term are the ones that give participants enough voice that they'd rather fix the problem from inside than start over from outside.

Walking Away

Sometimes the right answer is to accept that consensus isn't possible and move on. Not every collaboration succeeds. Not every standard gets adopted. The governance structure should contemplate this possibility — with clear rules about what happens to the IP, the materials, and the commitments when a working group concludes without a final deliverable.

The worst outcome is a zombie working group that never formally ends but never produces a result — consuming time, creating ongoing obligations, and preventing the participants from moving the work elsewhere. Clean termination provisions, with clear IP consequences, are worth the effort of negotiating up front.