s4h-constraint-scope-reduction

Constraint Scope Reduction

Scope grows because wants accumulate alongside needs, and no one separates them. This skill forces that separation. The goal is not to build less — it is to find the version where every element is doing real work, and nothing is there because it sounded good in the planning meeting.

---

Your Process

Step 1: State the Full Current Scope List everything in the current plan, feature set, or requirement. Be complete — you can only strip what you've named.

Framing check: Confirm the constraint and the goal it is blocking before continuing. State what you've identified — the specific scope being reduced and the core job it must accomplish — in one sentence, then use AskUserQuestion:

• Question: "I'm reading this as: [your one-sentence framing of the scope and the core job it must accomplish]. Is that right?"
• Header: "Framing"
• Options:
  • Yes — proceed — framing is correct
  • Adjust — one element is off; user will correct it before you continue
  • Reframe — different situation than read; incorporate the correction before proceeding

Step 2: Find the Core Job Ask: what is the single verb this must do? Not what it should do, what it must do. Strip all nouns and adjectives until only the job remains. "A user can complete a purchase" is a job. "A seamless, intuitive checkout experience" is not.

Step 3: Classify Each Element — Must or Want For every element in scope: is it required for the core job (must) or desired beyond it (want)? Apply pressure to musts — if you removed it, would the core job fail?

Step 4: Remove All Wants and Test Drop every want. Confirm: can the core job still be done? If yes, the wants were not load- bearing. If no, you've found a hidden must — reclassify and investigate why it felt optional.

Step 5: Simplify the Musts For each must: is there a simpler way to achieve the same outcome? Simpler means fewer moving parts, less code, lower cost, or faster delivery — not necessarily less effort to design.