6.1 Planning and analysis workflows
1. Move from raw concerns to structured problems.
Planning starts by moving from raw concerns to structured problems. People begin with stories, frustrations, and scattered observations, and the workflow helps them turn that into clearly framed problems—naming what is happening, to whom, where, and in what patterns—so later steps are not built on vague complaints.
2. Gather and synthesize information and perspectives.
Information and perspectives are gathered and synthesized deliberately. Rather than relying on a single report or viewpoint, the workflow prompts you to look for data, laws, lived‑experience accounts, and comparable cases, then pull them together into a shared picture that participants can inspect and critique.
3. Define baselines and goals for “better.”
Rights‑based baselines and goals for “better” are defined early. Before drafting solutions, the group clarifies what rights and democratic standards must be upheld and what “good enough” conditions would look like, so that proposals can be tested against a clear standard rather than drifting with political convenience.
4. Draft and revise candidate plans.
Candidate plans are drafted, iterated, and stress‑tested. Participants produce initial plan drafts, then refine them through feedback from affected parties, experts, and support team, checking for feasibility, unintended consequences, and alignment with baselines, and revising until there is a version that feels both principled and realistic.
5. Record decisions and reasoning.
Decisions and reasoning are recorded as you go. At each major choice point—such as choosing between options or narrowing scope—the workflow calls for short notes on what was decided and why, so that others can understand the logic, revisit assumptions later, and avoid repeating already‑explored dead ends.
6.2 Implementation workflows (campaigns, adoption)
1. Identify institutions and actors to target.
Implementation begins by identifying the key institutions and actors. For each plan, you map which bodies—government agencies, legislatures, courts, companies, schools, or community organizations—actually have the power to change policies or practices in the way the plan requires.
2. Design campaigns, asks, and engagements.
Campaigns, asks, and engagement tactics are designed with those actors in mind. Instead of generic awareness efforts, the workflow encourages you to craft specific asks that fit how each target institution makes decisions, along with tactics like meetings, public pressure, coalition letters, or media work that can realistically influence them.
3. Coordinate outreach and relationships.
Outreach and relationship‑building are coordinated rather than improvised. Implementation workflows include basic scheduling, division of labor, and communication plans so that different people and groups are not duplicating efforts, talking at cross‑purposes, or overwhelming targets with uncoordinated demands.
4. Support local adaptations of plans.
Local adaptations of plans are supported, not left to chance. Recognizing that contexts differ, the workflow makes space for local groups or partners to adjust language, tactics, and even some plan details within agreed‑upon baselines, while still feeding information back into a shared core so the overall effort stays connected.
5. Track adoption and commitments.
Adoption and commitments are tracked as explicit milestones. When an institution signals interest, makes a partial concession, or formally adopts part of a plan, those steps are treated as milestones to be logged, celebrated, and scrutinized, rather than as vague impressions that “things are moving.
6.3 Accountability workflows (monitoring, escalation, follow‑through)
1. Monitor what was promised vs. what happened.
Accountability workflows monitor what was promised versus what happened. Once commitments are on the table, the workflow tracks whether actions match them—such as whether a policy was actually implemented, resources were allocated, or practices changed—over the timescales that matter.
2. Gather reports from affected parties and allies.
Feedback from affected parties and allies is collected systematically. Rather than relying solely on official reports, the process encourages regular check‑ins, surveys, stories, and observations from people on the ground and partner organizations to see how changes are playing out in real life.
3. Log successes, failures, and partial wins.
Successes, failures, and partial wins are logged in a shared place. Outcomes—good and bad—are documented in ways that others can find later, including notes on context and contributing factors, so that learning is not limited to the memories of a few people who were closely involved.
4. Escalate when commitments are broken.
Escalation paths are defined for broken or stalled commitments. When targets fail to act or backslide, the workflow points to agreed next steps—such as public disclosures, new campaigns, or legal avenues—so that accountability does not depend on ad hoc reactions each time something goes wrong.
5. Feed results back into plans and messaging.
Results are used to revise plans, strategies, and narratives. Accountability is treated as part of ongoing learning: what you discover through monitoring feeds into changes in the plan itself, adjustments to future tactics, and updated public explanations of what worked, what did not, and why.
6.4 Roles across the workflow pipeline
1. Map which roles appear at each stage.
Different roles have clear responsibilities at each stage of the pipeline. Affected parties, facilitators, subject‑matter experts, support team members, and governance roles all appear in different ways during planning, implementation, and accountability, and the workflow maps who is expected to do what so responsibilities are not left to guesswork.
2. Clarify handoffs between roles and teams.
Handoffs between roles and teams are made explicit. When work moves from one stage to the next—for example, from planning to campaign design—the process includes defined handoff points where knowledge, documents, and contacts are consciously transferred, reducing the risk that momentum is lost.
3. Show how leadership shifts over time.
Leadership and initiative can shift over time without causing confusion. The workflow anticipates that different people may lead at different stages—such as affected‑party leaders in problem framing, subject-matter experts in technical drafting, and campaigners in implementation—and provides ways to signal those shifts while keeping accountability visible.
4. Highlight dependencies across hubs and issues.
Dependencies across hubs and issues are surfaced and managed. Because some plans depend on others or touch multiple domains, the role map highlights where coordination is needed between hubs or teams, helping to prevent conflicts, duplicated outreach, or contradictory asks.
5. Surface gaps where new roles are needed.
Gaps in capacity or missing roles are treated as design signals. When the pipeline repeatedly stalls at specific stages—for example, monitoring or communications—the workflow encourages you to treat that pattern as information that new roles, training, or partnerships may be needed, rather than as isolated bad luck.