Site icon Spherical Cow Consulting

Appeals Are Not Failures

Heather Flanagan

A hand connects puzzle pieces on a black background, completing a task or solving a problem. Artistic rendering of consensus building.

“I have written before about how different standards organizations are structured. I have also written about what it is like to be a working group chair or a contributor.”

A lot of that writing focuses on the ordinary work of standards development: building proposals, discussing tradeoffs, improving drafts, finding rough agreement, and moving work forward.

That is the happy path. Or, more accurately, that is the path we like to imagine when we talk about consensus-based standards development.

But consensus does not always happen cleanly. Sometimes the disagreement is not just a passing concern, a bikeshed, or a “please fix this before publication” comment. Sometimes a participant believes the group is about to make a decision they cannot accept. Sometimes they are willing to say so formally, loudly, and on the record. And standards’ processes offer them a way to do that.

In W3C, this can become a Formal Objection. In the IETF, this can become an appeal. Other standards organizations have similar ways to escalate disputes when the normal working group process has not resolved the issue. For simplicity, I’ll use appeal as the generic term in this post, while using Formal Objection when I’m talking specifically about the W3C process.

Here is the part that is easy to forget when you are in the middle of it: An objection or appeal is not automatically a failure of the process, nor is it automatically an attack on the people involved.

That does not mean it is fun. People are pretty passionate when it comes to developing standards, and being told they are wrong doesn’t make anyone happy.

Still, it is an important part of how consensus-based organizations protect themselves from pretending consensus exists when it does not.

A Digital Identity Digest
Appeals Are Not Failures

You can Subscribe and Listen to the Podcast on Apple Podcasts, or wherever you listen to Podcasts.

And be sure to leave me a Rating and Review!

Consensus is not unanimity

Standards development depends on consensus, but consensus is not the same thing as everyone being delighted.

If you have spent any time in standards work, you know this already. A room full of smart people with different priorities, business models, legal constraints, deployment realities, and architectural instincts will not always land in the same place.

The work of a group is not to eliminate disagreement. The work is to understand the disagreement well enough to know whether the group can still move forward.

W3C’s process recognizes this explicitly. A group may need to make a decision even where there is dissent, provided the legitimate concerns of dissenters have been duly considered as far as possible and reasonable. The process also notes that dissenters can escalate a sustained objection by registering a Formal Objection. (W3C)

A person can disagree and still live with the decision. They may think the group chose the second-best option. They may believe the wording could be better. They may wish the architecture had gone another way. Again, that is normal standards work.

A sustained objection is different. It means someone believes the decision is serious enough that it needs formal review.

That is not something to dismiss casually. It is also not something that should give any one participant a veto over the group.

And yes, that balance is exactly as easy as it sounds. Which is to say: not very.

Formal processes exist because working groups can get too close to the problem

Most working group conflicts should be resolved inside the working group.

That is where the technical expertise is. That is where the history of the discussion lives. That is where the people most likely to understand the tradeoffs are already engaged.

But sometimes the working group cannot resolve the conflict on its own. Maybe the disagreement is procedural. Maybe one side believes its concern was not fairly considered. Maybe the issue touches broader architectural, policy, legal, or organizational questions. Maybe the group has reached the point where every argument has been made three different ways, and nobody is moving.

At that point, escalation is not necessarily a sign that the group failed. It may be the mechanism that lets the broader organization bring in people with more distance from the day-to-day debate.

An appeal is not merely a note in the record saying, “I am unhappy.” It is a moment where someone can say, “This is wrong, and the result needs to change.”

The process then creates space for people who are not quite so deep in the weeds to review the arguments for and against that position. They can look at the decision, the objection, the group’s rationale, and the broader implications with more distance than the working group may have had by that point.

That outside review is the value of the process. It does not guarantee that the objection will prevail. It does mean the objection receives a structured, documented, and more neutral review before the organization decides whether the group’s decision should stand.

Please note that I don’t want people to think that an appeals process should be considered a routine “fresh eyes” mechanism. This is a serious escalation tool and is expensive in terms of time and resources for a standards organization to process. The tone should preserve that seriousness while still rejecting the idea that they are hostile or illegitimate.

The chair’s first job: do not take it personally

As a working group chair who has dealt with appeals related to my working group, my first piece of advice is simple:

Do not take it as a personal attack. (I know, easier said than done.)

