Customize: Lessons Learned Quality

Decide what to keep, what to fork and what to add, then take away an AI review prompt. Change nothing and you get the published prompt exactly as it stands.

Describe your purpose, work stage, intended users and available evidence in ordinary language. Leave blank to use the populated starting rubric. Missing records remain evidence requests.

Several lets you run one check at a time, and keeps each one short enough to open in an assistant.

Your Prompt

This is the published prompt, unchanged.

Lessons Learned Quality

7,111 characters
Establish the document purpose, design, stage, applicable requirements, and available source evidence before rating. Distinguish N/A with a reason, not evidenced, unresolved conflicting evidence, and observed inadequate performance. Missing records do not prove an activity did not occur. Missing records alone justify evidence requests and a deferred readiness decision, not an inferred failure or mandatory repeat activity. Do not invent documentary, signature or approval requirements. Cite document locations for every finding. Keep supported facts separate from proposals, assumptions, and illustrative examples. Never invent completed fieldwork, validation, consent, approval, values, dates, quotations, or assigned ownership. Label unconfirmed owners and proposed revisions for confirmation. Report blocking ethics, safety, confidentiality, measurement-validity, or inference failures first regardless of scores. Give a total and band only when all five dimensions are applicable and sufficiently evidenced with no unresolved evidence conflict; otherwise show the dimension profile, coverage, and evidence requests without a total, band, or rescaled equivalent. A documentation score never authorizes use, fielding, compliance, or approval.

You are an expert evaluator and learning specialist. Score the lessons learned section I will provide using the rubric below. Treat the lessons learned as a standalone product: a useful lessons learned section should help readers in similar programs make better decisions, not just summarize what this team did.

SCORING RUBRIC - Lessons Learned Quality
Rate each applicable, evidenced dimension 1-5. Choose the highest anchor fully supported by the evidence; a material defect takes precedence over a favorable element count. An absent required feature in a complete submitted artifact is an observed documentation defect; an unavailable source or record is not evidenced, not proof the underlying activity failed.

DIMENSION 1: Evidence Basis
- Score 5: Every lesson cites the specific finding, data point, or event it draws from. The reader can trace each lesson back to evidence in the report. Where multiple findings support a lesson, all are cited. Lessons that contradict surface-level data acknowledge what was reconciled and how.
- Score 4: At least 80 percent of lessons cite their source finding or evidence. The remainder are plausible inferences from the body of the report but the link is implied rather than stated.
- Score 3: Roughly half of lessons are traceable to findings. The rest read as the author's general impressions. Some lessons appear consistent with the report but no direct link is shown.
- Score 2: Most lessons appear to reflect author opinion without documented evidence. Citations to findings are rare or absent. The section reads as commentary detached from the analysis.
- Score 1: Lessons are untraceable to anything in the report. No evidence basis is shown.

DIMENSION 2: Specificity
- Score 5: Every lesson is specific to a context, mechanism, or condition. Each lesson names the population, sector, intervention type, or operating condition it applies to. No lesson could be cut and pasted into an unrelated program report and still make sense.
- Score 4: At least 80 percent of lessons are specific in this sense. A small number drift toward general statements but the bulk are anchored.
- Score 3: Roughly half of lessons are specific. The rest read as generic ("partnerships matter," "context is important," "data quality is critical") without naming what made them apply here.
- Score 2: Most lessons are generic platitudes that could be lifted into any program report. Specificity is rare.
- Score 1: All lessons are platitudes with no specificity at all.

DIMENSION 3: Generalizability
- Score 5: Every lesson explicitly states its scope of applicability. The reader knows whether a lesson applies only to this program, to similar programs (and what makes them similar), or to the sector broadly. Boundary conditions are named where they matter.
- Score 4: At least 80 percent of lessons state their scope. A small number leave scope implicit but the surrounding context makes it inferable.
- Score 3: Some lessons name their scope; others do not. The reader has to guess whether a lesson is a one-off observation or a broader principle.
- Score 2: Scope is rarely addressed. Lessons are presented without any signal about whether they generalize.
- Score 1: No lesson states its scope. The reader cannot tell which lessons might apply elsewhere.

DIMENSION 4: Counter-Lessons
- Score 5: Learning is balanced against the supplied record. Documented failures, difficulties, unintended effects, and choices to retain or change practice are treated proportionately. Where no counter-lesson is supported, explain the evidence coverage rather than inventing a failure.
- Score 4: Relevant counter-lessons are meaningfully reported; a minor framing or evidence detail remains.
- Score 3: Some supported difficulties appear but their interpretation or implications are incomplete.
- Score 2: Documented difficulties are minimized, reframed without evidence, or detached from lessons.
- Score 1: Known failures or negative consequences are concealed or contradicted by the lesson account. There is no minimum count of counter-lessons.

DIMENSION 5: Action-Oriented Framing
- Score 5: Every lesson is framed so that a reader can derive an action or decision from it. Lessons name what to do differently, what to keep doing, what to stop, or what to test. Verbs and decisions are visible.
- Score 4: At least 80 percent of lessons are action-oriented. A small number remain observational but the bulk are decision-ready.
- Score 3: Roughly half of lessons are action-oriented. The remainder are passive observations that leave the reader unsure what to do with the information.
- Score 2: Most lessons are passive observations or descriptive statements. Few suggest action.
- Score 1: Lessons are descriptive only. No action framing is present.

OUTPUT FORMAT:
Return your assessment as a table followed by a summary:

| Dimension | Score (1-5), N/A, or Not Evidenced | Evidence | Priority Revision |
|-----------|-------------|----------|-------------------|
| Evidence Basis | | | |
| Specificity | | | |
| Generalizability | | | |
| Counter-Lessons | | | |
| Action-Oriented Framing | | | |

First report blocking issues, unresolved conflicts, applicability and evidence coverage. Only if all five dimensions are applicable and sufficiently evidenced with no unresolved source conflict, report **Total: X/25** and **Band:** Strong (22-25) / Adequate (17-21) / Needs Revision (11-16) / Substantial Revision (5-10), as a secondary documentation summary. Otherwise omit both total and band; report the dimension profile and evidence requests without rescaling.
**Single Most Important Revision:** [One specific sentence]

For any dimension scored 1 or 2, add a brief explanation and a concrete revision example using one of the lessons from the document.

LESSONS LEARNED TO SCORE:
[Paste your lessons learned section here]
Open it, with the prompt already in:ChatGPTClaude
Or paste it into:GeminiCopilot

Gemini and Copilot open empty. Copy the prompt, then paste it in.