Lesson Content

The without-criteria review problem.

Most informal review processes are impressionistic: the reviewer reads something, forms a general impression, and provides feedback based on what stands out. This approach consistently misses things that do not stand out – gaps, inconsistencies, missing sections – because it does not systematically compare the work against what it should be.

Criteria-first review defines the standard before the review begins, then evaluates systematically against that standard. This is more exhausting to set up once – and dramatically more reliable in practice.

The criteria-first review process.

Step 1 – Define the criteria before reviewing.

"I am about to review [document type]. Before I share the document, help me define the criteria it should meet: what does a high-quality [document type] for [audience] include? Structure these as 8-12 specific criteria I can check one by one."

Gemini generates a set of review criteria. Review them yourself and add any that are missing for your specific context – then use this criteria set for the review.

Step 2 – Conduct the criteria-based review.

"Using these criteria [paste list], review the following document: [paste document]. For each criterion, tell me: does this document meet it fully, partially, or not at all? For any criterion not fully met, identify specifically what is missing or insufficient and what the document should include instead."

This produces a structured gap analysis rather than an impressionistic review – every criterion is evaluated, not just the ones that happened to catch the reviewer's eye.

Step 3 – Prioritize and address gaps.

Not all gaps are equal. After the criteria review:

"Of the criteria this document does not fully meet, which are most critical to fix before submission – and which are lower priority? Rank the gaps by their impact on the document's effectiveness."

This prioritization focuses revision effort on what matters most.

Rubric-based review for standardized deliverables.

For deliverable types you produce repeatedly – project status reports, budget proposals, performance reviews, grant applications – build a rubric once and reuse it:

"Create a reusable review rubric for [deliverable type] in [your context]. The rubric should include: the required sections, the criteria for excellence in each section, and the most common errors or omissions for this type of document. Format as a checklist I can apply repeatedly."

Save this rubric and use it every time you produce or review this deliverable type. The one-time investment builds a permanent quality standard.