First-time users, longtime strategies: Why Parkinson’s Law is making you less effective at work – and how to design a fix.
Summary
The speaker begins with a personal anecdote about frustration with British Airways’ enterprise systems, setting the stage for discussing the broader challenges users face with complex technology in large organizations. Drawing on historical examples such as the British Royal Navy's shift from coal to oil and the growth of the Admiralty staff, the speaker introduces Parkinson’s Law—coined by Cyril Northcoat Parkinson—which humorously explains why bureaucratic work steadily grows regardless of actual workload. The talk then transitions into the persistent complexity of enterprise software, citing Larry Tesler’s question of who should shoulder this complexity. Examples are shared from air traffic control, expert photo editing, and government tax and rights management systems to illustrate different levels of user expertise and system fitness for task. The speaker emphasizes the importance of designing systems not just for ease of use but for task fit and context, acknowledging the inevitability of some complexity. A telecom case study shows how redesigning and consolidating multiple legacy systems into a single interface (one screen) took years of cross-disciplinary collaboration and political navigation to improve business outcomes like reduced errors and increased efficiency. The speaker highlights the need for precise, measurable goals tied to business value rather than vague notions of 'great user experience.' Methods like impact mapping and value proposition design are shared as emerging approaches to align UX and product management work with organizational strategy. The talk closes by advocating that designers must engage deeply with technology choices and organizational politics to shape meaningful, scalable user experiences in enterprise contexts.
Key Insights
-
•
Parkinson’s Law explains why bureaucratic workforces grow regardless of actual workload, driven by middle managers creating more work to feel important.
-
•
Enterprise users often remain 'first-time users' due to constantly changing and complex systems without adequate training or support.
-
•
Larry Tesler’s question highlights the burden of software complexity: should it lie with users or designers? Often complexity is passed on to users.
-
•
Fitness for task is a more useful framework than simple usability or ease, since some complex tasks inherently require complex tools and expertise.
-
•
Improving enterprise software usability can involve simplifying tools, shifting or reducing complexity, revising procedures, or reengineering entire value chains.
-
•
Clear, measurable goals rooted in business impact are critical to justify and guide UX and product efforts in complex enterprises.
-
•
Designers must participate in strategic decisions around platform choice and organizational processes to influence long-term user experience outcomes.
-
•
Integration and consolidation of fragmented legacy systems into unified, user-centric platforms can drastically improve efficiency but requires patience and political skill.
-
•
Training and hiring experts for complex domains (e.g., air traffic control) is acceptable, but general enterprise users deserve simpler, fit-for-purpose tools.
-
•
Combining impact mapping, value proposition design, and agile delivery can help teams stay aligned on delivering user and business value in product development.
Notable Quotes
"Something’s going to go wrong. You know, something went wrong."
"What you want is a multiplication so that you can have people do the same work but have more people doing it so you'll feel more important."
"The new challenge of adulthood is keeping your cool in the face of broken technology as demands are placed upon you to perform very well."
"Users are not interested in learning the intricacies of the British Airways website. I have to deal with many different airline websites."
"It’s better to be honest about it: it’s actually very hard. It’s not impossible, but it’s hard and it takes a long time."
"You can’t convince any organization into having some great user experience by saying it would be nice for it to be simpler."
"If you say great user experience, no, it’s not specific, it’s not measurable, it’s not actionable."
"We want to reduce the time it takes from somebody starting in this role to be fully fluent with the system by a factor of four."
"There’s no point in sitting in your office because there’s no new information available there. Everything is probably pre-filtered."
"If the system is difficult, the users have a big burden upon them. And in some cases, that’s just how it is."
Or choose a question:
More Videos
"A taxonomy system is basically a way to tag different findings and reports so you can find relationships later."
Tony TurnerCapturing Deep Insights
September 30, 2021
"Government might expand its self-perception from service provider to facilitator who partners with constituents."
Frances Yllana Ann Buechner Jess Jones Betsy RamacciaD.E.A.R.R. Diaries (Discipline, Experience, Architecture, Reflection + Revolution)
November 16, 2022
"How do we continuously provide value throughout the product development cycle without overindexing on just one type of research?"
Anna Poznyakov Richa PrajapatiGet The Most Out Of Stakeholder Collaboration—and Maximize Your Research Impact
March 12, 2021
"Principles at this level act like a company mission that product teams can translate into their own more specific design principles."
Sarah WilliamsA Framework for CX Transformation
June 11, 2021
"Good UX is good business."
Product and Design at Bloomberg: A 15-year Evolution
December 6, 2022
"Prototyping and co-creation workshops have been a huge accelerant to the design process."
David CroninThe GE Design System and Thoughts about Craft at Scale
May 13, 2015
"This emerging AI technology has given us a golden opportunity to combine the heart and brain of technology and make meaningful impact."
Liwei DaiThe Heart and Brain of the AI Research
March 31, 2020
"Without a golden dataset, you have to build the golden dataset yourself."
Peter Van DijckHands-on AI #1: Let’s write your first AI eval
October 8, 2025
"Each team should talk about their core values like integrity, accountability, and respect to work together with the same mindset."
Jon Fukuda Amy Evans Ignacio Martinez Joe MeersmanThe Big Question about Innovation: A Panel Discussion
September 25, 2024
