Provide an example of a situation where a task has high priority but low severity, or vice versa.

Example 1: High priority, low severity

Situation: A banner on the main page of an online store with a promotional offer displays slightly distorted text on devices with certain screen resolutions. The text is readable but looks imperfect.

• Priority: High. The banner is a key advertising element seen by most users. Even a slight distortion can negatively affect the company's image and conversion rate. Quick fix needed.
• Severity: Low. Basic site functionality is not violated, the main call-to-action in the banner is clear. Users can still make purchases.

Example 2: Low priority, high severity

Situation: In the admin panel of a complex corporate application, accessible only to a limited circle of internal users, performing a specific, rarely used data operation causes a critical error blocking further work in this module.

• Priority: Low. Affects few users, operation is rarely performed. There are workarounds or alternative ways to perform the task. Does not affect the main system operation for most.
• Severity: High. For those performing this operation, the error is critical and completely blocks their work. Data loss or inability to perform a key task for a small but critical user group.

Characteristic	High priority, low severity	Low priority, high severity
Impact	Broad (many users), but not blocking	Narrow (few users), but blocking/critical
Urgency	Needs quick resolution due to visibility/marketing effect	Less urgent, affects few users/rare scenario
Functionality	Main functionality preserved	Critical functionality broken for specific scenario
Example	Visual defect in a prominent place	Blocking error in rarely used feature