O Construtor de Autoavaliação: Transforme Notas Brutas de Conquistas em Tópicos de Avaliação de Desempenho Polidos
Porque é que este prompt importa
Self-reviews that use vague, passive language (assisted with, was involved in, helped) get rated lower by managers even when the underlying work was significant — reviewers pattern-match specific, quantified language to impact and vague language to a passive contributor, regardless of what actually happened. A weak self-review doesn't just risk a lower rating; it becomes the written record a manager cites months later during promotion or layoff conversations, when nobody remembers the actual work — only what's on paper.
Para que o usamos
It's the week before performance review season, and you have a scrappy list of six months of Slack standups and sprint notes but no idea how to turn “helped ship the new onboarding flow” into something that reads well in a formal review.
Prompt
Act as a performance review coach who specializes in the XYZ formula (Accomplished [X] as measured by [Y] by doing [Z]) for turning vague work notes into polished, quantified self-review bullets. Context: My role is [YOUR JOB TITLE]. The review period is [REVIEW PERIOD, e.g., "H2 2026"]. Here are my rough, unpolished notes on what I did, in whatever form I have them (Slack standups, sprint notes, a messy list): [PASTE YOUR ROUGH NOTES HERE]. Task: For each rough note, produce two candidate bullets: (1) a "Conservative" version using only facts and numbers actually stated in my notes, and (2) a "Stretch" version showing what the bullet could become if I can supply one specific missing metric. Group the resulting bullets into three categories if the notes support it: Impact, Ownership, and Collaboration. Constraints: - Never invent a number, percentage, or outcome that isn't in my notes. If a bullet would benefit from a metric I haven't provided, write "MISSING METRIC: [specific question to answer]" instead of guessing. - Ban passive or vague verbs: helped, worked on, was involved in, assisted with, participated in. Require active ownership verbs: led, built, reduced, drove, designed, shipped, resolved. - Each bullet must be one line — if it needs two lines, it's actually two accomplishments and should be split. - Do not pad weak notes with unearned adjectives (Blizzard, seamless, robust) to compensate for a missing metric — flag the gap instead of disguising it. Output Format: For each original note, show: the raw note as I wrote it, then the Conservative bullet, then the Stretch bullet (or a MISSING METRIC flag if no stretch is honestly possible), grouped under Impact / Ownership / Collaboration headers.
Resultado
Role: Senior Software Engineer. Review period: H2 2026.
Impact
Raw note: "fixed a bunch of bugs in the checkout flow, customers were complaining"
- Conservative: Resolved recurring checkout-flow defects that were generating customer complaints, stabilizing the purchase path.
- Stretch: MISSING METRIC — ask support/product for the actual complaint-ticket count before and after your fixes, or the checkout error rate from monitoring. A bullet like "Reduced checkout errors by 41%, cutting related support tickets from 60/week to 12/week" is far stronger than "fixed a bunch of bugs" — go find that number before you write your review.
Ownership
Raw note: "helped with the migration to the new database"
- Conservative: MISSING METRIC — "helped with" is too vague to convert into any credible bullet, even a conservative one. Before this can become a review bullet, answer: what specifically did you own in this migration (a service, a data model, the rollback plan)? "Helped" reviewers cannot tell if you did 5% or 50% of the work.
- Stretch: Once you have that answer — for example, if you owned the write-path migration for the orders service — try: "Led the orders-service write-path migration to the new database, completing it with zero downtime across 3 weeks of phased rollout."
Collaboration
Raw note: "mentored the new hire, they're doing well now"
- Conservative: Mentored a new team member through onboarding, supporting their ramp to independent contribution.
- Stretch: MISSING METRIC — "doing well" needs a concrete marker. Did they ship their first PR in week 2 instead of the usual week 4? Did they pass their 90-day review with a specific rating? Try: "Mentored a new hire through onboarding; they shipped their first production PR in week 2, versus the team's typical 4-week ramp."
What this reveals: two of your three raw notes are currently unreviewable as written — not because the work wasn't valuable, but because the notes don't contain a number. That's exactly the gap to close before review season, not during it.
A maioria das autoavaliações falha por um motivo específico e corrigível: elas descrevem atividade em vez de impacto. "Ajudei com a migração" e "corrigi vários bugs" são afirmações verdadeiras sobre trabalho real, mas nenhuma sobrevive ao contato com um avaliador treinado para buscar a fórmula XYZ — realizou X, medido por Y, fazendo Z.
Este prompt foi criado para separar dois problemas diferentes que se confundem quando alguém tenta escrever uma autoavaliação de uma só vez: transformar uma frase vaga em uma bem estruturada, e encontrar uma métrica ausente. Um tópico "Conservador" usa apenas o que você já sabe. Um tópico "Ambicioso" mostra como a mesma conquista fica com uma métrica específica anexada.
A proibição explícita de números inventados é a restrição mais importante do prompt. Sinalizar "MÉTRICA AUSENTE" em vez disso força o resultado realmente útil: uma pergunta específica e respondível.
A estrutura de três categorias — Impacto, Propriedade, Colaboração — existe porque os avaliadores buscam sinais diferentes em cada uma. Classificar suas notas brutas nessas categorias antes de poli-las revela lacunas na história que você conta sobre seus próprios seis meses.