You built a solid plan. Then the ground moved. Then it moved again.

I keep hearing a version of this from leaders. The plan was good. The thinking was sound. And within a quarter it had been overtaken — not because anyone got it wrong, but because the conditions it was built on had already changed.

There was a time when a strategic plan gave you twelve to eighteen months of clear direction. Now market conditions change faster than planning cycles can keep pace. So the plan gets rewritten quarterly, and it is still behind.

What I want to name is what that does to everyone trying to do the work.

Unclear objectives create decision paralysis across every level of an organization. Teams that need to act quickly to seize an opportunity hesitate instead, waiting for clarification that may never come. Uncertainty delays action. Delay makes the original problem worse. And around it goes.

I call this the Chaos Engine, and it is only the first of nine disruptive forces converging on organizations right now. There’s a shortage of skills our educational systems don’t yet produce. A $900 billion exodus of talent walking out the door. A generation entering the workforce that simply will not participate in organizations that fear failure and profit without purpose.

Here is the part I most want to say.

The ways we have been taught to respond to disruption are making things worse. We take each force and hand it to a department — talent to HR, technology to IT, culture to an engagement survey. Each one gets its own budget, its own initiative, its own dashboard.

That model was built for a world where challenges arrived one at a time. They don’t arrive that way anymore.

Seventy percent of innovation initiatives fail. Not for lack of effort or intelligence. They fail because organizations attack these problems in isolation instead of as one interconnected system.

Thirty-six years ago, when Peter Senge published The Fifth Discipline, systems thinking was a revelation — but change still moved slowly enough that linear thinking could keep up. It was a nice-to-have.

That world is gone. The paradigm of business has shifted. These forces cannot be solved linearly, because they are not separate problems — they impact each other, and they are part of one system. Address one in isolation and you set off consequences in the others. They have to be solved systemically.

I have spent 36 years watching what happens when organizations make that shift. One healthcare insurer moved operating margins up $54 million against a $15 million goal, dropped voluntary turnover by 31 percent, and raised its Great Place to Work score twenty points — a jump that usually takes five years. Not through layoffs. Through seeing the system whole, and starting by actually listening to the people inside it.

That is what Innovation Ecosystems: A Dynamic Blueprint for Organizational Success and Engagement is about. It publishes with Hachette on October 20, with a foreword by Peter Senge and a cover quote from Tom Peters, and it features 35 of the most interesting thinkers I know.

Subscribe now

Save the date: Thursday, October 22, 2026

1:00 pm ET / 12:00 noon CT / 11:00 am MT / 10:00 am PT

6:00 pm UK / 7:00 pm Central Europe

We’re launching on Zoom, which means anyone can be in the room. No travel, no geography. We have space for 500 people, and we are inviting remarkable voices to speak, including Peter Senge, Alan Webber, co-founder of Fast Company, and thought leaders from the book.

Registration opens September 1, and I’ll send the link the moment it’s live. For now, please hold the date — and bring the people who need to hear this.

One more thing: hit reply and tell me where you see these forces feeding each other in your organization. I read every response, and your answers will shape what I write about next.

With gratitude,

Ilene

Leave a comment

A rabbi, a truth about loss, and the reason your skeptics may be your most valuable people

Some interviews for my book confirmed things I’d seen over 36 years of transformation work. A few reframed them entirely. My conversation with Rabbi Irwin Kula was the second kind.

We were talking about why innovation initiatives stall — why brilliant strategies with committed leaders and real budgets still hit a wall of resistance. And Rabbi Kula said something I’ve been carrying ever since:

“There is no possibility of having innovation without loss.”

For him, deep listening isn’t a communication tactic — it’s a psycho-spiritual practice. The goal is to move beneath the surface problem and uncover the real, often unarticulated, “job to be done.” He gave me an example I love: institutions routinely mistake their own problems for their customers’ problems. A synagogue worries about declining attendance — but no one wakes up in the morning feeling their problem is a “lack of church.” The real problems are loneliness. The need for meaning. The challenge of raising children in a complex world.

Every organization has its version of this mistake. The company worries about “innovation metrics” while its people are quietly carrying something else entirely.

And what they’re carrying, most often, is loss. Every change — even a good one, even a necessary one — asks people to give something up. A skill they spent a decade mastering. A team that felt like home. A story about their future that no longer fits. Rabbi Kula, drawing on his psychoanalytic lens, argues that when organizations offer no language and no structured way to process that loss, even the most promising ideas trigger unconscious resistance — stalls, silos, outright failure.

Then he said the thing that changes how you run your next meeting: the resistors are not obstacles to be overcome. They are carriers of crucial information. They intuitively sense the emotional costs of change, and listening deeply to them reveals the partial truths you need to refine and strengthen the innovation itself.

Read that again. The loudest skeptic in your organization may understand something about your initiative that your steering committee doesn’t.

And notice what all of this requires. People can only process loss where it’s safe to name it. No one tells you what they’re grieving — the expertise that’s now obsolete, the team being reorganized away, the future that no longer fits — in a room where vulnerability gets punished. Without psychological safety, the loss doesn’t disappear. It goes underground. And underground loss surfaces as the resistance that kills initiatives. That is why psychological safety isn’t a wellness perk. It is the precondition for innovation itself — the soil in which everything else either grows or doesn’t.

Rabbi Kula practices what he calls “relational holding” — listening in which the listener is willing to be changed by the relationship itself. Not listening to respond. Not listening to confirm. Listening that leaves you different than it found you. He calls the dialogue that follows “wandering together” — and in his view, the next leap in human progress won’t be measured by the sophistication of our technologies but by our ability to integrate humility, curiosity, and self-awareness into how we work together.

That may be the truest sentence in my entire book, and I didn’t write it. One of the 35 remarkable people who trusted me with their wisdom did.

One more thought before I close. This matters more now than it did a generation ago, because the paradigm of business has shifted. Change is no longer an occasional event that organizations endure and recover from — it’s the permanent condition of work. In the old paradigm, helping people process loss was a kindness. In the new one, it’s a core leadership capability. Continuous change means continuous loss — and only organizations safe enough to metabolize loss can move.

Worth considering: in your last change initiative, did anyone make space for what people were losing — or only enthusiasm for what they were gaining?

Subscribe now

Leave a comment

Innovation Ecosystems: A Dynamic Blueprint for Organizational Success and Engagement (Hachette) arrives October 20 — with a foreword by Peter Senge and a cover quote from Tom Peters.

The pre- order for the book on Amazon is available

https://www.amazon.com/dp/1399833049/?bestFormat=true&k=innovation%20ecosystems%20ilene%20fischer&ref_=nb_sb_ss_w_scx-ent-bk-ww_k0_1_35_di&crid=2IH5YSMB667S1&sprefix=innovation%20ecosystems%20ilene%20fischer

Of the nine disruptive forces I write about in my book, there’s one that audiences go quietest about when I name it.

It isn’t AI. It isn’t the talent shortage. It’s the Cultural Collapse — the slow erosion of trust inside organizations.

Here’s why it silences a room: everyone has felt it, and almost no one has been allowed to name it.

When trust breaks down, employee performance collapses regardless of talent or compensation. Let me say that again, because it took me years inside organizations to fully believe it: regardless of talent or compensation. You can recruit the best people in your industry and pay them beautifully, and if they don’t trust that their ideas are safe, that their effort matters, that leadership says what it means — their performance will collapse anyway. Not dramatically. Quietly. Which is worse.

I’ve spent 36 years watching where this shows up first, and it’s almost always the same place: middle management.

Middle managers spend 41% of their time on tasks that add no value. Think about that. Nearly half the working life of the people who connect your strategy to your front line is consumed by work that produces nothing — while they absorb pressure from above (”transform!”) and resistance from below (”we’ve seen this before”). They are the transmission system of every organization, and in most organizations right now, the transmission is grinding.

And here’s the mistake I watch organizations make when they finally decide to act. They try to install innovation on top of the broken trust — a new lab, a new methodology, a new set of values on the wall — while leaving the traditional management structure fully intact.

