The "How" of Enterprise Information Architecture
Summary
Enterprise IA problems are rarely caused by tricky information architecture. Instead, people and organizational problems manifest in bad IA. Sarah will share tools you can combine in different ways to help move your individual IA strategy forward.
Key Insights
-
•
Information architecture involves three core models: navigation, content (object), and information (taxonomies/metadata).
-
•
Most IA professionals rarely create traditional site maps; they focus on structural models instead.
-
•
The biggest challenge for IA in enterprises is not designing better systems, but getting organizational buy-in and ownership to implement changes.
-
•
A concrete, well-defined goal with clear final steps and resource needs is vital to making things happen in large organizations.
-
•
The political stream (internal worries and priorities) must align with problem and solution streams for successful change initiatives.
-
•
Enterprise change often requires working through product managers or backlog owners rather than relying on top executives like the CEO.
-
•
Small, visible wins (like installing a consistent header) can unlock momentum for bigger, more complex IA improvements.
-
•
IA experts need to understand organizational mechanisms and politics without losing their critical perspective or desire to improve things.
-
•
Building early credibility by being helpful on small tasks helps foster trust and support from other teams like developers.
-
•
UX and IA practitioners need to engage deeply with business realities and technical systems to have meaningful conversations and collaborate effectively.
Notable Quotes
"My job wasn’t to do good IA, it was figuring out how to be allowed to do good IA."
"The intellectually honest answer to most questions about information architecture is, I’m not sure, or it depends."
"Getting from terrible to not terrible is often more challenging than going from good to delightful."
"You can’t make anyone else care. We’re asking the wrong question."
"Windows of opportunity happen when problem, solution, and political streams align."
"Nobody cares about IA. If they did, they’d be IAs or at this conference."
"No amount of power is enough to make a wide-ranging agenda move forward on its own."
"If I do my job right, you never decide what goes in a dropdown again."
"This header took six minutes of IA work—but two years to make happen."
"Enterprise scale is what makes this hard, but also what makes it really satisfying."
Or choose a question:
More Videos
"Widgets are more than UI; they combine front end code, back end services, and analytics into a reusable package."
Dawn ResselFull-Stack User Experiences: A Marriage of Design and Technology
June 9, 2016
"Operations is the de-risking activity that creates scalable processes for better outcomes - Theresa."
Bria Alexander Patrizia Bertini Peter Boersma Jon Fukuda Dave Malouf Theresa Slate Changying (Z) ZhengCharting the future of DesignOps: A community workshop
April 18, 2024
"Communities are the glue that bring together work across silos, people, and practice."
Kara KaneCommunities of Practice for Civic Design
April 7, 2022
"We found out there wasn’t just one best in class solution and needed a hybrid approach."
Anna AvrekhUser Research, Design, and Product - A Love Story
March 11, 2021
"All your team wants to do is win at career Bingo or career Snakes and Ladders, hopefully more ladders."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"The product team and the product organization are not real estate agents and we don’t speak the same language."
Sean Fitzell Sarah Han Kayla FarrellCraft of User Research: Building Out Jobs to be Done Maps
March 12, 2021
"Design system contributors need help along the way—think of it like training wheels before they ride independently."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"Sketch made it possible to build a scalable library that millions of customers rely on with just a couple clicks."
Mitchell BernsteinOrganizing Chaos: How IBM is Defining Design Systems with Sketch for an Ever-Changing AI Landscape
September 29, 2021
"Growth boards helped us identify teams that hit their runway early and needed to pivot or spin down, reallocating resources strategically."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
