Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Agility Shift

Agility Shift

Creating Agile and Effective Leaders, Teams, and Organizations
Build teams that adapt when plans fail, before a crisis forces them to learn.
by Pamela Meyer 2015 240 pages
3.34
143 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat agility as a trained organizational capability, not a crisis reflex

Agility is built deliberately. The Agility Shift is the ongoing development of the competence, capacity, and confidence to learn, adapt, and innovate as circumstances change. Competence means having relevant skills and knowledge; capacity means being able to use them amid uncertainty; confidence means trusting that oneself and others can respond effectively. The book opens with a workshop scheduled on the day a company announced mass layoffs. The facilitator abandoned her original agenda, acknowledged the team’s shock, and helped members support one another and find ways forward. The situation changed; the work became helping people meet it.

Readiness has business value. The book cites research associating agile firms with faster revenue growth and higher profits, but its argument is broader: agility also supports engagement and purposeful work. It is not a rare gift reserved for crisis heroes. It is a shared capability that people can practice before they need it.

Analysis

The useful shift is from praising quick reactions to building the conditions that make good reactions possible. That resembles preparedness in emergency medicine: teams rehearse roles and communication because stress can narrow attention and make familiar routines hard to access. The workshop story also shows that agility is not synonymous with speed. The facilitator first recognized the participants’ reality, then changed course. A caution follows: resilience language can be misused to ask employees to absorb preventable disruption. Organizational agility should include changing harmful systems, not merely asking people to cope better.

Build a Relational Web before you need rescue

Relationships make resources usable. A Relational Web is the personal and organization-wide network through which people share support, coordination, knowledge, ideas, and tangible resources. It includes current and past relationships, colleagues’ skills, institutional expertise, and resources such as facilities or reputation. After a 2013 tornado devastated Washington, Illinois, neighbors searched for one another, used a Facebook group to connect survivors with help, and shared vehicles, meals, and labor. The town’s response depended on connections already present, then widened as volunteers from nearby communities joined in.

The web helps people interpret events. It supports sense making, understanding what is happening, and meaning making, deciding what it means and what to do. Relationships can also reduce stress and make it easier to think clearly. A contact list alone is not enough: ties become useful through trust, interaction, and mutual help.

Analysis

This account makes social capital concrete: a network is valuable not because names are stored somewhere, but because people can mobilize help and knowledge through it. The idea connects with research on collective efficacy, the shared belief that a group can act together, which helps explain why community ties matter during emergencies. Yet networks are not automatically inclusive or beneficial. They can reproduce status hierarchies, exclude outsiders, or circulate bad information. A strong web therefore needs diverse connections, clear communication, and enough trust for people to question assumptions rather than simply reinforce one another.

Prepare people to act when plans meet reality

Preparation outlasts prediction. The book does not argue that planning is useless. Plans clarify priorities and values, but they rest on assumptions about a future that may change. Preparation develops the readiness to adjust when it does. Captain Chesley Sullenberger spent 42 years flying before he had to land a disabled passenger plane on the Hudson River. The emergency lasted roughly 208 seconds. His experience did not predict that exact event; it prepared him to recognize the situation and act with the resources available.

Interact, not just collect data. More information can help, but it cannot guarantee control in a fast-changing situation. Teams must share observations, test their interpretation, and coordinate a response. The shift is not away from analysis, but away from treating analysis as a substitute for action and communication. Plans should guide judgment, not overrule new evidence.

Analysis

This distinction echoes a core principle in high-reliability work: procedures matter, but competent teams notice when conditions no longer match the procedure’s assumptions. Preparation is thus not an excuse for improvisation without discipline. It combines shared priorities, practiced skills, and permission to update a plan. The tension is practical: too little analysis can create reckless action, while endless analysis can delay a needed response. A useful test is whether added information is changing the decision, or merely postponing responsibility for making one.

Use five dynamics to turn values into daily agility

Five practices reinforce one another. The book’s five dynamics are relevance, responsiveness, resilience, resourcefulness, and reflection. Relevance links decisions to purpose and customer needs. Responsiveness means acting effectively and in time. Resilience means regrouping and adapting after disruption, not necessarily returning to the old normal. Resourcefulness means using available people and tools creatively. Reflection turns experience into learning. Together, these dynamics help an organization spot what matters, act, recover, improvise, and improve.

