Summary
Peter Morville, a pioneer in information architecture, shares his journey from library science to helping organizations tackle complex information challenges. Through his work with Macy’s, he learned that surface-level fixes fail without deeper systemic change. At the Library of Congress, he encountered organizational culture as a barrier even when governance and authority were aligned for reform. His work with a database vendor revealed the tension between valuing complexity and the need for elegant simplicity. Morville underscores the evolution from viewing organizations as machines to understanding them as ecosystems, emphasizing systems thinking and the core role of context, connections, and culture in user experience. He discusses key models like fuzzy and centered sets for categories, the significance of keystone species in ecosystems, and the dynamics of changing culture through double loop learning. Drawing lessons from natural ecosystems, philosophy, and architecture, he advocates for mapping invisible systems and co-creating change within organizations. Throughout, Morville stresses the intertwined nature of information, culture, and design and calls for embracing organic simplicity inspired by nature to create better digital and organizational environments.
Key Insights
-
•
Surface-level improvements in information architecture often fail without addressing deeper organizational culture and governance.
-
•
Organizational culture can be a powerful barrier to change, even when authority and governance structures are in place.
-
•
Complex products can be resistant to simplification because cultures often celebrate complexity despite recognizing the need for simplicity.
-
•
Systems thinking helps us understand organizations as ecosystems rather than machines, requiring new models and metrics.
-
•
Categories are not always clear-cut; most have fuzzy or centered boundaries, which better reflect real-world cognition and culture.
-
•
Mapping connections in space and time reveals consequences and feedback loops that influence system behavior.
-
•
Context is central to information architecture and user experience; understanding user and organizational context is crucial.
-
•
Changing culture requires ‘double loop learning’—shifting underlying beliefs, not just behaviors—and is inherently difficult.
-
•
The concept of keystones in ecosystems is a powerful metaphor for critical elements that hold complex systems together.
-
•
Mapping invisible systems and sharing these maps are vital acts for collaboratively navigating complexity towards clarity.
Notable Quotes
"Every few years consultants come in and tidy up our mess, but as soon as they leave, we mess it all up again."
"The Library of Congress web presence was a findability nightmare, like the Winchester Mystery House."
"When you’re in a culture that celebrates complexity, making things simple is still a very hard thing to do."
"Categories are dangerous but not bad."
"Most categories are fuzzy; there’s no clear boundary between what’s in or out."
"We often use radio buttons when check boxes or sliders would reveal the truth."
"The system always kicks back—the consequences of our actions unfold over time."
"Changing culture is hard because we’re willing to change actions but resistant to changing beliefs."
"Information architects use nodes and links to create environments for understanding."
"When we understand organizations as ecosystems, we recognize the need for organic simplicity."
Or choose a question:
More Videos
"The role of the service designer shifts from design savior to facilitator, spacemaker, and guide."
Kyle GodbeyNon-linear service design for complex adaptive systems
December 10, 2025
"High quality personal connections mean you can engage on a level playing field with serious professionals."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"Start with quick wins, show value, and communicate loudly to get buy-in for more design ops capacity."
Rachel Radway Katie Bingham Joe WiertelThe Many Paths Of Design Operations
September 8, 2022
"When I started, I was the first designer among engineers who already prized ease of use as a key advantage."
JJ KercherA Roadmap for Maturing Design in the Enterprise
June 15, 2018
"Who do you see? Who do you not see? Why do you not see them?"
Brendan JarvisFraming Tomorrow by Questioning Today
June 8, 2022
"People product managers, program managers, and other partners will start to ask for design ops investment because they know it makes their product more successful."
Alnie FigueroaTeamwork: Strategies for Effective Collaboration with Other Program Management Teams
September 8, 2022
"In government, the motivation is reduction of misery: why are we up at 3 AM fixing something avoidable?"
Louis RosenfeldDiscussion: What Operations can teach DesignOps
November 6, 2017
"You need to come up with your own definition of design maturity based on your team’s understanding and context."
Francesca Barrientos, PhDYou Need Your Own Definition of Design Maturity
June 8, 2022
"We can stop gluing feathers to wings and flapping wings; static wings are the way to fly."
Dan WardFailure Friday #1 with Dan Ward
February 7, 2025
