Listen. Understand.
Align. Act.
Measure. Learn.
Collective action is not a meeting series. It is a disciplined cycle that turns what a community knows into what a community does — and then checks whether it worked. This is the cycle Trenton Collective runs with partners.
A Cycle, Not a
Checklist.
Every stage of this model produces something the next stage needs. Listening produces evidence. Evidence produces shared understanding. Shared understanding makes it possible to agree on goals. Goals make coordinated action possible. Measurement tells the group whether the action mattered. Learning changes the next round.
Skip a stage and the whole thing weakens. Groups that align without understanding end up with goals nobody believes. Groups that act without measurement cannot tell effort from progress. Groups that measure without learning produce reports instead of change.
The loop matters more than any single stage. Trenton Collective’s job is to keep it turning when the day-to-day work of direct service makes that hard.
Someone has to hold the shared work: the data, the calendar, the definitions, the follow-up, the uncomfortable question about whether the outcome moved. When that role is unassigned, collaboration decays into good intentions. Trenton Collective exists to hold it.
6
Stages in the cycle, each with a defined output
0
Stages where measurement is optional
Every Stage Has
an Output.
A stage is finished when it has produced something the next stage can use. That discipline is what separates collective action from a standing meeting.
ListenGo to residents first, not last.
We start with the people closest to the problem. That means resident surveys, community listening sessions, focus groups, and conversations in the places people already trust — not just public meetings that require someone to show up on our schedule.
We also listen to organizations. Frontline staff usually know where the system breaks long before it appears in any dataset. Their observations are evidence, and we treat them that way.
What this stage produces: a documented record of what residents and practitioners say the problem actually is, in their words.
UnderstandBuild one picture the whole group can see.
Next we combine what we heard with what can be counted: public data, administrative data, partner records, and existing research. The point is not a longer report. The point is a shared picture — specific enough to argue with, clear enough for a room of busy people to hold in their heads.
This is where disparities surface. Citywide averages hide neighborhood-level gaps, and neighborhood averages hide which households are being missed entirely. We look for both the pattern and the exceptions, including assets that existing efforts are not using.
What this stage produces: a shared analysis of the problem, its drivers, and the current landscape of who is doing what.
AlignAgree on a small number of outcomes that matter.
Alignment is the hardest stage and the one most often skipped. It means a group of independent organizations agreeing, out loud, on the specific outcomes they are trying to change together — and on how success will be defined before anyone claims it.
We facilitate that conversation and write down what was agreed: the common agenda, the shared outcomes, the indicators, the roles, and who is accountable for what. Alignment does not require that every partner do the same thing. It requires that every partner know how their piece connects to the others.
What this stage produces: a common agenda with shared goals, agreed measures, and named roles.
ActCoordinate, do not consolidate.
Aligned action means each partner does what it does best, sequenced so the pieces connect for the resident rather than for the org chart. Referrals land somewhere real. Handoffs have owners. Gaps that nobody was mandated to fill get named and assigned.
Trenton Collective does not take over partner programs and does not compete for the direct-service role. We coordinate: convening the group, tracking commitments, brokering connections, and surfacing the friction that keeps the plan from working in practice.
What this stage produces: coordinated strategies in the field, with a visible record of who committed to what.
MeasureTrack the outcome, not just the activity.
Measurement starts before the work does. We establish baselines, define indicators precisely enough that two organizations count them the same way, and set a schedule for collection and review. Activity counts still matter — they tell you whether the plan is being executed — but they are not evidence of progress.
Results go back to the same group that set the goals, in a form they can use: dashboards, short briefs, and plain answers to the question “did it move.” That includes reporting when the answer is no, or not yet, or we cannot tell.
What this stage produces: a live view of shared progress that every partner can see, including the parts that are not working.
LearnChange the strategy, then run it again.
Learning is a decision-making stage, not a debrief. The group reviews what the measurement shows, asks what would have to be true for the outcome to move faster, and adjusts — reallocating effort, dropping what is not working, and taking what works to more places.
Then the cycle restarts with better questions than it started with. Over time this is what compounds: not a single program, but a group of organizations that has gotten measurably better at reading its own city and responding to it together.
What this stage produces: revised strategy, reallocated effort, and a sharper set of questions for the next round of listening.
The Collective
Action Model.
The same cycle, drawn as the sequence of things it produces. The dashed line underneath is the part most collaborations get wrong.
Resident voice, partner records, and public data on the same table.
Partners read the same picture of the problem before proposing solutions.
A short list of outcomes a group of organizations commits to together.
Each partner does what it does best, sequenced so the pieces connect.
Agreed indicators, collected on a schedule, visible to everyone involved.
What the data says changes the strategy — not just the next report.
Not an Afterthought.
A Through-Line.
In most collaborations, evaluation arrives at the end — when a funder asks for it, and when it is too late to change anything. In this model, measurement is present in every stage.
Questions are designed so answers can be tracked over time, not just quoted once.
Baselines are established before anyone proposes a solution, so later change is legible.
Indicators and definitions are agreed as part of the goal — not negotiated afterward.
Collection is built into the work rather than bolted on as extra reporting for partner staff.
Findings are reviewed by the people who can act on them, on a cadence set in advance.
We report what the data supports and nothing more. When a baseline is still being established, we say so. When an indicator has not moved, we say that too. A backbone organization that inflates results is worse than no backbone organization, because it makes the whole group’s evidence untrustworthy.
What We Do —
and What We Don’t.
We hold the
shared work
- Collect and analyze community data
- Convene and facilitate cross-sector groups
- Design shared outcomes and measurement
- Track commitments and report progress
- Broker connections and surface gaps
Partners hold
the delivery
- Run the programs and services they do best
- Bring frontline knowledge to the analysis
- Commit to shared goals and indicators
- Share data under agreed terms
- Adjust practice based on what the group learns
What we are
not doing
- Competing with partners for direct-service roles
- Speaking for organizations that did not agree
- Claiming partner outcomes as our own impact
- Adding reporting that serves no one at the table
- Launching a program because it is fundable
Run This Cycle
With Us.
The model works when enough of Trenton’s organizations are in it. If your work touches any of the issues we apply it to, the next step is a conversation about what you are trying to move.