Designing small in agile contexts is harder than it looks — not because of speed, but because it demands resisting the designer's natural instinct to solve the whole system at once. The key challenge is identifying the smallest slice of an experience that still delivers real user value, as opposed to dividing work by technical layers, which produces components that are useless in isolation. That constraint, though uncomfortable, is what enables fast learning loops and meaningful discovery about what users actually need.