Chapter 11: Standards Governance Structures

Governance in standards is where the theoretical frameworks of patent policies, organizational structures, and decision-making rules meet the practical reality of getting a group of competitors to agree on something. The governance structure determines who has power, how decisions get made, what happens when people disagree, and — critically — how the organization evolves over time.

This chapter covers the anatomy of standards governance, from boards and working groups down to the mechanics of chartering, membership design, and operational management.

11.1 Organizational Anatomy

Most standards organizations share a common structural pattern, though the terminology varies.

At the top sits a governing body — a board of directors, a steering committee, or in simpler structures, just the founding members acting collectively. This body sets the strategic direction, approves budgets, admits new members, and oversees the organization's operations. In contractual consortia, this function may be performed informally by the signatories to the agreement.

Below the governing body sit technical committees or working groups where the actual specification work happens. Each working group typically has its own charter defining its scope, its IPR mode, its deliverables, and its decision-making rules. The working group is where engineers draft text, debate technical choices, and iterate toward a final specification.

Some organizations add an intermediate layer — a technical steering committee that coordinates across multiple working groups, resolves cross-cutting technical issues, and ensures consistency between related specifications.

The relationship between these layers matters for IP purposes. As discussed in Chapter 8, patent commitments may apply at the organization level or the working group level. Understanding which layer your client's commitment attaches to is one of the first things to check when evaluating a new engagement.

11.2 Membership Models

How membership is structured determines who participates, who has influence, and who makes patent commitments. The design choices here have direct consequences for both governance and IP.

Open vs. Restricted Membership

Some organizations have fully open membership — anyone can join, anyone can participate, and everyone gets a voice. IETF is the extreme version: no formal membership at all, individual participation, and decisions by rough consensus. Most W3C working groups are open to any W3C member.

Others restrict membership, either by requiring an invitation, setting qualification criteria, or limiting the number of participants. This is common when a small group of companies wants to collaborate without opening the process to competitors they'd rather not include. The restriction has to be done carefully — antitrust law requires that similarly situated parties be treated alike, and exclusion needs objective justification.

Tiered Membership

Larger organizations typically use tiered membership. A common pattern:

Steering or founding tier. These members have the most influence — they sit on the governing body, approve specifications, and control the organization's direction. The top tier usually carries the highest dues and the greatest patent commitment obligations.

General or contributing tier. These members participate in technical work and have a voice in working groups, but may not have a vote on organizational governance. Their dues are typically lower.

Observer or associate tier. These members can follow the work and may attend meetings, but have limited or no voting rights. Some organizations use this tier as an on-ramp for companies evaluating whether to commit more deeply.

The naming conventions are inconsistent across the industry. "Founders" doesn't necessarily mean you were there at the founding — it's often just a label for the top membership tier. "Participant" may or may not carry patent commitments depending on the policy. Don't assume the label tells you the legal consequences. Read the agreement.

Permanent Board Seats and Succession

In smaller consortia, it's not uncommon for founding members to hold permanent seats on the board — seats that are guaranteed to the company for as long as they remain members, regardless of elections or rotations. This provides the founders with stability and control over the organization's direction, and it can be a powerful incentive for early commitment.

The interesting governance question is what happens when a founding member leaves. In some organizations, the seat reverts to the founding tier and is filled by another qualifying member. In others, the permanent seat simply disappears, and the board shrinks. In a well-designed structure, the vacated seat becomes an open seat available to any member at the appropriate tier — which can change the power dynamics significantly if the remaining founders now share the board with members who joined later under different expectations.

This is worth thinking about at the design stage. Permanent seats create stability in the short term but rigidity in the long term. If the organization's membership evolves — and it will — the governance structure needs to accommodate the change without requiring a constitutional crisis.

Who Is a "Participant" — Patent Commitment Implications

This is the practical punchline of membership design. The patent policy defines who makes a commitment and at what level. In some organizations, all members at every tier make the same commitment. In others, only the top tier commits, and lower tiers receive the benefit without contributing to the patent pool.

When advising a client on which tier to join, the patent commitment is often the decisive factor. A client with a significant patent portfolio may prefer a lower tier that doesn't trigger a broad commitment. A client with few patents may prefer the top tier for the governance influence, since the patent commitment costs them little. Understanding this dynamic — and being explicit with your client about what each tier means for their IP — is essential.

