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
Hacking for Agile Change

Hacking for Agile Change

with an agile mindset, behaviours and practices
Help teams adapt to change without turning agility into another set of rules.
by Lena Ross 2017 228 pages
3.90
21 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Build agility in thinking, behaviour, and delivery, not by adopting Scrum alone

Agility is more than method. Ross distinguishes capital-A Agile, associated with the Agile Manifesto and software practices, from lowercase agile, meaning adaptive ways of thinking and acting. A team can use Scrum or another Agile framework without the wider organisation becoming responsive. Ross’s model treats agility as a capability built from three connected layers: mindset, behaviours, and practices. Organisational agility depends on people developing all three, not on a project label or a new set of templates.

Start with the people. The book’s practical premise is that change work should be scaled to the situation. A small, visual draft may serve a conversation better than a polished slide deck, while regulated work may need more governance and time. The goal is to adapt the method without losing the human purpose of the change.

Analysis

The distinction guards against a familiar category error: adopting a process and assuming the culture has changed with it. A method can create useful routines, but it cannot by itself produce trust, curiosity, or shared responsibility. This is a capability view, not a rejection of formal frameworks. Its useful test is whether the team can respond to new information while still meeting real constraints. Flexibility should not become a euphemism for unclear accountability, especially where safety, compliance, or contractual obligations set firm boundaries.

Treat incomplete plans as invitations to learn, not reasons to freeze

Practise adaptive thinking. Ross describes an agile mindset as open to new ideas, curious, resilient, and willing to work without a complete picture. A growth mindset treats ability as developable through practice and feedback, rather than fixed. A beginner’s mindset adds the discipline to question familiar assumptions and suspend judgement. Together, they make uncertainty something to investigate instead of something to disguise with premature certainty.

Change one variable. Ross uses the film Groundhog Day to illustrate iterative learning: its protagonist changes his choices bit by bit as he learns from repeated experience. In project work, the equivalent is sharing a rough draft, testing an assumption, and adjusting after feedback. The point is not to celebrate every failure. It is to make experiments small enough to teach the team before a costly decision hardens.

Analysis

This approach resembles scientific inquiry: state what is uncertain, make a limited test, observe what happens, and revise the explanation. It also counters perfectionism, which can make work look finished while preventing useful feedback. Yet experimentation is not automatically wise. A team needs a clear purpose, boundaries on risk, and a way to distinguish informative failure from avoidable carelessness. The mindset becomes credible when leaders accept feedback about their own decisions, rather than asking only others to be adaptable.

Let affected people define the problem before teams design the fix

Begin with lived experience. Design Thinking is a human-centred, feedback-driven approach for understanding needs before settling on a solution. Ross presents five iterative activities: empathise with users, define the problem, generate ideas, prototype possibilities, and test them. In change work, the users may be employees whose daily routines will be altered, not only external customers.

Make experience visible. Personas summarize recurring user characteristics, while journey maps record what people do, think, and feel across stages of an experience. A team might map current work, identify pain points, and then sketch a proposed future journey for users to challenge. The maps are working documents, not declarations of what people must want. A rough storyboard, role-play, or wall of notes can reveal problems before a full solution is built.

Analysis

The strength of this method is that it makes employee experience an input to design rather than a communications problem to solve after decisions are made. It also gives emotion a legitimate place in operational discussion. The main risk is treating a persona as a real person: a composite profile can flatten differences or become an excuse to speak for users. Direct observation and conversation should remain the evidence base, with maps treated as hypotheses that people can correct.

Reduce threats to status, certainty, autonomy, relatedness, and fairness before demanding adoption

Use SCARF to diagnose reactions. SCARF is Ross’s cited framework for considering five social needs that can shape a person’s response to change: status, certainty, autonomy, relatedness, and fairness. A threatened sense of competence, an unclear future, reduced choice, weakened belonging, or perceived unfairness can make a change feel costly. The same change may therefore feel promising to one employee and threatening to another.

Ask before assuming. A team discussion can identify which concerns are most pressing. If details are not yet known, leaders can still provide a date for the next update. They can explain how decisions will be made, invite employees to shape workable details, and acknowledge the loss of colleagues after a restructure. These steps do not erase uncertainty, but they can make it less isolating and more manageable.

Analysis

