Arnstein's Ladder and the Uncomfortable Truth About Project Delivery
In 1969, a woman named Sherry Arnstein wrote a paper about urban planning. It was published in the Journal of the American Institute of Planners, which is not a publication that typically causes software executives to break into a cold sweat. And yet here we are.
The paper introduced a framework called the Ladder of Citizen Participation. Eight rungs. Three categories. One spectacularly inconvenient observation: that most of what governments called "citizen participation" was, in practice, a sophisticated method of doing exactly what they'd already decided to do while making people feel briefly consulted.
Arnstein was talking about urban renewal programmes. Housing policy. The federal government and its relationship with communities who had the misfortune of living in areas someone had decided to improve.
She was also, without quite knowing it, describing every technology project I have ever been involved in.
The Ladder
Before we get to the unsettling part, here is what the ladder actually says.
Arnstein divided participation into three zones, containing eight rungs. The bottom two rungs she called Non-Participation. The middle three she called Tokenism. The top three she called Citizen Power. She was quite clear about which of these she thought was the point of the exercise, and it was not the bottom five.
Rung 1: Manipulation. Citizens are placed on advisory committees to lend legitimacy to decisions already made. Their role is not to participate but to be seen to participate. The distinction matters.
Rung 2: Therapy. Citizens are consulted about their concerns. This sounds helpful. The concerns are not acted upon. The consultees have been, in Arnstein's words, "educated" rather than heard. The implicit message is that they have the wrong feelings about the right decision.
Rung 3: Informing. People are told what is happening. One-way. This is often mistaken for communication, in the same way that a foghorn is sometimes mistaken for a conversation.
Rung 4: Consultation. Opinions are gathered. Workshops are held. Reports are written. Recommendations are considered. A small number of the less threatening ones are incorporated. Progress.
Rung 5: Placation. A representative of the affected community is given a seat on the committee. They have observer status. Their job is to report back that they attended, which is technically true and substantially meaningless.
Rung 6: Partnership. Power is genuinely shared. Decisions are made together. Both parties have to actually agree. There are arguments. This is, it turns out, how things that work tend to get built.
Rung 7: Delegated Power. Significant decision-making authority moves to the people doing the work. Governance happens at the edges rather than the centre. The people in charge of the outcome are, in a novel development, the people responsible for it.
Rung 8: Citizen Control. Full autonomy. The community governs the programme themselves. This is either magnificent or catastrophic, depending almost entirely on the quality of the people now in control.
The Equivalence Nobody Asked For
Here is the observation that ruined several of my more comfortable assumptions.
If you take Arnstein's Ladder, strip out every reference to urban planning, and replace "citizen" with "delivery team" and "powerholder" with "steering committee," you get an almost perfect description of project delivery outcomes, ordered from worst to best.
The correlation is not approximate. It is, in my experience, startling.
Projects at the bottom of the ladder fail. Projects at the top succeed. The relationship between participation level and delivery quality is so consistent that I have started to use Arnstein's rungs as a diagnostic tool before committing to anything larger than a departmental spreadsheet.
Let me show you what this looks like in practice.
The Eight Rungs, Translated
Rung 1: Manipulation
The system has been selected. The vendor has been briefed. The requirements document will be written by the implementation partner to match the product they are selling. The team will be invited to a "discovery workshop" to confirm the findings. The findings will be positive.
Typical outcome: The project delivers something. Nobody who uses it is entirely sure what the something is, or why it works the way it does, or whether it was always meant to be this slow.
Rung 2: Therapy
Change management has been commissioned. A consultant will run sessions to help the team "understand the journey." Resistance is noted, documented, and addressed through further sessions. The project proceeds. The concerns were real. The system was not designed around them.
Typical outcome: The project goes live on schedule. The workarounds begin within a fortnight. The change management consultant is long gone.
Rung 3: Informing
There are town halls. There are email updates with a subject line that begins "Exciting news about." There are FAQs. The team learns what they are getting approximately when they get it. This is considered good communication by everyone involved in producing it, and nobody involved in receiving it.
Typical outcome: The project delivers something close to what was specified. Whether what was specified was what was needed is a question that will be answered gradually and expensively over the following eighteen months.
Rung 4: Consultation
Workshops. Surveys. A forty-page requirements document. Three of the forty pages influenced the actual design. This represents a meaningful improvement on rung three and is celebrated accordingly.
Typical outcome: Slower and more expensive than rung three. Marginally better result. Substantially more resentment, because people who were asked and then ignored feel worse than people who were never asked at all. This is one of the cruel mathematics of participation.
Rung 5: Placation
A representative from the delivery team has a seat on the steering committee. They cannot vote. Their role is to provide what the minutes will describe as "operational perspective." They raise concerns. The concerns are minuted. The project proceeds.
Typical outcome: See rung four, but now someone has a title and a calendar full of meetings they cannot influence. After six months they will either leave the organisation or become a project manager themselves, completing a cycle that has repeated throughout human history.
Rung 6: Partnership
Power is shared. The people who will use the system have a genuine say in how it is designed. The people who will build it have a genuine say in what is feasible. There are arguments. The arguments are productive. Things that sound excellent in a boardroom turn out to be impractical in an operations centre, and this is discovered before rather than after they are built.
Typical outcome: Slower to start. Faster to finish. The thing that is built is the thing that was needed, which is a distinction from the thing that was specified that organisations routinely underestimate until they have spent several years living with the difference.
Rung 7: Delegated Power
The delivery team owns the outcome. They set the approach, manage the scope, and are accountable for the result. Governance provides guardrails and resources, not decisions. The team cares because it is actually theirs.
Typical outcome: Fast. Accountable. High-quality. Middle management is occasionally uncomfortable with this, which is not the team's problem and should not be made into one.
Rung 8: Citizen Control
Full autonomy. The team governs the programme. There is no external authority to appeal to, defer to, or blame.
Typical outcome: Bimodal. With an experienced, aligned team and a clear shared vision, this is the best project delivery you will ever see. Without those things, it is a fascinating case study that you will describe at conferences for years in the past tense.
The Counterintuitive Part
The conventional assumption is that more management oversight produces better outcomes. This assumption is so widespread that organisations build entire governance frameworks around it. They add committees, approval gates, and review boards. They create the conditions for rungs one through five, and then they wonder why delivery is slow and output is mediocre.
The data, and thirty years of watching projects succeed and fail, suggest something considerably more awkward: the organisations with the tightest control over their projects tend to have the worst delivery outcomes, and the organisations that trust their teams with genuine power tend to have the best ones.
This is not a new observation. It is, in fact, a 1969 observation. It has simply been slow to travel from urban planning to enterprise IT, possibly because the journey requires passing through several layers of middle management.
The Diagnostic Question
Before your next project starts, or before you accept that the current one is going the way it is going, ask this question: where on Arnstein's Ladder does the delivery team actually sit?
Not where the project charter says they sit. Not where the governance framework implies they sit. Where they actually sit, on a Tuesday afternoon, when a decision needs to be made about scope or approach or timeline. Who makes that decision, and is the person making it the person who will live with the consequences?
If the honest answer is rung three, four, or five, you have identified your problem. It may not be the only problem. It is very likely to be the largest one.
The uncomfortable truth that Arnstein identified in 1969, and that project managers have been rediscovering at considerable expense ever since, is that participation is not a courtesy extended to the people doing the work. It is the mechanism by which the work gets done well.
Consulting people and then ignoring them does not merely fail to help. It actively makes things worse, because it generates resentment without generating information, and spends time without producing decisions. It is the worst of both worlds, packaged in a format that feels like engagement and functions like delay.
A Note on Rung Eight
Full autonomy is not the goal. This is worth saying clearly, because the ladder implies a simple "higher is better" relationship that is not quite right.
Partnership and Delegated Power (rungs six and seven) are where the best project delivery consistently happens. Rung eight works when you have the right people, the right clarity of purpose, and the right organisational maturity to sustain it. When you do not have those things, rung eight produces something impressive in its own way: a project that is completely owned by everyone and therefore controlled by no one, in which all decisions are democratic, all opinions are equally valid, and nothing ships until the last person has had their last concern addressed.
There is, as Arnstein would have recognised, a version of full citizen control that is itself a form of non-delivery. The goal is not maximum autonomy in the abstract. The goal is the right level of power in the right hands at the right time.
Rungs six and seven, consistently applied, get you there. They are less philosophically satisfying than rung eight and considerably more effective than rungs one through five. In project management, as in most things, the middle of the top half is where you want to be.
One More Thing
Arnstein wrote her paper because she was frustrated. The federal government was running community participation programmes that gave communities the form of involvement without the substance of power. She called this out, named it precisely, and drew a ladder so that people could point to the rung they were actually on rather than the one they were claiming to occupy.
Fifty-seven years later, the same gap between claimed participation and actual power exists in organisations everywhere. The language has updated. Workshops have become sprints. Town halls have become all-hands. The underlying dynamic has not changed especially much.
The ladder is still accurate. The rungs are still diagnostic. And the distance between rung three and rung six is still, in my experience, approximately the distance between a project that will be written up as a cautionary tale and one that will be worth writing up at all.
Sherry Arnstein probably did not know she was writing a project management framework. She was right anyway.