By Low Friction Lab ·
The best version of a school process is rarely the version presented on launch day. It is the version people can still use on a busy Tuesday—when a substitute needs support, a meeting runs long, and the copier has ideas of its own.
That is not a cynical standard. It is a respectful one.
Start with the conditions of use
Before refining a process, ask where and when people will encounter it. Will a teacher use it between classes? Will a principal need it while responding to three other needs? Will a family see it first on a phone?
Those conditions should shape the design:
- Put the next action where it can be seen.
- Keep required information together.
- Use the same words across messages and tools.
- Make the common path unmistakable.
- Provide a clear route for exceptions.
Reduce recall
Every step people must remember is a step the system may lose. Good routines do not rely on someone recalling a detail from a slide deck three weeks later.
Create a small, visible prompt at the moment of action. A two-line checklist attached to the form is often more useful than a ten-page implementation guide stored elsewhere.
A system becomes more dependable when the environment carries part of the memory.
Test the rough draft
Do not wait for polish. Ask two or three people to use the first version with a realistic scenario. Watch for pauses, questions, and workarounds. Each one points to friction the design can address.
Then test again on an ordinary day. Sustainable systems are built in the context where they must survive.