When you have spent months, or years, helping a group move work forward, an objection can feel like a judgment on your leadership. It can feel like someone is saying you were unfair, careless, biased, or asleep at the wheel. Sometimes they may even say something close enough to that to make your coffee taste worse.

Still, do not start there.

Start from the assumption that the objector is using a process available to them because they believe the decision matters. They may be right. They may be wrong. They may be partly right in ways that are inconvenient for everyone. Standards work has a way of producing that last category with alarming efficiency.

Your job as chair is not to win against the objector. It is to ensure the group’s process is understandable, fair, and well-documented.

That means the record matters. Meeting notes matter. GitHub issues matter. Mailing list threads matter. Decision records matter. The rationale for closing an issue matters. The explanation of why one option was chosen over another matters. It all matters not because documentation is magical, because it isn’t. Documentation will not make everyone happy.

What documentation does is let people who were not in every meeting understand what happened. It lets reviewers distinguish between “we ignored this concern” and “we considered this concern and still made a different decision.” Those are not the same thing.

The threat of objection should not control the group

There is another trap chair and editors need to avoid: changing behavior because someone threatens to object.

Participants should know that a Formal Objection or appeal is an available option. That is part of the process. I would go so far as to say chairs should make that clear when a group is approaching a decision that some participants cannot support.

There is nothing wrong with saying, in effect:

The group appears to be moving toward this decision. If you believe this decision creates a serious technical or procedural problem that you cannot accept, the process gives you a way to raise that formally.

That is not an invitation to grandstand. It is an acknowledgment of the rules. The threat of an objection should not become a lever that changes how the chair runs the group. Do not shortcut consensus because someone is threatening to object. Do not avoid calling a decision because someone is threatening to object. And definitely, do not give one participant’s concern more weight merely because they used capital letters, invoked process language, or made everyone in the meeting deeply interested in the exact time.

Make the best decision the group can make. Make sure the concern has been heard. Make sure the response is substantive. Make sure the record is clear. Then move forward according to the process.

If the objection comes, the group should be able to show its work.

That is the goal. Not perfection. Not universal happiness. A clear, fair, reviewable process.

Neutral review is a feature, not an insult

One of the hardest parts of escalation is letting other people review the situation.

That can feel uncomfortable. Chairs are used to being responsible for the group process. Editors are used to defending the text. Participants are used to arguing from their own lived history of the work.

But when a dispute escalates, the ability to bring in a more neutral view is exactly the point.

In W3C, the Team first investigates and mediates the Formal Objection, trying to understand the issue and the viewpoints involved. If the issue cannot be resolved, the matter may go to a W3C Council, which is tasked with deciding whether to affirm or overturn the decision being objected to. (W3C)

W3C’s less formal guide to the Council process makes the human reality clearer: there are steps for trying to resolve the objection before starting the full process, producing a Team Report, forming a Council if needed, reaching a decision, and writing a report. It also notes that withdrawal of the Formal Objection is the best outcome and should always be sought.

The best outcome is not always “the objector loses” or “the group wins.” Sometimes the best outcome is that the concern is better understood, the document is improved, the rationale is clarified, and the objection is withdrawn.

Good objections can improve standards

Here is the positive case for appeals: they can make standards better.

A well-formed objection forces clarity. It asks the group to explain what it decided and why. It may surface a real architectural issue, a fairness concern, an accessibility problem, an internationalization gap, a privacy risk, an implementation burden, or a process problem that the group did not take seriously enough.

That does not mean every objection is correct. Some objections are weak. Others are late or are attempts to relitigate decisions that were already discussed thoroughly. Some are, let us say, more energetic than helpful.

But a process that only works when everyone behaves perfectly and agrees on everything is not much of a process.

The point is not that every objection should prevail. It’s more that serious objections should receive serious review. That review protects the objector, yes. It also protects the group. It protects the standard. It protects the organization’s credibility.

Consensus-based standards bodies depend on trust. Participants need to believe that decisions are not made merely by who has the most people in the room, the loudest voice on the call, or the most patience for email threads that should probably have ended three Tuesdays ago.

Formal escalation mechanisms help maintain that trust.

Advice for contributors: be clear about what you need

If you are a contributor considering an appeal, be precise.

If your answer is “I do not like this outcome,” pause. That may be true, but it is not enough.

