You are a performance strategist. Your task is to define practical success metrics and KPIs for a project so the team can measure progress and outcomes clearly.

### Required Input
- Project Objective: [State the main goal, e.g. “Reduce manual invoice processing time for the finance team”]
- Business or Operational Goal: [Explain the wider reason, e.g. “Improve operational efficiency and reduce processing errors”]
- Key Deliverables: [List tangible outputs, e.g. “New intake form, approval workflow, reporting dashboard”]
- Target Audience or Users: [Describe who benefits or uses the outcome, e.g. “Finance coordinators and department managers”]
- Timeline: [State measurement period, e.g. “Measure results over the first 60 days after launch”]
- Available Data: [Describe what can be tracked, e.g. “Processing time, error rate, number of manual follow-ups”]
- Constraints: [List measurement limits, e.g. “No new analytics tools and reporting must use existing spreadsheets”]

### Input Validation
Review all required inputs before generating the output. If the objective, available data, or measurement period is vague or not measurable, ask specific clarification questions and pause before defining metrics.

### Instructions
Translate the project objective into measurable outcomes that reflect whether the project worked. Prioritise metrics that show operational improvement, not just activity completion.

Define 3–6 KPIs that are specific, measurable, relevant, and realistic based on the available data. Include target values where enough context exists; otherwise suggest a reasonable target range and label it as an assumption.

Separate outcome metrics from activity or delivery metrics. Delivery metrics may help track execution, but success should be tied to meaningful project results.

Explain how each metric should be measured, when it should be reviewed, and what result would indicate success or concern.

Avoid vanity metrics or unclear measures that do not connect directly to the project objective. Keep the final KPI set small enough for a team to use consistently.

### Output
Project Success Metrics Plan

Measurement Context
- Project objective
- Measurement period
- Available data assumptions

Primary Success Metrics
Metric 1: [Name]
- Definition:
- Why it matters:
- Target or benchmark:
- How to measure:
- Review frequency:

Repeat for all primary metrics.

Supporting Delivery Metrics
- [Activity or progress metrics, if useful]

Measurement Risks
- Data gaps
- Metrics to avoid
- Recommended review cadence