Case Study: DVD-CCA — Governance Complexity in Practice

The DVD Copy Control Association (DVD-CCA) is worth examining as an example of how complex governance structures can become when the stakeholders span fundamentally different industries.

DVD-CCA was established to manage and license the Content Scramble System (CSS) — the copy protection technology used on DVDs. It brought together three distinct industry groups: the entertainment industry (motion picture studios and content providers), consumer electronics manufacturers (companies building DVD players and drives), and the computer industry (hardware and software companies enabling DVD playback on PCs).

Each of these groups had different interests. The entertainment industry wanted strong copy protection. Consumer electronics manufacturers wanted interoperability and low licensing costs. The computer industry wanted flexibility to implement DVD playback in software.

To manage these competing interests, DVD-CCA used a governance structure with a twelve-member board — but the seats were not equally distributed. The entertainment industry held six seats, while consumer electronics and the computer industry held three each. This reflected the content owners' view that copy protection was fundamentally about their content, and that they should have the strongest voice in how it was managed. The imbalance created its own dynamics: the technology industries had to coordinate with each other to have any chance of outweighing the entertainment bloc on contested issues.

Separate membership classes for each sector were defined by objective qualification criteria — the entertainment industry class, for instance, required demonstrated box office revenue above a threshold, ensuring that the governance wasn't diluted by entities without meaningful stake in the outcome.

The voting structure added another layer of complexity. Rather than simple majority voting across all members, DVD-CCA used an industry-by-industry voting model where each of the three industry groups voted separately on certain matters. A proposal needed support within each group to advance — meaning the entertainment industry couldn't simply use its six-seat advantage to overrule the technology industries on every question, and a single industry group could effectively block progress on issues requiring cross-industry consensus.

Within the industry groups, voting reportedly followed a sequential structure — companies voted in a defined order, and the results were visible to other members. This created strategic dynamics that went well beyond the merits of any given proposal. If the first company in the order voted against a measure, it sent a signal to the rest of the group. Companies voting later could see which way the wind was blowing before committing. The order in which you voted — which might be determined by something as arbitrary as alphabetical order within the industry segment — could determine whether you were the one setting the tone or the one reacting to it.

This voting structure turned every decision into a multi-dimensional strategic exercise. Companies had to think not just about whether they supported a proposal on the merits, but about what their vote would signal to their industry peers, how the other industry groups would react, and whether a blocking vote from one group would create leverage for negotiations on other issues. Adding to the complexity, the order in which industry groups voted first rotated — so for each vote, a different industry was in the position of setting the initial tone. This rotation prevented any single industry from permanently controlling the signaling dynamic, but it also meant that strategic calculations shifted with every ballot. Alliances formed across industry boundaries. Companies that were competitors on the board found themselves voting together against a different industry group on copy protection scope, then opposing each other on licensing terms.

The structure also separated specification development from licensing and certification. The technical standards for CSS were developed through one process, while the licensing terms and compliance requirements were managed through another — each with its own governance dynamics.

This level of complexity was appropriate for DVD-CCA's specific situation: a technology that sat at the intersection of three powerful industries with conflicting incentives, significant money at stake, and content protection requirements that created genuine adversarial dynamics between content owners and technology implementers. It is not the norm for most standards engagements. Most projects don't need twelve-member boards with weighted industry-segment representation.

But DVD-CCA illustrates several governance principles that apply broadly:

When your stakeholders have genuinely different interests, the governance structure needs to account for those differences — through membership classes, board composition, or voting rules.
Unequal board representation creates its own dynamics — the minority groups must coordinate to be effective, which can either foster productive alliances or entrench adversarial positions.
The design of the voting structure shapes the strategic behavior of the participants — sequential visible voting creates different incentives than simultaneous secret balloting.
Separation of functions (spec development, licensing, certification) can reduce conflicts of interest and provide antitrust protection.
Objective membership criteria matter — without them, every admission decision becomes a political fight.
Complexity has a cost. The more elaborate the governance, the harder it is to operate, to amend, and to explain to new participants.

Dues and Financial Sustainability

