Outcome & Constraints
Define the consequential decision first before touching any data
The OLPADR engagement does not begin with data collection. It begins with precision. Before a single spreadsheet is opened, we ask: "What decision is this evaluation informing and what constraints will bound it?" This step formally identifies what must be protected (non-negotiable outcomes) and what is structurally off-limits (legal, financial, or time constraints that define what is possible).
Without this step, every subsequent stage measures the wrong thing with technical precision. Organisations spend months producing evaluation data that answers a question no funder actually asked one of the most expensive and invisible failures in the sector. The Outcome Statement locks the evaluation question before any resource is spent answering it.
What We Do At This Step
We extract 3–5 quantifiable outcomes from your mission description and formally document every constraint that will shape the engagement. Nothing is assumed. Nothing is undefined.
Artifact Delivered
Outcome Statement (who / what / by when) · Constraint Log (legal, financial and time limits bounding the evaluation)
What Leaks Without This Step
Every subsequent step produces technically precise answers to the wrong question. Funders receive data about outcomes they never asked for. The evaluation looks rigorous on paper and is completely useless in practice.