Notions

Earlier in this series, I explored how judgement becomes more important as the time and effort required to produce work decreases. That raises a further question: what should guide that judgement? Taste helps us recognise a promising direction, but our decisions also need reasons we can explain, question, and share. Dieter Rams offered a practical foundation through his ten principles for good design. They connect the quality of an object with its usefulness, clarity, honesty, longevity, and environmental impact. What interests me is how they make judgement open to discussion. We can examine a design against these principles, identify where it succeeds, and explain where it falls short. They give us a framework through which understanding can develop. [Dieter Rams’ ten principles](https://www.vitsoe.com/us/about/good-design). The principle I keep returning to is “as little design as possible.” I read this as a discipline of restraint: understanding the problem well enough to recognise what is necessary and what we can leave out. As our tools make it easier to generate, add, and automate, that discipline becomes increasingly relevant. Greater capability gives us more choices, including the choice to intervene less. For me, this extends into the effect our work has on people’s lives. A system can be carefully designed and still ask too much of someone’s attention, collect more information than it needs, or make decisions that should remain theirs. Evaluating the quality of the execution also means questioning the purpose and reach of the thing we are building. A related concern appears in Pope Leo XIV’s encyclical *Magnifica Humanitas*, which questions promises of technological progress that deepen inequality or leave people’s needs unresolved. Its warning about placing hope in continual upgrades raises a question for design: how do we recognise when a new capability contributes to a better life? [*Magnifica Humanitas*](https://www.vatican.va/content/leo-xiv/en/encyclicals/documents/20260515-magnifica-humanitas.html). At the scale of everyday practice, these questions become quite concrete. Removing a step from a process may make it easier to use, but some decisions benefit from a pause. People need time to understand consequences, give meaningful consent, and reconsider. The appropriate pace depends on what is at stake. The same care applies to the tools we make available. Giving communities the ability to adapt and own technology can support greater independence. It also requires attention to how those tools are maintained, how harm is addressed, and who has a voice in their development. Access is one part of an ongoing responsibility. Working towards these outcomes can be difficult within commercial constraints. Conversion targets, engagement measures, and growth expectations influence which problems receive attention and which solutions are rewarded. A designer’s personal convictions can be difficult to sustain without support from the wider team and organisation. This is where written principles become useful. They give people a shared basis for questioning a decision, explaining a concern, or defending a choice whose value may be difficult to measure. They become more meaningful when they shape reviews, project requirements, and the criteria by which work is approved. Metrics still have a role. They can reveal patterns and help us assess whether a change has achieved a particular goal. Understanding its wider effect requires listening to the people involved and examining what those measurements leave out. Sometimes the most responsible decision will be to collect less, automate less, or leave a feature unbuilt. As more execution is delegated, I see a greater responsibility to be clear about the principles directing it. We need to explain our choices, remain open to challenge, and revise our understanding when the work affects people in ways we did not anticipate. Judgement develops through that process, just as craft develops through practice. For anyone starting out, or feeling worn down by the pace of change, this is where I would place some of that attention. Learn the tools, but also spend time understanding the people and problems your work serves. There is still meaningful work in asking a better question, recognising an overlooked need, or deciding that a simpler approach is enough. Keep designing. Keep reflecting. Keep looking up.