It doesn’t just fail. It backfires. Attempting to adopt an innovation ecosystem inside an unchanged traditional structure creates internal contradictions that damage both systems — often doing more harm than leaving everything alone. People watch the new thing contradict the old thing, and the trust erodes further. Each failed initiative makes the next one harder.

This is why the Cultural Collapse can’t be solved as a standalone “culture problem.” It’s one of nine forces converging at once, and they feed each other: trust erosion accelerates talent loss, talent loss deepens innovation paralysis, and around it goes.

The way through is not another initiative. It’s the foundation the initiatives keep skipping: psychological safety — created through deep listening, the practice of genuinely hearing what people are holding before asking them to carry something new. When people are truly heard, trust stops being a poster and starts being an experience.

That rebuild is what my book is about — and I’ll be sharing much more of it here in the weeks ahead.

Worth considering: in your organization, is trust something people experience — or something leadership announces?

Share

Leave a comment

Ilene Fischer: Author- Innovation Ecosystems: A Dynamic Blueprint for Organizational Success and Engagement (Hachette) arrives October 20 — with a foreword by Peter Senge and a cover quote from Tom Peters

.

When I look at this cover — the network of nodes connecting across the page — I see the book’s central idea made visible. These forces are not separate. They are connected.

Here is what I mean.

Organizations today are facing nine disruptive forces simultaneously:

🔹 The Chaos Engine — the relentless pace of change and AI making every strategic plan obsolete before execution

🔹 The Great Talent Drought — an 85-million-worker global shortage as the era of the single-specialty worker ends and the demand for multi-talented, cross-disciplinary people outpaces the supply

🔹 The $900 Billion Exodus — 70% of preventable turnover linked to management

🔹 The Innovation Paradox — trillions spent on innovation, yielding only incremental change while breakthroughs remain out of reach

🔹 The Planning Paralysis Crisis — spinning wheels in endless analysis to avoid uncertainty, consuming resources without producing results

🔹 The Policy Whiplash Crisis — regulatory chaos making long-term planning impossible

🔹 The Cultural Collapse — when fear replaces trust, performance collapses and middle managers burn out trapped between executive demands and frontline resistance

🔹 The Generation Z Revolution — the largest incoming workforce refusing broken cultures and choosing organizations where purpose is real, talent is expressed, and the work actually matters

🔹 The Quantum-AI Convergence — cutting-edge technologies requiring seamless cross-functional integration that traditional management’s departmental silos make technically impossible

Most leadership teams experience these as nine separate fires and try to solve each one individually and linearly. The talent shortage belongs to HR. The innovation slowdown belongs to the lab. The AI question belongs to IT. Each fire gets its own initiative, its own budget, its own steering committee. And each initiative quietly fails.

Not because the people running it lack skill or commitment. But because the world is now moving too fast and is too complex for the old linear playbook. When you solve one of these disruptions in isolation, you don’t fix the system — you sub-optimize it. The unintended consequences ripple outward and amplify every force you haven’t touched yet. Culture frays and your best talent leaves. Talent leaves and innovation stalls. Innovation stalls and results decline. Results decline and culture frays further. One loop, four disguises, and no single initiative touches it.

Thirty-six years ago, when Peter Senge published The Fifth Discipline, systems thinking was a revelation — and largely a luxury. Change moved slowly enough that linear thinking could keep up. It was a nice-to-have.

That world is gone.

Systems thinking is the imperative of our time — the most important leadership skill leaders can develop. Not as a concept to admire, but as a practice to live. When you learn to see these nine forces as one interconnected system and act on the whole rather than the parts, something remarkable happens: the same forces that were driving your organization into the ground begin driving it forward — creating exponential momentum that builds on itself. Virtuous cycles replace vicious ones. I have watched it happen, inside real organizations, over 36 years.

That is what this book is about. It is the paradigm shift our moment demands.

This is the book I have spent 36 years building toward. I hope it finds the leaders who need it most.

Leave a comment

Pre-order your copy here: https://www.amazon.com/dp/1399833049

And if this resonates — please share it with someone who may appreciate it. The launch is as much about the community that shows up around the book as it is about the book itself.

I want to say something I believe with every fiber of my 36 years in this work:

The single most important leadership skill of our time is not strategy. It is not execution. It is not even vision.

It is systems thinking.

Not as a concept to admire. As a practice to live — every day, in every decision, in every conversation about what is going wrong and what to do about it.

Here is why I feel this so urgently. Organizations today are facing nine disruptive forces simultaneously — forces moving at a speed and in a complexity that no traditional management approach was designed to handle. And the leaders I watch struggling hardest are not the ones lacking intelligence or commitment. They are the ones trying to solve these forces one at a time, linearly, as if each disruption were a separate problem with a separate solution.

It is not. They are a system. And when you address a system linearly, you do not solve it. You sub-optimize it — fixing one part while the untouched parts quietly undermine everything you just built.

Last week I introduced The Chaos Engine — the relentless acceleration of change, led by AI, that is breaking strategic planning processes built for a slower world. I ended with a promise: that the way through is not better prediction, but learning to see organizations as complex adaptive systems.

This week I want to show you what that actually means — because The Chaos Engine is only one of nine disruptive forces converging on organizations right now:

1. The Chaos Engine — shifting priorities and decision paralysis

2. The Great Talent Drought — an 85-million-worker shortage

3. The 00 Billion Exodus — 70% of turnover linked to management

4. The Innovation Paradox — trillions spent, breakthroughs avoided

5. The Planning Paralysis Crisis — analysis consuming resources, not eliminating uncertainty

6. The Policy Whiplash Crisis — regulatory chaos making long-term planning impossible

7. The Cultural Collapse — trust erosion defeating talent and compensation alike

8. The Generation Z Revolution — the largest incoming workforce refusing to work in broken cultures

9. The Quantum-AI Convergence — technology that organizational silos make impossible to integrate

And the single most important thing to understand about them is this: they are not nine separate problems. They are one system.

Most leadership teams experience these nine forces as separate fires. The talent shortage belongs to HR. The innovation slowdown belongs to the innovation lab. The AI question belongs to IT. The generational friction belongs to a task force. Each fire gets its own initiative, its own budget, its own steering committee.

And each initiative quietly fails — not because the people running it lack skill or commitment, but because the forces are connected through feedback loops that no single initiative touches. Let me make three of those loops visible.

The first is the talent-attraction loop. When culture frays — when psychological safety erodes, when ideas die without a hearing, when the gap between stated values and lived reality becomes undeniable — talented people leave. Not for money. For meaning. Their departure loads more work onto everyone who stays, which accelerates burnout, which accelerates the next departure. Meanwhile the organization responds linearly: recruit harder, pay more. But compensation is a balancing transaction; purpose is a reinforcing loop. New hires walk into the same culture that expelled their predecessors, and the cycle continues — now with the added cost of a perpetual replacement machine. The Talent Drought, the Gen Z Revolution, and Policy Whiplash all flow through this single loop, amplifying each other as they go.

The second is the knowledge-spillover loop. Breakthrough innovation depends on something deceptively fragile: dense, serendipitous human connection. The unplanned conversation. The half-formed idea shared across a boundary. The question from someone in a different discipline that unlocks a problem you’ve been circling for months. When disengagement rises, these collisions quietly stop. Disengaged people don’t linger after meetings. They don’t share unfinished thinking. They don’t cross hallways. Stalled innovation is not usually a pipeline problem or a process problem — it is the downstream consequence of an engagement problem. The engine isn’t broken. It’s starving.

The third is the planning-capital loop. The speed of change introduced by AI — and soon, quantum computing — renders long-term plans obsolete before they can be executed. Planning breaks down. And when planning breaks down, leaders and investors respond the way humans respond to rising uncertainty: with caution. Investment freezes. Experiments get starved precisely when experimentation is the only reliable way to learn. The organization becomes most conservative at the exact moment the environment demands it become most exploratory.

