In the age of information overload, our best tool is not the brush, but the scissors.
Many people think a designer’s job is to add: add features, add graphics, or add layers of interaction. However, the most difficult and valuable task is curation. When a client says they need to “see everything on one screen,” our job is not just to do it. Our responsibility is to ask what “everything” really means and what decisions the user actually makes with that data.
Designing is editing the user’s reality so they only see what matters, when it matters. If an interface shows twenty indicators but only three are critical, you are not informing the user. You are creating noise. A designer must remove the extra parts so the user can reach their goal efficiently.
Curation as an Engineering Process
The role of an “editor” is not based on feelings; it needs a methodology to filter information without losing depth:
- The Cut: Every visual element consumes the user’s “mental CPU.” As editors, we must check every data field with a simple question: “If we remove this now, what does the user actually lose?” If the answer is “nothing or very little,” the data is extra. Visual clarity is a safety measure. Fewer distractions mean fewer mistakes.
- Urgency vs. Importance: A good editor knows that not everything belongs on the front page. In design, this means creating dynamic views. We don’t hide information; we organize its visibility. The design must edit the interface in real-time: if the system is stable, the design is minimal. If there is a problem, the interface changes to prioritize that issue. This is contextual editing.
- Synthesis: A complex chart can be edited into a simple status icon or a clear sentence. Our job is to find the simplest way to show a complex reality. Instead of forcing the user to read a table with a thousand rows, the designer-editor provides a summary. This is not about making things simple for no reason; it is about making them clear so the user can act.
Conclusion: Less Noise, More Precision
It is much easier to say “yes” to every feature request than to explain to a stakeholder why hiding data makes it more valuable.
We do not design to fill empty spaces; we design to remove distractions. Clarity only happens when a designer has the judgment to know what to leave out. In the end, a good design is one that meets all needs with nothing left over.