If your answer is “I believe the group failed to consider this specific issue, and here is the decision record showing why,” that is more useful.

The stronger your objection, the less it should rely on speculation about motives. The IETF’s statement is refreshingly direct here: appeals are expected to contain factual information and reasoned argument, and to avoid speculation, conjecture, characterization of intentions, or personal accusation.

That is good advice well beyond the IETF. Argue the decision, the process, or the technical consequences. Do not argue motive.

Advice for chairs: keep your ducks in a row

If you are chairing a group, the best time to prepare for a possible appeal is long before anyone says the words “I’m going to submit an appeal.”

That preparation is not defensive. It is good chairing. You’ll want to make sure issues are tracked, decisions are recorded, and dissent is captured accurately. Make sure participants understand when the group is discussing, when it is deciding, and when a decision has been made. Make sure objections receive substantive responses, not just “the group disagrees” and that people know what options remain open to them. Honestly, you should be doing this as a matter of course. It’s your job as chair.

This does not mean turning every working group into a courtroom. Please do not do that. Standards work already has enough procedural gravity.

It means creating a record that reflects reality: what the group discussed, what concerns were raised, how the group responded, and why the chair determined that the group could move forward.

If an objection happens, others should be able to follow the sequence of events without reconstructing the entire history from folklore, hallway conversations, and the emotional residue of one particularly memorable meeting.

Appeals are part of the system

The longer I work in standards, the more I appreciate the processes that let people disagree formally.

Not because I enjoy conflict. I really do not; it can be exhausting. I enjoy well-scoped agendas, clear issue tracking, and meetings that end early. It’s delightful when it all works out that way. But my enjoyment doesn’t really matter as disagreement is part of the work. The question is not whether standards organizations can avoid conflict because, frankly, they shouldn’t. The question is whether they can handle conflict in a way that is fair, documented, and oriented toward progress.

An appeal is not automatically a sign that something has gone wrong. Sometimes it is a sign that the process has reached the point where the disagreement needs more structure, more review, and more distance.

That is not the happy path, but that doesn’t make it wrong. When handled well, it can leave the group, the standard, and the organization stronger than they were before.

📩 If you’d rather receive an email than hope you catch the social media announcement when a new post is live, I have an option for you! Subscribe to get a notification when new blog posts go live. No spam, just announcements of new posts. [Subscribe here] 

Transcript

Standards organizations are built on consensus. In fact, if you spend enough time around Internet standards work, you start hearing the word constantly.

There are consensus calls, consensus decisions, rough consensus discussions, sustained objections, and endless conversations about whether a group has enough support to move forward.

When the process works well, it can feel surprisingly elegant.

A group starts with a difficult technical problem. People bring different deployment realities, business constraints, architectural opinions, and use cases to the table. Then, after plenty of debate and revision, the group eventually reaches a decision most participants can live with.

Nobody gets everything they wanted. However, the work moves forward.

That is the happy path.

When Consensus Does Not Come Easily

Of course, the happy path is not the only path.

Sometimes disagreement runs deeper than wording preferences or editorial concerns. Occasionally, someone believes the group is making a fundamentally wrong decision.

When that happens, standards organizations typically provide a formal escalation process.

At the W3C, that mechanism is called a Formal Objection. In the IETF, the equivalent process is generally referred to as an appeal. Other organizations use different terminology, but the goal is largely the same:

Importantly, an appeal is not automatically a sign that the process failed.

In many ways, it is actually evidence that the governance process is functioning as intended.

Appeals Are Part of Governance

It is easy to view appeals as personal attacks, especially for working group chairs.

After all, chairs often spend months or years helping move work forward. They organize meetings, track issues, summarize debates, respond to concerns, and try to maintain forward momentum through highly technical discussions.

As a result, hearing someone formally say, “This decision is wrong,” can feel deeply personal.

However, that reaction can be misleading.

An appeal is not necessarily an accusation of incompetence or bad faith. Instead, it is a procedural tool designed specifically for consensus-based organizations.

Its purpose is simple:

Someone believes the group reached the wrong conclusion, and they want broader review outside the immediate working group.

That outside review matters because working groups can become extremely close to their own work. Over time, participants may:

Consequently, an appeal creates an opportunity for fresh perspective.

That does not mean the objection automatically succeeds. Appeals are not vetoes. A participant cannot simply stop the work because they feel strongly about an issue.

