Approach
We strengthen the networks that make solutions possible
The hardest problems in public health are structural. They live between organizations, in handoffs, funding lines, and relationships. Our method is built for that reality.
Principles
What guides the work
Structure before solutions
We resist proposing interventions until the system is legible to everyone at the table. A plan built on a partial picture spends real money solving the wrong constraint.
Shared understanding is the deliverable
A map that only the consultant understands has failed. We build interpretations collectively so partners own the conclusions and can defend them without us in the room.
Neutral, not passive
We facilitate without a stake in which agency wins. That neutrality is what lets us push a group past comfortable consensus toward an actual decision.
Design for the capacity you have
Our partners are lean. We build measures and tools that a two person team can maintain, not systems that assume a dedicated analyst who does not exist.
Evidence, applied honestly
We ground work in published theory and method, and we say plainly when the evidence is thin. Overstating certainty is how public health loses credibility.
Leave capability behind
Success is measured by what your team can do the year after the contract closes. Dependency on a consultant is a failure mode, not a business model.
The sequence
How an engagement moves
Four phases, adapted to scope. A short assessment might run in six weeks. A statewide mapping effort runs across multiple years with the same underlying logic.
Understand your system
We start by clarifying who is actually in the system, what data already exists, and what decision is waiting on better information. This phase surfaces the disagreements early, while they are still cheap to resolve. Typical activities include stakeholder interviews, document and data inventory, indicator review, and a readiness conversation with leadership about what the work can and cannot deliver.
Map it as a network
We render the system visually. Systems mapping traces how a person moves through the contact points available to them and where they fall out. Stakeholder network mapping shows which organizations are connected, which are isolated, and where a single relationship is holding up a whole pathway. Journey mapping puts the lived experience next to the organizational chart, which is often where the most uncomfortable findings appear.
Decide together
Maps do not change systems, decisions do. We facilitate structured prioritization that moves a group from a wall of observations to a short list of commitments with named owners, dates, and a way to tell whether they happened. When a group is stuck between competing interpretations, neutral facilitation is usually what unblocks it.
Sustain the capability
We hand off measures, templates, and skills. That includes an evaluation approach your team can run, documentation written for the staff who will inherit it, and training so interpretation does not depend on any one person. Where useful, we build lightweight tools that automate the reporting your partners dread most.
Methods
What we bring to the table
Established public health methods, formal research technique, and models we developed because the existing ones did not fit the problem.
Facilitation methods
- Group facilitation
- Topical training
- Stakeholder network mapping
- Journey mapping
- Learning collaboratives
Research and analysis
- Topic modeling and quantitative text analysis
- Mediation analysis
- Survey design and psychometrics
- Outcome and process measure development
- Risk index modeling
Frameworks we developed
- Data Empowerment Model, a three tier progression from access to fluency to action
- Inhibitor Abandonment Matrix, a model of why people stop using digital mental health tools
Technology
We build the tool the work actually needs
Most partners do not need another platform. They need one specific thing to stop being manual. A quarterly report that takes three days to assemble. A referral log kept in four incompatible spreadsheets. A survey whose results nobody has time to summarize before the next meeting.
When a problem is shaped like that, we build for it directly. That might be a mapping instrument a facilitator can run without us, a tracker that keeps a coalition honest between meetings, a survey and analysis pipeline, or a reporting workflow that produces the funder summary automatically from data your team already enters once.
Two rules govern this work. It has to be maintainable by the people who will inherit it, which means simple, documented, and free of anything requiring a specialist to keep running. And it has to be yours, not something you rent from us. We hand over the tool and the understanding of how it works.
We take the same position on artificial intelligence. We use it where it genuinely returns hours, we say plainly where it does not, and we train partners to tell the difference for themselves.
Bring us the part of the system nobody can see
We will tell you honestly whether mapping, evaluation, or facilitation is the right first move.