One aspect of membership design that deserves attention is dues structure. Membership fees fund the organization's operations — staff, infrastructure, events, legal costs. The structure of these fees sends signals about who the organization is for.

Setting dues at the outset is more art than science. You don't know how much the organization will spend — that depends on how the work evolves, whether you hire staff, whether you hold events. You don't know how many members you'll attract — that depends on the technology's importance, the competitive dynamics, and whether the value proposition is compelling. So you pick a number, and you adjust later.

In practice, dues serve a function beyond revenue: they help companies self-select into the right tier of engagement. A high dues number at the steering level signals that this tier is for companies that are serious about the work and willing to invest. Companies that aren't prepared to commit at that level will self-select into a lower tier — or not join at all. This filtering function is often as important as the revenue itself. It ensures that the decision-making table is populated by participants with genuine commitment to the outcome.

The risk of setting dues too high is excluding participants whose technical contributions are valuable even if their budgets are limited — startups, academic institutions, smaller companies. Many organizations address this with sliding-scale dues based on company size or revenue, or with fee waivers for academic and nonprofit participants. Getting the balance right — enough revenue to sustain operations, enough filtering to ensure committed participants, low enough barriers to attract broad technical input — is one of the ongoing challenges of organizational design.

11.3 Forming a New Organization or Project

From the White Binder to Modular Frameworks

The history of standards formation is a story of progressive simplification.

In the early days, each new collaboration required a bespoke agreement negotiated from scratch. A representative example from the early 2000s: two major technology companies — fierce competitors, deeply distrustful of each other — negotiated a bilateral agreement to collaborate on a series of XML-based interoperability specifications. Each side was concerned that the other would use the collaboration to gain an unfair advantage.

The result was an agreement that ran over thirty pages and took more than a year to negotiate. It covered governance, IP, confidentiality, decision-making, dispute resolution, and every conceivable contingency — including elaborate mechanisms for what happened if the parties couldn't agree, involving written notices, escalation timelines, and fallback procedures so convoluted that the drafters themselves had difficulty explaining them. The confidentiality terms were unusually restrictive. The dispute resolution provisions reflected legal teams that had been in litigation with each other and expected to be again.

This was the state of the art when you wanted to do a standards collaboration. You pulled out this kind of agreement, and you spent six to nine months negotiating every detail with counterparts who assumed the worst about your intentions. It worked — in the sense that it produced specs — but the overhead was enormous, and the agreements were so complex that they became barriers to participation. Nobody new wanted to sign something they couldn't understand, and nobody who was already in wanted to try to amend it.

The agreements were also shaped by the relationships — and the distrust — between the parties. Language that seems bizarre in isolation often made sense as a response to a specific fear or a specific negotiation dynamic. But that context was lost once the agreement left the room. Future participants would read these clauses and have no idea why they existed. The language would migrate from one agreement to the next — copied, not understood — and accumulate like geological layers of prior disputes.

The next evolution was the form consortium agreement — a template that reduced the negotiation from a blank page to a starting point. A well-designed form might be 13 pages rather than 33, with modular IP provisions that could be swapped depending on the engagement. This cut setup time significantly, but still required negotiation and execution by every participant.

The current generation — represented by frameworks like JDF and the Community Specification License — eliminates the negotiation entirely. The governance terms are predefined and non-negotiable. The IP modes are selected from a menu. A new project can be chartered and operational in days. The tradeoff is flexibility — you can't customize the framework — but for most engagements, the predefined options fall within the range of reasonable, and the speed advantage is decisive.

Chartering Working Groups

When a new working group is formed, the charter is the foundational document. It defines:

Scope — what the group can and cannot work on. As discussed in Chapters 9 and 10, getting scope right is one of the hardest and most consequential decisions. Too narrow and the group can't adapt. Too broad and participants face open-ended patent exposure.

IPR mode — which patent policy applies. In organizations that offer multiple modes, this is selected at the working group level, not the organization level. Different working groups within the same organization can operate under different IP terms.

Deliverables — what the group is expected to produce. A specification? A reference implementation? A test suite? A profile? The deliverables determine the scope of the patent commitment and the criteria for declaring the work "done."

Decision-making rules — how the group reaches consensus, whether it uses voting, and what the thresholds are. These are covered in depth in Chapter 12.