The examples show the stakes. Ericsson relied on an Albuquerque chip supplier after a fire, while rival Nokia quickly searched for alternatives through its network. The book reports that Ericsson lost revenue and market share after the disruption. The lesson is not simply to buy more backup supplies. Organizations need to notice warning signs, mobilize relationships, and learn from the response.

Analysis

The five dynamics function best as a connected operating model rather than five independent virtues. Purpose helps determine which signals matter; reflection improves future responses; resilience depends on both available resources and relationships. This is close to the logic of adaptive systems, where effective behavior emerges from feedback among parts rather than command from a single center. The framework also poses a measurement challenge. Speed is easy to count, while purpose, learning, and recovery quality are harder. A dashboard that rewards only quick response can produce hasty decisions and conceal whether the response solved the real problem.

Let leadership follow responsibility, not titles

Anyone can take the lead. The book defines leadership as accepting responsibility for an emerging challenge or opportunity, rather than as authority attached to a job title. At UPS, a weekend facilities manager answered a ringing phone outside his usual duties. A mother was searching for a wedding dress lost in the delivery system. He contacted people who could help, located the package, and arranged delivery in time for the wedding. His effectiveness depended on initiative and on knowing whom to involve.

Make initiative safe enough. Under social or physical threat, people can become defensive and lose access to flexible thinking. Leaders can help by modeling curiosity, welcoming questions, and giving colleagues room to experiment. Leadership also includes followership: stepping back when another person has the expertise or momentum. Empowerment works best when people know the purpose, decision boundaries, and support available to them.

Analysis

Distributed leadership is more than encouraging initiative. It reallocates decision rights to people close to the relevant information, a move that can reduce delay and improve service. The wedding dress story captures the human upside of that design. Still, empowerment without clear boundaries can transfer risk downward while leaving authority at the top. Effective organizations pair discretion with escalation paths, adequate training, and accountability for system-level barriers. Safety also does not mean comfort at all times. People need enough trust to raise concerns, including concerns that challenge a leader’s preferred story.

Make teams improvise through short, customer-tested cycles

Build on what appears. Meyer compares agile teams to improvisational theater groups. Players establish a few shared starting conditions, accept new contributions, and develop the scene together rather than following a fixed script. In work, those starting conditions might be a customer need, a budget limit, or a technical requirement. The team must keep checking that everyone understands them the same way. Studies of SWAT teams and film crews found that prepared teams could handle surprises by communicating, shifting roles, and using available resources.

Short cycles reveal reality sooner. Agile software teams break work into sprints, often two to four weeks long, and test usable versions with customers. Brief stand-up meetings surface progress and obstacles; review meetings help the team adjust its process. This contrasts with a waterfall approach, where much is specified upfront and feedback may arrive too late or cost too much to incorporate.

Analysis

Improvisation here is disciplined cooperation, not unstructured spontaneity. A shared purpose and a few explicit constraints create enough stability for creative work, while frequent feedback prevents the team from confusing its internal assumptions with customer value. This resembles iterative design and scientific experimentation: make a bounded attempt, observe what happens, and revise. Short cycles are not universally superior, however. Work involving irreversible decisions, strict safety standards, or long research timelines may require extensive upfront analysis. The key is to place feedback as early as the risks and nature of the work allow.

Learn in real work, then reflect before habits harden

Experience becomes learning through reflection. Learning agility means learning during action and carrying lessons from one setting into an unfamiliar one. The book distinguishes operational knowledge from relational, embodied, reflective, and contextual knowledge, which develop through interaction and direct experience. Anne Schwartz’s UPS career illustrates the point: she moved from package driving through new roles and locations into global leadership and talent development. Each stretch assignment required her to learn while working, not wait until she had mastered the next job in advance.

Make learning continuous. The book cites estimates that 70 to 90 percent of workplace learning is informal, while formal training often transfers poorly to daily work. It recommends stretch assignments, cross-training, timely feedback, and structured reflection on what happened and what should change. Learning experiences should grow in complexity gradually, so people can build confidence without being exposed to unnecessary risk.

Analysis

This approach treats learning as a capability of the workplace, not merely a product delivered by a training department. It aligns with experiential learning, where a person tests an idea, observes consequences, and revises understanding. Reflection is crucial because experience alone can reinforce a mistaken explanation. Stretch assignments also require safeguards: a novice should not be left alone with high-stakes responsibility simply because pressure is thought to build agility. Good development pairs challenge with coaching, psychological safety, and chances to apply lessons before the next leap.

