Class of Service: Not All Tickets Are Equal

Imagine an Emergency Room. A patient walks in with a broken toe. Another comes in with a heart attack.

Do you treat them "First In, First Out"? No. The heart attack skips the line.

Software is the same. A "Server Down" bug is a heart attack. A "Fix CSS padding" task is a broken toe.

Yet, most teams treat everything as "Standard." Class of Service (CoS) is how you tell the team how to treat a ticket based on its urgency.

Here is what we'll cover:

1. The 4 Classes of Service.
2. Swerving Logic: When to interrupt the team.
3. The Cost of Delay.

1. The 4 Classes

Explicitly label your tickets with these classes.

A. Expedite (P0 / Emergency)

• Definition: The house is on fire. Production is down. Major revenue loss.
• Rule: Drop everything. Break WIP limits. Swarm.
• Color: RED.

B. Fixed Date (Deadlines)

• Definition: "Black Friday Sale." "Regulatory Compliance by June 1st."
• Rule: If we miss the date, the value drops to zero. Prioritize ensuring it hits the date.
• Color: ORANGE.

C. Standard (The Bulk)

• Definition: Normal features. "Add Dark Mode." "Update Profile."
• Rule: First In, First Out (FIFO). Optimize for flow.
• Color: BLUE.

D. Intangible (Chores)

• Definition: "Update Docs." "Clean up old branches." "Upgrade non-critical library."
• Rule: Do this when there is downtime. Low cost of delay.
• Color: GREY.

2. The "Expedite" Tax

You might think: "If Expedite is so fast, why not make EVERYTHING Expedite?" Because Expedite disrupts Flow.

When an Ambulance speeds through traffic, everyone else has to stop. The overall system slows down. Rule of Thumb:

• Expedite tickets should be < 5% of your work.
• If you have a "P0 Emergency" every day, you don't have an emergency. You have unstable software. Stop building features and fix the stability.

3. Cost of Delay (CoD)

How do you decide the Class? Ask: "What does it cost us if this is 1 week late?"

• Standard: "It annoys users, but they won't leave." (Low CoD).
• Fixed Date: "We get fined $10,000 per day after June 1st." (High CoD cliffs).
• Expedite: "We lose $1000 every minute." (Immediate CoD).

Summary

1. Label your work. Don't treat a typo the same as a outage.
2. Protect the Standard Lane. Only Expedite when absolutely necessary.
3. Visualize it. Make Expedite tickets look different on the board (e.g., a Swimlane at the top).