How do you prioritize tasks when everything seems urgent?

Question

This question assesses your time management, communication, and decision-making skills under pressure. Common at fast-paced startups and enterprise companies alike.

Interview OS Community · Accepted Answer

## My Prioritization Framework

### 1. Impact vs Urgency Matrix

```
              High Impact         Low Impact
High Urgency | [1] DO NOW         | [2] DELEGATE
Low Urgency  | [3] SCHEDULE       | [4] ELIMINATE
```

### 2. Real Example

Our team had 4 "urgent" tasks in one sprint:
1. **Production bug**: Users can't login → [1] DO NOW
2. **CEO demo**: Feature request for investor pitch → [3] SCHEDULE (build minimal version for demo)
3. **Security patch**: Dependency with CVE → [3] SCHEDULE (next morning, not midnight)
4. **Refactoring**: Code quality improvement → [4] ELIMINATE (this sprint)

### 3. Communication

I didn't just reorder tasks silently:
- Told PM: "Login bug first, everything else waits"
- Asked CEO team: "What's the minimum viable for the demo?"
- Informed security: "Patching tomorrow morning, risk is low"
- Told team: "Refactoring moved to next sprint, here's why"

## Key Principles

| Principle | Example |
|-----------|---------|
| **User impact first** | Production bugs > new features |
| **Communicate trade-offs** | "If I do X, Y will be delayed" |
| **Ask for help prioritizing** | "Which of these 3 is most important to YOU?" |
| **Don't work overtime** | Sustainable pace > burnout sprint |
| **Document decisions** | "We prioritized X over Y because..." |

## What NOT to Say
- "I just work harder / longer hours" → unsustainable
- "I do everything" → no prioritization
- "I let my manager decide" → no ownership
- "I pick the easiest one first" → wrong prioritization

Interview OS

How do you prioritize tasks when everything seems urgent?

Question Details

Suggested Solution

My Prioritization Framework

1. Impact vs Urgency Matrix

2. Real Example

3. Communication

Key Principles

What NOT to Say

Discussion (0)