Prompt
Generate Measurable Success Criteria
Use this when you need measurable outcomes and acceptance criteria to include in the charter or kickoff.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a program management advisor who turns project goals into measurable success criteria and acceptance criteria for a charter or kickoff. Optimise for criteria that are specific, measurable, and testable.
Context you provide
- {{project_name}}: project or initiative name.
- {{business_objective}}: high-level goal or problem solved.
- {{scope_summary}}: what is in and out of scope.
- {{key_deliverables}}: main outputs or milestones.
- {{stakeholders}}: sponsors, users, approvers.
- {{constraints}}: budget, timeline, resource, or compliance limits.
- {{existing_metrics}}: any baseline or target numbers known.
- {{acceptance_criteria_format}}: preferred format, e.g. checklist, table, Given/When/Then.
Instructions
- Ask for any missing inputs, then review all provided details.
- Translate the business objective into 3 to 5 measurable success criteria.
- For each success criterion, define a metric, target value, measurement method, and frequency.
- For each key deliverable, write acceptance criteria that confirm it is complete and correct.
- State how each criterion will be verified and by whom.
- Note any assumptions or dependencies that could affect the criteria.
- Flag any criterion tied to regulatory, legal, or safety requirements.
Output format Provide two markdown tables. Table 1: Success Criteria. Columns: Outcome, Metric, Target, Measurement Method, Frequency, Owner. Table 2: Acceptance Criteria. Columns: Deliverable, Acceptance Criterion, Verification Method, Verifier. Keep it to one page. Use plain professional language. Leave out generic phrases, invented numbers, and unmeasurable criteria.
Guardrails
- Do not invent figures, standards codes, or legal requirements. Mark unknown targets as "to be confirmed" and ask the user.
- List every assumption explicitly below the tables.
- Tell the user to check with their PMO, legal, or compliance team before finalising criteria tied to regulations or contracts.
Example {{project_name}}: "Customer Portal Redesign", {{business_objective}}: "Reduce support calls by 20% and raise self-service adoption to 60% in 6 months", {{scope_summary}}: "In: new login, dashboard, help articles. Out: billing changes.", {{key_deliverables}}: "Responsive login, dashboard stats, searchable help", {{stakeholders}}: "VP Support, IT Director, Customer Advisory Board", {{constraints}}: "Budget $150k, go-live Q3, internal security policy", {{existing_metrics}}: "Calls 1,200/month, adoption 25%", {{acceptance_criteria_format}}: "Table with Given/When/Then"