Created by the First Role Skills Editorial Desk. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
Start with the work
A realistic scenario
Three requests arrive together: one person cannot print, six people cannot log in, and payroll cannot submit a required file. Which should be handled first?
Avoid rework
Three beginner mistakes
Treating every request marked urgent as P1
Using job seniority as the priority rule
Escalating without recording impact and evidence
The method
Complete it in six controlled steps
- 01
Define impact
Measure how many people or critical processes are affected. Record whether a workaround exists and whether data, safety, money, or a deadline is at risk.
- 02
Define urgency
Ask when harm will occur if nothing changes. A high-impact issue with a safe two-day workaround may be less urgent than a time-bound payroll failure.
- 03
Apply the matrix
Use P1 for critical widespread or business-stopping incidents, P2 for major degradation, P3 for normal individual issues, and P4 for planned requests or questions.
- 04
Record the reason
Write one sentence: 'P2 because six users are blocked and no workaround is confirmed.' This makes reassessment possible.
- 05
Follow the escalation route
Use the team's actual incident channel and on-call process. A priority label alone does not notify the right person.
- 06
Reassess when facts change
Lower or raise priority when scope, workaround, or deadline changes. Keep the original timeline and explain the change.
See the difference
Before and after
P1 - executive cannot print a draft
P3 - one user affected, secure PDF workaround available, needed tomorrow. Owner: service desk queue.
Original practice
Complete the exercise
Classify eight fictional tickets using the impact-urgency matrix. Write a one-sentence rationale for each and compare two borderline cases.
Use only fictional or fully anonymized data. Never upload an employer's confidential information to a portfolio.
Explain your decisions
Turn the exercise into credible evidence
Your evidence should include the completed matrix and the rationale column, not only the final P1-P4 labels. Choose two requests that could reasonably change priority when a new fact appears. Explain what that fact would be, how the label would change, and which route would be notified. This shows that priority is a revisable operational decision based on impact, urgency, workaround, and deadline rather than the requester's tone or seniority.
Quality gate
Check your own work
- Impact counted
- Urgency dated
- Workaround checked
- Reason recorded
- Escalation route used