The charter is often the last thing people want to spend time on — everyone is eager to start the technical work. But time spent on the charter is time saved later, because charter ambiguity becomes governance disputes once the work is underway.

The Pre-Draft Advantage

One governance dynamic that's rarely written down but profoundly affects outcomes: whoever writes the first draft has an outsized influence on the final result.

In most working groups, the initial draft specification — sometimes called the "seed" or "input document" — comes from one or two companies that have already built something and want to standardize it. The working group then iterates on that draft. In theory, the process is open and every participant can reshape the document. In practice, the initial draft sets the architecture, the terminology, the approach. Subsequent contributions tend to modify and extend rather than replace.

This matters for two reasons. First, the company whose technology starts as the initial draft has a significant backwards-compatibility advantage. Their existing products are likely to be aligned with the standard as it evolves. Competitors may need to adapt their implementations.

Second, the initial draft sets the frame for the patent commitment. The scope of the specification — and therefore the scope of the necessary claims — is shaped by the initial architecture. If your technology is the starting point, your patents are more likely to read on the final spec, but you're also more likely to have anticipated and managed that exposure.

Getting a seat at the table early — and ideally being the one who writes the first draft — is one of the most effective strategic moves in standards engagement.

Feedback Mechanisms and External Participation

Most standards organizations have mechanisms for people outside the membership to provide feedback — feedback agreements, public comment periods, liaison relationships with other organizations.

The lesson for practitioners: if your client is contributing through a feedback mechanism rather than as a full member, make sure they understand what rights they're granting. The feedback agreement may be more expansive than the membership agreement in some respects — particularly around patent commitments to contributed material.

11.4 The Linux Foundation Model

The Linux Foundation deserves specific discussion because of its scale and influence in the current landscape.

Operational Backbone

The Linux Foundation provides operational infrastructure for hundreds of projects — accounting, tax filing, bank accounts, event management, legal support, and program management. For projects hosted under the Linux Foundation, this eliminates the need to build operational capability from scratch. You don't need to file for nonprofit status, set up a bank account, or hire an accountant. The infrastructure exists.

This is a genuine advantage, particularly for projects that need to move quickly or don't have the resources to stand up an independent organization. The Linux Foundation's scale means it has established processes for everything from membership invoicing to conference logistics.

Community Governance vs. Corporate Governance

A dynamic that surfaces in many hosted projects — at the Linux Foundation and elsewhere — is the relationship between community governance and corporate governance.

The project's technical community — the engineers writing the spec or the code — operates by consensus, with influence earned through contribution and engagement. This is community governance. It's meritocratic in principle, even if it's imperfect in practice.

The project's organizational governance — the board, the membership tiers, the budget — operates by corporate governance rules. Board seats go to companies that pay the highest dues. Votes are cast by corporate representatives, not individual contributors.

These two governance models coexist within the same project, and they don't always agree. The technical community may reach consensus on a direction that the board doesn't support. The board may set priorities that the technical community doesn't share. Managing this tension is one of the most important — and most underappreciated — aspects of standards governance.

The best organizations acknowledge both models explicitly. They define which decisions belong to the technical community (spec content, architecture, feature prioritization) and which belong to the corporate governance (budget, membership, organizational strategy). When the boundary is unclear — as it often is — they have a process for resolving the conflict that doesn't require one side to simply override the other.

11.5 Competitive Dynamics in Governance

Standards governance exists in a competitive environment. The participants are often competitors, and the governance structure is a playing field on which competitive dynamics play out — sometimes constructively, sometimes not.

Constructive Competition

In a well-functioning standards body, competition drives better outcomes. Companies advocate for their technology, argue for approaches that align with their products, and push for specs that serve their customers. This is the intended dynamic. The process aggregates these competing interests and produces a specification that reflects some balance among them.

Destructive Competition

Sometimes participants engage for the purpose of slowing things down — not to improve the spec, but to prevent it from succeeding. A dominant incumbent may join a competing standards effort specifically to delay it, protecting their existing product from disruption. They'll propose endless amendments, argue every procedural point, and object to consensus without offering alternatives.

This is harder to detect and harder to counter than it sounds. In open source, you can overpower an obstructionist by committing more code. In standards, due process gives every participant a voice, and someone who contributes nothing technically can still exercise procedural rights. A small company that knows how to play the game can be remarkably effective at blocking progress — for good reasons or bad ones.