Map the ecosystem beyond your company walls

The useful network is wider than the org chart. A business ecosystem includes interdependent companies, suppliers, customers, educators, regulators, community groups, and other participants whose fortunes affect one another. Mapping these relationships can reveal missing connections, potential partners, and resources the organization does not possess internally. Sun Microsystems and AT&T helped promote interoperable computer systems through collaboration around Unix, changing the competitive landscape beyond any single firm. The broader lesson is that shared infrastructure and knowledge can create opportunities that isolated organizations cannot reach as easily.

Participation should create mutual value. The book points to open innovation, coworking spaces, and B Corp networks as ways organizations exchange ideas and resources. It also argues that ecosystem health depends on contributions to communities and the environment, not only short-term gains for one company. Mapping matters only if it leads to conversations, partnerships, and useful action.

Analysis

The ecosystem perspective corrects a narrow view of competition: rivals can compete in one arena while sharing standards, suppliers, or knowledge in another. This resembles ecological interdependence, where system health depends on relationships rather than the dominance of a single organism. Yet collaboration is not automatically virtuous. It can expose sensitive information, concentrate power, or distribute benefits unevenly. Partnerships need clear expectations about ownership, reciprocity, and risk. The book’s emphasis on community benefit is a useful counterweight to the assumption that every network should be judged only by what it returns to the focal firm.

Hire and reward the behaviors that keep adaptation alive

Agility must be built into people practices. A résumé cannot show how someone responds when a plan breaks. The book recommends observing candidates, discussing past situations that demanded adaptation, and giving applicants collaborative exercises that resemble the work. Look for curiosity, communication, cooperation, and the ability to learn, not just polished performance in familiar conditions. UPS’s use of social media recruiting grew from 19 hires in 2009 to 24,475 in 2013, illustrating how an organization can use its wider network to find talent.

Reinforce agility in the moment. Replace distant, once-a-year judgments with regular conversations and specific recognition of useful behavior, learning, and team contributions. Ask people what forms of recognition feel meaningful. Retention depends on keeping the promise: relevant work, room to contribute, coaching, sustainable workloads, and trust that motivated people can do their jobs.

Analysis

This section rightly treats recruitment, feedback, recognition, and retention as one system. Hiring for adaptability while rewarding only predictable output sends contradictory signals; people learn quickly which behavior actually advances them. The playful assessment exercises can reveal collaboration patterns that interviews miss, but they must be job-related, accessible, and designed not to confuse extroversion with agility. Recognition also needs care. Public praise motivates some employees and embarrasses others, while individual awards can obscure collective work. Asking about preferences and recognizing both process and results makes the system more credible.

Analysis

The book’s central contribution is to locate agility in relationships and routines, rather than in heroic individual instincts or a fashionable management method. Its theater lens is unusually productive: improvisation becomes a practical model for coordination under incomplete information, while the accounts of UPS, Umpqua Bank, Ericsson, and Mightybytes show how that model can be translated into ordinary organizational choices. The argument moves across levels, from bodily stress responses to teams, firms, and business ecosystems, and insists that capacity at one level cannot compensate indefinitely for breakdowns at another.

The strongest synthesis is that readiness requires both connection and permission. A network without decision rights cannot move quickly; autonomy without shared purpose can fragment effort. The five dynamics and the Relational Web therefore work as complements: purpose guides attention, interaction mobilizes resources, and reflection updates behavior. This is a more human account of organizational design than treating employees as interchangeable components.

Some claims require careful reading. The reported performance advantages of agile firms are associations, not proof that agility alone caused higher profits. Many cases are success stories selected to illustrate the argument, so they cannot establish how often these practices fail. The neuroscience language also simplifies a complex brain into a neat contrast between threat and higher reasoning. These simplifications make the model memorable, but leaders should not treat them as exhaustive science. Nor should resilience become a polite word for tolerating chronic understaffing or arbitrary change.

The most durable practical lesson is to build a capacity for revision: connect people before a crisis, give them bounded authority, test work early, and learn openly from outcomes. The book’s 2015 statistics and company snapshots are historical evidence, not current benchmarks. Its deeper framework remains useful precisely because it is less about copying a company’s software or structure than about designing relationships and feedback so people can respond well when the situation changes.

