Summary
The speaker opens by recounting their frustrating experience with the British Airways system, highlighting typical enterprise system issues where users become perpetual first-time users due to complexity and poor design. They reference the British Royal Navy's transition from coal to oil and the consequent rise in Admiralty staff, linking it to Parkinson's Law, introduced by Cyril Northcote Parkinson, which explains bureaucratic growth driven by self-serving work multiplication. The talk discusses the challenge of complexity in enterprise software, citing Larry Tesler's question about who must bear this complexity, and stresses that users often shoulder burdens born from legal, technological, and organizational constraints. Using examples from airport radar systems, expense reports, traffic control, and a major telco’s system overhaul, the speaker illustrates the trade-offs between ease of use and power, the need for training for expert users, and the benefits of rethinking entire value chains. They recount how simplifying tools combined with clear, measurable business outcomes like reducing training time or errors can drive adoption and improvements. The speaker also highlights working closely with organizational stakeholders, pacing projects, and integrating UX with product management through methods like impact mapping and value proposition design, advocating for goals that focus on value delivered rather than vague notions of 'great UX.' Overall, the talk calls for patience, strategic thinking, and a holistic grasp of technology, politics, and business to create meaningful improvements in enterprise user experiences.
Key Insights
-
•
Enterprise users are often perpetual first-time users due to complex and infrequent system interactions.
-
•
Parkinson's Law explains bureaucratic growth as self-reinforcing work creation among middle management.
-
•
Complexity in enterprise systems often shifts the burden onto users rather than eliminating it.
-
•
Training and revising procedures can sometimes be better solutions than redesigning interfaces.
-
•
Powerful tools require users to become part of the system through mastery, trading ease for control.
-
•
Simplification efforts must be tied to clear, measurable business outcomes to gain organizational support.
-
•
Redesigning entire value chains can lead to major UX improvements rather than incremental tweaks.
-
•
Designers need strategic, technical, and political savvy to influence platform and organizational decisions.
-
•
Users are generally not interested in learning new systems deeply, especially for infrequent tasks.
-
•
Combining impact mapping with value proposition design helps keep product teams focused on real value.
Notable Quotes
"Enterprise experience is often about broken technology and users having to keep their cool under pressure."
"You want subordinates, not helpers, because helpers can become rivals – that’s Parkinson’s Law."
"Once automation is running, support staff get cut and users have to manage more complex systems themselves."
"Users aren’t interested in learning intricacies of systems they use infrequently – they want fit for task."
"If the system is difficult, sometimes all you can do is watch a movie and feel better later."
"Designers have to be part business, part political, and part technical to influence big system changes."
"Great user experience is not a goal. You need specific, measurable goals like reducing training time by four."
"Simplifying systems takes patience and happens slowly, often involving years of work and negotiation."
"When users are expert in their domain but novice to the system, usability is critical to reduce errors."
"Sometimes fixing tax systems by leveraging existing data completely removes user burden and errors."
Or choose a question:
More Videos
"The blueprint is really within all of us — all the things that have brought us to this moment should come to our teams."
Jennifer KanyamibwaCreating the Blueprint: Growing and Building Design Teams
November 8, 2018
"In large organizations, research teams usually pay for the repo but the value is delivered across the whole company."
Brigette Metzler Dana ChrisfieldResearch Repositories: A global project by the ResearchOps Community (Videoconference)
August 27, 2020
"We assigned people to attend other teams’ meetings to help with integration and started being seen as leaders."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"If you want to bring dots closer together, you have to constantly notice how things change in the moment."
John Mortimer Milan Guenther Lucy Ellis Patrick QuattlebaumPanel Discussion
December 3, 2024
"Recruiters are often optimized for technical hiring and design is only one percent of the company’s population."
Dante GuintuHow to Crush the Talent Crunch
September 8, 2022
"Sustainability is dead because we don’t know what to sustain; we need to create flourishing communities instead."
Richard BuchananCreativity and Principles in the Flourishing Enterprise
June 15, 2018
"Melinda Belcher has had great success first as an outside consultant and then as an inside enterprise manager."
Dan WillisTheme 3: Intro
January 8, 2024
"Innovation is novelty with impact — three words to remember."
Dan WardFailure Friday #1 with Dan Ward
February 7, 2025
"Let’s shake s*** up."
Chris GeisonTheme Two Intro
March 28, 2023