Now notice what these three loops have in common. Each one connects forces that live in different departments on the org chart. Each one defeats any initiative aimed at only one of its parts. And each one runs on culture — because culture is not an HR concern. It is the medium through which talent, engagement, and innovation interact. A toxic culture is a system that filters out exactly the people and ideas the organization needs most.

This is the paradigm shift at the heart of my book: the leader’s function is not to solve each of the nine disruptions individually. It is to manage the entire field of relationships among them. Managing the part — “fix the talent drought” — fails. Managing the interaction — optimizing the connection between talent, culture, and innovation — is where the leverage lives.

When you address these forces systemically, something remarkable happens: solving one strengthens your capacity to solve the others. The system becomes self-reinforcing in the right direction. Virtuous cycles replace vicious ones. That is not a metaphor. I have watched it happen, inside real organizations, over 36 years.

This is what Meg Wheatley and Fritjof Capra were pointing to: organizations are living networks, not machines. You cannot repair a living network part by part. But you can strengthen the relationships that allow it to heal itself.

The leaders who will succeed in the decade ahead are not the ones with the best answers to each individual disruption. They are the ones who learn to see the whole system — and act on it.

Over the coming weeks, I’ll take these loops one at a time — how they work, how they fail, and where the leverage points hide.

For now, one question worth sitting with: which two challenges in your organization are secretly the same problem?

My book, Innovation Ecosystems, publishes on October 20 from Hachette.. Everything in this series comes from it — and the book goes much further.

Leave a comment

Everything is moving faster than our organizations were built to handle.

Markets. Technology. Regulation. Workforce expectations. Geopolitics. And leading all of it — AI, which isn’t changing every quarter or every month. It’s changing every week, rewriting assumptions before the ink is dry on any strategic plan built around them.

This is genuinely new. Not an acceleration of something familiar — a qualitative shift in the nature of the environment organizations are operating in. The speed and complexity of interconnected issues converging simultaneously is something leaders haven’t faced before. The old playbooks weren’t built for it.

What makes this especially difficult is how the breakdown gets misdiagnosed. When organizations struggle to execute — when leadership sets clear priorities and six months later the organization has touched seventeen things and completed none of them — the instinct is to look for familiar culprits. A talent problem. A culture problem. A management problem. People are exhausted. Cynicism is rising. Leadership is frustrated.

The frustration is understandable. The diagnosis is wrong.

The real problem is frequently structural: the organization was designed for a pace of change that no longer exists. Supply chain disruptions that occurred every two to three years now arrive every three to six months. Regulatory changes come faster than compliance systems can process them. And AI is rewriting the technology landscape faster than any planning cycle can track.

This has a predictable systemic effect.

Unclear objectives create decision paralysis. Decision paralysis delays action. Delayed action allows problems to compound. Compounded problems create more uncertainty. The loop is self-reinforcing — and it amplifies every other organizational challenge. Talent challenges become harder to address when nobody can articulate a stable direction. Innovation stalls when teams can’t commit long enough to prototype and learn. Culture erodes when people experience their work as perpetually interrupted.

The organizations navigating this most effectively have recognized something fundamental: you cannot address these challenges linearly — one variable, one solution, one department at a time. Addressing a challenge linearly in a complex environment creates unintended consequences that ripple into areas you never anticipated. Fix the symptom without understanding the system, and the system generates new symptoms faster than you can address them. You have to look at the root cause and the entire system at once, understanding how each issue impacts the next.

This is where two thinkers I return to often become essential.

Meg Wheatley, in *Leadership and the New Science*, drew on quantum physics and biology to argue that organizations behave more like living systems than like machines. In living systems, relationships are primary. Order emerges not from control but from connection — from the quality of the interactions between people, ideas, and conditions. When you try to manage a living system the way you manage a machine — imposing structure, eliminating variance, optimizing parts in isolation — you don’t get stability. You get rigidity. And rigid systems break under pressure rather than bending and adapting.

Fritjof Capra, in *The Web of Life*, goes deeper into the science of this. Complex adaptive systems — whether ecosystems, organisms, or organizations — are characterized by nonlinear dynamics, emergent properties, and self-organization. They cannot be understood by analyzing their components in isolation because the properties that matter most arise from the interactions between components, not from the components themselves. The whole is genuinely different from the sum of its parts. And interventions that ignore this — that treat the system as if it were a collection of independent parts — produce unintended consequences precisely because the interactions continue operating in ways the intervention didn’t account for.

The distinction between complicated and complex is critical here and worth making explicit. A complicated system — an airplane engine, a logistics network, a supply chain — has many parts and requires expertise to understand, but it is ultimately knowable. You can map it. You can identify what’s broken. You can fix the broken part and restore function. Complicated problems yield to analysis and expertise.

A complex adaptive system is fundamentally different. It is not just difficult to understand — it is genuinely unpredictable, because it continuously adapts. The system responds to interventions. It learns. It self-organizes around new conditions. What worked last time may not work this time, because the system has changed in response to what happened last time. The Chaos Engine is a complex adaptive systems problem. And organizations trying to solve it with complicated-problem thinking — more analysis, better planning, cleaner processes — are applying the wrong framework to the wrong kind of challenge.

One of the deepest sources of organizational paralysis in the face of accelerating change is what systems thinkers call mental models — the invisible assumptions leaders hold about how the world works and how organizations should operate. These aren’t conscious beliefs. They’re the water leaders swim in: assumptions so embedded and so long unquestioned that they feel like reality rather than interpretation.

One of the most common and most damaging mental models operating in organizations right now: “it shouldn’t move this fast.” Leaders who hold this model — and many do, because they built their careers in a world that moved more slowly — are not simply mistaken about the pace of change. They are fighting or ignoring reality. And that fight shapes everything: which problems get framed as temporary versus structural, which solutions get considered, which voices get heard, and which information gets filtered out because it doesn’t fit the model.

Mental models don’t announce themselves. A leader whose mental model says “this is temporary disruption, things will stabilize” will consistently underinvest in building adaptive capacity — because adaptive capacity is expensive and unnecessary if things are about to stabilize. A leader whose mental model says “we just need better execution of our current strategy” will consistently misdiagnose execution failures that are actually strategy failures. The model generates its own confirmation. It is self-sealing.

We’ll go deeper on mental models in a future post. For now, the essential point is this: the organizations building genuine resilience against The Chaos Engine are the ones that have done two things simultaneously — adopted a complex adaptive systems understanding of what they’re actually navigating, and begun surfacing and examining the mental models that have been shaping their responses to it.

They haven’t eliminated uncertainty. They’ve built the organizational architecture — and the leadership awareness — to move through it.

Everything is moving faster than our organizations were built to handle.

Markets. Technology. Regulation. Workforce expectations. Geopolitics. And leading all of it — AI, which isn’t changing every quarter or every month. It’s changing every week, rewriting assumptions before the ink is dry on any strategic plan built around them.

This is genuinely new. Not an acceleration of something familiar — a qualitative shift in the nature of the environment organizations are operating in. The speed and complexity of interconnected issues converging simultaneously is something leaders haven’t faced before. The old playbooks weren’t built for it.

What makes this especially difficult is how the breakdown gets misdiagnosed. When organizations struggle to execute — when leadership sets clear priorities and six months later the organization has touched seventeen things and completed none of them — the instinct is to look for familiar culprits. A talent problem. A culture problem. A management problem. People are exhausted. Cynicism is rising. Leadership is frustrated.

The frustration is understandable. The diagnosis is wrong.

The real problem is frequently structural: the organization was designed for a pace of change that no longer exists. Supply chain disruptions that occurred every two to three years now arrive every three to six months. Regulatory changes come faster than compliance systems can process them. And AI is rewriting the technology landscape faster than any planning cycle can track.

This has a predictable systemic effect.

