Defining a community and a need
5 min read
Lesson objectives
- Define a community and distinguish a stated request from an evidenced, bounded need; output a need statement with population, place and evidence limits.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
When an initiative coordinator says, “This neighbourhood needs another centre,” the proposed solution has arrived before the problem is established. Some residents may need a place to learn. The obstacle might instead be opening hours at an existing room, travel to it, or a programme that does not fit. A useful diagnosis separates three questions: who is within the decision, what observable condition affects them, and what evidence supports that description. A “community” is not automatically everyone in a city. Define it by a place, shared relationship or common interest, then ask who the definition leaves out. If the available register covers only people who already use a facility, those kept away by opening hours or transport are missing from the register. The community affected by a decision is wider than the people visible in its records.
A need is a gap between a present condition and a valued, attainable condition for those affected. A request is the way a person or group describes a preferred response. Treat the request as a lead, not as either a command or an error. A working need statement says: “Among [population] in [scope], [observable condition] occurs during [period], as indicated by [evidence], creating a need for [desired change].” If a new building, app or campaign is placed in the final slot, check whether it is only one means of reaching the change. “We need an app” does not tell us who is unable to use a service, why access fails, or what an app would improve. Separating the outcome from the means allows the community to compare less costly and more accessible responses.
Build a small evidence map. An administrative register can show recorded use, but not people who never reached the service. Interviews with users and non-users can expose possible causes, but convenience interviews do not yield a representative population percentage. Observing a crowded hour or an inaccessible entrance can support an account of the access process, but it cannot by itself establish every cause of non-use. Check what each source counts, not just how many sources you have: request or person, which period and catchment area, and whose voice is absent? UNICEF's community engagement standards describe direct involvement of local populations in decisions and implementation and the importance of local ownership. In this programme that means the facility's account alone cannot stand in for the community's account of its own priorities.
Lesson summary
Community context and needs diagnosis: Define a community and distinguish a stated request from an evidenced, bounded need; output a need statement with population, place and evidence limits.