Instead, the process ensures the concern receives formal consideration.

What a Good Appeals Process Should Do

A strong appeals process serves multiple purposes simultaneously.

First, it gives the objecting party a meaningful way to challenge a decision.

Second, it allows the working group to explain the reasoning behind its decision.

Finally, it gives reviewers enough context to evaluate the technical, procedural, and organizational implications involved.

Ultimately, the organization decides whether the original decision should stand.

That is not dysfunction. That is governance.

At the W3C, for example, a Formal Objection is a serious escalation mechanism. It is not simply a way to say, “I am unhappy.”

Instead, it communicates something much more specific:

“This decision is wrong, and here is why it needs to change.”

Reviewers can then examine:

Importantly, the process does not guarantee any particular outcome.

The objection may succeed. It may fail. The group may revise the specification, clarify language, or maintain the existing decision entirely.

What matters most is that the concern receives structured review.

Why Documentation Matters

For working group chairs, preparation for a possible appeal begins long before anyone uses the word “appeal.”

In practice, it starts with good process hygiene.

That may not sound exciting, but it becomes critically important later.

Chairs need to ensure the group is:

Simply saying, “The group disagrees,” is rarely sufficient.

A stronger process record explains:

This does not mean turning standards work into a courtroom. Standards development already contains enough procedural gravity.

Instead, the goal is clarity.

If an appeal occurs, reviewers should be able to understand the sequence of events without reconstructing history from fragmented mailing list threads, hallway conversations, or emotionally charged GitHub debates.

Good documentation protects everyone involved:

Appeals Should Not Control the Group

Another important point for chairs is this:

The possibility of an appeal should not dictate how the group operates.

Participants absolutely should know formal escalation paths exist. In fact, chairs should communicate that openly when difficult decisions approach.

There is nothing wrong with saying:

“The group appears to be moving toward this decision. If you believe it creates a serious technical or procedural problem, the process provides mechanisms for formal escalation.”

That is not inviting drama. It is acknowledging the rules.

However, chairs should avoid allowing appeal threats to distort consensus-building itself.

For example:

Instead, chairs should focus on helping the group reach the best decision possible while maintaining a clear and fair process record.

If an appeal eventually happens, the group should simply be able to show its work.

Advice for Contributors Considering an Appeal

For contributors, the situation looks somewhat different.

If you are considering an appeal, clarity becomes extremely important.

Specifically, ask yourself:

Simply saying, “I do not like this outcome,” is not enough.

Strong objections remain disciplined and focused.

The best appeals avoid speculation about motives or personal attacks. Instead, they concentrate on:

That distinction matters.

Standards work often involves real stakes. Companies may have products in development. Communities may have concerns about privacy, accessibility, security, interoperability, or competition.

People may have invested years trying to ensure particular problems are not ignored.

Nevertheless, appeals become far more effective when they stay grounded in evidence and process rather than assumptions about intent.

Appeals Can Improve Standards Work

Not every appeal is destructive.

In fact, some appeals improve the standards process significantly.

A well-formed objection can:

Sometimes the final result is not that one side “wins” or “loses.”

Instead, the process produces a stronger outcome overall.

The group may clarify ambiguous text, narrow scope, strengthen rationale, or improve implementation guidance.

Occasionally, concerns are addressed so effectively that the objection itself is withdrawn.

That is not procedural failure.

That is success.

Standards Organizations Need Formal Disagreement Mechanisms

Of course, not every appeal is equally strong.

Some arrive late. Some attempt to reopen extensively discussed issues. Others confuse “I dislike this result” with “the process was broken.”

That happens.

However, a process that only functions when everyone behaves perfectly is not much of a process at all.

Consensus-based organizations need structured ways to handle serious disagreement while still allowing work to move forward.

That balance is difficult, but necessary.

Over time, one of the most valuable aspects of standards governance becomes the ability to disagree formally without collapsing the process entirely.

Conflict is unavoidable.

The real question is whether organizations can handle disagreement fairly, transparently, and productively.

Final Thoughts

Appeals are not the happy path in standards development.

However, they remain an important and legitimate part of the process.

When handled well, they can strengthen working groups, improve specifications, and reinforce the credibility of the organization itself.

And sometimes, that is exactly what good governance is supposed to do.

Exit mobile version