Chapter 18: Closing Thoughts: What It All Adds Up To

When I started the Coffee & Standards series inside Microsoft, the goal was modest — help a handful of attorneys and engineers understand the machinery of standards well enough to spot the issues that mattered. What came out of those sessions turned into this book, and along the way the material got broader than I expected. We covered IP policies. Governance structures. Voting mechanics. Open source licensing. Antitrust. Due process. The convergence of standards and open source. The looming impact of AI. Twenty years of maxims about law, people, and practice.

That's a lot of ground. And it's worth pausing at the end to ask what it all adds up to.

18.1 The Arc of the Practice

Standards work looks technical from the outside — IPR policies, balloting procedures, normative references, necessary claims. But underneath the technical surface, every chapter of this book is really about the same handful of questions.

Who gets to decide? Governance design — member classes, voting thresholds, working group charters, appeals procedures — is fundamentally about how authority gets distributed among participants with different interests. Get this right and the process is productive. Get it wrong and you get paralysis, dominance, or exit.

Who bears the cost? Patent policy — RAND, royalty-free, non-assert, exclusion — is the economic architecture of a standard. It determines who can implement, on what terms, and how the value flows between innovators and adopters. The IP framework isn't a legal afterthought. It's the commercial engine.

Who bears the risk? Antitrust rules, due process criteria, disclosure obligations, and confidentiality provisions exist because standards activity brings competitors together in a room. The rules exist to ensure that collaboration stays on the right side of the line between pro-competitive coordination and anticompetitive behavior.

Who gets the legitimacy? The same due process features that protect against antitrust challenge also unlock government recognition — A-119, Regulation 1025/2012, the TBT principles. The process that earns legitimacy in one forum tends to earn it in all of them.

Every topic in the book reduces to some combination of these four questions. If you recognize them when they show up, you'll see the structure underneath any engagement.

18.2 The Themes That Kept Recurring

Rereading the chapters, a few themes run through almost every topic. They're worth naming.

Process is substance. How a decision gets made shapes what gets decided. The governance design isn't neutral plumbing — it encodes who has leverage, what tradeoffs are easy, and what objections get taken seriously. Practitioners who treat governance as an afterthought miss most of what's happening.

Standards commoditize; they don't revolutionize. Standards take a technology that's already largely settled and turn it into plumbing. The revolution happens somewhere else — in products, in research, in open source projects that nobody standardized. By the time a standard exists, the disruptive part is usually over. Understanding this keeps expectations calibrated.

The IP framework is the heart of it. If you only had time to understand one thing about a standards engagement, it would be the patent policy. Everything else — governance, process, voting — can be fixed. A broken IP policy, especially one that's been committed to over years of participation, is nearly impossible to unwind.

Convergence is the direction of travel. Standards and open source used to be separate worlds with separate frameworks, separate communities, and separate legal analyses. They aren't anymore. A practitioner in either world who doesn't understand the other is operating at a disadvantage — and the gap will only grow.

Optics and legitimacy matter. A standard developed through a process that looks fair carries weight that a substantively identical standard developed behind closed doors does not. This isn't cynicism; it's how the system actually works. Whether you're defending against an antitrust challenge, seeking government adoption, or trying to attract implementers, the perceived legitimacy of the process is part of the output.

Judgment beats formalism. Rules help, but every rule has edge cases. The practitioners who add value are the ones who understand the purpose behind each rule well enough to know when to apply it, when to adapt it, and when to recognize that the situation is outside the rule's contemplation.

18.3 What Standards Work Teaches You

There's a question I get asked a lot by lawyers earlier in their careers: is standards work a good place to spend time? My answer is yes — and not primarily for the reasons people expect.

Standards work will teach you IP. It will teach you antitrust. It will teach you governance design, contract drafting, and organizational strategy. Those are real substantive skills, and there are worse places to learn them.

But the durable lessons from standards work aren't the doctrinal ones. They're the ones about how institutions actually function, how people behave in groups, and how decisions get made in rooms full of people with different interests.

You learn that relationships are the substrate everything else runs on — that the person across the table today will be across the table again next year, and your reputation carries from one engagement to the next. You learn that diplomacy is a professional skill, not just a personality trait. You learn to distinguish what you want to argue from what you need to win, and to save your capital for the battles that matter. You learn that process and substance are the same thing seen from two angles.

You also learn humility. Standards work surrounds you with technical people who are very good at what they do, from industries you've never worked in, solving problems you don't fully understand. The lawyers who thrive in this environment are the ones who keep learning — who make their clients smarter and let their clients make them smarter in return. The lawyers who struggle are the ones who stay in their wheelhouse.

None of this is unique to standards. What's unique is that standards work concentrates all of it in a relatively small professional community with unusually long time horizons. It's the kind of environment where you can spend a career and still be learning. That's rare, and it's worth appreciating.

18.4 Coffee & Standards

The original sessions that seeded this book were called Coffee & Standards because that's literally what they were — a standing invite to grab coffee and talk through whatever was on my mind that week. No slides. No required reading. Just a conversation about the practice.

I've tried to keep that feel in the book. Some chapters are more technical than others. Some are more personal. The goal throughout was not to produce a treatise but to produce something that reads the way I'd explain this material to a colleague at the coffee machine — with the rough edges left in, the analogies deployed freely, and the judgment calls flagged as judgment calls rather than dressed up as settled law.

If you've read this far, a few parting thoughts:

Treat this book as one practitioner's perspective, not the last word. The range of reasonable in standards work is wide. Other practitioners will disagree with positions taken here, and some of those disagreements will be well-founded. Read, adapt, and form your own view.

Don't confuse the map with the territory. This book describes a system of IP policies, governance structures, and procedural rules. The system is real, but it's not self-executing. The actual work happens through conversations, drafts, meetings, and relationships. The frameworks in these chapters are tools for navigating the actual work. They are not substitutes for it.

The people make it worth doing. Over two decades I've been fortunate to work with engineers, attorneys, policy staff, and business leaders across dozens of organizations and many countries. The technical problems are interesting. The institutional puzzles are fascinating. But the people — their generosity, their humor, their willingness to engage across differences of company and country and interest — are the reason this practice is something I'd happily do all over again.

If there's a central claim in this book, it's that standards work rewards practitioners who combine substantive rigor with human judgment, and who understand that the two are not in tension but in harmony. The frameworks are the scaffolding. The people are the building. Both matter.

Thanks for reading. Happy to chat.

— David