Unclear objectives create decision paralysis. Decision paralysis delays action. Delayed action allows problems to compound. Compounded problems create more uncertainty. The loop is self-reinforcing — and it amplifies every other organizational challenge. Talent challenges become harder to address when nobody can articulate a stable direction. Innovation stalls when teams can’t commit long enough to prototype and learn. Culture erodes when people experience their work as perpetually interrupted.

The organizations navigating this most effectively have recognized something fundamental: you cannot address these challenges linearly — one variable, one solution, one department at a time. Addressing a challenge linearly in a complex environment creates unintended consequences that ripple into areas you never anticipated. Fix the symptom without understanding the system, and the system generates new symptoms faster than you can address them. You have to look at the root cause and the entire system at once, understanding how each issue impacts the next.

This is where two thinkers I return to often become essential.

Meg Wheatley, in *Leadership and the New Science*, drew on quantum physics and biology to argue that organizations behave more like living systems than like machines. In living systems, relationships are primary. Order emerges not from control but from connection — from the quality of the interactions between people, ideas, and conditions. When you try to manage a living system the way you manage a machine — imposing structure, eliminating variance, optimizing parts in isolation — you don’t get stability. You get rigidity. And rigid systems break under pressure rather than bending and adapting.

Fritjof Capra, in *The Web of Life*, goes deeper into the science of this. Complex adaptive systems — whether ecosystems, organisms, or organizations — are characterized by nonlinear dynamics, emergent properties, and self-organization. They cannot be understood by analyzing their components in isolation because the properties that matter most arise from the interactions between components, not from the components themselves. The whole is genuinely different from the sum of its parts. And interventions that ignore this — that treat the system as if it were a collection of independent parts — produce unintended consequences precisely because the interactions continue operating in ways the intervention didn’t account for.

The distinction between complicated and complex is critical here and worth making explicit. A complicated system — an airplane engine, a logistics network, a supply chain — has many parts and requires expertise to understand, but it is ultimately knowable. You can map it. You can identify what’s broken. You can fix the broken part and restore function. Complicated problems yield to analysis and expertise.

A complex adaptive system is fundamentally different. It is not just difficult to understand — it is genuinely unpredictable, because it continuously adapts. The system responds to interventions. It learns. It self-organizes around new conditions. What worked last time may not work this time, because the system has changed in response to what happened last time. The Chaos Engine is a complex adaptive systems problem. And organizations trying to solve it with complicated-problem thinking — more analysis, better planning, cleaner processes — are applying the wrong framework to the wrong kind of challenge.

One of the deepest sources of organizational paralysis in the face of accelerating change is what systems thinkers call mental models — the invisible assumptions leaders hold about how the world works and how organizations should operate. These aren’t conscious beliefs. They’re the water leaders swim in: assumptions so embedded and so long unquestioned that they feel like reality rather than interpretation.

One of the most common and most damaging mental models operating in organizations right now: “it shouldn’t move this fast.” Leaders who hold this model — and many do, because they built their careers in a world that moved more slowly — are not simply mistaken about the pace of change. They are fighting or ignoring reality. And that fight shapes everything: which problems get framed as temporary versus structural, which solutions get considered, which voices get heard, and which information gets filtered out because it doesn’t fit the model.

Mental models don’t announce themselves. A leader whose mental model says “this is temporary disruption, things will stabilize” will consistently underinvest in building adaptive capacity — because adaptive capacity is expensive and unnecessary if things are about to stabilize. A leader whose mental model says “we just need better execution of our current strategy” will consistently misdiagnose execution failures that are actually strategy failures. The model generates its own confirmation. It is self-sealing.

We’ll go deeper on mental models in a future post. For now, the essential point is this: the organizations building genuine resilience against The Chaos Engine are the ones that have done two things simultaneously — adopted a complex adaptive systems understanding of what they’re actually navigating, and begun surfacing and examining the mental models that have been shaping their responses to it.

They haven’t eliminated uncertainty. They’ve built the organizational architecture — and the leadership awareness — to move through it.

Leave a comment

Subscribe now

Those nine forces: the pace of change, the talent drought, disengagement, stalled innovation, the breakdown of planning, policy whiplash, fraying culture, generational shifts, and the integration of AI.

It is time, 36 years after The Fifth Discipline, for systems thinking to finally become part of the toolbox every executive uses. The complexity organisations face today is calling out for it. Drawn from 36 years inside real organisations, the book offers a tested methodology for addressing all nine forces — systemically. The methodology includes systems thinking, iteration that creates virtuous cycles, and the creation of psychological safety through deep listening. Together these transform how projects and innovation actually happen. The book is a roadmap — and it has been successfully implemented in many organisations.

🇬🇧 UK readers: you can pre-order through Bookshop.org between 13–17 May and save 20% with codePREORDER20. Every sale supports independent bookshops across the UK.

https://uk.bookshop.org/p/books/innovation-ecosystems-a-dynamic-blueprint-for-organizational-success-and-engagement-ilene-fischer/3f64a3e65ba73196?ean=9781399833042

You have been reading me for months — some of you for years. You let me into your inbox, which is no small thing in this noisy world. I have written to you about disruption and culture and what it actually takes to change the way people work. And now I want to tell you what comes next.

After 35 years of doing this work, my book is real.

Innovation Ecosystems: A Dynamic Blueprint for Organizational Success and Engagement will be published with Hachette this November. Peter Senge wrote the foreword. Tom Peters gave me the cover quote. I appreciate their support; they have been important mentors in my career.

The book is the distillation of what I have been writing about here, and what I have spent decades inside organizations learning and wverything I have been listening for, It is about creating cultures of acknowledgement and appreciation — places where people are seen and heard for who they actually are and for what they contribute, where they can speak openly, where they can bring their talent and their passion into their day-to-day jobs. That is what creates real engagement. And real engagement is what drives performance.

It is also about something more urgent. Organizations today are facing nine disruptive forces all at once — the pace of change, the talent drought, disengagement, stalled innovation, the breakdown of planning, policy whiplash, fraying culture, the Gen Z revolution, and the AI and quantum convergence. Most leaders are trying to solve each one individually. That's why they are failing. These forces are connected. They have to be addressed as a system. It is time to apply systems thinking to the way we work — a tool that was a great idea when Peter Senge’s The Fifth Discipline came out 36 years ago, and that we are finally ready to use to create virtuous cycles of growth instead of vicious cycles of burnout.

This is not just a book launch. It is a movement. And I would love for you to be part of starting it with me.

Two ways in:

The Early Reader List. If you’d like to know the moment the book opens for pre-order, just reply to this email. Pre-orders during launch week move books onto bestseller lists, and every one matters.

The Launch Team. I have a limited number of Advance Reader Copies coming from Hachette. If you’d like to receive one in exchange for an honest review on Amazon during launch week, reply and tell me. You will get the book before it is available anywhere, and your honest review will help it find the readers who need it most.

Whatever you choose — even if you just want to write back and say hello — I would love to hear from you.

With appreciation and gratitude,

Ilene

Leave a comment

I’ve been thinking about a meeting I sat in years ago, and I can’t seem to let it go.

A mid-level manager — I’ll call her thoughtful, because that’s the word that keeps coming back to me — raised a concern about a strategic decision the executive team had already made. She wasn’t grandstanding. She wasn’t trying to win. She had spent months watching the decision play out at the operational level, gathering data, noticing what the people above her couldn’t see from where they were sitting. And she brought it into the room respectfully, the way you bring something fragile.

The executive dismissed her in thirty seconds. Didn’t engage with the data. Didn’t ask a single question. Just moved on to the next agenda item like she hadn’t spoken.

The meeting ended. People filed out. And for the next three years, no one in that organization brought a difficult truth to leadership.

Not because they didn’t have difficult truths. They had plenty. They just all saw — in that one moment — exactly what happens to the person who tells one.

I keep coming back to this story because I think it’s the most honest illustration I know of how psychological safety actually dies. Not through a policy change. Not through a reorganization or a values refresh or a town hall gone sideways. It dies in a single moment that everyone in the room remembers and nobody ever discusses out loud.

One visible consequence echoes through an organization for years.