The framework is useful because it turns a vague claim of resistance into questions about the specific conditions people experience. It also discourages managers from interpreting disagreement as a character flaw. The neuroscience language behind threat and reward can sound more precise than the evidence warrants, so the model is best used as a practical lens, not a diagnostic instrument. Importantly, a reassuring message cannot compensate for a genuinely unfair decision or for a loss of autonomy that leaders refuse to discuss.

Replace one-way announcements with visible work people can shape

Make communication participatory. An Enterprise Social Network, or ESN, is an internal online space for sharing information and collaborating. Ross describes using these channels for project updates, questions, polls, photographs, and open discussion. Working Out Loud means making work visible while it is underway so colleagues can offer ideas, identify related efforts, or avoid duplicating work. It is an invitation to contribute, not a requirement to surrender decision ownership.

Show the work. Visual boards and simple sketches can make progress and uncertainty easier to discuss than long text-heavy presentations. A team might post a draft plan, ask for feedback, and use a project hashtag to keep related conversations findable. Ross’s example of opening a developing workshop to colleagues brought in interest from other business areas and helped avoid duplicated effort.

Analysis

Visible work changes communication from broadcasting conclusions to exposing decisions while they are still shapeable. That can surface expertise across silos and make participation practical rather than ceremonial. But openness needs boundaries: sensitive employee information, confidential decisions, and unclear ownership can make public collaboration harmful or chaotic. Leaders should say what feedback can change, who decides, and when input closes. Otherwise, an invitation to participate risks becoming theatre, which can reduce trust rather than build it.

Make learning peer-led, short, and easy to share across teams

Use the knowledge already present. Social learning is learning through interaction with peers, rather than relying only on formal courses. Ross recalls France’s école mutuelle, or mutual schools, where older students taught younger ones during a teacher shortage. In her workplace, NED talks adapted the short-talk format for employees to share expertise at lunchtime. Sessions lasted no more than 20 minutes and were recorded for colleagues who could not attend.

Turn learners into teachers. The talks connected people across divisions, gave speakers practice explaining their knowledge, and created recordings that could be revisited. The practical lesson is to ask a colleague returning from a course or conference to share what matters, or invite employees to teach a skill they use daily. A peer-led session can spread useful knowledge without requiring every learner to attend the same formal program.

Analysis

Peer teaching makes expertise visible and can give learning a route through existing relationships, not just through budgets and training calendars. Preparing to teach also encourages the speaker to organize what they know. The approach works best when the organization protects time, recognizes contributors, and checks whether the audience can apply the material. Informal learning is not a substitute for required professional instruction or consistent standards. It is a low-friction complement, especially where useful knowledge is dispersed among employees.

Use small rituals to expose work, solve blockers, and improve each cycle

Make progress observable. A Kanban board is a visual display of work moving through stages such as to do, doing, and done. A short stand-up meeting can help a team report recent progress, near-term work, and blockers. Lean Coffee is a structured meeting where participants propose and vote on the topics, so discussion follows their immediate concerns rather than a preset agenda.

Learn from each cycle. A retrospective reviews what worked, what could improve, and what the team should try next. A future-spective reverses the view: the team imagines a successful future outcome and considers what helped or obstructed it. Ross also recommends rituals that mark beginnings, small wins, and endings. Together, these practices make work, uncertainty, and learning easier to see, while giving teams repeated moments to coordinate and adjust.

Analysis

These practices make adaptation routine instead of leaving it to occasional strategy sessions. Boards reduce the effort needed to see bottlenecks, and recurring reviews help convert experience into changed practice. Their value depends on psychological safety and follow-through: a board that exposes delay without enabling help can become a surveillance device, while a retrospective without owners or actions becomes a ritual of complaint. The format should remain proportionate to the work. Not every team needs a daily meeting or elaborate ceremony.

Give the change a story people can retell accurately

Explain the change as a journey. A story links the previous situation, a disruption, the response, and the resulting difference. Ross recommends building this account with the project team so members can clarify the purpose in plain language, rather than receiving a finished script. Her example follows several separate change teams through an organizational realignment, the creation of a shared practice, and the introduction of common tools and resources.

