|
Getting your Trinity Audio player ready...
|
Eric Ries:
Welcome, everyone. I’m incredibly excited to host this unique five-part roundtable, where we’ll explore the core principles of The Lean Startup—not in theory, but through vibrant dialogue with some of the most brilliant and thought-provoking minds across business, design, technology, psychology, and leadership.
Whether you're launching your first product, leading innovation within a large organization, or simply fascinated by how breakthrough ideas grow into lasting impact, these conversations are for you.
The Lean Startup was never meant to be a static method—it’s a living mindset. It’s about moving fast, but more importantly, it’s about learning fast. It’s about facing uncertainty with courage, and using continuous feedback to turn ideas into reality.
Over the course of these five sessions, we’ll cover the pillars of this approach:
Build-Measure-Learn Loop – the core engine of progress in uncertainty
Validated Learning – how to turn assumptions into knowledge
Pivot or Persevere – the moment of decision when direction matters most
Innovation Accounting – how to track true progress beyond vanity metrics
Continuous Deployment & Agile Development – the systems and mindsets that accelerate feedback and evolution
To help us explore these ideas more deeply, I’ve invited an extraordinary group of leaders—founders, visionaries, strategists, and scholars—each of whom brings their own experience, insights, and even challenges to this conversation.
These are not staged interviews. They’re explorations—where disagreement is welcome, candor is encouraged, and growth is inevitable.
Let’s begin with the heartbeat of the Lean Startup: The Build-Measure-Learn Loop.
(Note: This is an imaginary conversation, a creative exploration of an idea, and not a real speech or event.)
Build-Measure-Learn Loop
Moderator: Eric Ries
Guests: Elon Musk, Yvon Chouinard, Tony Fadell, Tim Brown, Marc Andreessen
Eric Ries:
Welcome, everyone. Today, we're diving deeper into the Build-Measure-Learn Loop, the core of the Lean Startup approach. It’s about accelerating feedback, reducing waste, and ensuring what we build actually matters to real people. This isn’t just a strategy—it’s a survival system in uncertainty.
Let’s kick things off with Elon. You’re known for rapid iteration at companies like SpaceX and Tesla. How do you handle “building to learn” in such high-risk environments?
Elon Musk:
Well, the idea of Build-Measure-Learn maps closely to our engineering loops. At SpaceX, we launch prototypes that we know might fail—but we do it to compress years of learning into months. Each launch tells us something—about design flaws, materials, even cost structure. Learning beats perfection.
Eric Ries:
You once said, “Failure is an option here.” That really echoes the lean mindset—fail early to succeed sooner.
Elon Musk:
Exactly. You can’t fear failure in the short term if you want success in the long term. Our first three rockets blew up. People thought we were doomed. But each failure was actually a massive leap forward in knowledge.
Eric Ries:
Tony, you helped create the iPod and later Nest. How do you apply Build-Measure-Learn in consumer hardware, where expectations are often much higher?
Tony Fadell:
In hardware, you can’t A/B test a thermostat every night like in software—but you can build low-fidelity models, test user reactions, and simulate behavior. At Nest, we mocked up ugly prototypes and watched how people interacted with them in real homes. That measured learning shaped everything—from the UI to the click wheel.
The key is to let real users show you what works, even if you’re cringing at what you’re giving them to test.
Eric Ries:
So it’s not about skipping quality—it’s about delaying polish until the right insights emerge.
Tony Fadell:
Right. Polish the right thing, not just what looks cool.
Eric Ries:
Yvon, Patagonia has always pushed innovation in environmental sustainability. How have you used fast-feedback loops to make bold product decisions?
Yvon Chouinard:
We experiment constantly—materials, supply chains, business models. Our recycled fleece started as a “what if” test. We made a small run, got real feedback, and adjusted. Later, with “Worn Wear,” we asked: Will customers buy used clothes if we clean and repair them?
We didn’t guess—we tried it in one store. When it worked, we scaled it. Build small, measure authentically, learn honestly.
Eric Ries:
You brought values into the loop. How did those guide your experiments?
Yvon Chouinard:
Values are our north star. If a product hurts the planet, it’s a failed experiment—even if it sells well. You learn more when you test against principles, not just profit.
Eric Ries:
Tim, IDEO has been synonymous with design thinking. How does that integrate with the Lean Startup loop?
Tim Brown:
Design thinking starts with empathy. We build quick prototypes, not just to test function but to understand feeling. Lean’s loop formalizes that learning: you build, gather behavioral feedback, and refine. We once prototyped a healthcare service by staging a mock clinic in a parking lot. We learned more in one afternoon than in weeks of planning.
Eric Ries:
So even experiences—like how someone waits or interacts—are measurable signals.
Tim Brown:
Exactly. Behavior is data. Prototypes should make people do things, not just say things.
Eric Ries:
Marc, from a venture capitalist’s perspective, how do you evaluate a startup using this model?
Marc Andreessen:
I want to see momentum in learning. If they say, “We launched, got 100 users, learned they hated feature X, and built Y instead,” I know they’re alive. A startup’s job isn’t to guess right from the start—it’s to iterate faster than competitors.
You’re not just funding a product—you’re funding a learning machine.
Eric Ries:
Beautifully said. The MVP isn’t a product—it’s an engine for growth through insight.
Eric Ries’s Closing Reflections:
I’m grateful for all of your insights. Here’s what I believe this conversation reinforces:
“Build” isn’t about perfection—it’s about purposeful imperfection. The MVP exists to provoke real reactions.
“Measure” must be honest. Skip vanity metrics—seek out real user behavior: Do they use it, love it, share it?
“Learn” is the reward. You either learn fast and adapt—or you drift quietly into irrelevance.
The Build-Measure-Learn loop works across industries—from rockets to thermostats, sustainable clothing to venture capital—because it mirrors how humans evolve: through experience, feedback, and growth.
The real power of Lean Startup isn’t in moving fast for the sake of speed, but in learning fast for the sake of truth.
Validated Learning
Moderator: Eric Ries
Guests: Steve Blank, Sara Blakely, Ash Maurya, Malcolm Gladwell, Clayton Christensen
Eric Ries:
Welcome back. Today’s focus is Validated Learning—a key Lean Startup principle that’s often misunderstood. It’s not about proving your idea is “right”—it’s about testing your assumptions with real users, real behavior, and real consequences. Steve, you coined the phrase "get out of the building." Why is that still the starting point?
Steve Blank:
Because the biggest lie in entrepreneurship is thinking you already know what your customer wants. You don’t. You might have a hunch, a strong feeling—but until you put it in front of real users and watch what they do, you’re flying blind. Startups aren’t smaller versions of big companies—they’re temporary organizations searching for a repeatable, scalable business model. Validated learning is how they find it.
Eric Ries:
And how do you advise founders who resist “wasting time” on early feedback?
Steve Blank:
I tell them, “Do you want to build what you think people want, or what they’ll actually pay for?” Because product-market fit isn’t about theory—it’s about validation through behavior. You don’t need millions of users to learn. Ten honest ones will do more than 100 surveys.
Eric Ries:
Sara, you created Spanx starting with one homemade prototype. How did you learn what the market actually wanted?
Sara Blakely:
I listened like crazy. I wore the prototype myself and talked to women constantly—friends, strangers, even department store clerks. I’d say, “Try this and tell me what you think.” When women lit up and said, “Where can I buy this?” I knew I had something.
I didn’t need a business plan or MBA. I needed real reactions. That was my validation—women didn’t just like it; they asked for it.
Eric Ries:
And that reaction led you to tweak and refine?
Sara Blakely:
Absolutely. I adjusted the waistband, the packaging, even the name—based on feedback. I wasn’t precious about my first version. My goal wasn’t perfection—it was connection. If it solved their problem, I was on the right track.
Eric Ries:
Ash, your Lean Canvas breaks big ideas into testable parts. How does it support the learning process?
Ash Maurya:
Founders fall in love with solutions. The Lean Canvas forces them to fall in love with problems. Each box on the canvas is a hypothesis—target customer, unique value prop, key metrics. You validate one piece at a time. You don’t build until the assumptions are de-risked.
Startups die from skipping this step. They build, launch, and… crickets. Learning after launch is expensive. Learn early, learn fast, and pivot with data—not gut feeling.
Eric Ries:
What’s one assumption you see founders overlook most?
Ash Maurya:
That people care enough to switch from their current solution. They might like your idea, but that doesn’t mean they’ll change behavior. Validated learning means putting your concept in front of people and seeing what they actually do, not what they say.
Eric Ries:
Malcolm, as someone who studies human behavior patterns, how do you see validation playing out in innovation?
Malcolm Gladwell:
The danger lies in our narratives. Founders want to believe a story—and confirmation bias helps them find “proof” everywhere. Real validated learning forces you to confront ambiguity. Sometimes the user behaves in ways that don’t fit your narrative.
I think of it like this: insight is often invisible until tested. Great entrepreneurs are great listeners—not just with ears, but with eyes. They observe behavior. They read silence.
Eric Ries:
So true. Clayton, your “Jobs to Be Done” theory has shifted how people understand user needs. How does that intersect with validated learning?
Clayton Christensen:
People don't just buy products—they hire them to do a job. Validated learning helps us ask: “What job is my customer trying to get done?” Instead of testing features, test outcomes. Does my product help them achieve what they were trying to accomplish?
If you observe someone struggling to complete a task, and your solution removes that struggle, that’s real validation. Forget about demographics. Focus on motivation.
Eric Ries:
That shift—from building for a persona to building for a “job”—is transformational. It’s what makes learning truly actionable.
Eric Ries’s Closing Reflections:
Today’s conversation brought clarity to what validated learning really means:
It’s not about being “right.” It’s about being willing to be wrong—and learning quickly.
Your idea is a set of hypotheses. Validation happens only through direct contact with customer behavior—not opinions or praise.
And most importantly: what customers do matters more than what they say.
We heard today how learning comes from observation, feedback, and humility. Whether you’re testing Spanx prototypes, mapping customer “jobs,” or sketching out lean canvases—real progress comes when you stop guessing and start testing.
Startups that prioritize learning become startups that last.
Pivot or Persevere
Moderator: Eric Ries
Guests: Reed Hastings, Howard Schultz, Whitney Johnson, Evan Williams, Nassim Taleb
Eric Ries:
Welcome back. Today’s topic might be the hardest choice a founder has to make: Should I pivot or persevere? It’s a moment of truth, when the data tells a story—and your ego has to listen. Let’s kick off with Reed. Your decision to pivot Netflix from DVDs to streaming, and later into original content, was a masterclass in adaptation. What made you pull the trigger?
Reed Hastings:
It was painful at first. DVDs were still profitable, and our brand was tied to them. But we saw the long-term trends—consumer behavior was shifting toward convenience and digital. We had to bet against our current success to stay relevant. The real signal came from customer feedback: “I love Netflix, but I hate waiting for DVDs.” That was all the data we needed.
Eric Ries:
So even success can be a trap?
Reed Hastings:
Absolutely. The trick is to recognize when your current path has diminishing returns. We ran small streaming experiments, watched engagement grow, and took the leap before it was urgent. That’s the power of leaning into discomfort when the data whispers before it screams.
Eric Ries:
Howard, Starbucks also had a pivotal moment—several, actually. What guided you through those choices?
Howard Schultz:
Our first pivot was emotional. Starbucks was selling machines and beans. I had a vision of community, warmth—a “third place.” That wasn’t on a spreadsheet. It was a feeling I validated in Italy and coffee shops I visited. Later, during the 2008 financial crisis, we had to close hundreds of stores and retrain baristas. That wasn’t just a strategy—it was a return to mission. Persevering wasn’t about pushing harder—it was about going deeper into our core values.
Eric Ries:
That idea of going deeper, not wider, really resonates. Whitney, you’ve written about reinvention as both an individual and business journey. How do you know when it’s time to pivot?
Whitney Johnson:
There’s a curve I call the S-curve of learning. At the beginning, growth is slow—you’re experimenting. Then there’s rapid acceleration. But eventually, growth plateaus. That’s when it’s time to leap—to pivot to the next challenge.
But fear often holds us back. Sunk cost bias is real. We get attached to the version of ourselves or our product that used to work. Pivoting requires two things: data, and courage. And the courage part is often harder.
Eric Ries:
Evan, you’ve had multiple success stories—Blogger, Twitter, Medium. What have you learned about pivoting that most people get wrong?
Evan Williams:
They think it’s a one-time, dramatic event. But the truth is, pivoting is a series of micro-decisions—shifts in product, messaging, or user focus. With Twitter, we saw people using SMS in ways we didn’t expect. That’s when we knew we had to pivot toward what users already loved.
The biggest mistake? Ignoring signs that something’s not working because you’re emotionally invested. Sometimes, your users are ahead of you. If you’re listening closely, they’ll tell you what to do.
Eric Ries:
Nassim, your idea of antifragility challenges traditional thinking. How do you see “pivot or persevere” through your lens?
Nassim Taleb:
An antifragile system gets stronger with stress. Startups should be like that. A pivot is not a weakness—it’s a response to volatility. If you learn from shocks and adjust, you thrive. If you cling to fragile assumptions and ignore noise, you die.
I don’t trust plans. I trust optionality. The more small experiments you run, the more information you gather. Don’t ask, “Should I pivot?” Ask, “What are my options—and which ones get stronger as things get chaotic?”
Eric Ries:
So in a way, pivoting becomes an exercise in robustness—not failure.
Nassim Taleb:
Exactly. Embrace volatility. Be fluid. Treat uncertainty as a signal, not a threat.
Eric Ries’s Closing Reflections:
What I took away today is that pivoting and persevering are not opposites—they are different kinds of learning:
Persevere when your core hypothesis is still valid, but your execution needs refinement.
Pivot when the data shows that your fundamental assumption—your user, your channel, your solution—is off.
And in both cases, success lies in your ability to detach from ego and listen to feedback with clarity.
You don’t pivot just because growth is slow. You pivot when learning has stopped.
And the most powerful pivots don’t abandon the mission—they realign it with a deeper truth.
Innovation Accounting
Moderator: Eric Ries
Guests: Jim Collins, Esther Dyson, Melinda Emerson, Ben Horowitz, Brené Brown
Eric Ries:
Welcome to today’s discussion on what I believe is one of the most underappreciated—and vital—aspects of the Lean Startup methodology: Innovation Accounting.
Most companies obsess over revenue and user counts, but early-stage startups often need a different lens. Innovation Accounting is about learning and measuring what actually matters. Jim, you’ve spent your career analyzing what makes companies great. How do you view progress in a world of uncertainty?
Jim Collins:
Thanks, Eric. I’ve found that the best companies build what I call a culture of disciplined thought and action. Even in startups, discipline doesn’t mean rigid control—it means consistently measuring what matters.
The question isn’t, “Are we growing?” It’s: “Are we making meaningful progress toward a scalable, sustainable model?” If your dashboard only shows vanity metrics, you’re flying a plane with a broken altimeter. Progress should be defined by cumulative, compound learning.
Eric Ries:
That resonates deeply. Esther, as both an investor and an analyst, how do you assess a startup’s learning process?
Esther Dyson:
I care less about what they’re selling today and more about how they’re thinking. Are they asking the right questions? Are they adjusting based on data, not ego?
I often look for three things:
Customer engagement trends – are people sticking around, not just signing up?
Iteration loops – how quickly are they testing and adapting?
Team behavior – do they learn out loud and share findings internally?
Vanity metrics don’t just deceive investors—they deceive founders. If you’re not tracking insights per experiment, you’re measuring the wrong thing.
Eric Ries:
Exactly. Melinda, you’ve worked with thousands of small businesses. What does innovation accounting look like outside of Silicon Valley?
Melinda Emerson:
It’s surprisingly similar! Whether you’re building a tech app or a neighborhood bakery, you’ve got to know:
Are people buying once or coming back?
What’s your cost of customer acquisition versus lifetime value?
Which offers are actually converting?
A lot of solopreneurs make decisions based on emotion. Innovation Accounting keeps you grounded in evidence. I tell them: track leads, conversions, retention, and referrals—that tells you if people are loving your product, not just liking it.
Eric Ries:
Ben, in your role as both an operator and a venture capitalist, how do you hold founders accountable when traditional KPIs don’t apply?
Ben Horowitz:
Great question. When a startup’s in early stages, I don’t care about flashy decks or how many press mentions they got. I want to know:
What specific learning did you get this week?
What metrics moved—and what actions caused it?
How are users behaving differently than last month?
And I watch for psychological signals. Are they facing the truth—or spinning a story? You can’t scale denial. Founders who lean into uncomfortable numbers tend to build lasting companies.
Eric Ries:
That’s so important—learning can’t happen without emotional honesty. Brené, this ties right into your work. What role does vulnerability play in measuring innovation?
Brené Brown:
Oh, it’s huge. Innovation requires people to experiment publicly. That’s vulnerable. Innovation Accounting asks teams to say, “Here’s what we thought would work—and it didn’t.” If your culture punishes that, you’ll get fake data and fearful teams.
Also, when teams feel safe, they report more accurate numbers. They’ll admit if users churned. They’ll surface confusion in the metrics. Without trust, you get a distorted mirror.
So the question becomes: Can you create a space where people feel safe enough to measure the truth?
Eric Ries’s Closing Reflections:
This conversation brought a deeper dimension to Innovation Accounting. Here are the big takeaways:
Real progress is measured by learning, not luck.
If you’re not learning why users do what they do, you’re not moving forward—you’re just moving.Vanity metrics lie. Behavior metrics tell the truth.
Sign-ups and pageviews look great on slides, but retention, engagement, and conversion are what actually matter.Culture and metrics are connected.
Without a culture of trust and emotional safety, your data will be filtered through fear and ego.
The startups that succeed aren’t just good at building—they’re great at measuring what matters. Because when you measure learning, you multiply your chances of survival.
Continuous Deployment & Agile Development
Moderator: Eric Ries
Guests: Satya Nadella, Jeff Sutherland, Sheryl Sandberg, Gene Kim, Eric Schmidt
Eric Ries:
Welcome to our final conversation in this series—an area close to my heart: Continuous Deployment and Agile Development. For Lean Startups, speed is not about rushing—it’s about learning fast. Let’s begin with Satya. Under your leadership, Microsoft embraced agility at a massive scale. What mindset shift made that possible?
Satya Nadella:
Thanks, Eric. The most important change was cultural. We moved from a “know-it-all” culture to a “learn-it-all” culture. Continuous deployment isn’t just a technical pipeline—it’s a philosophy of listening to users, shipping quickly, and being humble enough to adapt.
Agility happens when teams have clarity of purpose, but freedom of execution. When developers push code every day, they're not just building—they’re learning from every release.
Eric Ries:
So true. Jeff, as the co-creator of Scrum, what’s the connection between agile frameworks and continuous delivery?
Jeff Sutherland:
Agile isn’t about process—it’s about flow. Scrum empowers teams to deliver working software in short bursts. Add continuous integration and deployment, and the loop tightens even further.
One key insight: The faster the feedback, the faster the improvement. Whether it's customer feedback or internal QA, continuous delivery keeps the feedback within the sprint. That’s what makes agile teams truly adaptive—not reactive.
Eric Ries:
And how do you keep agility from turning into chaos?
Jeff Sutherland:
By anchoring everything in working software. Each release must deliver value, no matter how small. That way, you’re not just moving fast—you’re moving with purpose.
Eric Ries:
Sheryl, at Facebook, you scaled one of the fastest-growing tech companies in history. What role did speed and deployment cycles play in that growth?
Sheryl Sandberg:
Speed was essential, but we also had strong internal tooling and accountability. Engineers could deploy fast, but with testing, monitoring, and rollback options built-in. We used a mantra: Move fast with stable infrastructure.
Continuous deployment allowed us to experiment constantly. We’d A/B test headlines, button colors, onboarding flows. The point wasn’t just speed—it was rapid user feedback. You let the user behavior guide the product evolution in real-time.
Eric Ries:
So shipping fast becomes a listening tool.
Sheryl Sandberg:
Exactly. Every line of code is a question. Continuous deployment helps you hear the answer immediately.
Eric Ries:
Gene, your work in DevOps has transformed how companies integrate engineering and operations. What do most organizations get wrong when trying to deploy continuously?
Gene Kim:
They treat deployment as a tech problem—when it’s really a people and systems problem. DevOps is about breaking down silos. Dev, Ops, QA, Security—they should all be part of the same learning loop.
What works best is creating high-trust environments where teams own the outcomes. High-performing DevOps teams deploy more frequently, recover faster, and innovate more confidently. You measure success not by velocity alone, but by sustainability and resilience.
Eric Ries:
And what’s the risk of getting it wrong?
Gene Kim:
You create brittle systems that break under pressure. If developers fear deployment, they delay it. That slows learning, increases risk, and kills morale. Healthy systems deploy often, safely, and automatically.
Eric Ries:
Eric, Google is a model of continuous experimentation. How did you foster a culture that made that possible?
Eric Schmidt:
It starts with trust in small teams. We gave them autonomy, infrastructure, and access to data. They could run thousands of experiments without executive sign-off.
One example: Gmail. It launched as a beta product internally, iterated based on employee usage, and scaled up based on user behavior. Continuous deployment helped us refine while we scaled—instead of waiting for perfection.
The biggest insight? Speed matters. Not because of competition—but because user expectations evolve faster than you can predict.
Eric Ries’s Closing Reflections:
Today’s conversation crystallized what continuous deployment and agility are really about:
Speed is not about recklessness—it’s about responsiveness.
Continuous deployment allows you to turn every product change into a learning opportunity.
Agility is a systems mindset. It’s not just sprints and standups—it’s about culture, trust, and fast feedback loops across every function.
When you combine technical excellence with psychological safety, you unlock flow—and that’s when innovation compounds.
From startups to giants like Microsoft and Google, the lesson is clear: those who learn fastest win. And in a world that never stops changing, the real edge isn’t launching big—it’s learning continuously and adapting instantly.
Final Reflections by Eric Ries
Eric Ries:
Thank you for joining us through this journey. Over these five powerful conversations, we’ve heard from pioneers, rebels, builders, and deep thinkers. Each one challenged us to look beyond conventional wisdom—to rethink how we start, grow, and sustain innovation.
Here’s what I hope you take away:
Innovation isn’t magic. It’s not luck. It’s a discipline. A repeatable, learnable process grounded in curiosity, experimentation, and courage.
Speed alone isn’t enough. What matters is the direction you're moving. You can build fast and still fail—unless you’re also measuring and learning at every step.
The best decisions aren’t made by guessing. They’re made by testing. You don’t have to know everything at the start—you just need a system that helps you discover the truth quickly.
Culture is the foundation. Without trust, honesty, and vulnerability, no amount of agility will save a company from stagnation. The environments that support learning will always outperform those that punish it.
And finally, you are never done. Startups, teams, even global giants—every organization that thrives over time does so by continuously reinventing itself, staying close to its customers, and staying humble in the face of change.
The Lean Startup is not a fixed method—it’s a living commitment to learning. To making better decisions, faster. To building something real—not because it’s easy, but because it matters.
Thank you again to all our incredible guests. And thank you, the reader, listener, or learner, for showing up with curiosity. The next great innovation could come from you—and I hope this series gives you the tools, mindset, and inspiration to build it.
Now go out there and keep learning.
Short Bios:
Eric Ries – Entrepreneur and author of The Lean Startup, Eric pioneered a global movement around rapid innovation, MVPs, and data-driven growth.
Elon Musk – CEO of Tesla and SpaceX, Elon is known for rapid prototyping, first-principles thinking, and embracing failure as part of innovation.
Yvon Chouinard – Founder of Patagonia, Yvon built a values-driven company focused on sustainability, experimentation, and mission-first innovation.
Tony Fadell – Inventor of the iPod and founder of Nest Labs, Tony bridges sleek design with product iteration in hardware development.
Tim Brown – Chair of IDEO and design thinking pioneer, Tim emphasizes empathy, fast prototyping, and user-centered solutions.
Marc Andreessen – Internet pioneer and venture capitalist, Marc co-created the first popular web browser and co-founded Andreessen Horowitz.
Steve Blank – Serial entrepreneur and educator, Steve developed the Customer Development model and inspired the Lean Startup movement.
Sara Blakely – Founder of Spanx and self-made billionaire, Sara started with a prototype and grassroots feedback to disrupt women’s fashion.
Ash Maurya – Creator of Lean Canvas and author of Running Lean, Ash helps startups deconstruct ideas and test key assumptions systematically.
Malcolm Gladwell – Bestselling author and thinker, Malcolm explores counterintuitive truths in behavior, perception, and decision-making.
Clayton Christensen – Late Harvard professor and author of The Innovator’s Dilemma, Clayton developed the theory of disruptive innovation.
Reed Hastings – Co-founder of Netflix, Reed led strategic pivots from DVDs to streaming to content creation, driven by user trends.
Howard Schultz – Former CEO of Starbucks, Howard scaled the brand by focusing on purpose, experience, and cultural reinvention.
Whitney Johnson – Author of Disrupt Yourself, Whitney maps personal and business growth to S-curves and intentional pivots.
Evan Williams – Co-founder of Blogger, Twitter, and Medium, Evan repeatedly shifted direction based on emerging user behavior.
Nassim Nicholas Taleb – Statistician and author of The Black Swan, Nassim argues for antifragile systems that grow through volatility.
Jim Collins – Business strategist and author of Good to Great, Jim defines greatness through disciplined growth and measurable momentum.
Esther Dyson – Tech investor and analyst, Esther backs founders who learn fast, think long-term, and iterate ethically.
Melinda Emerson – Known as “SmallBizLady,” Melinda is a small business expert helping entrepreneurs track meaningful growth.
Ben Horowitz – Venture capitalist and author of The Hard Thing About Hard Things, Ben emphasizes honesty, resilience, and smart metrics.
Brené Brown – Researcher and author of Daring Greatly, Brené explores vulnerability, trust, and leadership culture in high-performing teams.
Satya Nadella – CEO of Microsoft, Satya transformed the company with a growth mindset, agile culture, and cloud-first innovation.
Jeff Sutherland – Co-creator of Scrum, Jeff championed agile development and iterative delivery through cross-functional teams.
Sheryl Sandberg – Former COO of Meta (Facebook), Sheryl scaled operations through fast feedback loops and experimental thinking.
Gene Kim – DevOps expert and co-author of The Phoenix Project, Gene promotes high-velocity, cross-team collaboration for sustainable growth.
Eric Schmidt – Former CEO of Google, Eric scaled the company through data-driven decisions, empowered teams, and rapid experimentation.
Leave a Reply