Systems are often presented as giant things: software, infrastructure, a perfect set of rules. But most useful systems begin much smaller. They begin as a promise you can keep more than once.
A checklist before publishing. A shared place for decisions. A naming convention that saves the next person ten minutes. These gestures are not glamorous, but they turn good intentions into a practice.
Design for the tired version of yourself
The system has to work on the day when the work is urgent, the context is thin, and nobody remembers why the folder was named that way. That is not a failure of discipline. It is the actual environment a system needs to support.
For me, a useful small system usually has three qualities:
- It makes the next action obvious.
- It keeps important context close to the decision.
- It is easy to change when the work teaches us something new.
Keep the doorway low
A system that needs a long explanation has already asked too much. Start with the lightest structure that could help: a short template, a visible status, a single source of truth. Then watch where people hesitate.
The goal is not to automate every human moment. It is to reserve human attention for the moments that deserve it.