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
"We keep our playbook in a place where anyone can edit it from the team."
Maria SkaadenPanel Discussion: Methodologies and Work Environments
November 8, 2018
"We underestimated the amount of work; each workshop took about 40 hours per person to prepare and run."
Elizabeth Sklar Jessica ShengCo-creating research enablement with your tech org: a case study
March 10, 2026
"You don’t have to overhaul your process to be inclusive; small changes embedded across stages make a huge difference."
Gabriela BarnevaOperationalizing Inclusive Design in Design Ops
September 11, 2025
"Space is congested, with thousands of satellites and tens of thousands of debris pieces orbiting Earth."
Michal Anne RogondinoSaving Outer Space: The First UX Design System for Our Nation’s Satellites
January 8, 2024
"Some situations are not worth saving. If you have no champion, no clarity, and no purpose, is it worth it to continue?"
Shahrzad SamadzadehWhat Is My Value? Two Takes and Some Mistakes
January 8, 2024
"Having a shared understanding of roles really cuts down on interpersonal tensions during team formation."
Ivana NgLevel Up Your Program with ProductOps
January 8, 2024
"We can no longer think of users as flat personas; we have to enrich those concepts with intersectional identities."
Lija HoganContexts of Use: A Framework for Connection
December 9, 2021
"You can’t just break apart these components and type; instead, you change their properties to adjust labels, colors, or icons."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"Even when we bring the data together, we’re still not necessarily synthesizing very well."
Brad Peters Anne MamaghaniShort Take #1: UX/Product Lessons from Your Industry Peers
December 6, 2022
Latest Books All books
Dig deeper with the Rosenbot
What are the benefits of linking AI-powered research repositories with tools like Slack for organizational adoption?
What are the best practices for editing research stories to balance completeness and clarity?
How do I handle tagging and linking to existing related work without overwhelming myself?