O Reconciliador de Atrasos Semanais: Transforme o Plano da Semana Passada vs o Que Realmente Aconteceu em Prioridades Realistas Para Esta Semana
Porque é que este prompt importa
Carrying forward 100% of unfinished work without diagnosing why it slipped just rebuilds the same overcommitted list — so the same items stall again, trust in your own estimates erodes, and the backlog of almost-done work keeps growing instead of shrinking. Naming the actual slippage pattern (sequencing, dependency, underestimate, interrupt, overcommitment) is the only way to stop repeating it.
Para que o usamos
You are a product manager (or any individual contributor juggling multiple workstreams) who ends most Fridays with 2-3 planned priorities still undone, and every Monday you face the same choice: silently carry everything forward, or sit down and actually figure out what happened before deciding what is realistic this week.
Prompt
Role: Act as a ruthless but constructive chief-of-staff who specializes in diagnosing why plans don't survive contact with the week. Context: - My role/function: [YOUR ROLE OR JOB] - Last week's planned priorities: [PASTE THE LIST YOU COMMITTED TO LAST WEEK] - What actually happened: [PASTE A ROUGH LOG — WHAT GOT DONE, WHAT GOT BUMPED, WHAT UNEXPECTED THINGS ATE YOUR TIME] - This week's fixed calendar load: [HOURS ALREADY COMMITTED TO MEETINGS / FIXED OBLIGATIONS] - This week's candidate priorities: [PASTE YOUR ROUGH, UNORDERED LIST FOR THIS WEEK] Task: Step 1 — Diagnose: For each item from last week that slipped, identify the TRUE root cause, choosing from: underestimated effort, dependency on someone else, a higher-priority interrupt, poor sequencing, or simply committing to too many items. Name the single most common cause across all slipped items. Step 2 — Reconcile: For each slipped item, decide whether it still genuinely matters this week or whether its relevance has decayed and it should be formally dropped — not silently carried forward and not silently forgotten. Step 3 — Replan: Build this week's priority list using available hours (total working hours minus the fixed calendar load from Context), sequenced by dependency and cost of delay, not just by who asked most recently. Constraints: - Do not carry over 100% of unfinished items by default — that is denial, not reconciliation. - Cap the final list at no more than [MAX NUMBER OF PRIORITIES, e.g. 5] items. - If the available-hours math does not support even the capped list, say so explicitly rather than quietly padding a list that will slip again. - Name capacity delusion directly when you see it (e.g., "this plan assumes zero interrupts, which contradicts what happened last week"). Output Format: 1. Root Cause Summary (2-3 sentences, naming the dominant slippage pattern) 2. Dropped Items table: Item | Why It No Longer Matters 3. This Week's Priorities table: Priority | Why It's In | Estimated Hours | Dependency Risk 4. One direct, blunt paragraph starting with: "If you only change one thing this week, it's..."
Resultado
**Root Cause Summary** Three of your four slipped items shared the same root cause: poor sequencing, not lack of effort. You started the vendor contract review and the Q4 roadmap draft in parallel on Monday, both stalled waiting on the same finance input, and neither finished. The onboarding doc rewrite wasn't a sequencing problem — it was a straightforward underestimate; you scoped it at 2 hours and it needed 6.
**Dropped Items** | Item | Why It No Longer Matters | |---|---| | Competitor pricing audit | Sales already pulled this data for Thursday's QBR independently — duplicate effort | | Slack channel reorg | Nice-to-have that nobody has asked about since you proposed it three weeks ago |
**This Week's Priorities** (capacity: 24 available hours after 16 hours of fixed meetings) | Priority | Why It's In | Est. Hours | Dependency Risk | |---|---|---|---| | Finance input for vendor contract + roadmap | Unblocks two stalled items at once; single conversation fixes both | 3 | Low — finance confirmed availability Tuesday | | Finish vendor contract review | Legal needs this by Friday for the renewal deadline | 5 | Medium — depends on finance input above | | Onboarding doc rewrite (properly scoped this time) | Already 60% done; finishing has a low marginal cost | 6 | Low | | Q4 roadmap draft v1 | Leadership review is in 9 days; a rough draft now beats a rushed one later | 8 | Medium — depends on finance input |
Total: 22 of 24 available hours. Two hours of buffer intentionally left unallocated, because last week had zero buffer and that is exactly why the interrupt from the client escalation blew up your whole Wednesday.
**If you only change one thing this week, it's this:** stop starting two finance-dependent items in parallel — book the 30-minute finance conversation first thing Monday morning, because last week proved that running both tracks simultaneously without that input just produces two half-finished things instead of one finished thing.
A maioria dos prompts de «planejamento semanal» simplesmente pega uma lista de desejos e a reordena. Eles pulam a parte que realmente importa: descobrir por que o plano da semana passada não sobreviveu ao contato com a realidade, para que você não reconstrua a mesma lista irrealista nesta semana.
Este prompt impõe uma sequência de três etapas — diagnosticar, reconciliar, replanejar — antes de deixar você mexer nas prioridades desta semana. A etapa de diagnóstico é a mais importante. «Não dei conta» não é uma causa raiz; esforço subestimado, dependência bloqueante, uma interrupção, sequenciamento ruim ou simplesmente excesso de compromissos, sim. Nomear o padrão real é o que impede que a próxima semana se pareça com a anterior.
A etapa de reconciliação é a parte que a maioria das ferramentas de planejamento ignora completamente. Itens inacabados não merecem automaticamente um lugar na lista desta semana — alguns simplesmente perderam relevância desde que foram anotados. O prompt obriga você a dizer isso em voz alta, com um motivo, em vez de deixar uma tarefa pendente se calcificar silenciosamente em um backlog permanente.
A etapa de replanejamento é deliberadamente limitada pela capacidade real. Você dá ao modelo suas horas realmente disponíveis — o total menos o que já está travado em reuniões — e ele precisa encaixar as prioridades nesse número real, não em uma semana imaginária de 40 horas onde nada mais acontece. Se a conta não fechar mesmo depois de limitar a lista, o prompt é instruído a dizer isso diretamente, em vez de prometer demais silenciosamente de novo.
Para quem é: qualquer pessoa que termina a maioria das semanas com parte do plano inacabada e começa a semana seguinte simplesmente copiando o que sobrou para uma lista nova, sem perguntar se essa é realmente a atitude certa.
Como adaptar: a entrada «o que realmente aconteceu» não precisa estar polida — um registro bruto e honesto do que foi feito, adiado ou bagunçado funciona melhor do que uma versão limpa, já que a etapa de diagnóstico precisa da bagunça real para encontrar o padrão real.