Lesson 1 · Module 5
Designing participatory community projects
Plan and start a project with your community, not for it: share power, listen before you design, map stakeholders and needs, and co-create a living project plan.
Introduction
“Never doubt that a small group of thoughtful, committed citizens can change the world; indeed, it’s the only thing that ever has.” — Margaret Mead
Think of a community initiative you have witnessed or been part of that failed to take root. Not because of lack of resources, or bad intentions, but because something felt wrong from the start. Perhaps the people it was meant to serve were never asked what they needed. Perhaps the priorities were set by people who did not live there. Perhaps the solution was elegant on paper and invisible in practice.
This is one of the most common and costly mistakes in social and community development work. Projects designed for communities rather than with them. The effort is genuine. The gap is in the design.
This topic is about closing that gap. Not through a perfect methodology, but through a shift in orientation — from expert to collaborator, from solution-provider to co-creator, from doing things to people to doing things together.
From hero to collaborator
What is participatory community development?
Many social initiatives fail not because of bad intentions, but because they are designed for communities rather than with them. Traditional development models often rely on what we might call the “hero approach”: an expert or organisation identifies a problem, designs a solution, and implements it for the community. The community is the recipient. The expert is the agent of change.
Participatory community development challenges this model at its roots. It shifts the paradigm towards what we might call the collaborator model — where communities define their own priorities, power is shared, decision-making is collective, and solutions are co-created by those who will live with them.
| Dimension | Hero model | Collaborator model |
|---|---|---|
| Who sets the agenda? | The organisation / expert | The community, with facilitation support |
| Who has the answers? | The professional | Everyone involved has relevant knowledge |
| Role of the facilitator | Problem-solver, deliverer | Process-holder, connector, catalyst |
| Measure of success | Outputs delivered | Community ownership and sustained change |
| Risk | Dependency and disengagement | Slower start, but deeper roots |
When communities are genuinely involved in defining what they need and designing how to address it, something changes. The project gains legitimacy — it is no longer something happening to people, but something people are creating. Sustainability increases because the community has ownership. Equity improves because diverse voices shape the priorities. And something harder to measure but deeply real also shifts: trust.
The ladder, the field and the question of power
Understanding participation as a spectrum
Not all participation is equal. This is one of the most important things to understand before you design anything. Well-intentioned projects regularly invite community members into processes that are, in reality, already decided. The meetings happen. The feedback is collected. And then nothing changes.
This experience — of being consulted without being heard, of being present without having power — erodes trust faster than being excluded altogether. It is called tokenism, and it is one of the most common failures in participatory work.
Arnstein’s Ladder of Citizen Participation
In 1969, urban planner Sherry Arnstein introduced a framework that remains strikingly relevant today. Her Ladder of Citizen Participation maps participation not as a single thing, but as a spectrum — ranging from manipulation to full citizen control. Her central argument was clear: the difference between the levels is the redistribution of power.
| Zone | Level | What it looks like in practice |
|---|---|---|
| Non-participation | Manipulation | People are brought into processes to be persuaded or educated about decisions already made. The agenda is closed. |
| Non-participation | Therapy | Engagement is used to address dissatisfaction without changing the conditions that cause it. |
| Tokenism | Informing | Information flows one way. People are told what is happening. Feedback is not expected. |
| Tokenism | Consultation | Opinions are gathered through surveys or hearings, but there is no commitment to acting on them. |
| Tokenism | Placation | Community members join advisory bodies but power holders retain final authority. |
| Citizen power | Partnership | Negotiation replaces tokenism. Decision-making is shared. Accountability is mutual. |
| Citizen power | Delegated power | Citizens hold majority authority in specific areas or programmes. |
| Citizen power | Citizen control | The community manages and governs the programme entirely. Institutions answer to the public. |
Arnstein’s enduring contribution is the uncomfortable question she forces us to ask: when we invite people to participate, what are we actually inviting them into? The ladder reminds us that engagement without power is not participation — it is performance. And communities learn to recognise the difference very quickly.
Paulo Freire and the right to co-create knowledge
A decade after Arnstein, Brazilian educator Paulo Freire offered a complementary insight from a different angle. In Pedagogy of the Oppressed (1970), Freire argued that traditional education — and by extension, traditional community development — treats people as empty vessels to be filled with knowledge and solutions. He called this the “banking model”.
Against this, Freire proposed a dialogical approach: one where people are understood not as recipients of knowledge, but as co-creators of it. The facilitator, in Freire’s vision, is not the one who has the answers. They are the one who creates the conditions for dialogue — where questions can be asked, reality can be named, and collective wisdom can emerge.
Together, Arnstein and Freire give us a powerful frame: genuine participation requires both structural power-sharing (Arnstein) and a cultural shift in how knowledge and expertise are valued (Freire). As a facilitator, you are working on both levels — in the design of your project and in how you show up in the room.
Listening before designing
Stakeholder mapping and community needs analysis
Before you design anything, you need to listen. Deeply, patiently, without an agenda. This is the most skipped step in community project design, and the one that costs the most later.
Listening before designing means investing time in understanding the community as a living system — who the key actors are, what relationships exist between them, what is already working, what tensions are present, and what the community itself identifies as priorities. This is not research done on the community. It is sense-making done with it.
Tool: stakeholder mapping
Stakeholder mapping is a participatory method for identifying and understanding the people, organisations, and groups who have a relationship with your project area. It is most powerful when done collectively — with community members as active contributors, not just interview subjects.
How to do it: a simple four-step process
- Name the stakeholders. Identify everyone who has an interest in, influence over, or is affected by the issue or area you are working with. Cast a wide net. Include unexpected voices.
- Map their relationships. Draw the connections between them. Who talks to whom? Who has power over whom? Where are the alliances? Where are the tensions? A visual map on a large paper or wall is far more useful than a list.
- Analyse their interests and influence. For each key stakeholder, ask: What do they want from this? What do they have to offer? What might make them resistant? What would make them become allies?
- Identify who is missing. Participatory projects regularly exclude the same groups: young people, women, people with disabilities, migrants, those living in poverty. Who is not yet in the room? How might you invite them in?
Stakeholder mapping is not a one-time exercise. It is a living document that you update as your project evolves and as new relationships form or shift. The Stakeholder mapping canvas (T1) in the facilitator toolbox below takes you through these steps.
Tool: community needs analysis
A needs analysis in participatory community development is not a survey. It is a structured listening process. The goal is not to gather data points but to understand how the community itself perceives its challenges, assets, and aspirations.
| Method | What it reveals |
|---|---|
| Asset mapping | What already exists in this community? What strengths, resources, skills, and connections can we build on? |
| Problem tree | What is the core issue? What are its causes (roots)? What are its effects (branches)? This is built collectively. |
| Community walk | Walk through the neighbourhood with community members as guides. Listen to what they point out, what they avoid, what they are proud of. |
| Story circles | Small groups share personal stories about a question: When did you feel most connected to this community? When did you feel most invisible? Stories reveal what surveys cannot. |
| Future visioning | Ask: If this community were exactly as you wanted in five years, what would it look like? This opens up aspiration without requiring immediate solutions. |
A good needs analysis doesn’t give you the project. It gives you the questions that will guide the design.
Designing with, not for
Co-creating a participatory project plan
You have listened. You have mapped. You have begun to understand the ecosystem you are working in. Now comes the moment that most project designers are most familiar with — but which, in a participatory approach, looks quite different from what they expect.
A participatory project plan is not a document you write alone and then present to the community for approval. It is something built together — in sessions where priorities are named collectively, roles are negotiated rather than assigned, and the design is visibly owned by those who will implement it.
The core elements of a participatory project plan
- Shared purpose statement. A one or two sentence description of what you are trying to change together, written in language that resonates with the community — not in grant language.
- Community priorities. The two or three issues the community has identified as most pressing, derived from your listening process.
- Participatory activities. The specific sessions, events, or processes you will facilitate — designed with the methods you have learned across Modules 1–4.
- Roles and responsibilities. Who does what — clearly distributed, with community members carrying real responsibilities, not just observer roles.
- Boundary partners. The people your project works with most directly. In line with the Outcome Mapping approach you will explore in Topic 3, name them now — this will anchor your later monitoring.
- Milestones and check-ins. Not a rigid timeline, but a set of moments where you pause to ask: Are we still on track with what the community wants? What needs to shift?
- Sustainability question. What happens when you step back? A participatory project should be building community capacity — not dependence on the facilitator.
Notice that this plan is more of a framework than a blueprint. The details will be filled in through ongoing dialogue with the community. The plan is a living document — designed to evolve as the project does.
Interactive activity: mapping your participation landscape
This mapping activity invites you to apply Arnstein’s Ladder and the hero → collaborator spectrum to a real community context you know — and to begin sketching the stakeholder landscape for your local facilitation project.
Reflection task: your design story
“The single biggest problem in communication is the illusion that it has taken place.” — George Bernard Shaw
Bring it to life: the listening session
The most powerful thing you can do right now is not to design your project. It is to have a conversation that begins the design together.
This challenge asks you to organise one small group listening session — a gathering of three to eight people from your community context — before you design anything else. The purpose is not to present your ideas. The purpose is to understand theirs. The Community listening session guide (T2) in the facilitator toolbox below takes you through a full session step by step.
Facilitator toolbox
Three downloadable tools to support your participatory project design process.
T1 – Stakeholder mapping canvas
A printable and editable canvas for mapping stakeholders visually. Includes guidance on identifying actors, mapping relationships, analysing interests and influence, and spotting missing voices. Designed to be used as a group exercise with the community — not completed alone at a desk.
T2 – Community listening session guide
A facilitation guide for running a one-to-two-hour community listening session from start to finish. Includes opening and closing rituals, question prompts, listening protocols, and tips for making the session accessible to diverse participants. Adaptable to different group sizes and cultural contexts.
T3 – Participatory project plan template
A one-page living template structured around the seven core elements described in “Designing with, not for” above: shared purpose, community priorities, participatory activities, roles and responsibilities, boundary partners, milestones and check-ins, and the sustainability question. Designed to be filled in collaboratively, revised often, and kept visible to the community.
Closing: the courage to begin together
“The quality of our collective future depends on the quality of the conversations we are willing to have today.” — Adapted from David Bohm
Designing a participatory community project is not an act of expertise. It is an act of courage — the courage to not know, to listen before acting, to share power rather than holding it, and to trust that collective intelligence is greater than individual cleverness.
You have spent four modules developing the inner attitudes, tools, and relationships that make this kind of design possible. Now you get to practise it for real, in a real community, with real people who have real things at stake.
Start small. Stay curious. Listen more than you speak. And remember: the goal of this project is not to deliver something impressive. The goal is to create conditions where the community can see its own capacity more clearly, and begin to act from it.
That is what facilitation is for.
Further reading
Designing participatory community projects
Your progress is saved in this browser. Register to save it on every device.
Text © IN.PACT partnership, shared under CC BY-SA 4.0. Images, videos and quoted works belong to their authors and are not covered by this licence unless stated.