Almost every team has a vague, shared sense that some part of how they work feels harder than it should. That feeling rarely turns into action, because it's too diffuse to actually do anything with. A friction log converts it into something concrete enough to prioritize and fix.
The practice itself is simple. What makes it work is doing it consistently enough that a real pattern emerges.
"Things feel slow" isn't something you can fix directly
A general impression that a process is clunky doesn't point at anything specific to change. The same impression, broken into ten logged instances of an actual moment of friction, usually reveals two or three that account for most of the frustration, and those are fixable.
Capture friction the moment it happens
Friction is easy to forget once it's resolved and the work moves on. A log only works if capturing an entry takes seconds, right when the friction happens, not as a recollection exercise at the end of the week when most of it has already been forgotten.
In Stelaah, a quick note or task can be logged against a project or client in seconds, giving a friction log a natural, low-friction home instead of a separate tool nobody remembers to open. See how notebooks works.
Log the specific moment, not the general complaint
"Approvals are slow" is a complaint. "Waited two days for sign-off on the homepage draft because the approver didn't know it was waiting" is a logged instance you can actually act on. Push for the second kind every time.
Review the log on a schedule, not when it's convenient
A friction log that's never reviewed is just a growing list nobody looks at. Set a recurring time, monthly is common, to go through recent entries as a team and decide what's worth fixing next.
Prioritize by frequency, not by whoever complained loudest
The friction that gets fixed first should be whatever shows up most often in the log, not whichever instance happened to someone senior or was described most dramatically. Frequency is a better proxy for actual impact than how memorable a single incident was.
A simple checklist
If you do nothing else, do these five things:
- Make logging an entry take seconds, not minutes.
- Capture friction the moment it happens, not from memory later.
- Log the specific moment, not a general complaint.
- Review the log on a recurring schedule, not only when convenient.
- Prioritize fixes by frequency in the log, not by who complained loudest.
Do that, and a vague sense that things feel slow turns into a short, concrete list of what's actually worth fixing next.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
