Your team has fixed the same problem three times. You bought the tool, rewrote the process, sent the training link, and the old behavior came back within a month. The work isn't failing because people lack instructions. It's failing because the solution asks people to change how they prioritize, share information, and make decisions, and no one has led that part of the work.
That's where adaptive leadership examples are useful. They don't just show a leader making a bold call. They show how a leader diagnoses whether the problem is technical or human, names the loss people will feel, and gives the group a practice it can repeat under pressure. In 2024, 78% of surveyed CEOs reported a high level of business uncertainty, while 77% of leaders saw room to improve organizational nimbleness, according to the Spencer Stuart survey of 1,036 CEOs and 1,285 directors.
The eight cases below cover technology, enterprise transformation, finance and operations, and creative and public sectors. Each one is broken into the adaptive behavior, the diagnostic question you can ask, and one replicable team practice. I recommend reading for the practice you can test this week, not for the biography. In 2024, 46% of surveyed executives identified the ability to adapt quickly to changing circumstances as a key management competency, in the Business Talent Group and Atreus Leadership+ Executive Survey. That skill is built in small, observable routines.
1. Adaptive vs. Technical Challenges Framework (Heifetz and Linsky)
Ronald Heifetz and Marty Linsky of Harvard Kennedy School make a distinction that saves leaders weeks of wasted effort. A technical problem has a known solution an expert can apply. An adaptive challenge requires people to change values, beliefs, habits, or ways of working. Applying a technical fix to an adaptive challenge is a common reason change efforts stall, even when the tool itself works.
Say an IT team rolls out a new cloud security policy. The settings are correct, but engineers keep sharing access informally to move faster. More training won't solve that. The team has to change its belief about speed versus control, and managers have to stop rewarding shortcuts that create risk.
Behavior, Question, and Practice
- Adaptive behavior: Diagnose before you prescribe, and give the work back to the people who must change.
- Diagnostic question: Does this problem persist because we lack expertise, or because people must change behavior, priorities, or loyalties?
- Replicable practice: Run a 30-minute diagnosis session. List what's technical, what's adaptive, and name the losses each group faces if the change succeeds.
Practical rule: If the solution requires people to let go of status, comfort, or a familiar identity, you're not facing a technical problem.
This needs repetition, not a single workshop. Recent research summarized in an empirical model of adaptive practices points toward recurring practices including iterative sensemaking, mobilization, calibrated authority, preparedness routines, and human-capacity management. Use small experiments and frequent check-ins. Say out loud what people will lose, such as autonomy, time, or a trusted routine. People resist loss more than they resist change, and naming it lowers the temperature enough for honest work to start.
2. Satya Nadella's Growth Mindset Culture Shift at Microsoft
When Satya Nadella became CEO of Microsoft in 2014, he didn't start with a new org chart. He targeted the culture that rewarded internal competition and being the smartest person in the room. Drawing on Carol Dweck's work, he contrasted a know-it-all culture with a learn-it-all culture, and tied that shift to Microsoft's move into cloud computing with Azure.
The trade-off is real. A learning culture sounds soft until you connect it to promotion, recognition, and what managers ask in reviews. Nadella described the approach publicly in his book Hit Refresh from 2017, but the operational lesson is simpler. People copy what leaders notice and reward, not what leaders announce.
Behavior, Question, and Practice
- Adaptive behavior: Model learning in public by admitting what you don't know yet.
- Diagnostic question: What behavior gets rewarded here, proving you're right or learning fast enough to change your mind?
- Replicable practice: End weekly reviews with one round of "What did you learn, and who outside this team helped you learn it?"
This matters now because tools change faster than habits. In 2024, only 15% of surveyed leaders said their company's innovation was keeping pace with rapid AI advances, despite 71% of organizations providing AI tools and 61% offering AI training, according to findings Slalom published in 2025. Access isn't the bottleneck. Leaders who ask "What have you learned?" more often than "Why did this fail?" get earlier signals, and their teams share knowledge across boundaries instead of protecting it.
3. Alan Mulally's Turnaround at Ford Motor Company
Alan Mulally became CEO of Ford in 2006, when the company was losing large amounts of money. His best-known move wasn't a slogan, although One Ford gave people a shared direction. It was a weekly Business Plan Review where senior executives reported status on a common color-coded scorecard, in front of each other, every week.
That rhythm exposed a human problem first. Leaders were hiding bad news because honesty felt unsafe. Mulally required candor and rewarded people who surfaced problems early. Ford also secured a large credit line before the 2008 financial crisis, which helped it avoid the bankruptcy and government bailouts that hit other automakers. The financial decision mattered, but the review discipline is what leaders can copy.
Behavior, Question, and Practice
Adaptive behavior: Make it safe to report red status before a problem becomes a crisis. Diagnostic question: Where is my team coloring work green to avoid an uncomfortable conversation?
- Replicable practice: Hold a 45-minute weekly review with no more than a handful of priorities on one shared scorecard.
- Closing move: Ask each owner, "What do you need from me?" and record the answer as your commitment.
Punish the first person who brings bad news and you'll get polished updates until the quarter collapses.
Don't turn the review into a status recital. If everything's green, you're not learning. Keep priorities small enough that the whole team can focus, and treat a red item as a request for help, not a character verdict. That's how transparency becomes an operating habit instead of a value on a wall.
4. Lou Gerstner's Transformation of IBM
Lou Gerstner joined IBM as CEO in 1993, when the company was near financial crisis and widely seen as fragmented and slow. The obvious technical answer was to break it apart or sell better hardware. Gerstner did something harder. He shifted IBM toward integrated services and solutions for customers and pushed competing divisions to work as one unit.
He also pushed back on vision talk at the wrong moment. Gerstner said IBM did not need a vision statement then, because the immediate priority was to execute. His account in Who Says Elephants Can't Dance? from 2002 remains useful because he treats culture and structure as operating problems, not communications problems.
Behavior, Question, and Practice
- Adaptive behavior: Start with what customers need, then remove internal barriers that stop teams delivering it.
- Diagnostic question: Are we organized around our history and internal status, or around the customer's problem?
- Replicable practice: Pick one customer journey that crosses three teams. Assign one shared outcome, one joint metric, and one weekly decision forum.
Cross-boundary work needs evidence, not encouragement. In the Center for Creative Leadership case study of Cape Fear Valley Health, 90% of participants improved their ability to work across boundaries and 95% reported improved ability to use feedback to make changes over an 18-month initiative. That case also recorded employee turnover declining by 3%.
Use that pattern in finance, operations, or service delivery. Define shared outcomes across departments, create structured feedback cycles, and track retention, customer satisfaction, and execution together. Leadership training alone won't hold. Governance routines and operational accountability have to carry the new behavior after the workshop ends.
5. Ed Catmull's Braintrust at Pixar
Ed Catmull, co-founder of Pixar, built the Braintrust to solve a creative problem that also appears in product, engineering, and operations teams. Directors present films in progress to other filmmakers and receive candid criticism. The director keeps creative control and decides what to change.
That boundary is the whole design. If reviewers can overrule the owner, people stop bringing unfinished work. If feedback stays vague to protect feelings, weak work survives too long. Catmull argues the greatest threat to creativity is fear of failure, and he lays out the approach in Creativity, Inc. from 2014.
Behavior, Question, and Practice
- Adaptive behavior: Separate feedback about the work from judgment about the person.
- Diagnostic question: Can people name a specific flaw in my plan in this room without paying for it later?
- Replicable practice: Hold reviews early, when work is still rough, and state at the start whether input is advisory or binding. Give reviewers one rule: name the specific problem you see and offer options, never a verdict on competence.
A product team reviews a prototype at 40% complete. Reviewers identify where users will get stuck, the owner listens without defending every choice, and the owner leaves with the decisions still in their hands. I recommend this format for any team where seniority suppresses dissent. Psychological safety gives hard information a way to arrive while you can still use it.
6. Google's Search Inside Yourself Mindfulness Program
Search Inside Yourself began at Google in 2007, developed by engineer Chade-Meng Tan. It combines mindfulness meditation with emotional intelligence and practical leadership skills. Participants practice attention training, self-awareness, and empathy so they can respond to stress and conflict more skillfully. The program later spread through the Search Inside Yourself Leadership Institute to other organizations.
Treat this example carefully. Meditation won't fix an overloaded roadmap, unclear authority, or a manager who avoids decisions. What it can do is give leaders a pause between trigger and response. That pause matters in adaptive work, where the first reaction is often to defend, blame, or rush to a technical fix.
Behavior, Question, and Practice
- Adaptive behavior: Regulate your own attention before you try to mobilize other people.
- Diagnostic question: Am I reacting to this person's words, or to the threat and frustration I'm carrying into the conversation?
- Replicable practice: Take three slow breaths before replying in a difficult meeting, then restate the other person's concern in one sentence.
A direct caution: Don't use mindfulness to ask people to tolerate a broken system more quietly.
Start small and keep it voluntary. Five to ten minutes a day is enough to build the habit, and no one should feel pressured to join. Pair the practice with observable leadership skills, such as listening without interrupting, asking a clarifying question, or naming your emotion without acting on it immediately.
During a budget review, a finance lead feels attacked. She takes the pause, asks what risk the engineering team sees in her numbers, and the room shifts from defending positions to examining the constraint. One question turns a standoff into a diagnostic conversation, and that is where many adaptive efforts are won or lost.
7. Jacinda Ardern's Empathetic Crisis Leadership in New Zealand
On March 23, 2020, New Zealanders learned they had roughly two days before a nationwide lockdown took effect. According to a PMC assessment of New Zealand's COVID-19 response, Prime Minister Jacinda Ardern had introduced a four-level alert framework on March 21, when the country had 52 confirmed cases and four probable cases. The Level 4 lockdown began March 25, with 102 confirmed cases.
The same assessment reports that the public had approximately 48 hours to prepare, a simple shared objective, and regular briefings. Ardern acknowledged the difficulty openly, addressed mental health and economic concerns alongside public health, and used "be kind" to encourage community responsibility. By June 8, community transmission had been eliminated. Empathy and decisive action worked together: the empathy made the action legible and sustainable.
Behavior, Question, and Practice
- Adaptive behavior: Explain the reasons behind difficult decisions, acknowledge emotional impact, and revise in stages as evidence changes.
- Diagnostic question: Do people understand what we're doing, why it matters, and what will trigger the next change?
- Replicable practice: Use a three-part update every week. State what changed, what hasn't changed, and when you'll update people again.
Update people even when there is no new information. Silence fills with rumor. Say what changed, what has not changed, and when the next update comes, and name the milestone that will let restrictions or controls ease, the way a numbered alert level tells people where they stand. Use simple language and don't pretend certainty you don't have. In a service outage, a restructure, or a client escalation, that rhythm gives people enough stability to keep adapting.
8. The U.S. Army After Action Review
The After Action Review, or AAR, was developed in the U.S. Army during the 1970s. Units use it after training exercises and operations to examine what happened, why it happened, and what should change next time. Business and software teams now run the same structure as retrospectives after projects and sprints.
The method asks four questions in a fixed order: What was supposed to happen? What happened? Why was there a difference? What can we improve? The order matters. Teams that skip to solutions before agreeing on the facts end up debating blame instead of causes.
Behavior, Question, and Practice
- Adaptive behavior: Turn experience into a specific change while memory is fresh, without assigning blame.
- Diagnostic question: What did we learn here that we will still be doing differently in 30 days?
- Replicable practice: Hold a 30-minute review within days of finishing a task, invite junior team members to speak first, and end with one or two actions that have owners and dates.
- Freedom within a frame: Keep clear boundaries for security, privacy, quality, and legal compliance, while teams choose how to improve inside those guardrails.
Junior members speak first for a reason. Rank anchors a room fast, and once a senior voice names a cause, dissent gets expensive. I recommend the facilitator stay out of the content and enforce only two things: facts before theories, and every action leaving the room with an owner and a date.
That balance between autonomy and control is getting harder to hold. A cross-industry survey covered in McLean & Company's HR Trends Report for 2026 announcement included 1,626 HR and leadership respondents and found organizational change outpacing leadership capacity amid AI and economic uncertainty. Adaptability can mean changing rules faster, with frontline input and evidence, rather than adding more of them.
Feedback loops work when frontline people have authority to name constraints. At UCI Health's Medical Intensive Care Unit, a nursing leadership case on the POWER strategy reports staff classified as engaged rising from 19% to 60% after two years, with the mean engagement score moving from 3.53 to 4.14. The results come from one unit's implementation, and what transfers is the design of the loop: shared decision spaces, transparency, weekly indicators, and a clear line between technical fixes and cultural change.
How the eight adaptive leadership examples compare
The eight examples share one move: the leader changes conditions so people do the adaptive work themselves. They differ in where that move applies. Read down the question column and stop at the one that fits your situation.
| Example | Diagnostic question | Signal the challenge is adaptive | Main trade-off |
|---|---|---|---|
| Adaptive vs. Technical Challenges Framework (Heifetz and Linsky) | Will expertise fix this, or must people change how they work? | The same problem returns after every technical fix | Careful diagnosis is hard to defend under time pressure |
| Satya Nadella's Growth Mindset Culture Shift at Microsoft | Do people treat gaps in knowledge as learning or as risk? | Employees hide what they do not know instead of asking | Culture change moves slowly and unevenly across teams |
| Alan Mulally's Turnaround at Ford Motor Company | Would anyone here report a red status this week? | Reports stay green while results keep worsening | Weekly reviews consume time teams could spend executing |
| Lou Gerstner's Transformation of IBM | Are we organized around our own structure or around the customer? | Customers get passed between units that each optimize locally | Integrating across divisions slows decisions that used to be local |
| Ed Catmull's Braintrust at Pixar | Will people show rough work before it is finished? | Work surfaces only when it is too late for feedback to help | Candid critique stings without trust already in place |
| Google's Search Inside Yourself Mindfulness Program | Can people pause before reacting under stress? | Tense conversations escalate faster than they resolve | Gains depend on sustained, voluntary practice |
| Jacinda Ardern's Empathetic Crisis Leadership in New Zealand | Do people understand both the decision and its cost to them? | Compliance holds on paper while trust erodes | Communication cannot substitute for sound policy |
| The U.S. Army After Action Review | Which gap between plan and outcome do we fix first? | The same mistakes recur project after project | Reviews become theater when no action follows |
If two signals fit, start with the cheaper practice to test. Green reports beside falling results call for Mulally's review. A problem that returns every quarter calls for the diagnostic first.
Turning Adaptive Leadership Examples Into Daily Habits
Go back to that opening problem, the one your team has fixed three times. Before you buy another tool or rewrite the process again, ask the diagnostic question from the Heifetz and Linsky case. Does this persist because we lack a known solution, or because people must change how they work, what they value, or who they trust? If the answer is the second one, your job is to mobilize people to do difficult work they would rather avoid.
Then pick one behavior and match it to the gap you found. If problems surface too late, borrow Mulally's weekly review and reward the first honest red status. If drafts stay hidden until they are polished, use Catmull's Braintrust rule and make feedback advisory so owners bring rough work earlier. If the team is strained during a messy transformation, copy Ardern's update rhythm, or add the Search Inside Yourself pause before a conversation you know will be tense.
Your Next Two Weeks
- Week one: Run one diagnosis session. Separate the technical work from the adaptive work, name the losses, and assign one bounded experiment.
- Week two: Hold a short After Action Review. Ask what was supposed to happen, what happened, why there's a gap, and what you'll change.
- Every meeting: End by asking what people learned and what they need from you.
Measure whether the practice changes behavior. Track adoption, cycle time, customer outcomes, and how many experiments become standard practice. Watch who speaks first, who brings bad news, and whether feedback turns into action. Those signals tell you more about human behavior than a launch announcement does. They also show you where leadership development is real and where it's only vocabulary.
When a signal moves the wrong way, treat it as diagnostic data. If nobody raises a red status in the weekly review, the constraint is psychological safety, so work on that before changing the meeting format. If the After Action Review produces no changes, it has slipped into the performative pattern that makes reviews useless. Adjust the practice and run the cycle again.
Adaptive leadership is built through repeated practice, reflection, and revising your approach when reality disagrees with your plan. Leaders who guide teams through sustained change still face the same basic test: can you diagnose, communicate clearly, and keep learning in public? Jay Kalatuarachchi, the technology and business leader behind Kushan Business Solutions LLC, writes about leadership and organizational change from a career spent leading teams and supporting organizations through transformation.
Start this week with one 30-minute session. Bring a recurring problem, ask whether it's technical or adaptive, and leave with one experiment, one owner, and a review date within 14 days. Then run the review and change one thing based on what you learn.