Make the logic memorable. A narrative helps people connect why the change is happening with what is changing and how the outcome is expected to help. It can be told in a meeting, shown as a storyboard, or adapted into a short video. The story should not promise a frictionless transformation. Naming the uncertainty and the people affected makes it more credible and easier for colleagues to explain consistently.

Analysis

A shared narrative can coordinate action because it gives employees a common account of purpose, sequence, and expected benefit. It is especially valuable when a complex program has accumulated documents but lost its simple explanation. Still, a compelling story can oversimplify trade-offs or turn an uncertain forecast into an inevitable happy ending. Its integrity depends on separating what is known from what is hoped for, and on revising the account when evidence or circumstances change.

Find trusted influencers beyond the org chart and involve them early

Map social influence. Formal titles do not reveal every person whose opinion travels through an organization. Ross draws on the story of Paul Revere and William Dawes, two messengers who spread the same warning during the American Revolution, but whose reach differed. The lesson is to look for trusted connectors and respected colleagues, not only senior decision-makers.

Discuss relationships together. A stakeholder matrix can list roles, interests, and engagement needs, but Ross argues that it should emerge from real conversations among project leaders. Teams can identify who gains or loses, who may influence others, who owns each relationship, and what the next engagement step should be. A grid that considers influence and perceived threat can help decide where to inform, consult, or collaborate, without confusing a spreadsheet with engagement itself.

Analysis

Informal influence explains why messages sometimes gain traction through peers even when official communication is weak. Mapping those networks can also reveal trusted critics whose questions expose genuine risks. The ethical boundary matters: social influence should not be exploited to manufacture consent or bypass affected people. Influencers are most useful when they help make discussion more representative, carry accurate information, and bring concerns back to decision-makers rather than simply endorsing a predetermined plan.

Embed change by modeling, rewarding, and measuring the behaviours it needs

Build conditions for repetition. Ross identifies four organizational levers: leaders model desired behaviours, teams recruit for the attitudes and skills they need, performance systems reward those behaviours, and public recognition reinforces them. A leader who calls for collaboration while protecting personal privilege sends a stronger signal through actions than through posters. Ross also warns that rewarding innovation while punishing every failed experiment undermines learning.

Measure adoption with users. A change plan should define what success looks like in practice, not only whether delivery tasks were completed. Journey mapping can ask affected employees what they expect to be doing, thinking, and feeling in the new state. The plan should identify who will support adoption after the specialist change practitioner leaves. Useful measures and clear ownership help new behaviours persist beyond launch day.

Analysis

This is the book’s strongest bridge between culture and management systems: people notice what leaders do, what organizations reward, and what gets measured. The logic is more durable than relying on values statements alone. Yet metrics can distort behavior when they reward visible activity rather than genuine adoption. Measures should combine operational outcomes with employee experience and should be reviewed for unintended effects. Recognition also needs to be fair and specific, or it can damage the trust it is meant to strengthen.

Analysis

Ross’s central argument is that agile change is a human capability, not a software method imported into every department. The book moves from mindset, to behaviour, to practice, then asks how those layers become organizational habits. That progression matters: iterative planning is unlikely to work when people fear admitting uncertainty, and collaboration is hollow if employees have no meaningful influence over decisions. The most useful thread is the insistence that change receivers are not merely an audience. They hold evidence about work as it is actually done, and their participation can expose flaws before implementation makes them expensive.

The book is particularly practical where it connects broad principles to low-cost routines: map a user journey, make work visible, invite peer teaching, review a small cycle, and identify informal influencers. These are not grand transformation slogans. They are ways to generate information and relationships that conventional top-down plans often miss. The recurring emphasis on fit-for-purpose delivery also prevents agility from becoming a demand for speed at any cost. Its limits are equally instructive. The book sometimes presents neuroscience as a firm explanation for complex organizational feelings. Models such as SCARF can prompt better questions, but they cannot reliably predict an individual’s response or replace evidence gathered from that person. Some claims about brain states and learning are simplified, so the practical methods are more dependable than every scientific rationale offered for them. The book also gives less attention to power conflicts that cannot be resolved through better facilitation: a change may impose real losses, and participation does not make those losses disappear.

The lasting value is therefore not a universal recipe. It is a disciplined orientation: treat plans as revisable, people as sources of design knowledge, and adoption as a condition to build rather than a box to tick. The methods are strongest when paired with honest limits, clear decision rights, and visible accountability.

