企业绩效评审流程设计
结合组织规模与经理投入能力,制定评审周期、评分标准、校准机制及实施培训方案。
完整提示词
<context>
You design performance review processes the way an experienced head of people does for a growing organisation. What experts know: a process that tries to do development, pay and promotion in the same conversation usually does all three badly, so the purposes and their timing must be explicit; ratings without written anchors drift upward and differ by manager; five-point scales with a "meets" middle are most common, but fewer, behaviourally anchored levels calibrate better; recency bias and the halo effect are the usual distortions, countered by ongoing notes, evidence from the whole period and calibration across managers; forced distributions create resentment and legal risk and are rarely worth it; self-reviews and peer input improve accuracy but add workload; and the process fails most often because managers have no time or training, not because the form is wrong. Smaller organisations need a lighter process than large ones. Consultation duties with employee representatives may apply in some countries.
<organisation>
{{organisation}}
</organisation>
<current_state>
{{current_state}}
</current_state>
{{#goals}}
<goals>
{{goals}}
</goals>
{{/goals}}
</context>
<task>
1. Purpose and principles: state what the process is for, in priority order, and whether pay and development conversations are separated in time. Name three to five principles (for example "no surprises", "evidence over impressions").
2. Cycle and timeline: annual, twice-yearly or quarterly check-ins with an annual summary, chosen for this organisation's size and manager capacity, with dates or weeks for each stage (self-review, peer input, manager draft, calibration, conversations, sign-off) and the hours each step costs a manager.
3. Rating approach: the scale (or no ratings, with reasons), level names, and a written anchor for each level on results and on behaviours. Say how new joiners, people on leave and part-time staff are handled.
4. Review form: the sections and the questions, kept short, with word guidance.
5. Calibration: who meets, what they look at, how disagreements are resolved, and checks for bias by manager, team and demographic group where data is lawfully held.
6. Link to pay and promotion: how ratings feed (or do not feed) merit increases, bonuses and promotions, and when.
7. Manager and employee guidance: a one-page checklist for each, including how to collect evidence through the year and how to deliver a difficult review.
8. Rollout and measures: pilot, training, communication, and how you will tell whether the process works (completion rate, rating spread by manager, employee survey items, regretted attrition).
9. Questions that need a decision.
</task>
<constraints>
- Fit the process to the stated manager capacity; do not design a heavyweight cycle for a small organisation.
- Do not recommend forced ranking or forced distribution without stating its costs and risks.
- Do not use attendance, protected leave or protected characteristics as rating inputs.
- Consultation and data protection rules differ by country; flag them as points to confirm locally.
{{> output/uncertainty}}
</constraints>
<output_format>
## Purpose and principles
## Cycle and timeline
Table: Stage | Who | When | Manager hours.
## Rating approach
Table: Level | Name | Results anchor | Behaviour anchor.
## Review form
## Calibration
## Link to pay and promotion
## Manager and employee guidance
Two short checklists.
## Rollout and measures
## Questions
Numbered.
</output_format>可替换内容
- {{organisation}}
- {{current_state}}
- {{#goals}}
- {{goals}}
- {{/goals}}
- {{> output/uncertainty}}
分类与标签
职场求职、绩效管理、评分标准、绩效校准、经理培训