Summary in 30 Seconds
Organizational agility grows through practice, not crisis alone. Trusted relationships help people share information and mobilize resources; clear purpose and decision boundaries let them act without waiting for permission. Short work cycles, often two to four weeks, expose customer feedback early. Since an estimated 70 to 90 percent of workplace learning is informal, stretch assignments, timely feedback, and reflection make daily work a source of growth. Connections beyond the company can reveal skills and partners it lacks.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.34 out of 5
Average of 143 ratings from Goodreads and Amazon.

Agility Shift receives mixed reviews, with an average rating of 3.29/5. Readers appreciate its introduction to agile concepts and emphasis on mindset change. Positive reviews highlight the book's insights on relational webs, continuous learning, and adaptability. Critics find it too broad, jargon-heavy, and lacking in practical examples. Some readers value its neuroscientific approach and ideas for team dynamics. Overall, it's recommended for those new to agility but may not offer much new information for experienced practitioners.

Your rating:
3.98
81 ratings
Want to read the full book?

Glossary

The Agility Shift

Readiness for changing contexts

The intentional, continuous development of the competence, capacity, and confidence needed to learn, adapt, and innovate in changing conditions. The term refers not only to individual flexibility but also to changes in team practices, organizational culture, and relationships that make effective responses more likely.

Relational Web

Network of usable support

A personal or system-wide network for mutual support, coordination, and sharing resources and ideas. It includes current and past relationships, skills, knowledge, experiences, and tangible or intangible resources. Its value changes with context: a connection that seems peripheral in ordinary work may become crucial during a disruption or opportunity.

Three Cs of the Agility Shift

Competence, capacity, confidence

The three interdependent ingredients of effective agility. Competence is the relevant skill, knowledge, and ability to respond. Capacity is the degree of uncertainty or volatility in which someone can still function effectively. Confidence is trust in one’s own and others’ ability to use their competence and capacity under changing conditions.

Five Dynamics of the Agility Shift

Five practices for agility

The book’s framework for sustaining agility through relevance, responsiveness, resilience, resourcefulness, and reflection. Together, these dynamics help people connect action to purpose, respond effectively, recover or adapt after disruption, improvise with available resources, and learn from experience. They are presented as interrelated practices, not as a one-time checklist.

playspace

Space to experiment together

A context in which people can explore new ideas, try different roles, and improvise with colleagues. It does not mean frivolous games or abandoning business goals. It means creating enough support and permission for participants to experiment, learn, and respond to emerging conditions without being confined by routine or job descriptions.

learning agility

Transfer learning across situations

The ability to learn in the midst of action and apply lessons from prior experience in unfamiliar contexts. It goes beyond being quick on one’s feet: it involves noticing what a new situation requires, translating relevant experience, and adapting rather than assuming the current challenge is identical to a past one.

SOAR

Strength-based planning process

A strategy and reflection approach organized around strengths, opportunities, aspirations, and results. It emphasizes existing capabilities, shared purpose, and desired outcomes rather than centering analysis on weaknesses and threats. In the book, SOAR sessions help organizations align values with work and surface ideas for new products, partnerships, or community projects.

VUCA

Volatility, uncertainty, complexity, ambiguity

An acronym first used by the U.S. Army War College to describe volatile, uncertain, complex, and ambiguous conditions. The book uses it as shorthand for environments in which events are difficult to predict, information may be incomplete, and plans can become obsolete. Such conditions call for readiness and interaction, not only more analysis.

bricolage

Creating with available resources

The capacity to make or solve something using resources already at hand. In the book’s account of agility, bricolage combines awareness of what is available with confidence to improvise. Constraints can help focus creative effort, while waiting for ideal tools or conditions may delay learning and useful action.

About the Author

Pamela Meyer is an author and expert in organizational agility and innovation. She wrote "Agility Shift," which explores the importance of adaptability in modern business environments. Meyer's work focuses on helping individuals and organizations develop the skills and mindset necessary to thrive in rapidly changing contexts. She emphasizes concepts like relational webs, continuous learning, and responsiveness to uncertainty. Meyer's approach combines insights from various fields, including improvisation and action learning, to promote agile thinking and practices. Her writing style is accessible, making complex ideas understandable for a wide audience.

Download PDF

To save this Agility Shift summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.32 MB     Pages: 16

Download EPUB

To read this Agility Shift summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.38 MB     Pages: 20
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...