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 System Usability Scale’s question about needing a technical person to use the system is confusing and inaccurate for screen reader users."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"It's kind of Peace Corps for nerds – people come in for a tour and try to have impact at scale."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"We stuck with NPS because it was a pure metric with a long history we could trend, instead of muddying things with loyalty or revenue."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Leadership doesn’t only mean managing; it can be mentoring, product leadership, or technical influence."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The chief of staff can be a natural next step from a design program manager or design ops leader of one."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Self-service was a model with the most unknowns but possibly the biggest rewards."
Amy EvansHow to Create Change
September 25, 2024
"Super speed means enabling rapid onboarding by centralizing and streamlining a previously disparate process."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"The enterprise feels like a big elephant; different people touch different parts and argue what it really is."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"You have to push against 200,000 years of human evolution to get researchers to create reusable knowledge."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
Latest Books All books
Dig deeper with the Rosenbot
What are the best practices for organizing metadata and tagging in research repositories to balance structure and flexibility?
What lessons did Sean and Sarah share about sustaining knowledge management beyond the closure of a government design team?
How does design ops anticipate and prepare teams for technological disruption and evolving designer roles?