What is friction in a household routine?

Friction is an observable condition that makes a routine slower, harder to start, easier to interrupt, or more likely to remain unfinished. Examples include a missing tool, unclear owner, inaccessible storage, repeated handoff, or unavailable shared resource. It is not automatically proof that a person lacks motivation. Describe the event and setting before assigning a cause or redesigning the system.

Why observe for seven days?

Seven days capture weekday and weekend variation while keeping the test short enough to review. It is a practical window, not a scientific law. A routine performed monthly needs a different period, and an urgent safety fault should not wait for more data. Choose a duration that produces several comparable attempts without requiring intrusive tracking or delaying appropriate action.

Should I time every step in a routine?

Only if timing answers a useful, consented question. Often a short note about where work stopped is enough. Continuous timing can add burden, change behavior, and feel intrusive in shared households. Never track another person secretly. Use approximate times for low-stakes planning, protect personal information, and follow qualified methods when the process affects work, care, accessibility, safety, or regulated activity.

How do I choose which friction to fix first?

Separate severity from frequency. Address hazards through the appropriate official or professional process even when rare. Among low-risk issues, choose a repeated snag with a reversible, affordable change that users accept. Consider access and whether the fix merely moves effort to someone else. Test one main variable so the next observation period can show what changed rather than producing several competing explanations.

What if the seven-day change does not help?

Remove or revise it and record what the test revealed. Check whether the proposed cause was wrong, the new location or sequence was inaccessible, people did not know about it, or friction moved elsewhere. A failed reversible experiment is useful when it prevents a larger rollout. Do not preserve a system solely because creating it took effort or because its labels look especially official.

Field Tests

Run a Seven-Day Friction Audit at Home

A Small Loop Fieldbook guide · Updated 2026-07-19 · 4 min read

Quick answerRun a seven-day friction audit by choosing one low-risk household routine, defining its trigger and finish, and logging each attempt with date, point of delay, observable cause, workaround, and unfinished result. Group repeated snags after the week, count events without confusing frequency with severity, and choose one reversible change with the users' consent. Repeat the same log for another seven days, then keep, revise, remove, or appropriately escalate the change. Protect private information and handle safety, access, maintenance, and high-stakes issues through qualified guidance.

Contents

Observe the snag before fixing the room
Define one start and one finish
Log five fields for seven days
Count events, not annoyance volume
Ask which condition can change
Run the change for another seven days
Keep, revise, or remove

Observe the snag before fixing the room

A seven-day friction audit records where one household routine slows, fails, repeats, or requires avoidable memory. Choose one routine—leaving the house, preparing lunch, doing laundry, receiving mail, or resetting a workspace—and observe it for a week before changing several things at once.

The field tests section uses short evidence windows because a single irritating Tuesday may be a clue, a coincidence, or simply Tuesday maintaining its reputation.

Do not track another person's behavior without their informed agreement. Keep private schedules, health information, access needs, and conflicts out of a casual shared worksheet.

Define one start and one finish

Write the routine's trigger and end state. For example:

Trigger: the evening meal is cleared from the table.
End: dishes are handled, food is stored safely, surfaces are ready for breakfast, and needed items are set for morning.

Keep safety requirements separate from convenience preferences. Food storage, appliance shutdown, medication, security, fire protection, and other high-stakes steps come from authoritative instructions, not from whatever makes the checklist visually balanced.

Log five fields for seven days

Create one row per attempt with:

date and approximate start time;
person or people involved, only with consent;
point where the routine slowed or stopped;
immediate observable cause;
workaround and what remained unfinished.

Write “clean container unavailable” rather than “kitchen badly organized.” Write “printer asked for a password not stored in the approved location” rather than “technology hates us.” The first versions can be tested. The second versions may be true in spirit but have limited engineering value.

Use short notes. The audit should take under two minutes per attempt unless the project genuinely requires more detail.

Count events, not annoyance volume

At the end of seven days, group similar snags. Suppose there were 12 routine attempts:

missing item: 4 attempts;
unclear next step: 3;
waiting for a shared resource: 2;
interruption: 2;
no recorded snag: 1.

The total is 4 + 3 + 2 + 2 + 1 = 12. That does not prove the missing item is universally the “root cause.” It shows where this small test found the most repeated friction.

Record severity separately. A rare safety fault matters more than a frequent extra walk across the room and should be handled through the appropriate professional or official process.

Ask which condition can change

For the most repeated low-risk snag, test one reversible change:

move a commonly used tool to the point of use;
add a labeled home for a shared item;
clarify who owns the handoff;
place approved instructions where the step occurs;
reduce duplicate options;
prepare one supply during the previous reset.

Get agreement before moving shared property or changing another person's routine. Accessibility can depend on object location, lighting, reach, labels, sound, texture, or consistency; “tidier” is not automatically more usable.

The reset-checklist guide turns a verified sequence into a small handoff; small systems keeps that tool proportional.

Run the change for another seven days

Keep the same fields and compare the same routine. If missing-item snags fall but waiting increases, the system moved friction rather than removing it. If nobody uses the new location, ask whether it is visible, reachable, memorable, and compatible with how the routine begins.

Avoid changing storage, ownership, reminders, and timing together. A better week would not reveal which change helped, and a worse one would produce four suspects wearing identical alibis.

Keep, revise, or remove

After the second week, choose one outcome:

keep the change and document its location or owner;
revise one feature and test again;
remove it because the cost exceeded the benefit;
escalate a safety, access, maintenance, or relationship issue to appropriate help.

Archive only the notes worth retaining and delete personal data according to the household's agreement. The audit succeeds when it improves a routine or disproves a proposed fix. Both outcomes save future effort, which is the closest a clipboard gets to applause.