Program Evaluation
Mission-driven engagements where donor relationships, program delivery, and governance determine impact.
Inside this journey
-
Pre-Discovery
Align the room on outcomes, decision process, and constraints before deeper discovery.
-
Stakeholder Alignment
Confirm decision roles, timelines, funding triggers, and what 'good' evidence means for each stakeholder.
Alignment Questions
Quick Intro — Who's in the Room?
- Who should we consider part of the formal decision team for this evaluation (names and roles)?
- Which single person is expected to sign the contract or authorize budget for this work?
- Who needs to be informed but is unlikely to influence the design (e.g., communications, beneficiaries, partner agency)?
- How stable is the decision team between now and the expected project timeline (turnover, political cycles)?
- Tell us anything about these people — personalities, prior experience with evaluations, or recent events — that will shape how decisions are made.
Who's Really Driving the Decision?
- If the person with the loudest voice wins, who would lose — and what would that cost your program or the funder?
- Which stakeholders have formal veto power over budget, methodology, or report release?
- Who in the group is most likely to prioritize reputational or political risk over methodological trade-offs?
- How have disagreements between key stakeholders affected past decisions on evaluations or program changes?
- How long has the core decision-making team worked together, and how does that tenure affect their willingness to accept critique or change?
What 'Good Evidence' Really Means to Them
- When you hear the phrase 'rigorous evidence,' whose definition of rigor matters most—and how do they describe it?
- For each key stakeholder, what concrete findings, metrics, or thresholds would make them conclude the evaluation succeeded (list person/role → evidence needed)?
- Do any stakeholders require specific statistical thresholds or power for decisions (e.g., p-values, minimum effect size, subgroup power)?
- If the answer above is yes, please specify the thresholds, who requires them, and why they matter.
- How important is demonstrating equitable impacts across subgroups to your decision-makers (e.g., race, income, geography)?
- Which forms of evidence will carry the most weight with each stakeholder: quantitative outcomes, qualitative stories, cost-effectiveness, implementation fidelity, or something else?
Timing, Triggers, and Funding Windows — What Breaks the Stalemate?
- If there’s one date or deadline that makes this project happen — or causes it to collapse — what is that date and why?
- Which external deadlines are tied to funding or reporting (select all that apply)?
- What funding triggers or milestones (e.g., match funding, enrollment targets, partner agreements) will unlock payment or continuation of the program?
- How flexible are timelines if the evaluation needs more time for IRB approval, data access, or partner coordination?
- Are there internal checkpoints where interim findings could influence decisions even before the final report (e.g., pilot adjustments, funding reallocation)? If so, what are they?
What's Getting Hidden Under the Surface?
- What inconvenient truth about the initiative would stakeholders prefer the evaluation not fully expose?
- Are there known data gaps, quality concerns, or partner conflicts that could limit credible conclusions?
- Which organizations or leaders are likely to resist independent findings, and what does their resistance usually look like?
- Have previous evaluations led to backlash, funding changes, or reputational harm? Briefly describe what happened and the fallout.
- How comfortable are stakeholders with public dissemination versus internal use only for the final report?
How Will People Actually Use the Findings?
- If this report produced one concrete decision six months from now, what would that decision be—and who would act on it?
- Which audiences need digestible summaries for non-research stakeholders (select all that apply)?
- Do any stakeholders require access to raw data, technical appendices, or replications rights?
- How will you measure whether recommendations were acted on and had the intended effect (short, medium, long-term indicators)?
- Who will be responsible for communicating findings externally, and are there communication constraints or approvals we must plan for?
Deal-Breakers, Red Lines, and Non-Negotiables
- What would make you walk away from this evaluation before it begins?
- Are there legal, ethical, or independence constraints that must be honored (select all that apply)?
- Are there stakeholders who must approve the final wording or visuals before release (name/role and scope of approval)?
- Which budget or payment terms are non-negotiable for you (select all that apply)?
- If a dispute arises about interpretation or acceptance of findings, what process should we use to resolve it (mediation, steering committee, funder final say)?
Confidence & Next Steps — Are We Ready to Move?
- On a risk scale, how risky is moving forward now versus waiting to clarify more?
- What are the top three unanswered questions that would need resolving before you could commit to a scoping or contract?
- Who should be in the next meeting (name and role), and what would success look like at the end of that meeting?
- Please list contact details (name, role, email) for the people to invite and any calendar constraints we should know about.
- Realistically, when could you give us a commitment to begin scoping (select one)?
-
Current State Mapping
Document program logic, existing metrics, data sources, partner relationships, and known risks to evidence quality.
Current State
Tell Us the Story Behind Your Program
- In one sentence, how would you describe the core purpose of this program?
- What are the primary activities or services you deliver (select all that apply)?
- Who is the program intended to serve? (population, age ranges, geography, eligibility criteria)
- Briefly summarize the logic linking your activities to the outcomes you expect.
- Which core assumptions about participants or context does your theory of change rely on?
- How long has the program operated at its current model or scale?
What's Really Driving Results (or Not)?
- Which part of this program do you suspect is creating the biggest impact—and why might that assumption be incorrect?
- Which outcome measures do you currently monitor on a regular basis?
- Of the outcomes you track, which three do decision-makers treat as most persuasive?
- How confident are you that your tracked outcomes accurately reflect real change (not just administrative artifacts)?
- Can you share recent trends or numbers for 1–3 priority metrics (briefly list values, time periods, and any caveats)?
- Which outcomes have stakeholders repeatedly asked for but you currently cannot measure well?
Where the Numbers Come From
- If your metrics were misleading, where in your data sources or collection would you expect the problem to originate?
- Which data sources feed your metrics (select all that apply)?
- Who technically owns each major data source, and are there formal agreements governing access?
- How frequently are the main data sources updated?
- Do you have documented codebooks, data dictionaries, or field guides for key datasets? Describe their completeness.
- Which data gaps or persistent missing fields cause the most analysis headaches? Please provide examples.
Who's at the Table—and Who's Missing?
- Who makes final decisions about program design, data sharing, and evaluation priorities—and are those roles aligned?
- Which partners regularly contribute to implementation, data collection, or interpretation?
- Do any partners or internal stakeholders have incentives that could bias how outcomes or data are reported?
- If you answered Yes or Unsure, describe the incentives, conflicts, or pressures and who they involve.
- How involved are frontline staff and program participants in shaping metrics or interpreting findings?
- Which voices (e.g., community members, frontline staff, local leaders) do you feel are underrepresented in evidence discussions?
Data Plumbing: How Information Flows (and Leaks)
- What is the weakest point in your data flow—the place most likely to silently corrupt a finding?
- Which tools and processes do you use to collect and store data (select all that apply)?
- What quality assurance practices are in place (training, double-entry, automated checks, audits)?
- Have you experienced data loss, corruption, or prolonged access delays in the last 12 months?
- How accessible are de-identified raw data and metadata to an independent evaluator, practically speaking?
- Who is responsible for maintaining the technical systems (title/role), and how quickly do they resolve issues?
What Keeps You Up at Night About Evidence?
- What is the single greatest risk you fear will invalidate or weaken any evaluation findings?
- Which of the following evidence risks have you encountered (select all that apply)?
- Which of these risks would you prioritize resolving before an evaluator begins analysis?
- Have you previously used statistical or design strategies (e.g., matching, instrumental variables, randomized assignment) to address bias? Please describe.
- How do concerns about equity (differential effects across groups) affect which risks you worry about most?
Past Evidence: Wins, Holes, and Hard Truths
- When past evaluations fell short, what was the real root cause—even if it wasn't written in the final report?
- Have you commissioned external evaluations previously? Which study types have you used?
- Which recommendations from prior evaluations were implemented and what changed as a result?
- Were there evaluation findings that stakeholders contested or disregarded? What made them contested?
- How satisfied have you been with previous evaluators on clarity, timeliness, and independence?
- What would you have wanted previous evaluators to do differently?
Decision Timelines and Success Signals
- If leadership asks tomorrow 'Did this program work?', what answer do they expect—and what evidence would satisfy them?
- List critical decision dates or funding milestones we should align to (e.g., board meeting, grant renewal deadline).
- How quickly do you realistically need preliminary findings or interim signals?
- Which specific success signals would trigger scale-up, redesign, or termination of the program?
- How should equity shape success criteria (select all that apply)?
- Who must formally accept the evaluation findings for them to be acted upon (roles/titles)?
Practical Readiness: Capacity, Resources, and Legal
- If we tried to launch a rigorous evaluation next month, what single missing resource or approval would block us from starting?
- What internal staff time and skills can you allocate to support evaluation activities (select all that apply)?
- Are there existing data-sharing agreements, MOUs, or legal constraints we should know about?
- Is IRB or equivalent human subjects review required, and what is its status?
- What is the realistic budget range you have available for an external evaluation?
- If the budget were limited, what elements of an evaluation are non-negotiable for you (e.g., independent analysis, sample size, disaggregation)?
Next Steps — What Would Success Look Like in This Partnership?
- If you could guarantee one thing from an external evaluator, what would it be—and why hasn't that happened before?
- How involved would you like to be in design and analysis decisions?
- Which deliverables matter most to you (select top 3)?
- How should findings be communicated to different audiences (e.g., funders, frontline staff, participants)? Please describe tone, format, or channels you prefer.
- What would make you decide to move forward with an evaluator in the next 30 days?
- Are there any immediate concerns, sensitivities, or political dynamics we should address before proceeding?
-
-
Outcome Discovery
Define evaluation questions, success signals, equity priorities, and how findings will be used by funders and leaders.
Discovery Questions
Starting Point: Why This Evaluation, Right Now?
- What is the immediate trigger that made you pursue an evaluation at this moment?
- Which organizational pain or opportunity do you hope this evaluation will address first?
- Who in your organization feels the most urgency about this work—and what happened to make it urgent?
- How would you describe previous evaluations or evidence-gathering you’ve done for this program?
- If we could deliver one clear finding by the end of the study, what single question would you want answered?
Are We Asking the Right Questions (Or Just The Safe Ones)?
- What assumptions about the program’s effects would you be willing to challenge if evidence suggested otherwise?
- List the top three evaluation questions you currently think matter most for decisions.
- Which of those questions is non-negotiable for funders or regulators to have answered?
- Which stakeholders might disagree about what counts as an important question, and how have those disagreements shown up before?
- If we had to prioritize just one question to answer with high confidence, which would it be and why?
What Would 'Success' Actually Look Like (Beyond Headlines)?
- If a future board meeting ends with the right decision for this program, what evidence from this evaluation will have made that possible?
- Which concrete signals would make you say the program is working—metrics, thresholds, or qualitative changes?
- Are there absolute thresholds or minimum effects below which the program would be considered unsuccessful?
- How important is demonstrating equitable outcomes (not just average effects) to your definition of success?
- Tell us about one past success signal you used to make a major decision—what was it and how did it change actions?
Who Will Use These Findings—and Will They Act Differently?
- Which decision-makers must be convinced by this evaluation for it to have impact, and what will they do differently if convinced?
- Which audiences will receive the report (select all that apply) and which of those need different formats?
- How will timing of findings affect decisions—are there specific windows (e.g., grant renewal, budget cycle) we must hit?
- Have any past evaluations resulted in action (e.g., program change, scaling) and what enabled that follow-through?
- Who will be the internal owner(s) responsible for translating findings into next steps, and what authority do they have?
Whose Outcomes Matter Most? Centering Equity and Lived Experience
- Whose experiences or subgroups are you most worried the program may be leaving behind?
- Which dimensions of equity should we explicitly analyze (select all that apply)?
- How have program participants and community partners been involved in shaping questions so far?
- What potential harms or unintended consequences should we monitor and report candidly?
- If we found disparate impacts across groups, how would you want those findings framed and acted upon?
What Can We Measure Honestly—Data Reality Check
- Which of your existing data sources are most likely to give us credible measures of the outcomes you care about?
- What major gaps do you anticipate in the data needed to answer priority questions?
- How accessible are participant-level data (consent, sharing agreements, identifiers)?
- If a critical outcome cannot be measured directly, which proxy measures would you accept as defensible?
- How long has data quality or completeness been a concern, and how has that affected past decisions?
Design Tradeoffs: Precision vs. Practicality
- Would you prefer a narrower study with high internal validity or a broader study that captures real-world variation?
- Which tradeoff would you be most willing to accept to keep costs and timeline manageable?
- How important is randomized assignment versus quasi-experimental approaches for your stakeholders' trust?
- If preliminary findings arrive earlier but are less certain, would you want them shared proactively or held until more certainty?
- Which methodological transparencies (e.g., pre-analysis plan, open data) would increase confidence in findings?
Emotional Landscape: How Do You Feel About Potential Findings?
- If the evaluation shows the program is not producing the expected outcomes, what emotions or reactions do you anticipate from your key stakeholders?
- How prepared is leadership to hear and act on potentially uncomfortable evidence?
- Which communication approach would help reduce defensiveness if findings are mixed or negative?
- Who in your network might amplify or undermine the evaluation’s credibility, and why?
- How long have these emotional dynamics influenced decision-making around program changes?
From Findings to Action: What Will Change?
- Imagine the report is delivered and drives the right decision—what specific organizational change follows?
- What resources or commitments (funding, staff time, training) are you willing to allocate to act on recommendations?
- Who needs to sign off on major changes recommended by the evaluation, and how quickly can they do so?
- What would count as a realistic early win after implementation of recommendations?
- If we identify quick wins, how would you prefer we present them to maximize uptake?
Practical Boundaries: Timeline, Budget, and Approvals
- What is your ideal timeline from kickoff to final report, and what deadlines are immovable?
- What budget range have you earmarked for this evaluation (including IRB, data access, and dissemination)?
- Which external approvals are likely required before data collection (select all that apply)?
- Are there regulatory or funder conditions that will restrict how findings are reported or shared?
- What’s one practical obstacle (legal, logistical, political) you expect and how have you navigated similar obstacles before?
Final Check: Where Do We Start Together?
- Which of the following would you like our team to prioritize in the first 30 days?
- Who should we meet with first internally and externally to build momentum?
- What would make you feel confident about moving from scoping to a signed project next?
- Is there anything we have not asked that you think is essential for us to understand before proposing a design?
-
Solution Experience
Translate the customer’s context into a shared vision of how the proposed study design will answer priority questions and inform decisions.
Experience Meetings
- Current-State & Consequence Alignment (Pre-Work Review)
- Solution Vision Workshop (Q→Decision→Evidence Mapping)
- Methodology Walkthrough & Evidence Proof
- Decision & Mutual Validation (Go/No-Go to Solution Scope)
- Facilitator: Schedule the Solution Scope kickoff and circulate required pre-work for that session.
- Customer: Confirm which decisions are in-scope for this study and any non-negotiable constraints.
- Both: Agree on which candidate pathway(s) will be taken to the Methodology Walkthrough for technical proof.
- Quick Recap of Decisions and Evidence Needs
- Confirm the technical feasibility that the study design will answer the priority questions with required precision and equity analysis.
- Agree the specific success signals, thresholds, and acceptance criteria that will be used to inform decisions.
- Identify outstanding data access, IRB, or resource blockers and assign owners to resolve them.
- Document trade-offs and sign off on preferred analytic approach and QA safeguards.
- Evaluator Team: Produce a technical appendix including sample plan, power/precision estimates, measures, and analysis plan.
- Customer: Confirm data access permissions and name contacts or provide letters of cooperation as needed.
- Both: Assign owners and deadlines to resolve any IRB/data/ethics blockers identified.
- Facilitator: Produce a short memo tying each method element to the decision it serves and the consequence it mitigates.
- Synthesis: How the Design Proves the Future-State
- Obtain explicit agreement that the proposed design, if executed, will produce the evidence required to make the named decisions.
- Agree and record acceptance criteria, decision triggers, and reporting expectations.
- Secure go/no-go to proceed into Solution Scope with named owners, timeline, and preliminary budget alignment.
- Assign owners and deadlines for outstanding items needed before scope finalization (IRB, data access, letters).
- Customer & Evaluator: Sign or initial a short 'Validation Memo' confirming the agreed future-state, acceptance criteria, and go/no-go decision.
- Facilitator: Draft Solution Scope skeleton (study design summary, key deliverables, timeline, preliminary budget) for the next stage.
- Assigned Owner(s): Begin IRB/data access steps and provide status updates by agreed deadlines.
- Opening & Objectives
- Confirm a single, clear current-state sentence agreed by all parties.
- Surface and quantify the primary consequence(s) of the current state that create urgency.
- Agree a concise future-state sentence that the study must demonstrate.
- Document the decision-makers, timelines, and immediate data needs to proceed.
- Customer: Provide final one-sentence current-state, consequence, and future-state statements in writing.
- Facilitator: Compile stakeholder list, available metrics, and any quantitative evidence cited in the consequence discussion.
- Customer & Facilitator: Agree on any missing data or clarifying interviews required before the Solution Vision Workshop.
- Recap: Current State, Consequence, Future-State
- Agree which evaluation questions are highest priority because they directly inform named decisions.
- Select 1–2 candidate study pathways that, if successful, will demonstrate the future-state.
- Define concrete decision triggers (what evidence will prompt what decision).
- Identify constraints and trade-offs to be resolved in the Methodology Walkthrough.
- Facilitator: Produce a Q→Decision→Evidence visual mapping and share with participants.
- One-sentence Current State Presentation
- Map Priority Evaluation Questions to Decisions
- Design Components: Sample & Comparison Strategy
- Review Success Signals & Acceptance Criteria
- Measures, Data Sources & Access Feasibility
- Timeline, Milestones & Preliminary Budget Alignment
- Explicit Consequence Discussion
- Sketch Candidate Study Pathways (Proof Hypotheses)
- Risk Acknowledgement & Contingency Triggers
- Stakeholders, Decisions & Timelines
- Evidence Scenarios & Decision Triggers
- Analysis Plan & Success Signals
- Trade-offs & Constraints Check
- Draft Future-State Statement
- Explicit Decision & Next Steps
- Independence, Ethics & Quality Safeguards
- Risk, Trade-offs & Contingency Plan
- Validation & Next Steps
- Validation Commitments
- Validation Checkpoint: Does this prove the Future-State?
-
Solution Scope
Define study design, sample and comparison strategy, data sources, deliverables, timeline, and roles.
Scope Configuration
- Deploy baseline and endline outcome surveys
- Implement administrative data linkage and cleaning
- Conduct in-depth participant interviews (audio/video)
- Facilitate stakeholder focus groups and transcription
- Transcribe interviews and produce coded transcripts
- Perform quantitative outcome analysis and statistical modeling
- Run propensity score matching and comparison analyses
- Conduct subgroup equity disaggregation and reporting
- Deploy observational fieldwork and fidelity coding
- Create interactive dashboards and data visualizations
- Prepare IRB submission and human subjects materials
- Draft concise findings brief and executive summary
- Provide data de-identification and secure sharing package
- Train staff on standardized data collection protocols
Scope Questions
Deploy baseline and endline outcome surveys
- Do you intend to collect baseline, endline, or both?
- What is the expected sample size per timepoint (approximate)?
- Which modes of administration do you prefer or require?
- Do you require use of validated/standardized instruments (e.g., PROMs, standardized scales)?
- If yes or partially, list the instruments or measurement domains required (or write 'N/A')
- What target response or completion rate do you consider acceptable for the study to be in-scope?
Implement administrative data linkage and cleaning
- Which administrative data sources do you plan to link (e.g., education, healthcare, benefits)?
- Are unique identifiers present to permit deterministic linkage (e.g., SSN, person ID)?
- What is the expected date range and frequency of administrative records needed?
- Do you already have data-sharing agreements or data owner approvals in place?
- Describe any known data quality issues (e.g., missing fields, inconsistent coding) or write 'Unknown'
- What deliverable do you expect from this module (cleaned merged dataset, codebook, linkage QA report, other)?
Conduct in-depth participant interviews (audio/video)
- What is the primary purpose of the interviews (theory-building, process understanding, outcome mechanisms)?
- How many interviews do you expect (approx.) and with which participant types?
- Which modalities are acceptable for interviews (in-person audio/video, phone, remote video)?
- Are audio/video recordings permitted by participants and data owners?
- Do interviews require translation or multilingual interviewers?
- What outputs do you expect (raw recordings, edited clips, transcripts, thematic memos)?
Facilitate stakeholder focus groups and transcription
- What stakeholder groups should be included in focus groups (e.g., program staff, beneficiaries, partners)?
- Preferred group size and number of sessions per stakeholder group?
- Do you require synchronous facilitation, asynchronous formats, or both?
- Are there accessibility or accommodation needs we should plan for (language, childcare, scheduling)?
- Should focus groups be recorded and transcribed, and are recordings acceptable to stakeholders?
- What facilitation outputs do you want (facilitator notes, verbatim transcripts, thematic synthesis)?
Transcribe interviews and produce coded transcripts
- Do you require verbatim transcription, intelligent verbatim, or time-coded transcripts?
- Which languages will require transcription and/or translation?
- Do you want qualitative coding applied to transcripts, and at what level (descriptive, thematic, codebook-driven)?
- What turnaround time is required for transcription batches?
- Are there confidentiality or redaction requirements before sharing transcripts?
- What final deliverables do you expect (coded transcripts, codebook, summary memos)?
Perform quantitative outcome analysis and statistical modeling
- What primary outcomes and metrics should the analysis focus on?
- What level of causal inference is required (descriptive, adjusted associations, causal estimation)?
- Are there specific covariates, controls, or risk adjustment variables you require?
- What software or reproducibility standards do you require for deliverables (R, Stata, Python, annotated code)?
- Do you require pre-specified analysis plans or registered protocols before analysis begins?
- What form of output do you expect (statistical tables, interpretation memos, replication code)?
Run propensity score matching and comparison analyses
- Is there a non-random comparison group available or do we need to construct one?
- What balance or overlap thresholds would you consider acceptable after matching?
- Which covariates are critical for matching and adjustment (list or write 'TBD')
- Do you prefer propensity score methods (matching/weighting) or alternative approaches (synthetic controls, regression discontinuity)?
- Are there known selection biases or eligibility rules we should incorporate?
- What outputs and diagnostics do you require (balance tables, sensitivity analyses, code)?
Conduct subgroup equity disaggregation and reporting
- Which subgroup dimensions are required (race/ethnicity, gender, age, geography, income)?
- Do subgroup analyses require statistical tests for interaction or effect heterogeneity?
- Are there equity or priority populations that must be oversampled or prioritized?
- What minimum cell size or privacy threshold should we enforce before reporting subgroup estimates?
- Should we include qualitative context to explain subgroup differences (e.g., targeted interviews)?
- What format do you want disaggregated reporting in (tables, stratified charts, narrative summaries)?
Deploy observational fieldwork and fidelity coding
- What behaviors/interactions or fidelity elements should observers code?
- Do you need trained external observers or can program staff conduct observations?
- What observation schedule is required (frequency, number of visits per site)?
- Do observations require video recording, live coding, or post-hoc coding from notes?
- What inter-rater reliability (IRR) standards should be met for coded fidelity measures?
- What deliverables do you expect (fidelity scorecards, site-level feedback, coding manuals)?
Create interactive dashboards and data visualizations
- What audiences will use the dashboard (program staff, funders, public stakeholders)?
- Which metrics/KPIs should be prioritized in visuals?
- Do you have a preferred dashboard platform (Tableau, Power BI, Looker, custom web)?
- Do dashboards require role-based access or data-level permissions?
- What update frequency is needed for the dashboard (real-time, weekly, monthly)?
- Do you require interactive features (filters, drilldowns, exportable tables)?
-
Mutual Commit
Agree on budget, payment milestones, IRB and data agreements, independence safeguards, and acceptance criteria.
Agreement Modules
- Statement of Work (SOW)
- Master Services Agreement (MSA)
- Budget & Payment Schedule
- Data Use & Access Agreement (DUA)
- IRB & Human Subjects Agreement
- Independence & Conflict of Interest Charter
- Confidentiality & Non-Disclosure Agreement (NDA)
- Acceptance Criteria & Sign-off Procedure
- Change Order & Scope Amendment Process
- Data Security & Privacy Addendum
- Partner & Subcontractor Agreement
- Publication, Attribution & Embargo Terms
- Insurance, Liability & Indemnity Terms
- Termination & Suspension Terms
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
Pre-Deployment Readiness
Confirm IRB approvals, data access, partner permissions, staffing, and sampling readiness before fieldwork.
Readiness Questions
Starting With Confidence: A Quick Snapshot
- In one sentence, what would make you feel confident we can start fieldwork next week?
- Which of these milestones is already fully complete for this project?
- Who is the single person on your team we should contact first if something threatens the start date?
- Realistically, how soon are you hoping fieldwork begins?
- What keeps you up at night about launching this study?
What Could Stop This Study From Starting?
- If the study failed to launch on the planned date, what would likely be the single biggest reason?
- For the risk you selected, how long has this been an unresolved concern?
- Who would be the decision-maker to resolve that issue, and what would convince them to approve moving forward?
- What fallback or mitigation have you already considered or put in place for this risk?
- On a scale between 'we can absorb a short delay' and 'a delay kills the study,' where are you?
Who Must Say Yes — And What Would Shake Them?
- Who are the external or internal stakeholders whose approval is required before fieldwork begins?
- For each stakeholder you selected, what specific evidence or assurance do they expect before granting permission?
- Which stakeholder is most likely to request changes that would materially alter the study design?
- Describe a recent example (even from another project) where a stakeholder request created a major shift — what happened and how was it resolved?
- How would you like us to surface and package materials to get a quicker 'yes' from these stakeholders?
Is Your Data Truly Ready to Tell the Story?
- If we attempted preliminary analyses tomorrow, which data sources would we actually be able to access?
- For each accessible source, what is the current access level?
- Are there known data quality issues (missing fields, inconsistent IDs, time lags) that would affect primary outcomes?
- How long would it take your team or data partners to provide a cleaned, analysis-ready extract if requested?
- Please list any unique data linking or de-identification requirements we should know about.
Permissions & Paperwork: Where Do Bottlenecks Live?
- Which legal or administrative approvals remain outstanding?
- For each outstanding item, who is responsible for advancing it and what is their planned completion date?
- Have any partners signaled they will require contract amendments or additional clauses before they permit data access?
- What IRB category do you expect this study to fall under?
- If the IRB issues conditional approval, what conditions would be unacceptable to you?
Are Your Partners Ready to Be Partners?
- Which partner organizations are essential for fieldwork operations (e.g., recruitment, access, local staff)?
- How would partners describe their current bandwidth for supporting this study?
- Have you documented partners’ responsibilities and commitments in writing?
- Tell us about any previous collaborations with these partners that succeeded or failed — what patterns should we watch for?
- What incentives or reassurances would increase partner engagement and reliability?
Can We Actually Staff This With Confidence?
- Which core roles are already staffed for deployment (e.g., field lead, data manager, survey enumerators, qualitative interviewers)?
- For roles not yet staffed, what is the main hiring or contracting constraint?
- How long does onboarding typically take for field staff in your context (training, background checks, IRB certifications)?
- What training or competency checks are non-negotiable before staff begin interacting with participants?
- If a key staff person becomes unavailable after launch, what's the contingency for immediate replacement?
Sampling & Field Readiness — Is the Frame Real?
- Do you have an actionable sampling frame (list of participants/units) that we can use to draw our sample?
- What percentage of the frame do you estimate is contactable and valid today?
- Are there known subgroups or strata we must oversample to address equity priorities?
- What approvals (consent, guardian permission, agency sign-off) are required to reach or recruit from the frame?
- If sampling must be adjusted in the field (low response, unreachable clusters), which trade-offs are acceptable to you (timeline extension, reduced power, additional waves)?
If Something Breaks — What’s the Real Plan?
- When deployment hits a significant obstacle (e.g., lost access to a data source), who has final authority to approve the fix or change?
- What decision-making timeline is acceptable for critical fixes (hours, days, weeks)?
- Describe one contingency you’d accept that still preserves the study’s core questions.
- How do you prefer we escalate problems to you (email, phone, scheduled huddle, emergency contact)?
- What would feel like a reasonable compensation or remedy to partners/participants if fieldwork requires extra burden due to adjustments?
Commitments, Timelines, and Final Sign-offs
- What is the non-negotiable earliest date we must finish deployment by (e.g., for funding, policy cycles)?
- Which deliverables or milestones must be completed before payment or fund release?
- Who will provide final sign-off that fieldwork is acceptable to proceed (name and role)?
- Are there pre-agreed acceptance criteria for fieldwork quality (response rates, data completeness thresholds, protocol adherence)?
- What final evidence or artifacts would make you comfortable to greenlight the first wave of fieldwork?
Agreeing on Small Next Steps (Practical, Concrete)
- Given everything above, what are the top three actions you want our team to take in the next 7 days?
- Which of those actions should we treat as urgent and why?
- Who on your side will be our touchpoint for these 7‑day actions (name, role, best contact)?
- How would you prefer we report progress on these items (daily checklist, brief status update, shared dashboard)?
- Is there anything else — a concern, context, or boundary — we haven’t asked about that would change how we approach readiness?
-
Deployment Enablement
Schedule and execute data collection and fieldwork with clear owners, milestones, and quality checks.
-
Validation Checklist
Verify data quality, interim analyses, and stakeholder review points prior to final reporting.
Validation Questions
Starting Bright: Quick introductions and what's on the table
- Briefly describe who you are, your role, and the program or grant that would be evaluated.
- Which of these best describes the primary customer group requesting this evaluation?
- Who within your organization is the final decision-owner for commissioning and accepting an evaluation?
- What triggered the idea for an external evaluation now?
- Roughly when would findings need to exist to influence that trigger (month/quarter and year)?
- Who else should be in the room for discovery conversations (names or roles)?
Are we asking the right question — or just proving what we already believe?
- What is the central question you expect this evaluation to answer—and why might that be the wrong question?
- Which outcome(s) do you currently treat as the most important?
- How were those outcomes chosen—board mandate, funder priority, historical practice, or something else?
- What would surprise you in the results—i.e., what finding would make you rethink how the program works?
- How confident are you that existing measures truly capture the change you care about?
Where the evidence is thin — what keeps you up at night about data?
- What single piece of information do you wish you had right now to make a better decision about this program?
- Which of these data sources are available or potentially available for analysis?
- Who owns or controls access to the most important data—and how easy would it be to request access?
- Have you previously commissioned evaluations or analyses for this program? If so, what were the key findings and limitations?
- Thinking about data quality, what specific issues do you anticipate (missing data, inconsistent definitions, small samples, access delays, etc.)?
Who really holds the keys — influence, approval, and credibility
- If the evaluation found that the program needed major changes, who could block implementation or reinterpret the results?
- Which stakeholders should explicitly approve study design, interim findings, and final acceptance?
- How do different stakeholders define 'good' evidence—rigorous causal proof, credible descriptive trends, or something else?
- What political or reputational pressures might shape how findings are received or shared?
- Are there equity priorities or communities we must center when designing questions and interpreting results? Please list and explain.
Imagine a decision that actually changes things — who benefits and how?
- Describe a concrete decision you want this evaluation to enable (e.g., renew funding, scale program, pivot model, inform policy), and why it matters.
- When that decision is made, what specific evidence threshold would make leaders feel comfortable (effect size, qualitative consensus, stakeholder endorsement, cost threshold)?
- Who will use the report and how—internal strategy, funder decisions, public reporting, or advocacy?
- How would different outcomes (positive, null, negative) ideally be communicated to funders, staff, and communities?
- What deliverables would be most useful (technical report, one-page brief, slide deck, data appendix, public summary)?
Design reality check — tradeoffs we're willing to live with
- Which tradeoff would you prioritize if constrained: speed of results, methodological rigor, or breadth of coverage?
- What sample sizes or subgroup analyses are non-negotiable for you (specific populations, geographies, or program cohorts)?
- Would you consider experimental or quasi-experimental designs (randomization, regression discontinuity, matched comparison)?
- Are there legal, ethical, or IRB constraints we must plan for (consent, vulnerable populations, data-sharing restrictions)?
- What budget range is realistic for this scope (ballpark), and are there milestones/payments tied to specific approvals or deliveries?
Risk radar — what's most likely to derail us and how would it feel?
- Name the single most realistic risk that would make this evaluation unusable or irrelevant.
- How long has that risk been present, and what attempts have been made to mitigate it?
- Which operational constraints would you be willing to invest in to reduce that risk (additional data collection, partner coordination, incentives, longer timeline)?
- If we find major data integrity problems mid-study, what decision-rule should we use about whether to pause, redesign, or stop?
- Who on your team should be responsible for rapid escalation when issues arise (name or role)?
What winning looks like — beyond a report
- When this evaluation is done, what concrete change would make you say it was a clear success?
- Which success signals matter most (policy change, funding decision, program redesign, stakeholder buy-in, improved equity outcomes)?
- How should we measure follow-through on recommendations—who owns tracking and what cadence is realistic?
- What level of transparency do you want around interim findings during fieldwork (regular check-ins, embargoed memos, public pre-briefs)?
- Who needs to be convinced of the findings for action to follow—list roles and what would persuade each of them.
Small, fast commitments that show forward motion
- What is the smallest, least controversial commitment you could make today to get this work started?
- Who will sign off on a mutual scope and budget (name or role), and what timeline do they need for review?
- Which documents or agreements must be in place before fieldwork (IRB, data sharing agreement, partner MOUs)?
- Please provide the contact information (name, role, email) for the person who manages legal/data agreements.
- Realistically, when could you commit to a scoping call to finalize design options?
-
-
Success
Review findings against success signals, surface actionable recommendations, and track follow-ups or enhancements.
Success Reviews
- Findings Alignment Workshop
- Recommendations Co-Creation Session
- Mutual Acceptance & Commit
- Implementation Planning & Monitoring Kickoff
- Stakeholder Reporting & Accessibility Review
Issues & Enhancements
- Document risks and contingency plans to manage foreseeable implementation challenges.
- Decision Context & Recap
- Obtain explicit acceptance decisions and sign-offs for top recommendations.
- Finalize budgets, payment milestones, and any conditional funding triggers.
- Establish governance, owners, and independence safeguards for implementation and reporting.
- Agree on the internal and external communication plan for the decisions.
- Produce a signed decision package summarizing accepted recommendations, budgets, owners, and acceptance criteria.
- Set up the implementation and monitoring cadence (meeting schedule, reporting deadlines).
- Draft public and internal communication materials for approval.
- Update contracts, payment schedules, and data-sharing agreements as required.
- Confirm Accepted Recommendations & Timelines
- Operationalize accepted recommendations with an actionable timeline and named owners.
- Define and build the monitoring dashboard and reporting cadence tied to acceptance criteria.
- Agree interim analysis plans and quality assurance checks to validate early signals.
- Welcome & Objectives
- Build and share the monitoring dashboard prototype with data definitions and owners.
- Schedule interim analyses and assign analysts/data stewards with deadlines.
- Publish the 90-day implementation plan with milestones and named owners.
- Register identified risks and assigned mitigations in a shared risk register.
- Audience Mapping & Objectives
- Approve clear, audience-specific reporting materials that convey findings and recommended actions.
- Ensure visuals and plain-language summaries accurately reflect evidence and consequences.
- Confirm transparency language to protect evaluator independence and methodological clarity.
- Finalize dissemination timetable and responsibilities for sharing results.
- Finalize and export executive one-pager, slide deck, and detailed report appendices.
- Produce translated/accessible versions and schedule targeted briefings for priority stakeholders.
- Obtain final approvals and execute the agreed dissemination plan.
- Archive methodological appendices and datasets per agreed data-sharing protocols and privacy safeguards.
- Achieve stakeholder alignment on a one-sentence current state based on the evidence.
- Agree which success signals are satisfied, partially satisfied, or unmet and why.
- Surface the concrete consequences of the findings to create urgency for action.
- Identify any critical evidence gaps or quality issues that block confident recommendations.
- Finalize and circulate the agreed one-sentence current state.
- Produce a short evidence memo mapping each finding to success signals with confidence ratings.
- Assign owners and timelines for any rapid follow-up analyses or data checks.
- Schedule the Recommendations Co-Creation Session after follow-ups complete.
- Recap of Validated Findings
- Produce a prioritized list of actionable recommendations explicitly linked to validated findings.
- Define a clear one-sentence future state that recommendations aim to achieve.
- Agree acceptance criteria and metrics for each top recommendation.
- Surface likely resource needs and equity impacts to inform mutual commitment.
- Document prioritized recommendations with supporting evidence and measurable acceptance criteria.
- Develop resource and timeline estimates for top recommendations.
- Conduct a brief equity impact check and note mitigation steps for each recommendation.
- Prepare materials for the Mutual Acceptance & Commit meeting (decision package).
- Define Future State (One Sentence)
- One-sentence Current State
- Executive Summary Draft Review
- Monitoring Metrics & Dashboard Design
- Review Acceptance Criteria & Metrics
- Budget, Payment Milestones & Funding Triggers
- Translate Problems into Candidate Recommendations
- Visuals & Data Translation
- Consequence Briefing
- Interim Analyses & Quality Checks
- Roles, Governance & Independence Safeguards
- Findings vs Success Signals
- Roles, Data Flows & Permissions
- Prioritize by Impact, Feasibility & Equity
- Transparency & Independence Statements