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
Systems Thinking in the Public Sector

Systems Thinking in the Public Sector

The Failure of the Reform Regime... and a Manifesto for a Better Way
Why public services miss citizens, and how to redesign work around what they actually need.
by John Seddon 2008 224 pages
3.94
102 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat public services as systems, not factories built to satisfy central targets.

A reform ideology took hold. Seddon traces the modern reform regime to market theories that treat people as self-interested and public servants as needing incentives, competition, targets, and oversight. Governments applied these ideas through quasi-markets, specifications, and inspection, often without first testing whether the designs improved service. The result was a large bureaucracy prescribing how services should work, while the people delivering them were judged on compliance.

Design shapes behaviour. The central criticism is not that officials are foolish or uncaring. Rules make compliance the safest response, even when it frustrates the service's purpose. An organisation can earn a high official rating while citizens struggle to get help. Seddon argues for understanding the service as a whole, starting with what people need and examining how the work actually performs before prescribing solutions.

Analysis

The institutional insight is powerful: people adapt to the incentives and constraints around them, so blaming individual workers for predictable system outcomes misses the mechanism. This connects to principal-agent theory, which studies how rules and rewards can distort behaviour when decision-makers cannot directly observe the work. Yet oversight is not automatically misguided. Public services must protect rights, public money, and consistent access. The useful distinction is between setting legitimate boundaries and dictating operational methods without evidence. A system can grant frontline teams room to improve while still making outcomes, safeguards, and the use of public funds transparent.

Offer meaningful housing choices, not extra steps that leave applicants waiting.

Choice needs a working service. In Delft, housing providers advertised vacant homes, explained allocation rules, and published who received each property. Applicants could focus on homes they had a realistic chance of getting. The British version added a requirement to register on a database before bidding, preserving old administrative work while adding advertising and response handling.

A bid is not a home. In one pilot area, 3,500 to 4,000 applications were made for only 100 properties in a two-week period. More registrations and praise for transparency did not show that more people were housed or that the process worked better for them. Seddon's alternative is to speak with applicants, explain whether and when housing is likely, and let them decide whether to wait. That also helps identify people who could be disadvantaged by online or paperwork-heavy systems.

Analysis

The housing example separates procedural choice from substantive agency. A person may have many formal options yet little ability to secure a suitable home; information about scarcity can be more useful than a new interface for bidding. This resembles the distinction in public policy between having options and having the practical capability to use them. The case also warns against treating user satisfaction with a feature as evidence of better outcomes. Still, direct meetings require staff time and careful, fair allocation rules. The design challenge is not to abolish choice, but to make choices intelligible, accessible, and connected to realistic possibilities.

Treat repeat calls and repeat visits as evidence that the service failed.

Separate wanted from unwanted demand. Seddon calls the service's intended requests value demand: for housing benefits, a claim or a report of changed circumstances. Failure demand is contact caused by the service not doing something right, such as a claimant asking where a payment is or being asked for documents already supplied. It consumes capacity without meeting a new need.

The numbers can tell different stories. In one council, the reported average for processing claims was 28 days, while the claimant's actual wait averaged 98 days. About 40 percent of claims were closed as having no entitlement when information was missing, forcing people to start again. The official figure improved, but the underlying problem remained. Tracking the whole journey from first contact to payment makes these failures visible and points managers toward their causes.

Analysis

Failure demand is useful because it turns complaints from isolated annoyances into operational evidence. In service design, repeated contact often signals that the first interaction did not resolve the user's problem, much as repeat visits to a clinic can reveal breakdowns in continuity or follow-up. The distinction also helps teams avoid celebrating higher throughput when they are processing avoidable work. However, not every repeat contact is proof of poor design: some cases genuinely change, and complex needs may require multiple conversations. The measure is most informative when teams classify why people return, then investigate patterns rather than treating every repeat as identical.

Measure outcomes citizens need, or targets will become the service's real purpose.

Numbers redirect attention. Seddon describes a relationship between purpose, measures, and method: what an organisation measures influences what it tries to accomplish and how it arranges the work. If planners are judged on decisions made within eight weeks, they may refuse, withdraw, or attach conditions to applications to stop the clock. The book reports that as many as 40 percent of applications could be churned this way, creating further work while the target appears satisfied.

