Taming Design Complexity with UX Models
Summary
Enterprise UX is incredibly complex and nuanced. Robert Reimann is the Senior Manager, UX Design at athenahealth, and in his talk at EUX 2017 he discusses how to improve the enterprise software user experience.
Key Insights
-
•
Enterprise software often prioritizes corporate goals over individual user needs, leading to poor user experiences.
-
•
Designing and scaling enterprise software is exceptionally complex, more so than consumer products.
-
•
Personas remain highly valuable in enterprise UX when based on rigorous user research and tailored to roles and skills.
-
•
Two-tiered persona models—broad suite-level and detailed module-level—help manage complexity and scope.
-
•
Non-user personas, including customers (buyers) and served personas, must be considered in enterprise design, especially in healthcare.
-
•
Data ecology and activity sequence models visualize how data flows and are critical for understanding user interactions with systems.
-
•
Organizational models reflecting formal and informal behaviors, as well as corporate culture, greatly impact the success of enterprise systems.
-
•
Different organizational cultures (clan, ad-hocracy, controlled, market) require distinct types of enterprise software support.
-
•
Concept maps are powerful tools for mapping complex objects and relationships in enterprise systems and beyond.
-
•
System models serve as a human-readable bridge between stakeholders and engineers, enabling alignment on system mechanics.
Notable Quotes
"Even with decades of UX thinking, many enterprise systems still feel stuck in the past and don’t deliver on their promises."
"Enterprise software mainly serves corporate goals but rarely serves people goals very well within the products."
"Designing enterprise software is not just complicated to use, it’s really complicated to design."
"Personas that aren’t based on customer data may ruin your product — that’s especially true in enterprise contexts."
"In enterprise products, personas are closely related to roles and skills, but user research is essential to understand needs."
"You need two tiers of personas: broad roles at the suite level and detailed flavors at the module level."
"Organizational DNA includes formal behaviors like policies and informal ones like communication styles that software must match."
"Corporate culture types—clan, ad-hocracy, control, compete—shape what software tools will succeed or fail."
"Concept maps are the best tool for managing complex webs of objects and relationships in a system."
"System models provide a human-readable level above the database, enabling stakeholder alignment on complex features."
Or choose a question:
More Videos
"Short-term learnings kind of roll into long-term ones as you iterate and build on historical findings."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Potential refers to not yet actualized possibilities that may or may not come to fruition."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"Hackathons are a fun activity to spend some creative time together and then go back to making the stuff that we normally make."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"Accessibility is more of a process than a result; it starts at the very beginning of product development with research including disabled users."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"If you don’t have the basics taken care of, infinite promotions and ping pong tables are just noise."
Tess DixonC'mon Get Happy
September 29, 2021
"Mastery is achievable, whether you have 10,000 hours or not—it’s about building that portfolio and case studies."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"Your career is a design project. It’s the only one you own, so own it like you would a product."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"One researcher per team for at least three days a week was considered an outrageous luxury at GDS in 2013."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"Without a design ops function, teams make their own flavors that dilute brand and accessibility."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
