Summary
With curation and support from Dan Willis, eight presenters told their enterprise UX stories: Kim Bieler, Jane Bungum, David Cain, Audrey Crane, Lada Gorlenko, Jordan Koschei, Liu Liu, and Eva Miller.
Key Insights
-
•
Enterprise users often resist new tools that seem to add work without clear personal benefit, as Dave found with application inventory tracking.
-
•
Successful design integration with engineering teams requires building trust and listening rather than relying solely on standard presentations, as Audrey experienced.
-
•
Clients may push for vague aesthetic changes like 'jazzier and sexier'—decoding such feedback is critical to delivering actionable designs, as Jordan learned.
-
•
Meditation and mindfulness practices can help designers manage the mental complexity and imposter syndrome common in large-scale projects, shared by Lou.
-
•
Enterprise design skills are often undervalued in agency hiring, though they involve solving deeply technical and organizational challenges, emphasized by Lada.
-
•
Early architectural decisions, like using MongoDB for a data-heavy UI, can become technical debts if not revisited as product needs evolve, as Kim revealed.
-
•
Diffuse responsibility and lack of communication within teams can prevent necessary technical changes until someone steps up to coordinate, demonstrated in Kim’s story.
-
•
Physical tools, simple documentation, and reducing reliance on user interfaces can greatly improve usability in noisy, constrained enterprise environments, shared by a design team.
-
•
In enterprises, appearing busy often trumps doing thoughtful work, contributing to resistance against workflow changes, as Dave illustrated.
-
•
Designers must balance educating clients on design thinking while respecting enterprise processes, turning disappointments into learning opportunities, advised by Jordan.
Notable Quotes
"People in the company knew I’m a problem solver and I’m good with ease of use."
"Everybody loves Excel, and we can’t run reports against Excel."
"It’s more important to appear to be doing something than to appear to be thinking about something."
"Programmers will keep fixing what’s not broken until it is broken."
"I should have been a human first and a designer second."
"It’s okay. I just wish it were a little bit jazzier and sexier."
"Anytime you have to justify something by saying just this one time, you know you’re going down a bad road."
"The harder I think the further I am from the answer."
"Are we bold enough to ditch the user interface in favor of a better experience, a transparent one?"
"Enterprise problems are often engineering problems as much as design problems."
Or choose a question:
More Videos
"Don't be cool, be good—work hard at managing your teams because they need you to nail it."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Developing trust means showing you understand what it takes to get something shipped, that you’re reliable, and that people can be vulnerable with you."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Human biases are the real problem behind algorithmic bias, not the algorithms themselves."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Transportation must evolve to be more sustainable and accessible for all."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"The greatest sign of success for a teacher is just to be able to say the children are now working as if I did not exist."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Thick data is the opposite of big data; it’s stories, qualitative, and crucial during moments of rapid change."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"If you don’t bring stakeholders into the research journey, they won’t believe or use the data."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"We manage the environment in which knowledge distribution takes place, not the process itself."
Designing Systems at Scale
November 7, 2018
"Decades worth of agricultural data had to be thrown out because they lacked control groups and statistical rigor."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024