
Adrian Jordan
-
2 min Read
Overview
Every year brings a new design tool that promises to change everything. Some of them are excellent, and I use many of them. But I have seen teams with the best tools struggle and teams with simple tools thrive. The difference is almost always the process: how ideas are shared, reviewed, decided and handed over.
A clear process answers practical questions before they become problems. Where do ideas live? Who reviews them and when? How do designs reach development? When those answers are simple and written down, any tool can support them, and switching tools later is painless.
A clear process keeps a team steady while the tools keep changing
One place where work in progress lives.
A fixed rhythm for reviews.
Clear owners for every decision.
A simple, documented handover.
Adrian Jordan
Process over preference
Arguments about tools are often arguments about process in disguise. When a team cannot agree on where files should live or how feedback should be given, changing the tool rarely helps. Agreeing on the steps first makes the tool choice obvious and keeps everyone focused on the work itself.


Keeping it lightweight
A good process should feel light. If it needs a manual, it is probably too complicated for a small team.
I aim for a handful of habits that everyone can remember and that take minutes, not hours, each week.
Simple habits, followed every week.




