Deciding what matters.
WHY IT IS NECESSARY
Everything cannot be built first, and treating everything as essential means nothing is prioritised.
WHAT TO CATEGORISE BY
What is essential for the system to be useful at all What is important but could follow What is desirable What is explicitly excluded
WHY THAT LAST CATEGORY MATTERS
Stating what will not be built prevents expectation and argument.
WHAT TO BE CAREFUL WITH
Everything being declared essential.
WHAT TO ASK WHEN THAT HAPPENS
If we could only deliver half of this, which half?
WHY THAT WORKS
It forces a real ordering without asking anyone to abandon anything.
WHAT ELSE TO CONSIDER
Which requirements reduce risk Which unlock others Which deliver value soonest
WHAT TO DELIVER FIRST
A thin path through the whole system, end to end.
WHY
It proves the approach works, and surfaces integration problems early.
WHAT TO AVOID
Building one part completely before starting another.
WHAT TO REVIEW
Priorities, as understanding develops.