The flip side is also true. Standards give smaller companies power they wouldn't have in a purely market-driven competition. One vote per company, regardless of size, means that a startup with a good technical argument can prevail against much larger competitors. The process rewards preparation, persuasion, and persistence rather than raw market power.

The Substance-and-Process Dynamic

A pattern you'll see repeatedly: if you can't win on substance, you win on process. If you can't win on process, you win on substance. The most effective participants understand both and move fluidly between them. They know the technical arguments, but they also know the rules — voting thresholds, procedural requirements, charter limitations — and they use them strategically.

This is not cynicism. It's the reality of multi-party governance. The rules exist to create fair process. Understanding them well enough to use them effectively is part of being a competent participant.

This puts a premium on actually knowing the rules, especially in organizations that run on Robert's Rules of Order — and a surprising number do, including many ANSI-accredited bodies and most national-body delegations. Robert's Rules is several hundred pages of procedural detail, and most participants in the room have, at best, a vague memory of it from a high school student council. The participant who actually knows the rules — when a motion is debatable, when a point of order can be raised, what counts as a quorum, which supermajority threshold applies to which kind of motion, how to table versus postpone, how to call the question — has a structural advantage that has nothing to do with the merits of their position. He who knows the rules best wins. This is not an argument for studying Robert's Rules of Order Newly Revised cover to cover. It is an argument for knowing the procedural environment of every organization you operate in well enough that you don't get out-maneuvered by someone who does. At minimum, identify the one or two participants in each working group who actually know the rules. Either work with them or be ready for them.

11.6 Institutional Inertia and Organizational Evolution

Standards organizations, like all institutions, develop inertia. The rules that made sense when the organization was founded may not make sense ten years later. The membership that was appropriate for the initial scope may not be appropriate as the work evolves. The governance structure that worked for five companies may not work for fifty.

The challenge is that changing governance in a standards organization is hard. In a corporate entity, you amend the bylaws — a process that's well understood and has established legal mechanics. In a contractual consortium, you need every party to re-execute the agreement, which effectively gives everyone a veto. Even in organizations with formal amendment procedures, the political cost of proposing changes can deter anyone from trying.

The result is that many organizations operate under governance structures that no longer fit their reality. Working groups that have outgrown their charters. Membership tiers designed for a different era. Decision-making rules that were calibrated for a smaller group. The governance debt accumulates silently until a crisis forces the conversation.

One principle that helps: design for evolution from the beginning. Build amendment procedures that don't require unanimity. Use frameworks like JDF that allow working groups to be chartered and rechartered without renegotiating the organizational agreement. Separate the organizational governance (which should be stable) from the working group governance (which should be adaptable). The organizations that handle growth well are the ones that anticipated it.

And if the organization can't evolve, be prepared for the work to move elsewhere. The best way to prevent a fork is to make one unnecessary — by keeping the governance flexible enough to accommodate the community's changing needs. Or, as a practical matter: the best way to avoid forking is to allow forking. The threat of exit is what keeps institutions responsive.

The Longevity Problem

A related challenge is that standards organizations rarely die cleanly. Contractual consortia lose momentum as participants move on — but the agreement just sits there, and the spec remains in the field. Nobody formally winds down the organization. Nobody maintains the website. Ten years later, someone wants to implement the spec and there's no authoritative source, no point of contact, and no clear picture of what patent commitments are still in effect.

Incorporated entities have slightly better mechanics for winding down, but even there, dissolution is expensive and time-consuming. The more common outcome is a slow fade — meetings get less frequent, participation drops, the staff (if there was any) moves on, and the organization exists in name only.

For practitioners, this means thinking about longevity at the design stage. Where will the canonical spec live if the organization ceases to function? Are patent commitments durable beyond the organization's active life? Is there a successor organization or a repository that will maintain the materials? These questions feel premature when an organization is just getting started, but they're much harder to answer after the fact.

Modern approaches — hosting specs on GitHub, using durable frameworks like JDF that persist under the Linux Foundation's infrastructure — reduce this risk. But they don't eliminate it entirely. The governance structure should contemplate what happens when the work is done and the participants lose interest. Because they will.