Problem Logging

Problem logging is the habit of writing down problems the moment they surface, so patterns and priorities become visible over time. The log replaces holding problems in memory or fixing each one in isolation.

The idea

Problems that only live in someone’s memory tend to get lost, downplayed, or fixed piecemeal without anyone noticing they keep recurring. A running log, such as a notebook, an issue tracker, or a simple list, turns scattered annoyances into a record. You can see which problems repeat, which ones cluster around the same root cause, and which ones are worth fixing or tolerating. It also separates noticing a problem from solving it. A busy moment does not force an immediate, half-considered fix.

When to use it

Any time work interruptions (“this is broken”, “this is annoying”) threaten to derail focused work
Recurring operational issues that no one has connected to a common cause
Personal or team retrospectives, where a log becomes the raw material for review

How to apply it

Capture the problem as soon as it’s noticed, briefly, without stopping to solve it.
Note when and where it happened.
Periodically review the log for repeats or clusters.
Prioritize fixes based on frequency and impact. Recency alone is a weak reason.

Watch out for

Letting the log become a graveyard that’s never reviewed.
Logging so much detail that capturing a problem becomes its own chore.
Using the log as a substitute for actually fixing anything.

Root Cause Analysis. A well-kept log surfaces the recurring problems worth root-causing.
Problem Solving. Logging feeds the intake stage of the broader process.
Common Cause. A log surfaces recurring issues that no one has connected to a common cause.