Prioritization: Urgent vs. Important Tasks

In my previous role, facing a similar scenario, I first applied the Eisenhower Matrix to categorize the tasks. The P0 production issue falls squarely into the 'Urgent and Important' quadrant because it directly impacts user safety and platform availability, which are non-negotiable at a company like Uber. Therefore, my immediate decision is to dedicate 80% of the engineering resources to resolving this critical incident. I would initiate an emergency war room, assign a dedicated Incident Commander, and ensure all communication channels are open to stakeholders. Simultaneously, I would communicate with the product team regarding the strategic project due next week. Since it is 'Important but Not Urgent,' I would negotiate a brief extension or re-prioritize its scope to focus only on high-value, non-blocking deliverables that can be paused safely. To manage resources, I might temporarily reassign one senior engineer from the strategic project to assist in the P0 investigation, ensuring we have the necessary expertise. Once the P0 is resolved and the system is stable, I would conduct a thorough post-mortem to implement safeguards against future occurrences. Finally, I would reconvene with the strategic team to adjust the roadmap, ensuring the delay does not impact our Q3 OKRs. This approach ensures we protect the core business while maintaining progress on long-term goals through clear communication and adaptive planning.