Approach
We sit between the consultant who departs and the agency that invoices
A translational strategy partner co-designs strategy with communities and leadership, then builds the operational systems that make the strategy self-sustaining.
The framework
The Translation Stack
Insight usually dies at a border: between data and decision, between community and institution, between commitment and design. Every service we offer maps onto one or more layers of the stack, and every proposal diagrams exactly which layers the engagement builds.
You can hold us to that diagram on scope, and your team can use it to see what it owns when we leave.
The Evidence layer is where our evaluation practice runs its full journey: readiness diagnosed, evaluation built, learning sustained.
The Translation Stack is one of four frameworks behind our work. See all four frameworks
Every engagement is scoped against these four layers
Before any proposal
How a discovery call works
On a first call, we ask questions in a fixed order, and we ask them before we write a proposal, so nothing in it is a surprise.
We read up on your programs, public commitments, and recent leadership or funding changes before we ask you to repeat any of it.
The answer usually tells us more than the RFP does.
What would the board be celebrating? We push past the first answer for specifics.
Where measurement, engagement, or infrastructure stands today, and how far that is from the strategic plan.
Capacity, trust, a consultant who didn't stick. Named now, so the proposal doesn't repeat it.
That conversation becomes the first two sections of every proposal we send: what you told us, quoted back accurately, and what we heard underneath it, the structural pattern beneath the presenting problem.
Every proposal, same skeleton
Every proposal opens with the same questions
You will never receive a proposal from us that hides the ball. Each one opens the same way, because trade-offs named early are trade-offs you can plan around.
Your words, quoted back accurately. If we heard it wrong, we fix it here, not in month three.
The structural pattern beneath the presenting problem. This is where the diagnosis lives.
Scope mapped to the Translation Stack, with the co-design moments marked.
The artifact table: every framework, protocol, library, and dashboard, named.
Investment anchored to the cost of the status quo, with trade-offs stated plainly.
What we hold ourselves to
Our commitments, in writing
Data informs; communities decide. Rigor is a form of respect.
We measure commitments by what they redesign.
Delay is a choice. Timelines deserve the same scrutiny as outcomes.
Every engagement should make you less reliant on consultants, including us.
The name is the value: people engaged as they are, not as institutions wish they were.