Public policy and impact management
Project management and impact evaluation
From designing the policy to proving it worked.
- Anticipate
- Decide
- Transform
- Demonstrate
Designing a policy and proving its impact are the same job, separated in time. We run them as one.
From signal to proof, in four movements.
This is how this focus runs. The movements it leads with carry more weight, but the arc closes in full: without the last one there is no way to prove the first one worked.
- 01Anticipate
What problem you are actually solving
Diagnosis, scenarios, risks and stakeholders: what the evidence says, who executes, and which constraints define what is feasible — before a design is committed to.
- 02Decide
What will be done, and in what order
The roadmap of the policy design, with the initial advisory session that first defines what you need and how to approach it. The decision comes before the document.
- 03Transform
The instrument execution runs on
Development plans and government plans: the design comes down to targets, owners and sequence. It is the deliverable that turns a decision into operations.
- 04Demonstrate
Evidence that it worked
Impact evaluation with traceable, defensible evidence that separates what the policy achieved from what would have happened anyway.
What actually reaches your hands.
- 01Public policy design: diagnosis, scenarios, risks, stakeholders and roadmap
- 02Impact evaluation with traceable, defensible evidence
- 03Development plans and government plans
- 04An initial advisory session to define what you need and how to approach it
Who works with this focus.
Foundations, organizations and executive-branch government.
Tell us which one you need. We'll answer with a diagnostic.
We start from your pending decision. Tell us what's on the table and we answer with a diagnostic, not a quote.