Part 5 of 9 · 1 min read
Scope: what the design will not do
Why saying no to features is part of the design, and how to do it politely.
Think of packing a suitcase for a weekend trip. Everything cannot fit. The traveller decides what to leave behind. A bag that tries to hold the whole wardrobe will not close.
A design is the same. Real products have hundreds of features. A design session has an hour, or a project has a deadline. The designer picks the few that matter most, and says plainly what is left out.
Scope
Scope is the list of what a design covers, and the list of what it deliberately leaves out. A clear scope has both lists.
Example: "In scope: upload a photo, view a feed of photos. Out of scope: comments, direct messages, ads."
A good scope has three parts:
- Core features. The two or three actions without which the product has no point.
- Later features. Things worth doing after the first version. They are named so that the design leaves room for them.
- Out of scope. Things not done at all, in this design.
Common mistake
Putting everything in scope. A design that tries to solve every problem solves none of them well, and it never finishes. Saying "out of scope for now" is a strong move, not a weak one.
A tip on tone. Do not announce a cut like a refusal. Offer it as a plan: "Comments are important. A good plan is to leave them for later and focus on upload and feed first. Is that acceptable?"
Check yourself:
- Name one feature of a chat app that is probably core, and one that could be later.
- Why list what is out of scope, and not just what is in?