A vague request for help is hard to act on, even for people who genuinely want to help. "Anything helps" leaves a reader guessing what would actually change the situation, and most people move on rather than guess wrong. HelpBLESS, a mutual-aid board where neighbours post needs and offers side by side, was built around the opposite instinct: clarity first, generosity second. The board at HelpBLESS pairs a request with the details a helper needs to say yes, and that pairing turned out to be the product, not a decoration on it.
What was built is deliberately plain. A person posts a need — a ride on a particular day, groceries for one week, help covering one bill — and another person posts what can be offered, whether time, a skill, or a direct gift. There is no feed to scroll endlessly, no ranking of the most dramatic story, and no intermediary deciding who deserves help. Requests and offers sit next to each other, in the open, so support can move directly between people. The goal is a concrete next step, not attention for its own sake.
The central design decision was to structure the ask. Instead of one open text box, the posting flow separates the need itself, the date or window when it matters, and what has already been resolved. Each field has a short prompt and an example, so a writer can see what a useful answer looks like before typing. The trade-off was obvious from the start. More fields mean more friction, and a person in a difficult week does not need a form that feels like an application. That cost was accepted because an unstructured post carried a larger one: helpers who could not tell what was needed, when it was needed, or whether the request was still open simply did not reply.
What worked was the specificity itself. Naming an exact need gave helpers something concrete to agree to, and it let several people each take one piece instead of one person feeling obliged to solve everything. A ride on Tuesday is a commitment a neighbour can check against a calendar; "help with transport sometime" is not. Separating what was already resolved also helped, because it stopped helpers from offering what had been covered and let them focus on the gap that remained. Short, structured posts are easier to scan than long appeals, and that matters when a visitor is deciding, in a minute or two, whether there is a request they can answer.
What broke was the first version of that same flow. The early form asked for everything at once, in long boxes with no examples, and the result was the vagueness it was meant to prevent. People wrote "anything helps" because the form gave them no guidance on what to say, and helpers hesitated for the same reason readers of a vague post always hesitate: they did not want to promise the wrong thing, or to intrude by asking for details the poster might not want to share. Offers had a related weakness. An offer without a time window stayed on the board long after the person could no longer honour it, and a request answered quietly was not always marked as resolved, so newcomers spent effort on needs that were already met.
What changed was the wording around the fields, not the idea behind them. The prompts were rewritten as plain questions — what is needed, when, and what is already covered — and the examples were drawn from ordinary requests rather than edge cases. Resolved requests were made easier to close, and offers were given a visible window so a helper could state plainly what was available and for how long. The form still asks for more than a single box would, but each field now earns its place by answering a question a helper would otherwise have to ask. The lesson is transferable beyond mutual aid: when a product depends on strangers cooperating, the interface is the etiquette. A form that asks for the right details, in the right order, is not bureaucracy; it is the thing that lets a willing stranger act without guessing. Builders who find their users hesitating should look first at what the interface leaves unsaid, because a clear ask is often the difference between goodwill that moves and goodwill that scrolls past.
What would make a request easier for you to answer — a firmer date, a clearer boundary, or knowing what has already been covered?
