# Mastering Design: Match Complexity with Capability Newsy: What is Good Design? Published: 2026-01-04T23:00:00.343Z Source: https://newsyai.com/edition/f66de12a-226a-4894-be30-6eea11c6828e Archive: https://newsyai.com/newsy/5c850c31-aa90-4fca-8708-9148e1d10645.md --- # What Is Good Design? ## Today’s Lens: W. Ross Ashby — Match Complexity With Capability > “Only variety can destroy variety.” — W. Ross Ashby, articulating the Law of Requisite Variety. Ashby’s point is harsh but clarifying: if your environment can present N different disturbances, your design must offer at least N meaningful ways to absorb, reroute, or damp them. Otherwise, some disturbance slips through and breaks the experience. In practice, you have two levers: - Amplify your system’s variety: richer controls, smarter defaults, adaptive paths. - Attenuate environmental variety: constrain inputs, pre-validate, hide sharp edges. A design is “good” when the regulator (your product) carries enough variety to keep essential variables steady for users—even as the world gets noisy. This isn’t about piling on features; it’s about carrying the right degrees of freedom where reality actually fluctuates. If a support flow faces a dozen distinct failure modes, one generic “Contact us” is insufficient; route by intent, context, and urgency to match the real spread of problems. Likewise, an interface for novices and experts can’t be one-size-fits-all; let capability scale with need. A quick 5‑minute check: 1) List the top disturbances your users meet (e.g., payment failed, wrong format, lost progress). 2) Count distinct responses your system truly offers. 3) Close the gap by either reducing disturbances at the source, or adding just enough targeted responses—no more, no less. — Sources (full URLs): - https://en.wikipedia.org/wiki/Variety_(cybernetics) - https://en.wikipedia.org/wiki/W._Ross_Ashby - https://en.wikipedia.org/wiki/An_Introduction_to_Cybernetics - https://ashby.info/archive.html - https://pespmc1.vub.ac.be/ASHBBOOK.html