Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Enterprise Information Architecture
Summary
We hear a lot of talk about “digital transformation.” But isn’t that what we’ve been doing since the Web emerged in the late 1990s? Why is this still so aspirational for so many organizations? In his consulting practice with Factor, Bram Wessel sees first-hand how enterprise-scale organizations are awakening to the reality that the information itself that drives experiences and gets implemented in technologies —the Information Layer, if you will— is increasingly a tangible organizational asset. As such, it’s as critical as any other kind of infrastructure. Bram joins Lou to ponder where we’ve been and where we might be headed in the realm of enterprise information architecture.
Key Insights
-
•
Information architecture evolved through three eras: technology, experience, and now the information era.
-
•
Early enterprise IA efforts were often undervalued, seen as an afterthought to implementing technology like CMS.
-
•
The information era recognizes information as a core organizational asset with real fiscal and strategic value.
-
•
Successful IA requires organizational alignment combining grassroots practitioners and senior champions.
-
•
Governance and a clear roadmap are critical to maintaining evolving information models within enterprises.
-
•
E-commerce taxonomy cannot simply be copied from merchandising structures; customer-facing navigation needs different taxonomies.
-
•
Many large organizations operate multiple unaligned information architectures across various systems causing costly data quality issues.
-
•
Enterprise IA maturity can be modeled in five stages from accidental silos to mastery with continuous improvement.
-
•
Taxonomy and ontology management tools like Synaptica, PoolParty, and Semaphore enable flexible, shared information models.
-
•
Fast-paced agile environments require parallel tracks for production and information strategy development with stable onboarding processes.
Notable Quotes
"There was a naive belief that just implementing content management systems would automatically make great experiences possible."
"We’re entering an information era because information itself is infrastructure and has actual monetary value."
"You need both a bottom-up and a top-down approach to achieve organizational alignment for information architecture."
"Customers can’t buy products they can’t find, and often that’s because product content isn’t related to non-product content."
"Organizational information models need to grow and be managed, not treated as static deliverables."
"Our role often feels like being information therapists – understanding pain and helping clients align their information."
"The first stage we see is the accidental stage with silos and no consistent information across the organization."
"Mastery means information is a strategic asset with quantifiable equity central to business identity and operations."
"You don’t need everyone to agree on every term, but you need governance to decide roles and approvals."
"In agile, you can’t move fast and break information strategy; you need a parallel track to feed changes into production."
Or choose a question:
More Videos
"If we wanted to scale and continue to grow, we were going to need something to help us."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Destiny is the belief that a certain future outcome is predetermined regardless of the path."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"Adobe’s Kickbox is a fantastic professional development tool, but it doesn’t drive new lines of business."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"Meeting designers where they spend their time, like integrating accessibility plugins into Figma, is the most effective way to make progress."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"We need to reject the notion that work is our only identity."
Tess DixonC'mon Get Happy
September 29, 2021
"Cross-functional relationships often matter more to output than relationships within the immediate team."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"Why don’t we do what we do for users but apply it to our own careers? Absolutely nutty, right? So we did."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"Context is really super important not only for design and research but for how you design organizations and ways of working."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"At Sage Sure, we build paved roads so people can choose to drive on them or carve their own path."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025