Human ResourcesPerformance & Development

AI Prompts for Performance Objectives and Goal Setting

Performance objectives fail in familiar ways: they are activities dressed as outcomes, they are copied from last year, they are not connected to anything the team is trying to achieve, or they are impossible to measure without a spreadsheet nobody keeps. Good objectives cascade from team goals, describe an outcome and the evidence of it, are few, and are set at a difficulty the person and manager both accept.

These prompts cascade goals into objectives, handle roles where outcomes resist quantification, and review a set for alignment and fairness. They produce drafts for a conversation between manager and employee; objectives set without that conversation are targets, not agreements.

Before you use these

Have these ready to replace the highlighted [variables]:

Team or department goals for the period
The role's responsibilities and the person's current scope
Last period's objectives and how they went
Any organizational rules (number of objectives, format, weighting)

The prompts

1. Cascade team goals into individual objectives
2. Write objectives for hard-to-quantify roles
3. Review a set of objectives for alignment and fairness

1. Cascade team goals into individual objectives

Best forObjectives that trace to what the team must achieve, stated as outcomes with evidence.

Inputs needed

Team goals
Role and scope
Last period's results

How to use itGive the team goals and the role. The model drafts three to five objectives with the outcome, the measure, the evidence and the link to the team goal — as a draft for the objective-setting conversation.

Expected outputDraft objectives with outcome, measure, evidence, team-goal link, difficulty note, and the questions for the conversation.

Act as a manager drafting performance objectives for [role, person's scope] for [period], for discussion with the employee.

Team goals: [list with measures]
Role and scope: [responsibilities, current projects, level]
Last period: [objectives and outcomes; what was learned]
Rules: [number of objectives, format, weighting]

1. Draft 3–5 objectives. Each: the outcome (what will be different), the measure or evidence (how we will know — a number, an artifact, a decision made), the link to the team goal, and the timeframe.
2. Difficulty: for each, whether it is a stretch, a core expectation or maintenance — and the balance across the set.
3. Dependencies: what the person needs from others to achieve each; make those visible.
4. Development link: one objective (or part of one) that builds a capability they need next.
5. Questions for the objective-setting conversation: where the employee's view is needed (feasibility, priorities, support), and what the manager should be ready to change.
6. What to cut: activities disguised as outcomes; objectives outside the person's control.

Draft, not decree. Present as a starting point for agreement.

2. Write objectives for hard-to-quantify roles

Best forRoles where outcomes are real but resist numbers — support functions, creative, research, leadership.

Inputs needed

Role's purpose
What good looks like in observable terms
Stakeholders served

How to use itDescribe what the role exists to achieve and who depends on it. The model writes objectives with qualitative evidence standards and the stakeholder judgments that will assess them.

Expected outputObjectives with outcome statements, evidence standards (artifacts, stakeholder assessments, milestones), the assessment method, and the pitfalls avoided.

You are writing performance objectives for [role], where outcomes are hard to quantify.

Role purpose: [what it exists to achieve]
What good looks like: [observable — decisions enabled, quality standards, stakeholder outcomes, risk avoided]
Stakeholders: [who depends on the role and for what]

1. Objectives (3–4): each as an outcome statement, with evidence standards that are observable without being numeric where numbers would mislead: artifacts produced to a defined standard, milestones reached, stakeholder assessments against stated criteria, problems prevented (with the indicator).
2. Assessment method for each: who judges, against what criteria, when, and how bias in stakeholder judgment is reduced (multiple assessors, criteria set in advance).
3. Leading indicators the person can see during the period.
4. Pitfalls avoided: proxy metrics that distort behavior (volume over quality), objectives that reward visibility over contribution.
5. The conversation: how to agree the evidence standards with the employee so they are not surprised at review.
6. Sample review language for a 'met' and a 'partly met' outcome, evidence-based.

Do not invent numeric targets for things that should not be counted.

3. Review a set of objectives for alignment and fairness

Best forChecking a team's objectives before they are locked: alignment, difficulty consistency, measurability, and equity across similar roles.

Inputs needed

Objectives for the team
Team goals
Levels and roles

How to use itPaste the team's objectives. The model checks each set and compares across people in similar roles for consistent difficulty and expectations.

Expected outputFindings per person and across the team: alignment gaps, activities disguised as outcomes, unmeasurable objectives, difficulty inconsistencies across similar roles, and the rewrites.

Act as an HR business partner reviewing a team's performance objectives before they are finalized.

Objectives: [per person: role, level, objectives with measures]
Team goals: [list]
Rules: [number, format, weighting]

1. Per person: alignment (does each objective serve a team goal?), outcome vs activity, measurability (is the evidence defined?), control (is it within their scope?), count and balance.
2. Across the team: for people in similar roles and levels, compare difficulty and scope of expectations; flag where similar roles have materially different bars, and where any group of people (by team, location, working pattern) has systematically easier or harder objectives — as a consistency issue to correct, not a judgment about individuals.
3. Development: whether each person has at least one growth element.
4. Rewrites for the weakest objectives.
5. Questions for managers where the intent is unclear.
6. Summary for the team lead: the three changes to make before locking.

Review objectives, not people. Consistency of expectations is the point.

Objective quality check

Run each objective through this before the objective-setting conversation.

It describes an outcome (what will be different), not an activity (what will be done)
The evidence of achievement is defined — a number, an artifact, a decision — and someone will actually capture it
It traces to a team goal the employee can name
It is within the person's control, or the dependency is written down
The difficulty is stated (core / stretch) and the set is balanced
There are no more than five, and at least one builds a capability the person needs next
It would read the same to another manager — no private meaning

Related prompts

Logical next step

After this, most HR teams move on to Performance Reviews.

Get the free HR & Recruiting AI Starter Kit → Nine of these prompts as an intake → assess → offer hiring workflow with an intake worksheet, delivered by email. See what's inside

All Human Resources prompts · Search the full library