Summary in 30 Seconds
Agility depends on adaptable thinking, collaborative behaviours, and practices suited to the work, not simply adopting a project framework. Start by learning from the people affected: map their experience, test ideas in small experiments, and adjust from feedback. Make progress and obstacles visible, use brief peer-led learning, and involve trusted informal influencers. To sustain adoption, leaders must model the desired conduct, reward it consistently, and measure whether it becomes part of daily work.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.90 out of 5
Average of 21 ratings from Goodreads and Amazon.

The book Hacking for Agile Change receives generally positive reviews, with an average rating of 3.90 out of 5. Readers appreciate its clear writing, useful diagrams, and practical tools for Agile change. While some content is familiar to experienced change managers, the book offers new ideas and techniques. It's praised for its structure and presentation, though the frequent use of "hack" can be tiresome. The book is seen as a valuable toolkit for those involved in Agile change, offering both familiar and novel approaches.

Your rating:
4.45
70 ratings
Want to read the full book?

Glossary

Agile Manifesto

Agile software principles

A statement created for software development that presents four values and twelve principles favoring customer value, frequent delivery, collaboration, adaptation, and reflection. Ross distinguishes this capital-A Agile tradition from the broader everyday use of agile to mean adaptable thinking and behaviour.

Design Thinking

Human-centred problem design

An iterative approach that uses observation of users and their needs to define a problem before creating and refining possible solutions. Ross describes five activities: empathise, define, ideate, prototype, and test. In change work, employees affected by a new process or structure can help shape the solution.

SCARF

Five social threat triggers

A framework associated in the book with David Rock for examining social experiences that may feel rewarding or threatening: status, certainty, autonomy, relatedness, and fairness. Change leaders can use these categories to ask what people perceive they may gain or lose. The framework is a prompt for discussion, not a fixed diagnosis.

Working Out Loud

Visible work and learning

A practice of making work visible while it is in progress so others can offer feedback, share related knowledge, or avoid duplicating effort. Ross describes it as a way to build connections and improve work through discussion. Visibility does not require giving up decision ownership, and expectations about participation should be clear.

Lean Coffee

Participant-set meeting agenda

A structured, informal meeting in which participants suggest discussion topics, vote on priorities, and move topics through a simple visual board. The format gives attendees influence over the agenda while retaining enough structure to keep the conversation moving. Ross presents it as a way to surface concerns, questions, and potential advocates.

Future-spective

Imagine success before work

A team planning exercise that asks members to imagine a project or work cycle has succeeded, then identify what helped, what obstructed progress, and what might go wrong. Unlike a retrospective, which reviews an experience that has already occurred, a future-spective uses an imagined outcome to anticipate conditions and prepare responses.

Dunbar’s number

Approximate stable group size

The book uses this term for the estimate that people can maintain stable social relationships with about 150 others. Ross applies the idea to organizational design, suggesting that smaller teams and units may support connection and trust. It is an approximate model, not a universal limit on effective collaboration.

Personal Learning Network

Self-directed learning connections

An informal network of people and resources through which someone learns beyond formal courses and assigned reading. It may include colleagues, professional communities, social platforms, conferences, podcasts, and online courses. The network is reciprocal: members learn from others and share their own knowledge in turn.

VUCA

Volatility, uncertainty, complexity, ambiguity

An acronym for volatility, uncertainty, complexity, and ambiguity, used in the book to describe conditions in which markets, technologies, and organizational demands change rapidly and unpredictably. Ross uses it to explain why leaders and change practitioners need adaptive planning, ongoing learning, and comfort with incomplete information.

About the Author

Lena Ross is the author of "Hacking for Agile Change," a book that provides tools and techniques for implementing Agile methodologies in organizational change. Ross's work focuses on practical applications of Agile principles, offering readers a toolkit of 52 "hacks" to facilitate change management. Her writing style is described as clear and easy to understand, with an emphasis on visual aids and diagrams to illustrate concepts. Ross appears to have experience in change management and Agile methodologies, combining these areas of expertise to create a resource for professionals seeking to apply Agile approaches to organizational transformation.

Download PDF

To save this Hacking for Agile Change 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: 17

Download EPUB

To read this Hacking for Agile Change 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.37 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 25,
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...