People are exquisitely sensitive observers of organizational reality. We underestimate this constantly. They see exactly what gets rewarded and what gets punished — even when the punishment is as subtle as a thirty-second dismissal, even when no one would call it punishment if you asked them directly. They update their behavior accordingly. They give you the carefully filtered version of their thinking. They tell you what they believe you want to hear. They bring you the ideas they’re confident you’ll approve rather than the ideas that might actually change something.

And here’s the part that haunts me: you lose access to the intelligence you need most precisely when you need it most.

I’ve been writing about this in my book, Innovation Ecosystems: A Dynamic Blueprint for Organizational Success and Engagement, and the more I dig, the more I’m convinced that psychological safety isn’t built the way most leaders think it is. It isn’t built in training sessions. It isn’t built in team workshops or off-sites or carefully worded values statements. It’s built — or destroyed — in moments. One at a time. In the small, almost invisible choices leaders make when someone tells them something inconvenient.

What actually builds it is simpler than most leaders expect, and harder than most leaders want to admit:

Subscribe now

Leaders who are visibly, demonstrably changed by what they hear.

Not leaders who say “great point” and proceed exactly as planned. Leaders who genuinely incorporate feedback, who attribute it publicly, and who shift direction based on what they learned from someone three levels below them. When people see that happen — when they watch someone speak an uncomfortable truth and get genuinely thanked for it, when they see a senior leader change their mind in public — the entire system begins to shift.

Because every interaction is a data point their team is using to calibrate what’s actually safe. Every response to challenge. Every reaction to failure. Every moment when the truth is inconvenient and the leader chooses it anyway.

So I’ll leave you with the question I’ve been sitting with myself, the one that’s been quietly rearranging how I think about my own leadership:

When was the last time someone in your organization genuinely changed your mind — and did they know it?

If you can’t remember, that’s information. If they didn’t know, that’s information too.

The moments are happening whether we notice them or not. The only real question is what they’re teaching the people who are watching.

More soon,

Ilene

Leave a comment

I’ve been thinking about a story this week that I keep coming back to — one of those stories that changes how you see everything you thought you understood about how organizations solve problems.

It goes like this.

One of the world’s largest consumer products companies — the kind of company with resources most of us can barely imagine — spent years trying to solve a single technical challenge. Not a minor one. A major one. The kind of problem that sits on an executive dashboard quarter after quarter, never quite moving.

Their internal teams were genuinely brilliant. Their labs were world-class. They had every advantage you could name — budget, talent, leadership commitment, patience, time.

And the answer remained stubbornly out of reach. Every development cycle stretched toward a horizon they couldn’t quite reach.

Then someone — and I love this part — asked a different question.

Not “How do we solve this?”

But “Who has already solved this?”

The answer, it turned out, was a small bakery in Bologna, Italy.

The bakery had been using an edible ink process for years. They’d developed it to print on cakes and cookies. It was elegant, it was precise, it worked beautifully — and it had been sitting there, in plain sight, for years.

Nobody at the company had thought to look there. Why would they? The bakery was in a completely different industry, serving an entirely different market, solving an entirely different problem. There was no obvious reason to connect the two worlds.

The company adapted the technology. Launched the product. Completed in under a year a development cycle that had previously stretched indefinitely.

I’ve been in this work for 35 years, and I can tell you: this story isn’t unusual. What’s unusual is that someone asked the right question in time.

Most organizations operate on a deeply embedded cultural assumption — one that rarely gets examined out loud, though it shapes nearly every decision about how resources get allocated. The assumption is this: the best solution to our problem must come from inside our own walls.

This isn’t a deliberate strategic choice anyone would defend if pressed. It’s a reflex. A quiet belief, absorbed over years, that the talent inside is inherently superior to whatever exists in the world beyond the organizational boundary. That “our people” are smarter. That our investment in internal capability means we shouldn’t need to look elsewhere. That looking outside is, somehow, an admission of inadequacy.

That belief costs billions of dollars every year. In duplicated effort. In extended timelines. In solutions that could have existed five years earlier if someone had simply paused to ask who had already solved this before a single dollar was spent on internal development.

I’ve watched it happen more times than I can count.

Here’s what I think is really going on, and why this matters for anyone leading an organization right now.

The companies thriving today — the ones genuinely building what I call innovation ecosystems — have done something most of their competitors haven’t. They’ve built deliberate, systemic capabilities for bringing the outside in.

They have processes for scanning adjacent industries. Not occasionally. Not when a problem gets desperate enough. Systemically. They have someone whose actual job it is to ask, every quarter: “Where else in the world is this kind of problem being solved, and what are we missing by not looking?”

They’ve built cultures that reward the person who finds a better answer outside more than the person who insists on developing everything internally. That sounds simple. It isn’t. It requires reversing decades of organizational muscle memory that equates “not invented here” with somehow being insufficient.

And — this is the part I want you to hear most clearly — this is not about not trusting your people.

Let me say that again, because I’ve watched this misunderstanding derail good intentions over and over: building open innovation capability is not a vote of no confidence in the talent inside your organization. It is exactly the opposite. It’s about multiplying what your people can accomplish — taking their expertise, their judgment, their hard-won institutional wisdom, and connecting it to insights and innovations they could never have generated alone.

Your team doesn’t get smaller because you brought in the bakery’s process. Your team gets bigger. Their reach gets bigger. The problems they can solve in a year instead of a decade get bigger.

Building this capability — the discipline to look before assuming, the culture that rewards finding a better answer wherever it exists — is one of the highest-leverage investments any organization can make in its long-term innovation capacity. I say this having watched it work in healthcare, biotech, pharma, consumer products, and financial services. The pattern is remarkably consistent across industries.

The best innovations almost always come from the unexpected intersection of two worlds that have never spoken to each other.

An edible ink printer in a Bologna bakery and a global consumer products company. A bee’s hive and a skyscraper’s ventilation. A forest’s mycorrhizal network and a logistics company’s routing system. These aren’t cute analogies. They’re the actual source of some of the most important breakthroughs of the last twenty years.

The companies that will thrive in the next decade are the ones that stop treating that intersection as a lucky accident and start treating it as infrastructure.

So here’s what I’d leave you with this week.

Somewhere in your organization right now, there’s a problem that has been quietly classified as “ours to solve.” It’s on someone’s dashboard. It’s been there for a while. People have been working on it — hard, in good faith, with real skill — and the horizon keeps receding.

What would happen if, before the next development cycle began, someone asked a different question?

Who has already solved this?

It’s such a small question. And it can change everything.

Until next week —

Ilene

Leave a comment

Every week, in boardrooms and leadership off-sites, I hear some version of the same question:

“How do we protect our people from AI?”

I understand the fear underneath it. AI is moving faster than most organizations can process, the uncertainty is real, and the leaders asking this question are genuinely trying to do right by their people. But here is what I have learned in 35 years of watching organizations navigate disruptive change: the question you ask determines the future you build. And this particular question will lead you somewhere you do not want to go. Not because it comes from a bad place. Because it frames AI as a threat to defend against rather than a capability to build with. And organizations that frame technology as something to survive consistently lose to organizations that frame it as something to harness.

The question that actually opens something up

What I find myself asking instead is this:

“What becomes possible for your people because of AI?”

Feel the difference. One question produces a playbook for managing a threat. The other opens a conversation about building something new.

AI does certain things extraordinarily well — finding patterns across vast datasets that no human team could process in time to act on, generating options faster than any brainstorming session, handling computational complexity that would otherwise consume your best people’s energy for weeks. These are remarkable capabilities. They are also not the capabilities that create lasting competitive advantage.

What AI cannot do — and why it matters

AI cannot exercise genuine judgment in ambiguous, high-stakes situations where the right answer is not a pattern to be found but a value to be applied. It cannot build the kind of trust that makes someone willing to tell you what is really going wrong. It cannot ask the question that reframes the entire problem — the one that comes from decades inside an industry, from having watched the same pattern play out enough times to finally see it clearly. It cannot create the conditions where a skeptical person finally says what they actually think. And it cannot hold space for the loss and grief that come when people are being asked to let go of something familiar.

