Say it like this
- We have a P0 on our hands.
- This is a P0 bug that needs immediate attention.
- We need to P0 this issue before launch.
- That should be marked P0, not P1.
- We declared a P0 incident.
Use it at work
Triaging
- This is a P0. Checkout is down for everyone.
- Is this really a P0, or a P1?
Responding
- All hands on the P0 until it's fixed.
- Drop everything. We have a P0.
Reporting
- We had two P0s this month.
- The P0 is resolved.
Don't say this
P0 should only describe critical issues that block work immediately. Multiple P0s per week suggests the label is being overused. If you have multiple high-priority items, they are probably P1 or P2.
Don't mix it up
| Term | What it is | Who writes or uses it | When |
|---|---|---|---|
| P0 | Highest priority, fix now | Engineering, product | Critical bugs |
| P1 | High priority, fix soon | Engineering, product | Serious bugs |
| SEV1 | Most severe incident level | Ops, on-call | Outages |
Practice
Try it
4 quick exercises
1. Your team found that users cannot log in to the app. How do you communicate this?
2. The payment system is completely down. We should _______ this as P0 right away.
3. Which sentence uses P0 incorrectly?
4. Rewrite using tech English: A very serious problem that must be fixed right now because customers cannot use the main feature of our product.
Say it out loud
Phrase 1 of 5
"We have a P0 on our hands."
We don't save your recording. The word check uses your browser's speech recognition.
More about P0
Real examples(5)
- in a standup
"We discovered a P0 in the login flow yesterday, so most of the team is still working on that fix."
- in a code review
"This memory leak could cause crashes in production. I'm marking it as P0 severity."
- in a team meeting
"The database is down, so this is a P0 incident. Everyone should focus on recovery."
- in Slack
"Just filed a P0: users can't complete checkout on mobile devices."
- in a retrospective
"We should have caught that P0 issue earlier in testing."
More mistakes(3)
Handle with care. P0 is a severity label, not a task type. Do not use it to describe general work items or low-priority bugs. Confusing P0 with P1 or P2 severity levels can cause miscommunication about urgency.
- ✕Can you P0 this feature request?✓Can you mark this feature request as P1?
P0 is for bugs or issues, not feature requests. Feature requests should use a different priority system or be marked P1-P3 based on business impact.
- ✕We should P0 the UI improvements.✓We should mark the UI improvements as P2 or defer them.
P0 is reserved for critical problems, not improvements or enhancements.
- ✕That is a small P0 issue.✓That's a P2 issue.
If an issue is small or easily fixed, it is not P0. P0 issues are always critical and urgent, regardless of fix size.
Other forms(4)
- P0 noun
"We have a P0 blocking our release."
- P0 issue / P0 bug noun phrase
"The team resolved the P0 bug in three hours."
- P0 (used as modifier) adjective
"This is a P0 severity problem."
- priority 0 / priority zero full form
"Login is down for everyone, so this is priority zero."
Often used with(6)
- declare a P0 · To officially label something as critical: We declared a P0 incident when the API went down.
- mark as P0 · To assign P0 severity to a bug: Please mark this as P0.
- P0 incident · A critical issue requiring immediate response: We are responding to a P0 incident.
- P0 bug · A critical defect blocking core functionality: We fixed the P0 bug before shipping.
- resolve a P0 · To fix a critical issue: We resolved the P0 in production.
- P0 severity · The highest priority level: This issue has P0 severity.
Similar words(4)
- Critical · More general term meaning very serious; P0 is the specific label used in ticketing systems.
- Sev 0 or Severity 0 · Alternative way to say P0; stands for Severity Zero.
- Blocker · A bug that blocks work; P0 is more specific and formal in priority systems.
- Hot fix · An urgent code change needed in production; related but not identical to P0.
Opposites(4)
- P3
- P4
- low priority
- deferred
Questions(9)
- What does P0 stand for?
- P0 stands for "priority 0". Priority scales usually run from P0 (critical) to P1 (high), P2 (medium) and P3 or P4 (low).
- What is a P0 bug?
- A P0 bug breaks something core, such as login, checkout or data safety, for many users. The team fixes it before any other work.
- What is a P0 incident?
- A P0 incident is a live outage or failure at the highest severity. It usually starts an incident call and an on-call response, followed by a post-mortem.
- What does P0 mean in software engineering?
- P0 stands for Priority Zero or Severity 0, the highest urgency level in bug tracking systems. It means a critical issue that must be fixed immediately because it prevents the product from functioning or causes severe data loss. When a bug is marked P0, engineers should drop current work and focus on resolution.
- How do you use P0 in a sentence at work?
- You use P0 as a noun or label: We have a P0 bug in production. You can also use it as an adjective: This is a P0 severity issue. In Slack or tickets, you might write: Marking this as P0—users cannot complete checkout.
- What is the difference between P0 and P1?
- P0 is critical and requires immediate response (within hours or minutes). P1 is high priority but can wait for the next scheduled release (within days). P0 blocks core functionality; P1 impacts functionality but has a workaround or affects fewer users.
- When should you NOT use P0?
- Do not use P0 for feature requests, minor bugs, cosmetic issues, or improvements. Only use P0 when something is truly broken and urgent: security vulnerabilities, complete service outages, data corruption, or critical user-facing failures.
- Is P0 formal or informal?
- P0 is neutral and standard in tech companies. You use it in formal incident reports, meetings, and tickets as well as casual Slack messages. It is professional jargon that is expected in tech workplaces.
- What happens when you declare a P0?
- Declaring a P0 typically triggers incident response: the team stops other work, an incident commander may be assigned, status updates are sent to stakeholders, and all available engineers focus on fixing the issue. It is a serious escalation.
