System Design Card 361 — Scope Control / Breakdown
Concern
Scope control keeps the design proportional to the prompt and prevents architecture theater. A first-pass URL shortener does not need global multi-region consistency if the prompt only asks for the basic service at moderate scale.
What Breakdown means for this concern
In BASIC, the Breakdown step is where you clarify the product goal, workload shape, and non-functional requirement that will dominate the design. For Scope Control, that means the candidate should make this concern visible at the right moment instead of bolting it on at the end.
Design move
A good move is to split the problem before trying to solve it. Tie the concern back to the user flow, the workload, and the dominant trade-off. That keeps the design grounded and makes it easier for the interviewer to follow why a cache, queue, replica, partition, or rate limiter is actually necessary.
Common miss
Candidates often overbuild early and then run out of time for the critical path. BASIC helps because the staged flow keeps this concern proportional to the prompt and connected to the rest of the architecture.
BASIC prompt
“When I reach the Breakdown stage, how does Scope Control change the architecture, the trade-offs, or the review checklist?”