> For the complete documentation index, see [llms.txt](https://circles.logos.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circles.logos.co/readme/for-circle-stewards/section-1-organising-circles-around-local-action/what-is-a-winnable-issue.md). # What is a winnable issue? In community organising, there is a concept known as an **“**issue-cutting” or “issue-based campaign” strategy. It involves selecting a clear, concrete, winnable issue that allows organisers to mobilise the community effectively, build solidarity among participants, and gain momentum to achieve broader social change goals. The idea is to: * **Identify an issue** that resonates broadly with community members. * Choose a **specific and achievable target** for action to ensure early victories. * Use these victories to **build collective confidence**, foster greater solidarity, and sustain long-term participation and growth within the movement. This method is particularly emphasised in the highly successful **organising methods developed by Saul Alinsky,** often summarised as: > “Pick the target, freeze it, personalize it, and polarize it.” (Saul Alinsky, Rules for Radicals) Such campaigns are foundational in community organising, leveraging clear and attainable goals to foster greater unity, build organisational strength, and enhance strategic positioning for future, more ambitious initiatives. This concept is highly related to fostering [Interaction Ritual Chains](https://notes.status.im/interaction-ritual-chains). {% hint style="info" icon="child-reaching" %} Remember, people participate because they care, not because the technology is interesting. {% endhint %} #### What Makes an Issue Winnable? * Aligned with Logos values: decentralisation, privacy, open infrastructure, autonomy. * Has emotional weight: people feel strongly about it. * Tangible and achievable: something your Circle can take action on and see progress. * Already has roots: there are local individuals, groups, or organisations already working on it. ### Winnable Issue checklist #### **Clarity & Focus** * \[ ] Is the issue clearly defined and specific (not vague or overly broad)? * \[ ] Can the problem be explained in one or two sentences? #### **Emotional Resonance** * \[ ] Does it provoke strong emotions (anger, hope, solidarity, urgency)? * \[ ] Does it affect people in your community directly or personally? * \[ ] Would people feel motivated to act or show up because of it? #### **Actionable & Measurable** * \[ ] Are there *concrete steps* the Circle could take toward a solution? * \[ ] Does the group have the resources, time and effort required to achieve this? * \[ ] Are there *clear indicators* of success or progress? * \[ ] Is there a clear start and finish? #### **Aligned with Logos Values** * \[ ] Does it align with decentralisation, transparency, privacy, or mutual aid? If you can check at least 80% of this list, you're likely working with a real winnable issue. If not, refine the problem or go deeper into community listening. Winnable issues emerge through conversation, care, and iteration. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://circles.logos.co/readme/for-circle-stewards/section-1-organising-circles-around-local-action/what-is-a-winnable-issue.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.