I want you to notice something about that list. These are not soft skills. They are not nice-to-haves. They are the precise capabilities that determine whether an organization can execute its strategy, retain its best people, and navigate genuine uncertainty. They are what AI makes more important, not less.

The part most strategies miss entirely

The organizations genuinely winning with AI have figured out the right division of labor. They use AI to accelerate the analytical and computational work so their people can do more of the irreplaceable work. Less time processing data, more time in the conversations that actually change things.

But that only works inside a culture built for it.

If your organization has a culture of fear and incremental thinking, AI will help you do both faster. That is not a joke — it is a genuine risk I watch play out in real organizations. A fearful culture with better AI tools becomes a fearful culture that moves faster toward outcomes nobody wants. AI amplifies what is already there. Deploy it into an organization with genuine psychological safety and real cross-functional trust, and it amplifies both. Deploy it into an organization where people are afraid to speak up, where the real conversations happen in the hallway after the meeting — and it amplifies that too.

The technology is not neutral. It is a multiplier. And multipliers make the underlying culture more of what it already is.

The leaders I have watched build something durable during periods of technological disruption share a specific orientation. They are not anti-technology. They are pro-sequence. They invest in AI capabilities and human capabilities simultaneously — and they understand that the order matters.

Technology deployed into a strong cultural foundation creates exponential value. Technology deployed into a weak one amplifies the weakness. That is not a technology decision. It is a leadership decision.

Culture first. Technology second. In that order, always.

I’d love to know what you’re seeing in your own organization. Are the questions being asked opening things up — or closing them down?

Leave a comment

We know the math. We’ve seen the post-mortems. 75% of mergers fail to achieve their stated goals.

And yet, in Mergers and Acquisitions, we treat this catastrophic failure rate as inevitable—the “cost of doing business.” It is practically built into the financial models.

But imagine applying that same math to any other critical business function. If clinical trials had a 75% failure rate, the world would stop.

I once found myself pitching cultural due diligence to a room full of private equity investors. These are brilliant people who build M&A deals for a living. I laid out the methodology. I showed the risk reduction. I showed exactly how the “people factor” consistently sinks returns.

And the response? Absolute, cold indifference. I could see the glazed look in their eyes. Not a single investor was interested.

This indifference is precisely why 75% of mergers fail.

In the frantic scramble for synergy and speed, we achieve perfect command over financial modeling, but we are fundamentally blind to the “living systems” we are buying. We treat people and culture as messy integration line items, things that just need to be managed, manipulated, and “fixed” after the close.

I saw the brutal consequences of this firsthand.

A PE firm brought me in after acquiring eight distinct home health and hospice companies in just 18 months. Think about that: eight completely separate cultures, eight different leadership teams, eight unique tribes. Suddenly, they were all told: “You are one organization. Now, adopt our superior system.”

The friction was immediate and intense. Performance dropped. Resistance was everywhere.

Subscribe now

But before we began integration, we decided to do one crucial thing that distinguished our work from standard restructuring:

We deeply listened from a place of no agenda.

This wasn’t a standard satisfaction survey or data-gathering exercise. This specialized methodology is the foundation of how we assess the health of an organizational ecosystem.

We didn’t go in with leading questions. We simply went in to understand and give voice to the emotional landscape. Our methodology was 108 in-depth, one-on-one dialogues across all eight companies. Zero leading questions. Zero prescribed outcomes.

None of what we heard would ever appear on any due diligence report, but every single word was determining whether this merger would succeed.

We heard the complex human dynamic that always follows a buyout. We heard relief from some: “This acquisition saved us.” But we also heard the “quiet terror” and grief from others—people who weren’t being difficult; they were just mourning the family environment they had built over a decade.

But here is the core truth of leadership that we must confront:

You cannot announce a new culture to a workforce that is still actively grieving its old one.

When we Deeply listened from a place of no agenda, something crucial happened. For many, it was the first time since the acquisition that anyone had asked how they were doing—and genuinely waited for the answer.

When people feel heard, they feel visible. The anxiety loosens. Only then can they begin the essential work of releasing and letting go of their organizational resistance to change.

When you remove the deep-seated fear, people stop expending energy protecting what they are scared to lose. Without that release, any “new culture” launch is just noise. People will nod, say all the right things, and go right back to quietly preserving the status quo.

Instead of forcing integration, we used this co-creative methodology to build a Third Culture—shared commitments that all eight helped to define. They chose it. They owned it.

This is the phase most acquirers skip. They assume that talent will issue ultimatums when that happens.

They don’t.

They silently update their LinkedIn profiles and go somewhere that feels like home. And the very value that justified the deal—the tacit knowledge, the established trust, the emotional commitment—walks right out with them.

We cannot achieve the value that justified the deal if the very engine of that value walks out the door. We must begin asking the human questions before the term sheet is signed: “What do these people fear losing? What would they protect at personal cost?”

Worth considering: When did the word “culture” first appear in your last integration planning—before the term sheet, or after the close?

If it’s after the close, your best talent is already gone.

This framework for deep listening and ecosystem health is one of the pillars of my new book, Innovation Ecosystems: A Dynamic Blueprint for Organizational Success and Engagement, launching November 2026 with Hachette. Foreword by Peter Senge.

Leave a comment

Share

I’ll tell you exactly why your last initiative failed.

Not the strategy. Not the budget. Not the people.

You skipped Phase 1.

In every Innovation Ecosystem I’ve built over 35 years, the first phase is called Release. And almost every organization I’ve ever worked with tries to skip it — because it feels slow, because it feels soft, because the pressure to launch is always more urgent than the discipline to listen first.

Release is simple in concept and demanding in practice: before you build anything new, you create the space for people to let go of what they’re carrying.

The fear from the layoffs eighteen months ago that nobody has named out loud.

The cynicism from the initiative that got funded with fanfare and quietly defunded six months later.

The exhaustion of being asked to “embrace change” and “lean into uncertainty” for what feels like the fifteenth consecutive year.

The unspoken belief — earned through repeated experience — that this new initiative will end the same way as all the others.

None of that disappears when you launch something new. It doesn’t evaporate in the kickoff meeting. It doesn’t dissolve during the strategy offsite. It goes underground.

And underground resistance is the most powerful force in organizational change. It doesn’t show up in town halls. It doesn’t appear on engagement surveys. It shows up in the meeting where nobody pushes back — because they learned long ago that pushing back is pointless. It shows up in the initiative that technically launches but never gains momentum.

What makes Release counterintuitive is that it asks leaders to invest time before anything visible gets built. No announcements. No launches. Just listening. In organizations relentlessly oriented toward output, this feels almost impossibly slow. But organizations that skip it pay a much higher price later — in resistance that surfaces at the worst moment, in momentum that collapses, in talented people who engaged briefly and permanently disengaged when the pattern repeated.

Release requires deep listening — not surveys, not pulse checks, not town halls where leaders present and employees politely absorb. Real conversations where leaders create genuine safety for people to say what they actually think, without consequence.

When people feel truly heard — often for the first time in their professional careers — something shifts that no methodology can manufacture.

The resistance begins to melt. Not because you convinced them. Because they finally felt safe enough to put it down.

THAT is when innovation becomes possible. Everything before that is noise.

Worth considering: What are the people in your organization still carrying from past initiatives — and has anyone actually created the conditions to hear it?

Leave a comment

Most conversations about culture change start and end with leadership behavior.

And leadership behavior matters enormously. But it’s only one piece of a more complex system. After 35 years of transformation work, here’s what I know:

Culture is not what leaders say. It’s not even just what leaders do.

It’s how people actually work together every day — the unwritten norms, the lived values, the specific behaviors that get rewarded or punished in practice, regardless of what any values statement declares.

Change the way people work — structurally, deliberately, with intention — and the culture changes. Not because you announced it. Because people experienced something different and updated their assumptions accordingly.

