Prioritize conflicting tasks under shifting deadlines

## Assumptions (made explicit) - It’s Friday morning with one 8‑hour block before EOD. - PM needs the readout by EOD Friday to prep a Monday launch decision. - The P0 is live and impacting dashboards currently used by multiple teams. - No additional staffing today; I can timebox/triage but not fully re‑architect. If any assumption is wrong, I would re‑confirm before starting. ## Prioritization Framework (decision rules) I use four lenses and simple rules: 1. Cost of Delay (CoD): Business impact if delivery slips by 24 hours. 2. Blast Radius: How many users/teams/decisions are affected right now. 3. Reversibility: How hard it is to undo a decision made without the input. 4. Time to Mitigate: Can I quickly stop the bleeding or provide a safe workaround? Decision rules: - Rule 1: Triage any P0 with high blast radius immediately; timebox the first fix attempt (60–90 min). If not fixed, implement a safe workaround and annotate affected surfaces. - Rule 2: Next, prioritize the deliverable that gates an irreversible or high‑cost decision (PM readout for launch) over an executive update that’s reversible (forecast can be delivered in lean form and deepened later). - Rule 3: Narrow scope to a “minimum decisionable product” (MDP) for each deliverable; defer non‑critical analyses. - Rule 4: Communicate early with pre‑commitments, risks, and explicit trade‑offs; get stakeholder buy‑in on scope. ## Applying the Framework - (C) P0 data quality: - CoD: Extreme; wrong data may mislead many decisions today. - Blast Radius: High; dashboards across teams. - Reversibility: Low; once bad decisions are made, cleanup is costly. - Action: Triage now; timebox to 60–90 min; if not fully fixable, apply workaround and annotate. - (B) Experiment readout (launch gating): - CoD: High; delays can slip Monday’s launch or risk shipping the wrong thing. - Blast Radius: Medium–high; impacts customers and ops if launch is wrong. - Reversibility: Medium/low; rollbacks are costly and reputation‑impacting. - Action: Do second; deliver a lean, decision‑ready readout. - (A) CFO forecast update: - CoD: Medium; important but a top‑line, range‑based update can satisfy EOD. - Blast Radius: Medium; executive visibility but less immediate operational harm. - Reversibility: High; numbers can be refined on Monday. - Action: Do third; deliver a single‑page top‑line update with assumptions and risks. ## Exact 8‑Hour Sequence (time‑boxed) - 0:00–0:15 - Spin up an incident channel. Confirm scope/impact with Ops. Post immediate comms plan and next update time. - 0:15–1:30 (75 min) - P0 triage: Identify last good timestamp, revert offending change if known, disable/flag corrupted metrics, backfill if feasible. Add dashboard banner: “Data stale from HH:MM; use with caution.” - 1:30–1:45 - Status updates to all stakeholders. Lock P0 workaround or handoff ongoing fix details to Ops with clear ownership of next steps. - 1:45–4:15 (150 min) - Experiment readout (MDP): validate data quality; run primary metric, effect size, CI; guardrails; decision recommendation; create 3–5 slide summary. - 4:15–4:30 - Share draft readout with PM; gather must‑fix feedback only. - 4:30–7:15 (165 min) - Forecast update (MDP): refresh inputs, produce range‑based forecast, sensitivity on 1–2 key drivers; one‑pager with assumptions. - 7:15–8:00 - Final QA, send deliverables, confirm Monday follow‑ups, post end‑of‑day status in a single update to all. Contingency: If P0 exceeds 90 minutes without a stable mitigation, freeze broken tiles, pin a last‑known‑good snapshot, and proceed to B and A while Ops continues remediation. ## What I Defer or Say No To (by deliverable) - P0 incident: - Defer: Full root‑cause analysis, long‑term fixes, and retrospective to next week. - Yes now: Triage, rollback/flag, user‑facing annotations, safe state. - Experiment readout: - Defer: Nice‑to‑have cuts, non‑gating secondary metrics, polished visuals. - Yes now: Primary KPI, CI/effect size, guardrails, power/SRM checks, clear ship/no‑ship with risks. - Forecast update: - Defer: Model re‑spec, new features, category deep dives, full slide deck. - Yes now: Top‑line range, key drivers, scenario band, assumptions and risks. ## Guardrails and Mini‑Checklists - P0 triage quick checks: - When did the anomaly start? Which metrics/dashboards impacted? Any deployment/event at that time? Can I revert or hotfix quickly? If not, disable corrupt tiles and annotate. - Experiment readout quick checks: - Sample Ratio Mismatch (SRM) test. - Data freshness given P0; exclude corrupted window if needed. - Primary metric effect size and 95% CI; harm probabilities vs guardrails. - Example: Uplift = +2.5% (95% CI: +0.4% to +4.6%), P(harm > 0) < 5%; Recommend staged rollout with monitoring. - Forecast quick checks: - Use last‑known‑good data cut. Produce range with sensitivity to 1–2 drivers. - Example: Q4 revenue estimate $124M–$129M (base $126.5M), ±$2.5M driven by order volume and AOV; risks: promo depth, seasonality variance. ## Example Stakeholder Messages (concise) - To Ops (P0) at start: - “On the P0 now. First update in 60 min. I’ll timebox triage to 90 min; if not fully resolved, I’ll freeze impacted tiles to last‑good state and add a banner. Can you confirm the earliest anomaly time and any recent ETL/deploys?” - To PM (experiment) after P0 mitigation begins: - “Heads‑up: I’m triaging a P0 until ~1:30. I will deliver a decision‑ready experiment readout by 4:30 covering primary KPI, CI, guardrails, and recommendation. I’ll defer secondary cuts and polish to Monday. If data freshness is impacted by the P0, I’ll note exclusions. Risk: medium that we use a slightly smaller window; mitigation: guardrails and staged rollout.” - To CFO (forecast) after P0 mitigation begins: - “Plan: I’ll send a one‑page revenue forecast update by 7:15 with top‑line range, key drivers, and assumptions. I’ll defer deep dives and model changes to Monday. If today’s P0 affects any inputs, I’ll use the last‑known‑good cut and flag assumptions. Please confirm this scope meets today’s need.” - End‑of‑day status (all): - “Status EOD: (1) P0 mitigated: dashboards annotated; last‑good snapshot pinned; full RCA Monday. (2) Experiment readout sent: primary KPI +2.5% (95% CI +0.4% to +4.6%); recommend staged rollout with guardrails; details attached. (3) Forecast update sent: $124M–$129M with assumptions and risks. Monday: finalize RCA, deep‑dive experiment cuts, and forecast refinements.” ## Pre‑commitments and Risk Management - Pre‑commitments: - Deliver P0 mitigation within 90 minutes (rollback/annotation) or freeze to safe state. - Provide PM a decisionable readout by 4:30 with clear recommendation and risks. - Provide CFO a one‑pager by 7:15 with a defensible range and assumptions. - Risks and mitigations: - If P0 data gap overlaps experiment/forecast windows, use last‑good window and document exclusions; avoid over‑precision. - If experiment is borderline, recommend staged rollout and define kill‑switch metrics. - If forecast uncertainty is elevated, widen the interval and call out top risk drivers. ## Why this order - It minimizes immediate organizational harm (P0), preserves a time‑critical product decision (experiment readout), and still provides executive visibility with acceptable uncertainty (forecast). Seniority alone doesn’t drive priority; cost of delay, blast radius, and reversibility do.