Targets hide variation. A target is an imposed number, not a reliable account of what a system can do. When managers react to ordinary fluctuations as if each were a special failure, they can make performance less stable, a phenomenon Seddon calls tampering. Measures should instead reveal actual capability over time and be tied to the service's purpose, such as when a homeowner can begin building.

Analysis

The argument draws on statistical process control: performance varies, and a single data point rarely explains why. A time series can distinguish a persistent pattern from an unusual event, helping managers avoid frantic interventions that add complexity. The planning example shows how a metric can alter behaviour even when nobody intends to game it. A caution is essential, though: public organisations sometimes need deadlines and legal standards. The danger is using a convenient proxy as if it were the full outcome. Good measurement makes trade-offs visible, including timeliness, fairness, decision quality, and the consequences of delay.

Study the work before changing it, starting with demand and ending with causes.

Begin with direct observation. Seddon's Vanguard model for "check" is a way to learn how a demand is handled and why performance takes the shape it does. It begins by defining purpose from the user's point of view, then identifying the types and frequency of demand. Next, managers measure actual end-to-end performance, follow real cases through the work, and identify the system conditions creating waste. The final step is to examine the management assumptions that sustain those conditions.

Follow cases, not diagrams. In housing benefits, tracing actual claims exposed handovers, duplicate documents, and repeated requests for information that a process chart or policy manual could conceal. After redesign, some councils processed benefits in an average of five to six days, compared with a 52-day average in one documented system. The point is not to copy that number, but to discover what a particular service can achieve by removing the causes of delay.

Analysis

This method resembles ethnographic fieldwork: researchers learn about a system by observing people in context, rather than relying only on what procedures say should happen. It also resembles scientific inquiry because it starts with a question, gathers evidence, and revises assumptions. That combination makes the approach practical, not merely philosophical. Still, observation alone can be partial. Staff may change behaviour when watched, and a few traced cases may not represent the whole service. Strong diagnosis combines observation with repeated measurements, varied cases, and the perspectives of users and workers. The discipline lies in testing explanations, not just collecting vivid anecdotes.

Put the expertise to solve common problems where citizens first ask for help.

Design around real requests. Once managers know what people usually need, they can train staff to resolve those common requests at the first point of contact. Less predictable cases can draw on specialist help without transferring ownership away from the person serving the citizen. This contrasts with a front-office and back-office split, where forms are passed along, information is fragmented, and the person who first heard the problem may never see its resolution.

Give people a worthwhile job. Seddon argues that workers should control the work they are responsible for, while managers improve the conditions around it. One call-centre example describes training cut from eight weeks to two, with new staff able to handle more calls when they started. The point is not simply faster training. Work becomes more motivating when staff have the knowledge and discretion to solve problems instead of following scripts and sending cases elsewhere.

Analysis

The design links service quality with job quality. In organisational psychology, autonomy and competence are often treated as conditions that support motivation; here, they are also practical resources for handling varied human needs. Keeping a case with one accountable worker can reduce handoffs and give that worker feedback about whether the response worked. The limit is that expertise cannot be placed everywhere, especially in small or highly specialised services. A sensible design therefore distinguishes predictable requests from unusual ones and makes specialist support easy to pull in. Frontline discretion needs training, clear legal boundaries, and reliable access to expert advice.

In policing and care, compliance can crowd out the help people actually need.

Policing became paperwork-heavy. Seddon describes officers divided among specialist units, reporting systems, and inspection processes. The book cites officers estimating that paperwork could consume up to 80 percent of their time, and estimates that 60 to 80 percent of policing activity was mandated waste. The system prioritised recording and closing cases, even when those activities did little to prevent crime or support an investigation.

Care became a sequence of hurdles. In one council, the wait from asking for adult social care to receiving it averaged 68 days and could reach 230. People could face repeated assessments by separate departments, while each department met its own targets. These examples show how activity can appear orderly from inside an organisation while the person needing help experiences delay and disconnection. In both services, the central problem is not simply low effort. It is a design that directs effort away from the human purpose of the service.

Analysis

These cases make visible a common feature of high-stakes systems: documentation can protect accountability, but excessive process can displace the work it is meant to support. In policing, records can enable coordination and scrutiny; in care, assessments can help ensure fair access. The design question is whether each required step changes a decision, reduces risk, or improves support. If not, it may be procedural activity without public benefit. The book's estimates are striking, but they should be treated as findings from the author's observed cases, not universal statistics. Local measurement is essential before deciding which controls to remove.