Here’s what makes this genuinely hard: organizational history doesn’t disappear when a new leader arrives.

I’ve walked into organizations where a fear-based CEO left two years earlier — replaced by someone genuinely committed to psychological safety and innovation. The new leader was doing everything right. And people still weren’t bringing real ideas forward.

Why? Because the scar tissue from the previous era was still there. Invisible on any org chart. Completely real in every interaction.

People remembered — viscerally — what happened the last time someone spoke up. The last time an experiment failed publicly. The last time a difficult truth reached leadership. Those memories shape behavior long after the person who created them is gone. History lingers. Sometimes for years.

This is why culture change requires more than a new leader with better intentions. It requires:

→ New norms — explicitly established, consistently reinforced, visibly modeled at every level → New structures — ways of working that make the desired behaviors the default, not the exception → New experiences — moments where people discover, through direct personal experience, that the old rules no longer apply

A norm that innovation is welcome means nothing without a structure that protects time for it, a process that routes ideas to real decisions, and a visible outcome where someone’s idea actually changed something.

Lived values are what people experience in the room — not what’s written on the wall.

Worth considering: What does the history of your organization still make people believe — and what specific experience would need to happen for them to believe something different?

Leave a comment

Research suggests it typically takes seven years for deep listening to become natural in an organization. The Innovation Ecosystem framework compresses that to 12-18 months—but only if leaders are willing to do the honest work of examining what’s actually in their left column.

Innovation doesn’t die in strategy sessions. It dies in the gap between what leaders say and what they actually think.

Worth considering: What’s currently in YOUR left column that might be shaping your team’s willingness to bring you real ideas?

Leave a comment

She came to me after her third all-nighter in a row.

VP of Strategy. Fifteen years at the company. Brilliant, committed, and completely done.

“I’m not leaving because of money,” she said. “I’m leaving because nothing I build here ever matters. Every idea dies in committee. Every initiative gets defunded. I’m exhausted pretending to innovate while we’re actually just maintaining.”

Three months later she was gone—taking fifteen years of institutional knowledge, client relationships, and unrealized potential with her.

This story is playing out in organizations everywhere. Right now.

Research shows 70% of preventable turnover links directly to daily management experiences, not compensation. The global economy faces a projected shortfall of 85 million skilled workers by 2030. And replacing a single employee costs 50-200% of their annual salary—not counting the 6-9 months before their replacement reaches full productivity.

But here’s what the data doesn’t capture: the IDEA that never got proposed. The breakthrough that died with the departure. The client relationship that quietly transferred.

The organizations winning the talent war have figured out something fundamental: people don’t stay for salaries. They stay for meaning.

The most effective talent retention efforts I’ve witnessed didn’t start with compensation reviews. They started with a harder question: Do people here experience genuine impact? Do they feel their full capability is being used? Is there a clear line between their daily work and something that actually matters?

What does that look like practically? Innovation teams with real authority. Protected time for experimentation—not stolen from already-full workloads. Psychological safety deep enough that failure is a learning event, not a career event.

One healthcare organization I worked with dropped voluntary turnover by 31% in twelve months. Not one salary was raised. They changed how people experienced their work.

The Great Talent Drought isn’t an external market problem. It’s a culture problem. And culture problems have culture solutions.

Worth considering: If your best person left tomorrow, what would you wish you had done differently in the last six months?

Leave a comment

“We’ve tried seventeen different innovation methodologies in five years. Every single one failed.”

The room went silent. Not surprised. Just relieved someone finally said it out loud.

Here’s what I’ve learned after 35 years in boardrooms and 45+ interviews with the world’s leading innovation thinkers: that CEO is not an outlier. He’s the rule.

70% of corporate innovation initiatives fail to deliver lasting results. The consultants leave. The frameworks gather dust. The innovation labs stand empty. And leaders keep asking: “Why aren’t we innovating?”

In October 2025, the Nobel Committee gave us the answer—validated across two centuries of economic data. Three economists proved that sustained growth depends on what they called self-generating processes: systems where each breakthrough creates the conditions for the next one.

Not programs. Not methodologies. Not quarterly initiatives. SYSTEMS.

This is what the successful 30% of innovation efforts have that the failing 70% don’t. They don’t treat innovation as a project to complete. They build ecosystems—integrated environments where Culture, People, and Technology reinforce each other continuously.

One global consumer products company built an open ecosystem where over 50% of innovations now include external partners. A major technology company didn’t launch a new program—their CEO transformed the entire operating culture from know-it-all to learn-it-all. The results followed.

The difference isn’t budget or talent. It’s ecosystem thinking versus isolated initiative thinking.

Organizations attempting system-wide change before employees are psychologically ready will fail—every time. It’s like asking someone to dance on hot coals. No matter how good the music, they can’t move when they’re in pain.

My book, Innovation Ecosystems: A Dynamic Blueprint for Organizational Success and Engagement, launches November 2026 with Hachette. Over the coming weeks I’ll be sharing the real stories, research, and practical tools that shaped it—because this work is too important to wait until publication day.

Because innovation ecosystems aren’t built alone. They’re built by communities of practitioners learning and experimenting together.

Worth considering: What’s the innovation challenge your organization keeps failing to solve—and what methodology have you already tried?

Leave a comment

Subscribe now

Week one of implementation: disaster.

Customers hated it. Operations couldn’t execute it. Finance wouldn’t fund it.

Meanwhile, across the hall, another team spent TWO DAYS building a rough prototype with pipe cleaners and cardboard. Tested with five customers. Got brutal feedback. Rebuilt in three days.

By week three: working solution customers loved.

Same company. Same challenges. Opposite approaches. Completely different outcomes.

This is the innovation murder mystery nobody talks about.

WHY PLANNING KILLS INNOVATION

Planning assumes you can predict the future.

You can’t.

Markets shift. Customers change minds. Technology evolves. That six-month plan you sweated over? Obsolete before you execute.

Deeper problem: Planning creates an illusion of progress while preventing actual learning.

Teams spend months in conference rooms debating hypotheticals instead of hours with customers discovering reality.

Maybe innovation is the reaction to the prototype.

You can’t innovate in theory. You have to build something and see what happens.

THE POWER OF ROUGH PROTOTYPES

Picture this: Senior executives on floor with pipe cleaners, Legos, magazines. Building three-dimensional models.

Sounds absurd, right?

Watch what actually happens:

CFO builds a tower of blocks showing workflow. Intern weaves pipe cleaners into a network. The engineering head cuts magazine images into a collage.

Hierarchies dissolve. Hidden assumptions surface. Breakthrough insights emerge.

Physical creation engages different brain pathways than verbal debate. When hands start building, minds stop defending.

That executive insisting “it can’t be done”? She just built a model proving exactly how it could work.

THE EXPONENTIAL LEARNING CYCLE

Each iteration doesn’t just improve linearly. It multiplies learning velocity.

Prototype 1: Solves obvious problem

Stakeholder feedback: Reveals three underlying issues you never saw

Prototype 2: Addresses those

New feedback: Uncovers systemic challenges

Prototype 3-4: Creating value in ways nobody imagined

You’re not just improving solution. You’re eliminating entire categories of problems. Opening new opportunities.

Traditional development: 12-18 months to discover you built the wrong thing

Rapid prototyping: 4-6 weeks to discover what customers actually need

The difference isn’t speed. It’s exponential learning.

THE FAILURE THAT TAUGHT EVERYTHING

The healthcare team prototyped a patient communication system.

Version 1: Total failure. Patients confused. Staff hated it. IT couldn’t support it.

But that failure taught what six months of planning never would have:

- Patients wanted simple texts, not a complex app

- Staff needed mobile access, not desktop

- IT could leverage existing systems

Version 4: 85% patient adoption first month. Staff satisfaction up 40%. IT costs 60% below projections.

Prototype “failed.” But it generated learning that made success inevitable.

WHY THIS TERRIFIES TRADITIONAL ORGANIZATIONS

