Design That Solves: Beyond Single Solutions
What Is Good Design?
Today’s Lens: Wendell Berry — Solve for Pattern
“A good solution solves more than one problem, and it does not make new problems.” — Wendell Berry, “Solving for Pattern.” (loa.org)
Berry’s deep point: good design isn’t a single fix—it’s a fit. It works with the larger pattern so well that solving one thing quietly improves three others and avoids ripple‑side damage. That standard is higher than “works on my screen.” It asks: does this feature clean up adjacent workflows, reduce future maintenance, and lower attention costs—without creating new failure modes? If not, keep designing. (loa.org)
Put it to work
- Pattern map: Sketch the neighboring “systems” your change touches (people, data, ops, policy). Draw arrows for flows; circle where side effects could appear. Aim for upgrades in multiple circles. (loa.org)
- Multipliers over patches: Prefer moves that stack benefits (e.g., one rule that simplifies pricing, support scripts, and UI copy). If a fix helps only one team and burdens another, it’s probably a patch, not a design. (progressive.org)
- Side‑effect audit: For every benefit you claim, list “what might this break?” Reduce any new cognitive, technical, or ethical debt before shipping. (interactioninstitute.org)
- Use what’s at hand: Bias toward constraints and components you already have; far‑fetched additions often import hidden complexity. (archive.strongtowns.org)
Carry this line today: good design improves the whole pattern—and leaves no new mess behind. For the source essay and collections that include it, see The Gift of Good Land and the Library of America edition of Berry’s essays. (books.google.com)