Make public value practical by studying services, community problems, and local needs.

Public value widens the lens. Mark Moore's idea asks public managers to consider benefits to the wider community, not just the person in a single transaction. The book's example is a librarian who notices children using the library after school, secures funding, and changes opening hours. The service adapts to a need that was not part of its original routine.

Different work needs different methods. Seddon distinguishes providing a service, solving a community problem, and shaping a place's future. Each calls for understanding the issue before choosing an intervention. Studying requests across services may reveal connected needs, while local patterns of crime, dumping, or housing demand can inform practical responses. Public value offers a useful purpose, but it does not itself specify how to improve. Managers still need evidence about demand, outcomes, and whether a chosen method works.

Analysis

Public value is a useful corrective to the idea that a public service can be judged only by individual consumer preference. Public institutions also sustain shared goods, such as education and safe communities, whose benefits are collective and long-term. The librarian example shows how frontline observation can reveal a public benefit that rigid job definitions might miss. The hard question is whose values count when priorities conflict. A library's extended hours, for instance, require resources that could serve another purpose. Deliberation and elected accountability remain important, but they work best when grounded in clear evidence about needs and consequences.

Judge public managers by what they learn from work, not inspection preparation.

Reform the machinery of reform. Seddon argues that the specifications and inspection regime generates several kinds of waste: the cost of writing requirements, inspecting them, preparing for inspections, complying with bad designs, and demoralising staff. Reducing the number of targets is not enough if the underlying demand for compliance remains. The book notes that the government cut local authority targets from about 1,200 to 198 in 2007, while maintaining that the right alternative is not fewer arbitrary targets but measures that help people understand and improve their work.

Inspect learning, not performance theatre. Seddon's proposed inspection asks managers what measures they use to understand and improve their service, then examines those measures where the work happens. The centre should share knowledge about methods, while managers retain responsibility for choosing what fits their local circumstances. This shifts the test from whether an organisation performed for the inspector to whether it can show that it is learning from actual service outcomes.

Analysis

The proposal treats accountability as an inquiry into organisational learning rather than a ritual of evidence production. That is attractive because it can preserve scrutiny while reducing pressure to stage-manage performance. It also raises a governance challenge: managers may select measures that flatter their service or overlook harms that are difficult to quantify. Independent inspection remains valuable when it tests the validity of local measures, checks legal and ethical duties, and listens to service users. The strongest version of Seddon's alternative is therefore not inspection-free government, but inspection that examines real work, tests the quality of learning, and avoids prescribing a single operating model.

Analysis

Seddon's most consequential move is to relocate the cause of poor public service from individual character to system design. A missed payment, a repeated call, or an officer buried in forms is not merely an isolated failure. Each can be evidence that the organisation has arranged work around internal convenience, reporting, or risk avoidance rather than the citizen's need. This perspective is unusually practical because it joins a theory of management to observable evidence: follow the request, measure the whole journey, and examine the conditions producing delay and rework.

The book is strongest when it demonstrates how a seemingly rational metric changes conduct. A target for processing time encourages closure rather than resolution; a call-handling measure rewards speed even when the caller's problem remains. These are not mysterious side effects. They are predictable responses to a narrow definition of success. The analysis also explains why adding technology or centralising administration can amplify defects instead of fixing them: the organisation may automate the wrong flow.

The argument is less complete when it treats targets, competition, inspection, and standardisation as uniformly damaging. Public services face real duties to protect vulnerable people, allocate scarce resources fairly, prevent fraud, and explain decisions. Local discretion can improve responsiveness, but it can also produce inconsistency, weak oversight, or unequal treatment. The book's own logic suggests a way to address this tension: measure outcomes that matter, keep safeguards explicit, and inspect whether local methods work rather than imposing one process everywhere.

The enduring lesson is not that management should disappear. It is that managers should stop pretending they can control a service through distant proxies. Their task is to create conditions in which people doing the work can see demand, resolve it, learn from failure, and improve the system. That shift requires evidence and judgement, not another reform slogan.

