Summary
For those of us in roles that aim to link experiences, see things end-to-end, or understand systems as ecosystems, the constant currents of change can make it feel like we’re endlessly adapting just to keep up. We long for a stable point of definition and clarity amid all this motion. In this talk, I’ll draw from my experience across various roles and companies to help you recognize and navigate the broader forces shaping our related fields. Using metaphors like oxbows, rivers, and estuaries, and with practical examples, I’ll share tactics for navigating change with intention, helping you stay grounded in the long game while seizing “act now” opportunities.
Key Insights
-
•
Integrative roles such as service design, product management, and UX research face unique boundary-spanning challenges involving complex cognitive and emotional labor.
-
•
Organizational maturity is nonlinear; fast-moving, product-led companies and slower, service-design-mature companies have complementary strengths.
-
•
There is a widespread 'battle of models' as different teams create overlapping sense-making frameworks like journey maps, value streams, and architectural diagrams.
-
•
Trying to force one unified model across an organization is typically ineffective; embracing diverse models and finding commonalities is more productive.
-
•
The river metaphor (water, obstacles, route, markers, safety) is powerful for understanding how to read and navigate organizational change currents.
-
•
Oxbow lakes metaphor warns that pushing hard in one direction can isolate teams or disciplines when larger economic or organizational 'floods' reshape the context.
-
•
Estuaries metaphor highlights the creative potential at boundaries where different disciplines and perspectives mix, but also the sensitivity and fragility of such ecosystems.
-
•
Patient opportunism—choosing when to leverage currents and when to push against them—is critical to long-term success and avoiding burnout in integrative roles.
-
•
Many key decisions impacting customer experience happen in engineering or architecture teams that may not traditionally include service design participation.
-
•
Perceptions of progress can be skewed; although some disciplines feel stagnated, other evolving disciplines offer opportunities for collaboration and innovation.
Notable Quotes
"You have to go from being able to deliver a message in three bullets and then turn around in the next moment and deliver a massive service blueprint or customer journey."
"Maturity is not linear; the tanker company had a lot to learn from the speedboat, and vice versa."
"Everyone is circling around similar topics but in very different ways—there’s a battle of models but more similarities than differences."
"Sometimes leaders focus so much on scanning the river they’re not observing the surroundings—the banks tell you if the river is deep or shallow."
"If you need to cross a dangerous river, you don’t paddle straight into it; you use the opposing force of the river to move forward."
"Trying to force one preeminent model for the company is a recipe for disaster—embrace models and understand why people are using them."
"It is impossible to survive in this industry by pushing against the current all the time; you must put yourself in positions to leverage the current."
"Some of the most important decisions for service design happen on whiteboards among engineers, often without service design representation."
"The estuary is highly resilient but also very sensitive to industrial waste—creative collaboration areas in organizations are similar."
"Patient opportunism means most of the time having the current at your back and only occasionally angling directly against it to avoid burnout."
Or choose a question:
More Videos
"Ethical judgment is the ability to maximize benefits while minimizing harm to the communities we work with."
Sarah Fathallah Alba VillamilBeyond insights: Rethinking the role of researchers as stewards of organizational wisdom
March 13, 2025
"Executives like NPS because it’s a simple, quick-to-understand number, even if they don’t fully grasp its nuances."
Jack MoffettUX Metrics That Matter and The Future of our Design at Scale Conference: A Community Conversation
September 22, 2022
"You get a dashboard that shows who applied, who qualified, and even who didn’t qualify—all in real time."
Lily Aduana Savannah Hobbs Brittany Rutherford5 Reasons to Bring Your Recruiting in-House (and How To Do It)
March 12, 2021
"We’re in this initial stage of tinkering, just trying to make the tech behave the way we expect it to."
Sheryl Cababa Ethan Marcotte Milena PribicDay 2 Panel
June 5, 2024
"True success means designing teams for resilience so they’re ready for whatever season comes."
Mariesa LenzWhat Beekeeping Taught me about Product Teams
October 29, 2025
"We have to step outside research and understand AI, technology, and product processes to put ourselves in the right space."
Megan Blocker Lada Gorlenko Fatimah Richmond Molly StevensWhat UX research maturity looks like and how we get there [Advancing Research Community Workshop Series]
November 9, 2023
"Surgeons don’t stop healing people because they’re assisted by robot arms. We get new tools to support us and need to learn how to use them."
Jamika BurgeEmbracing change: Navigating shifting landscapes with compassion and agency
March 11, 2025
"If you don't have shared language and values, you can't coordinate your actions or agree on what to do."
Paul Pangaro, PhDSystems Disciplines: Table Stakes for 21st Century Organizations
June 6, 2023
"The self-service model works best for projects with concrete and well-defined design objectives at the surface layers."
Nora Tejeda Giovanna AlonsoScaling Design Capabilities at BBVA Through a Self-service Design Model
June 10, 2021
Latest Books All books
Dig deeper with the Rosenbot
Why is establishing ownership and governance early critical for AI pilots to succeed?
Who are the multiple user types involved in designing services for public sector innovation portfolios?
What are effective methods to create feedback loops between strategy, orchestration, and implementation teams?