Exercise 2: Why Both Frameworks Are Needed Together — Possible Solution
====================================================================

WHAT EACH FRAMEWORK IS ACTUALLY FOR
------------------------------
Per this chapter, "where SEV levels primarily encode severity, this
matrix is explicitly a priority tool." SEV levels answer Chapter 2's
severity question (how bad is the actual impact); the Impact/Urgency
matrix answers Chapter 2's priority question (how urgently should this
be worked right now).

WHY NEITHER ALONE CAPTURES BOTH QUESTIONS
------------------------------
Per this chapter, "using both frameworks together is what actually
captures both of Chapter 2's own axes properly, rather than collapsing
everything back into a single number." Using only SEV levels would
answer severity but say nothing about urgency/timing; using only the
Impact/Urgency matrix would capture priority but lose the objective
severity classification. Using just one collapses two genuinely
separate questions back into one, which is exactly the conflation
Chapter 2 warned against.

THE WORKED EXAMPLE THAT DEMONSTRATES THIS
------------------------------
Per this chapter, the footer typo ticket is "SEV4" (trivial severity)
and "Low impact, high urgency" on the matrix - and the chapter notes
"the matrix is what actually captures why it still needs handling
within the hour, something the SEV level alone was never designed to
express." The SEV4 rating alone would suggest no urgency at all; only
the matrix reveals the time-sensitive priority that the severity
rating was never meant to capture.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains what each framework specifically measures, connects that
back to Chapter 2's own severity/priority distinction, and uses the
chapter's own footer-typo example to show concretely what gets lost if
only one framework is applied.