El Conciliador de Retrasos Semanales: Convierte el Plan de la Semana Pasada vs lo Que Realmente Pasó en Prioridades Realistas para Esta Semana
Por qué importa este prompt
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 qué lo 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.
La mayoría de los prompts de «planificación semanal» simplemente toman una lista de deseos y la reordenan. Se saltan la parte que realmente importa: averiguar por qué el plan de la semana pasada no sobrevivió al contacto con la realidad, para que no reconstruyas esta semana la misma lista poco realista.
Este prompt obliga a seguir una secuencia de tres pasos —diagnosticar, conciliar, replanificar— antes de dejarte tocar las prioridades de esta semana. El paso de diagnóstico es el más importante. «No llegué a hacerlo» no es una causa raíz; un esfuerzo subestimado, una dependencia bloqueante, una interrupción, una mala secuenciación o simplemente un exceso de compromisos sí lo son. Nombrar el patrón real es lo que evita que la próxima semana se parezca a la pasada.
El paso de conciliación es la parte que la mayoría de las herramientas de planificación omiten por completo. Los elementos sin terminar no merecen automáticamente un lugar en la lista de esta semana — algunos simplemente han perdido relevancia desde que los anotaste. El prompt te obliga a decirlo en voz alta, con una razón, en lugar de dejar que una tarea pendiente se fosilice silenciosamente en un backlog permanente.
El paso de replanificación está deliberadamente limitado por la capacidad real. Le das al modelo tus horas disponibles reales —el total menos lo que ya está bloqueado en reuniones— y debe encajar las prioridades en ese número real, no en una semana imaginaria de 40 horas donde no pasa nada más. Si las cuentas no cuadran incluso después de limitar la lista, el prompt tiene instrucciones de decirlo directamente en lugar de volver a prometer de más en silencio.
Para quién es: cualquiera que termine la mayoría de las semanas con una parte de su plan sin hacer y empiece la siguiente simplemente copiando lo que sobró a una lista nueva, sin preguntarse si eso es realmente lo correcto.
Cómo adaptarlo: la entrada de «qué pasó realmente» no necesita estar pulida — un registro crudo y honesto de lo que se hizo, se pospuso o se descontroló funciona mejor que una versión depurada, ya que el paso de diagnóstico necesita el desorden real para encontrar el patrón real.