Four territories and one question: does this solution leave the larger pattern healthier than it found it? Below, the terrain, the shapes an engagement takes, the method underneath, and the standards I hold it to.
Different sectors, same question: does this solution leave the larger pattern healthier than it found it?
Soil, carbon, and ecosystem markets designed so more value reaches the growers and land stewards doing the work: program design, measurement honest about its own uncertainty, and the farmer-facing translation that decides whether any of it gets adopted.
Who it serves Growers, land stewards, program teams, buyers, and researchers.
Electrification where it actually happens: one house, one contractor, one block. Anchored on Chicago's North Shore. The transferable part was never the equipment. It is the translation layer and the operating system around it.
Who it serves Contractors, homeowners, utilities, and municipalities.
Ownership, procurement, and governance designed to keep more value circulating in the communities that create it, from design to pilot to scale. The longest arc, and a lens that runs beneath the other two.
Who it serves Businesses, workers, institutions, local governments, and community organizations.
Where a tool meets the place it is deployed: governance, data practice, and the question of what a model cannot know from nowhere. Newest of the four, and the one that keeps arriving inside the other three.
Who it serves Builders, institutions, affected communities, and public agencies.
These are starting shapes, not packages. I scope the smallest useful piece of work once I understand what is actually stuck.
A bounded inquiry when the problem is consequential but the diagnosis is unclear.
Typically 2–4 weeks
Usually some combination of a system and stakeholder map, a barrier diagnosis, decision framing, a synthesis brief, and a recommended next sequence.
Turn the diagnosis into a program, tool, story, workflow, pilot, or decision system.
Typically 6–12 weeks
A program or pilot design, a methodology, a decision tool or workflow, and the operating model around it.
Ongoing strategic capacity for a team moving through a complex change.
Ongoing, usually monthly
Embedded or fractional advisory: partnerships, program iteration, market development, operating system design, stakeholder coordination, and implementation support.
The method is simple so the thinking can be rigorous.
Strategy starts where the work actually happens: the field edge, the shop floor, the kitchen table, the service call.
Trace how money, energy, trust, and information really move. The stuck point is rarely where it hurts.
One or two changes that solve more than one problem without creating new ones. Not a forty-item roadmap.
A real thing (a program, a system, a pilot, an operating cadence) proven in use, not in a deck.
The work isn't done until your people can run it, extend it, and explain it without me.
Berry's “Solving for Pattern” offers fourteen tests for a good solution. These five are my working synthesis, not quotations. They are the ones that most often change a recommendation before I ask anyone else to live with it.
A model makes some relationships visible by leaving others out. Before I ask anyone to act on one, I make its boundary, assumptions, evidence, and uncertainty visible, and bring in the people who will live with what it omits.
How the standards become methodA few sentences about what feels stuck is enough to start. I read every inquiry myself.
Replies personally and promptly