A quick origin story. Over the last couple of years a lot of us have been doing real work on the ground: gardens, restoration, microeconomies, solar hubs, agroforestry. We’ve also been building the tools to support it. But we keep running into the same wall. It’s hard to make that work legible. When a funder asks “what’s your impact?”, we reach for abstract language instead of pointing to a clear baseline and a clean set of numbers. We feel the impact. We just don’t yet share a common way to capture and report it.
So this isn’t about starting from scratch. The work is already happening and the tools already exist. This is about pausing, or working in parallel, to make all of it more legible. The clearer we get on how we capture and report impact, the better we can improve the tools we’ve already built.
Building on what we’ve already started
This also isn’t the first time Regen Coordination has reached toward this. We’ve already laid groundwork on common impact data standards, an initial step forth toward the coherency and shared aspects we’re describing here. This workshop is a way to carry that work forward: bringing more communities into the conversation and turning those early standards into something we genuinely share and use together, rather than letting that effort sit in isolation.
Why higher than just Greenpill
We’re actively building a Greenpill Impact Framework and that remains a priority. But the patterns we’re wrestling with, making work legible, mapping activities to outcomes, finding shared metrics, aren’t ours alone. Bloom Network, RefiDAO, and others are holding the same questions. It feels far more powerful to do this mapping at the Regen Coordination level, where we can align on shared language once rather than each reinventing it. The goal isn’t to merge anyone’s tools. It’s coherence.
What we’re proposing
A Regen Coordination workshop run as a cooking session. We gather, build the recipe (the spec for you techies: what to capture, how to report it, what language we share), and hand it off to be baked. Then we come back, taste it, and refine.
We’d love your thoughts on a few things:
-
When you talk to a funder or supporter, where does your impact story break down? What’s hard to make legible?
-
What would a shared impact vocabulary need to include to actually work across our different communities?
-
Are there metrics or baselines you already track that others could learn from?
-
Who else should be in the room? Names, projects, communities holding pieces of this puzzle.
We’ve opened a quick poll to gauge what people most want to cook first: https://t.me/c/2214404857/1/2628
Drop a reply even if it’s half-formed. This thread is intentionally a work in progress, and the best recipes come from many hands.
Many hands make the load light.