Summary in 30 Seconds
Public services work better when organized around citizens' needs rather than internal targets and compliance. Repeated calls, visits, and requests for already supplied information signal service failure, not new demand. Following cases from first contact to resolution exposes delay and rework: one benefits system averaged 52 days, while redesigned services reached five to six. Give frontline staff the expertise to resolve common problems, and judge managers by how well they learn from outcomes.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.94 out of 5
Average of 102 ratings from Goodreads and Amazon.

Systems Thinking in the Public Sector receives mixed reviews, with an average rating of 3.93/5. Positive reviews praise its insights into public sector failures, critique of target-driven management, and advocacy for systems thinking. Critics argue it lacks evidence and clear solutions. Some readers find it eye-opening, while others see it as similar to other improvement methodologies. The book is commended for its readability and organization, but criticized for being overly critical without sufficient backing. Overall, it's seen as valuable for those in or interested in public sector management.

Your rating:
4.44
80 ratings
Want to read the full book?

Glossary

Failure demand

Avoidable repeat work

Demand created because a service failed to do something, or failed to do it correctly, from the user's perspective. Examples include progress-chasing calls, repeat visits, and requests to resubmit information already provided. Seddon treats failure demand as a signal of poor service design and a source of avoidable cost.

Value demand

The service's intended work

The requests a service exists to handle. For housing benefits, these include making a claim and reporting a change of circumstances. Identifying value demand helps define the service's purpose and the work needed to meet it, while distinguishing that work from demand caused by previous failures.

Capability chart

Performance over time

A time-series measure showing how a system performs and how much its results vary. Seddon uses capability charts to compare actual performance with the service's purpose, rather than relying on an arbitrary target or a single data point. The chart helps managers understand what the system can predictably achieve and investigate changes in performance.

Purpose, measures, method

A linked management relationship

The relationship among what a service exists to achieve, how its performance is measured, and how its work is designed. Seddon argues that imposed targets can become the service's practical purpose and constrain its methods. Measures derived from the user's purpose and used by the people doing the work can support learning and improvement.

Vanguard model for check

A system diagnosis method

A structured way to learn how a demand-based service works before changing it. It examines purpose, the types and frequency of demand, performance from the user's perspective, the flow of actual cases, the conditions producing waste, and the assumptions held by managers. Its goal is knowledge about current performance, not advance agreement on a predetermined solution.

Nominal value

What matters to the user

Seddon's service-oriented use of the idea of a nominal value: the outcome or experience that matters to the individual receiving a service. A service should be designed so the person can obtain what they need with minimal unnecessary effort. The concept shifts attention from producer-defined categories to the user's actual purpose.

System conditions

Features shaping work

The arrangements that influence how work flows and what results it produces. These can include measures, roles, procedures, technology, organisational structure, and contracts. Seddon argues that waste and poor service are often caused by these conditions, so improving a visible process without changing its underlying conditions may produce only limited or temporary gains.

Deliverology

Target-led delivery management

Michael Barber's approach to driving government priorities through targets, delivery plans, progress reviews, reporting, and central pressure on responsible organisations. Seddon argues that it concentrated attention on compliance and measurable activity without a reliable method for improving the work itself. The book presents policing as an example of bureaucracy expanding around this approach.

Public Value

Benefit to the wider public

Mark Moore's framework for thinking about the value public services create for society, including benefits beyond an individual's immediate transaction. It asks public managers to consider community outcomes and the public's role as a wider beneficiary. Seddon sees this as a promising philosophy but argues that managers still need practical methods for understanding demand and improving services.

About the Author

John Seddon is an author and management thinker known for his work on systems thinking in organizations. He has written extensively on improving efficiency and effectiveness in both public and private sectors. Seddon is critical of traditional command-and-control management styles and advocates for a more holistic, systems-based approach. His ideas often challenge conventional wisdom in management practices, particularly regarding target-setting and performance measurement. Seddon's work draws comparisons to lean management principles and the Toyota Production System. He has authored multiple books on the subject and is recognized for his efforts to reform management thinking in the public sector.

Download PDF

To save this Systems Thinking in the Public Sector summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.33 MB     Pages: 17

Download EPUB

To read this Systems Thinking in the Public Sector 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.41 MB     Pages: 20
Want to read the full book?
Follow
Listen1 mins
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...