Summary
Enterprises are increasingly complex. Workers are faced with more information, more tools, more demands, and research needs to keep up. The field of Systems Thinking can help researchers uncover the models behind this complexity. This talk covers practical techniques for illuminating how models are interconnected, where feedback loops exist, and how we might transform these complex systems to drive innovation. It highlights how we can understand these systems without losing sight of the workers themselves… their ideas, concerns, motivations, and needs. Marrying systems clarity with this human perspective is critical, and is something researchers are uniquely positioned to do.
Key Insights
-
•
Systems thinking offers a essential lens to research complex products by revealing whole systems and their subsystems simultaneously.
-
•
Effective research balances understanding detailed subsystems with maintaining a holistic system-level perspective to avoid 'blind men and the elephant' problem.
-
•
Feedback loops—reinforcing and balancing—help explain dynamic behaviors in product ecosystems and user interactions.
-
•
Bounded rationality causes users in different system roles to make reasonable decisions with limited visibility, often leading to systemic challenges.
-
•
In Customer 360 Audiences, data engineers lack visibility into marketers' downstream needs, causing inefficiencies and user frustration.
-
•
Intangible elements like emotions and user confidence significantly impact how users experience and perceive product subsystems.
-
•
Redrawing system boundaries based on research insights can lead to pivotal product strategy shifts, as Salesforce experienced prioritizing foundational features.
-
•
Mental models about data ownership and collaboration between roles shape communication and product adoption, requiring targeted enablement.
-
•
Keeping system diagrams and research at appropriate abstraction levels helps communicate complexity without overwhelming stakeholders.
-
•
Collaborative exploration of system boundaries with stakeholders ensures the research stays focused on core system elements and relevant opportunities.
Notable Quotes
"Systems Thinking can give us this new lens to think about research in the middle of complexity."
"If you dive too deep into the subsystems or the bits right away, then your understanding of the whole is going to be lacking."
"People make decisions with limited information, especially about more distant parts of the system."
"Marketers don’t try very interesting things when their confidence in data is low, which can create a downward spiraling reinforcing loop."
"Our big idea was big and they wanted it, but what they wanted way more was the foundational features."
"You drew the boundaries wrong, so we pivoted and re-drew the boundaries, and those foundational features became our marquee product launch."
"Data is like a black box. It’s owned by IT. I’m not allowed to know how it works, but I kind of resent that it introduces delays into my marketing processes."
"Drawing a boundary was the hardest part for me, like stopping drawing the systems."
"System diagrams are a nice level of abstraction over something that is really complicated underneath."
"If you can draw that picture and tell that story, it just makes it easier for everybody to talk about how it's really going to be used."
Or choose a question:
More Videos
"Saying no shouldn’t be about being difficult but about accountability beyond any one person."
George AyeThat Quiet Little Voice: When Design and Ethics Collide
November 16, 2022
"Engaging communities requires thinking beyond western-centric tools, considering language and cultural relevance for accessibility."
Xenia Adjoubei Sean BruceEmpowering Communities Through the Researcher in Residence Program
March 29, 2023
"Budgets are tight across research, design, and product; all-in-one platforms are costly and often don’t fit those budgets."
Benjamin Wiedmaier Annie MayfieldRedefining Toolkits: Unbundling to Create a Perfect Match
March 11, 2025
"Design systems help address integration challenges and differing cadences between design and development."
John DevanneyThe Design Management Office
November 6, 2017
"Just because you've been right in the past doesn't guarantee you'll be right in the future."
Steve Sanderson Alissa Briggs Jeff Gothelf Bill ScottDiscussion
May 14, 2015
"In the enterprise space, the UX function is added later. It’s not part of the company’s original DNA."
Jemma AhmedTheme 2 Intro
January 8, 2024
"The only person who gets to decide what it means to be badass is you."
Megan KiersteadYou Are a Badass at UX: Overcoming Imposter Syndrome
March 10, 2021
"We moved from versioning the entire system quarterly to individually versioning components, so changes are easier to track and prioritize."
PJ Buddhari Nate BaldwinMeet Spectrum, Adobe’s Design System
June 9, 2021
"Dunbar's number explains why groups around 150 people work best as communities."
James LangIf you can design an app, you can design a community
May 22, 2025