Rapid prototyping requires what most cultures can’t stomach:

- Showing unfinished work publicly

- Embracing visible failure

- Releasing control of outcomes

Traditional culture: Perfectly private, hides failures, controls everything

Ecosystem culture: Share rough work early, celebrate intelligent failures, discover what emerges

Organizations that master this don’t just move faster. They develop an unfair advantage: learning from reality instead of assumptions.

THE BOTTOM LINE

Right now, your competitors are perfecting plans that’ll be obsolete before implementation.

What if you tested real solutions with real stakeholders in days?

Next time someone proposes a six-month planning process, ask: “What could we learn in six weeks of prototyping?”

The answer will terrify your planning committee.

That’s exactly why you should do it.

Subscribe now

Leave a comment

Subscribe now

A healthcare CEO looked like he hadn’t slept in weeks. Customer satisfaction tanking, retention declining, competitors circling. They’d tried everything — training, process improvements, tech upgrades — nothing moved the needle.

“We’ve tried everything,” he said.

Not quite. They hadn’t tried building an Innovation Ecosystem.

Twelve months later:

• $54M operating margin increase (goal: $15M — 360% over target)

• Customer satisfaction up 23 points

• Member retention up 15%

• Great Place to Work: 50 to 70

• Voluntary turnover down 31%

But numbers are the outcome, not the story.

We began the way every Innovation Ecosystem begins — six weeks of Deep Listening at every level, every department. Not surveys. Not town halls. Real listening that drew out what people had never felt safe saying — how ideas died in committee, how collaboration was career-limiting, how “innovation” had come to mean extra work with no reward.

Most organizations skip this step entirely, rushing straight to methodology and strategy. That is precisely why they fail. Everything that goes unheard — the frustration, the skepticism, the unspoken “we’ve tried this before” — doesn’t disappear. It becomes resistance. And resistance quietly kills change initiatives from the inside. Deep Listening melts that resistance before it can take hold, transforming it into the engagement and commitment that innovation actually requires.

What Deep Listening surfaces is never what leadership expects. People here didn’t lack ideas or commitment. They lacked safety. The organizational memory was long and the scar tissue deep — failed initiatives, quiet defundings, risk-takers who tried and were punished for it. But underneath that cynicism was something else entirely: hunger, untapped expertise, and a genuine commitment to serving customers better.

Deep Listening created something this organization had never had: psychological safety. Not the kind announced in a town hall. The kind that emerges when people experience — perhaps for the first time — that someone is truly listening without an agenda. When people felt truly safe, resistance melted into possibility. And that possibility became the foundation for everything that followed.

With psychological safety established, 120 people came together for a two-day offsite. The CEO set the tone: “I don’t have all the answers. That’s why you’re here.”

For the first time, people saw they wouldn’t be handed a solution — they would collaborate to create one. They didn’t wait to be assigned — they volunteered for five cross-functional teams, and a waitlist formed.

Read that again: a waitlist formed. In an organization where cynicism ran deep and trust was fragile, people were fighting to get on the teams. That is what psychological safety makes possible.

Those teams looked unlike anything this organization had seen before — claims processors working alongside IT directors, finance analysts partnering with customer service reps, departments that hadn’t spoken in years now solving problems together. Leadership protected the time and resources these teams needed and held firm. That commitment wasn’t incidental to the results. It was essential to them.

The discoveries came fast — and they were humbling.

The customer team realized the organization had never actually measured what customers valued. One question — “What matters most about your healthcare insurance?” — changed everything. Customers wanted faster claims, clearer communication, and easier access. Armed with that insight, the team focused first on claims processing — the top priority. Through rapid prototyping, they went from a failed first attempt to a 60% reduction in claims processing time. Each failure taught them something the next prototype could address. This is the power of rapid prototyping within an Innovation Ecosystem — not to get it right the first time, but to continuously gather feedback from all stakeholders, incorporate their insights, and build iteratively until the solution reflects the full intelligence of the system.

The efficiency team found three departments independently verifying the same data — tripling work with zero added value. Their fourth prototype eliminated the redundancy entirely and improved accuracy by 40%.

The technology team discovered expensive software sitting unused because employees had no voice in selecting it. A co-design process that brought users into the selection changed everything — adoption jumped from 20% to 80%.

As word spread about these early wins, momentum built organically. What began as five teams grew to forty — colleagues who had watched the first wave of results now wanted to be part of creating the next ones. Original members became mentors, carrying the methodology into every corner of the organization. Six months in, after hitting milestones no one thought possible, they celebrated — not with a corporate all-hands, but with a marching band and customers sharing how their experiences had been transformed.

This is what Innovation Ecosystems makes possible — not programs imposed from above, but conditions created from within where people bring their full capability to work, silos dissolve, and rapid learning replaces planning paralysis.

The $54M was never the goal. It was what the system made inevitable.

My book, Innovation Ecosystems: A Dynamic Blueprint for Organizational Success and Engagement, publishing November 2026 with Hachette, goes deep on exactly how to build these conditions in your organization — the Seven-Phase Framework, the three core components, and the real stories of organizations that made the shift.

What would become possible if you stopped launching innovation and started building it as an ecosystem?

?

Let me tell you about Sarah—brilliant engineer, eight years at a Fortune 500 company, consistently top-rated performer. She just quit.

Not for money. Yes, another company offered 20 percent more, but that’s not what drove her out. She left because her ideas were never truly heard—worse, she felt invisible to her management. Like she didn’t matter. No path for meaningful growth. Work felt disconnected from her life’s purpose and the organization’s purpose. Innovation was happening AROUND her rather than WITH her. She was being informed of decisions, not invited to shape them.

This crisis is devastating organizations across every industry, every sector, every size company. We ARE in a TALENT SHORTAGE and a TALENT ENGAGEMENT CRISIS—each crisis feeding the other in a vicious cycle.

The brutal data: An 85 million global shortage of workers with specialized skills that take years to develop—think AI experts who are also healthcare experts.

Separately, organizations hemorrhage $900 billion annually in turnover costs. And 70 percent of preventable turnover links directly to MANAGEMENT EXPERIENCES and cultures that exclude people from meaningful participation—not compensation.

People aren’t leaving jobs. They’re leaving managers and the soul-crushing systems and cultures those managers represent.

THE DEATH SPIRAL

Here is the reinforcing loop: Can’t find talented people → overload existing employees → burnout → turnover → deeper shortage. Meanwhile, Gen Z watches this chaos and thinks, “Why would I sign up for that nightmare?”

When organizations stop treating people as executors of someone else’s plans and empower them with real authority to experiment and shape solutions, everything changes. It’s not MORE money. It’s MEANINGFUL work.

When I implemented innovation ecosystems at one organization, we gave people genuine voice in decisions, made their impact visible, and created psychological safety not only to experiment but to be truly heard. Turnover dropped 40 percent in 12 months. Same compensation. Same benefits. Different culture built on trust and psychological safety.

THE REAL COST NOBODY CALCULATES

When Sarah left, the organization lost: Eight years of institutional knowledge. Stakeholder relationships she’d built across departments. Deep understanding of critical projects only she grasped. Team confidence in her judgment.

They hired a replacement at 20 percent higher salary. Spent six months on ramp-up. Lost momentum on three major projects. Team morale never recovered because everyone knew—Sarah didn’t leave for money. The organization failed her.

Multiply this across thousands of employees daily: $900 billion annually in compounding losses of knowledge, relationships, momentum, and trust.

WHAT ACTUALLY WORKS

After 35+ years in organizational transformation: Organizations that retain top talent don’t have better benefits or higher salaries. They build psychological safety as the foundation—where speaking up isn’t career suicide and experiments don’t end in punishment. They have leaders who genuinely listen and act on what they hear. They have systems that enable innovation rather than constrain it. They have cultures where people see their fingerprints on outcomes that matter.

The formula: Psychological safety unlocks trust. Trust creates meaning. Meaning produces a visible impact.

How many Sarahs can your organization afford to lose?

Refer a friend