Melody Olson
Leadership Advisor | Writing Activate: Go Deep. Move Fast.
Palo Alto, California, United States
Actions
Melody Olson spent seventeen years at Google, where she worked as an engineer and eventually Senior Engineering Director leading 220+ person teams in Google Maps and Ads. She led teams through product cycles, organizational redesigns, and technology transitions — including AI-first solutions for geospatial understanding, 3D, Street View hardware and foundational data systems serving Google Maps' two billion active users.
Across her career, Melody kept seeing the same pattern: teams with similar talent and resources ending up in very different places. The difference was rarely the talent. It was whether someone made the stakes clear, shaped the right team around the right problem, and set up the team to move.
Melody is writing Activate: Go Deep. Move Fast., drawing from her own experience and on interviews with senior leaders at Google, Netflix, NVIDIA, Datadog, Anthropic, Apple, Coupang, and beyond. She writes and advises technology leaders and starting in July, 2026 she will be based in the Bay Area.
Area of Expertise
Topics
Right Problem. Right Team. The Work AI Can't Fix
The most common way talented teams lose their edge isn't a dramatic failure. It's good work, shipped on time, slowly disconnected from what matters.
A tech lead at a fast-moving company builds systems that improve a key metric by hundreds of percent. The data is never used. The metric measures activity, not impact. The real problem requires alignment across multiple teams, decisions above her authority, and expertise her team doesn't have. She raises it. Nothing changes. The team keeps delivering what it can deliver — good work, disconnected from what actually matters.
That's not an edge case. Across over thirty interviews with leaders at Netflix, NVIDIA, Datadog, Coupang, Apple, and beyond, the same pattern showed up. Teams optimize locally because nobody does the work outside the code: shaping the problem, shaping the team, making sure it all connects.
In the conversations where teams broke through, two things were different. Someone made the stakes concrete enough that the team felt pulled toward the work instead of pushed. And someone shaped the team around the problem — not the org chart — even when that meant forming temporary teams across organizational boundaries.
AI is making code faster. That's real. But it doesn't fix this problem — it makes it more expensive. More of the wrong thing, built faster. More coordination overhead. The work AI can't do — deciding whether the problem is worth solving, making the stakes real, shaping teams around them — is the work that matters more now, not less.
This talk shows what that work actually looks like, through stories from leaders who got it right and honest accounts of what happens when it doesn't get done. Drawn from 17 years leading 220+ person engineering teams at Google and research for the book Activate: Go Deep. Move Fast.
Go Deep Where It Matters: Leadership Moves That Unlock Teams
Most teams don't fail dramatically. They slow down. Work ships, progress gets reported, and nothing looks obviously wrong — but the team is no longer working on what matters. This is the most common way strong teams lose their edge, and it's the hardest pattern for leaders to see when they're in the middle of it.
This workshop puts you inside that problem and gives you two concrete leadership moves to address it.
We start with the same question asked across 30+ interviews with leaders at Netflix, NVIDIA, Datadog, Google, Apple, Coupang, and Anthropic: when you've had a team that was aligned, adapting, and really working on what mattered — what made the difference? You'll work through this in small groups, then flip to a harder question: given what you just described, what's missing on a team you're leading right now?
From there, we work through the two moves that showed up most consistently across those interviews. The first is making the stakes concrete — translating abstract strategy into something immediate enough that the team feels pulled toward the work instead of pushed. The second is shaping the team around the problem, not the org chart — including forming temporary teams across boundaries and giving clear ownership.
You'll leave with a specific diagnosis of where depth is missing on your own team and a plan for what to do about it. Drawn from 17 years leading engineering teams at Google and research for the book Activate: Go Deep. Move Fast.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top