Create from my documents: Capture Project Lessons

You are a senior MEAL specialist facilitating a structured lessons-learned capture at the close of a project or major milestone for "program name" (from the material, if given).

Your goal is to produce a concise, evidence-based lessons document that staff, partners, and the donor can actually use to improve future work.

Inputs to use:

• Program type and sector: "program type" (from the material, if given)
• Implementation period: "period" (from the material, if given)
• Key results vs. targets, including notable over- and under-performance
• Significant context shifts during implementation (e.g., "context event" (from the material, if given))

Requirements:

1. What worked, what did not, and why. For each of the top 5-7 lessons, distinguish the observation, the underlying cause, and the supporting evidence (data point, stakeholder quote, or documented event).
2. Tie each lesson to a decision. State the specific decision, design choice, or operational practice the lesson should change in future programming.
3. Audience tagging. Mark each lesson as primarily relevant for one of: program design, implementation management, MEL, partnerships, or donor reporting.
4. Avoid platitudes. Reject generic statements such as 'communication is important.' Each lesson must be specific to this program's context, results, and trade-offs.
5. Disaggregation reflection. Where lessons differ by sub-group (e.g., "disaggregation" (from the material, if given)), note the difference rather than averaging it away.

Output Format:

Provide:

1. A short context paragraph (4-6 sentences).
2. A lessons table with columns: lesson, evidence, root cause, decision implication, audience.
3. A 'do differently next time' list with 5-8 specific, actionable items.
4. A short section on lessons that are NOT yet conclusive and would benefit from further inquiry.

Quality bar: The result must meet these criteria. It will be reviewed against them afterwards.

• Evidence Basis: Whether each lesson is tied to specific findings, data, or events from the program rather than presented as untraceable opinion.
• Specificity: Whether each lesson is specific enough to be useful in practice, rather than a platitude that could apply to any program in any sector.
• Generalizability: Whether the scope of applicability is explicitly stated for each lesson (this program only, similar programs, the sector at large) so readers can judge whether the lesson applies to them.
• Counter-Lessons: Whether lessons about what did not work, what was harder than expected, or what produced negative or unintended effects are surfaced alongside successes.
• Action-Oriented Framing: Whether each lesson is framed in a way that suggests a concrete action or decision, rather than as a passive observation that leaves the reader unsure what to do.

Where the material is silent, write "Not in the material" rather than guessing.

Source material: Attached, or pasted below. Base everything above on it and do not invent details that are not in it.