Summary
The Internet and Web have reached a tipping point. We’re now witnessing the surfacing of harmful patterns and norms that we designed—often unintentionally—into our products, services, and communities, and the world we live in. Designers who work in the enterprise are, like their peers in startups and big dotcoms, vulnerable and culpable and need to consider some big questions: How well do we manage our data? How inclusive are our development practices? How broadly and deeply do we think about the impact of what we build and deploy before we scale it for our customer base? We need to move forward with intent. We need to govern our digital spaces. A necessary first step towards that goal involves designers examining—with honesty and introspection—our role in the creation of what’s online. The World Wide Web is nothing more than the accumulation of what digital makers have put there. We made this mess, and we need to talk about how we are going to clean it up. Digital governance expert Lisa Welchman will reflect on how 25 years of passionate and agile web development got us where we are today, and the consequences of the lack of self-governance by the digital maker community. She will show us a path forward from this mess, outlining questions we can ask and steps we can take to govern better what we have created and what we will create in the future.
Key Insights
-
•
Digital governance is fundamentally about decision making and organizational responsibility, not just tools or workflows.
-
•
Many digital governance failures stem from unclear ownership of strategy, policy, and standards within organizations.
-
•
Collaborative governance involves multiple levels: core strategy teams, distributed content makers, working groups, and community contributors.
-
•
External vendors often deepen digital silos if not properly integrated into governance frameworks.
-
•
Governance can be designed to enable speed and innovation, not just control or restriction.
-
•
The internet and digital technologies undergo a lengthy maturation cycle similar to historic technologies like automobiles.
-
•
Algorithmic biases often reflect organizational biases; fixing algorithms requires fixing institutions.
-
•
Proactive digital safety can be conceptualized like crash-test dummies for online systems, focusing on inclusivity, morality, and safety.
-
•
Participation in internet and web governance organizations like W3C or the Internet Society is crucial but underutilized by digital professionals.
-
•
Generosity and sharing cultures, as exemplified by the development of the three-point seatbelt, are critical for progressing digital governance.
Notable Quotes
"People can have the same values and ideas but if you don’t tune them properly, you just don’t get what you want."
"Digital governance is about who’s supposed to make the decision, not what the decision is."
"Governance isn’t the byproduct of a project; digital is a system you have to design and iterate continuously."
"You can’t expect people to comply with standards if you don’t know who they are."
"Your external vendors may not have your organizational best interests at heart because it’s not their business model."
"Governance frameworks can facilitate whatever pace or style of work an organization wants."
"Every bad thing that can happen in the real world can now happen on the internet — and every good thing too."
"Human biases are the real problem behind algorithmic bias because organizations embed those biases first."
"We are the fix — everything online is made by people, so we can change it together."
"Governance participation isn’t optional if you want to avoid reactive impositions down the line."
Or choose a question:
More Videos
"Having a back office support in place made it much easier to convince new researchers to join the team."
Veevi RosensteinBuilding for Scale: Creating the Zendesk UX Research Practice
January 8, 2024
"Think about who decides what, when, where, by which criteria and how these decisions connect—this helps influence decision making."
Silke Bochat5 Antifragile Strategies for a DesignOps 2.0
September 23, 2024
"Throwing away old methods for something new can unlock skills you didn’t know you had."
John DonmoyerShipping your code generation experiments to production
June 11, 2025
"These questions haven’t gone away as I speak and do workshops and things like that around the book."
Christian CrumlishIntroduction by our Conference Chair
December 6, 2022
"Encourage adoption by sharing documentation in relevant channels, referring team members to it, and including it in onboarding."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"DesignOps has an obligation to bring positivity back into design practice."
Dave Malouf Patrizia Bertini Jon FukudaThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 2)
April 28, 2022
"Without physical health, we cannot have creative health, and then we cannot have organizational health."
Alana WashingtonTheme 1: Introduction and Provocation
January 8, 2024
"Shared outcomes and shared goals are critical to any measurement initiative."
Kristin Skinner Kamdyn Moore8 Types of Measures in Design Operations
April 16, 2020
"Design ops isn’t rocket science, but between us it might actually be harder."
John Calhoun Rachel PosmanMeters, Miles, and Madness: New Frameworks to Measure the (Elusive) Value of DesignOps
September 24, 2024
Latest Books All books
Dig deeper with the Rosenbot
How did the Lab balance flexibility for individual project documentation with the need for an integrated knowledge system?
How does a knowledge management system help design teams adapt to rapid political and organizational changes in government?
How can organizations prioritize which research knowledge to include in their repositories?