The Friday Friction Review: A Five-Minute Habit for More Accessible UK Teams
Photo: wfmillar , CC BY-SA 2.0, via Wikimedia Commons
A small habit with a wide reach
Digital accessibility often gets treated as a project with a start date, a steering group and a launch campaign. Yet many of the barriers that slow colleagues down are small, recurring and local: a scanned PDF with no text layer, an agenda shared only as an image, a hybrid meeting where remote participants cannot hear the room, or a set of instructions buried in a long chat thread. A friction log gives teams a lightweight way to notice these issues and act before they become normal.
The idea is simple. Once a week, a team spends five minutes recording the frictions they encountered and agreeing one or two practical fixes. It is not an audit, a complaints channel or a replacement for formal accessibility testing. It is a habit of attention. The aim is to enable colleagues to do their best work, and to make small improvements part of the ordinary rhythm of the team.
What the review is, and what it is not
A Friday friction review works best when it is:
- Short. Five minutes in an existing team meeting, or an asynchronous form completed by Friday lunchtime.
- Specific. Notes describe the barrier and its impact, not the person who raised it.
- Owned. Each item has a named person and a realistic date, even if the fix is simply to change a template.
- Blame-free. The purpose is to improve the system, not to score individuals.
- Private by default. The log should not include sensitive health information or personal details. If an issue relates to an individual adjustment, it should go through the appropriate confidential route.
It is not a substitute for an accessibility audit, a formal grievance process or a reasonable adjustments request. Nor should it become a dumping ground for every frustration. Keep the focus on barriers that affect participation, communication or access to information and tools.
A five-minute template
A simple table is enough. Teams can use a shared document, a form or a channel post. The following fields keep the habit light:
| Field | What to record |
|---|---|
| Friction | What got in the way? |
| Where | Meeting, document, intranet page, software, room or process. |
| Impact | Who was affected, and how? |
| Quick fix | What can be changed this week? |
| Owner | One named person. |
| Review date | Usually the next Friday. |
Managers can prompt the team with three questions: What took longer than it should? What did someone have to ask for twice? Where did a format or tool exclude someone from the conversation? These questions surface practical issues without requiring anyone to disclose a disability.
From notes to fixes
The value of the log comes from the follow-through. A useful pattern is to sort items into three groups.
- Fix now. Small changes that need no approval: adding a text layer to a PDF, switching on live captions, sharing an agenda as text, using the chat to repeat questions in hybrid meetings, or replacing an image-only instruction with accessible text.
- Fix with a template. Recurring issues often point to a missing standard. If meeting notes are consistently hard to scan, create a simple accessible template. If documents routinely lack headings, add a checklist to the team's document library.
- Escalate. Some barriers need IT, facilities, HR or a supplier. Record the issue, the owner and the date it was escalated. Do not let it disappear simply because it left the team.
A short monthly review can spot patterns. If the same software quirk appears four weeks running, the fix is probably a configuration change or a supplier conversation, not another reminder to the team.
Making it stick in a busy week
The main risk is that the habit becomes another administrative task. Keep it small and attach it to something that already happens. A Friday team huddle, a weekly project check-in or a regular manager one-to-one can host the review. Rotate the note-taking so it does not fall to one person. Celebrate quick fixes visibly; it reinforces that small actions matter.
Leaders can help by modelling the behaviour. When a manager records their own friction, such as a meeting format that made it hard to follow the discussion, it signals that the log is about improving the system rather than judging colleagues. Over time, the team builds a local memory of what works.
Start with one team and one quarter
A pilot in a single team for a quarter is enough to test the habit. Agree the template, choose a weekly slot and review the log after four weeks. Ask whether the team found it useful, whether fixes were completed and whether anything should be changed. Then decide whether to extend it.
The friction log will not solve every accessibility challenge. It will, however, help UK teams notice the small barriers that are easy to accept and easy to fix. Enablement is often less about a grand programme and more about a regular, shared habit of making the next week slightly easier than the last.
