In IT service management, a single support ticket rarely tells you anything. The real signal shows up on the third or fourth repeat, when the same kind of incident keeps landing on the same kind of system, at the same kind of moment. One ticket is an event. Three tickets are a pattern.
Most self-awareness advice treats a single strong reaction, a single hard week, a single argument, as if it were the whole diagnosis. It isn’t. It’s one ticket.
Three short logs make the pattern visible instead of guessed at.
Key Takeaways
- A single reaction, argument, or hard week is one data point, not a diagnosis, the same way one support ticket rarely reveals anything on its own.
- The Before Log tracks the five minutes before you procrastinate on something you’d normally just do, not the task itself.
- The Reaction Log tracks which comments or feedback land harder than their size should justify, and who said them.
- The Good-Decision Log tracks the one decision each week you’re glad you made, along with where you were and what state you were in.
- The pattern only becomes visible when you read all three logs together after two weeks, not by reviewing any single entry alone.
The Before Log. For two weeks, write one line right before you procrastinate on something you’d normally just do: what happened in the five minutes before. Not the task itself, the five minutes before it.
The Reaction Log. For two weeks, write down the specific comment, compliment, or piece of feedback that lands harder than its size should justify. One line: what was said, and by whom.
The Good-Decision Log. At the end of each week, write down the one decision from that week you’re glad you made. Not the outcome, just the decision. Note where you were and what state you were in.
After two weeks, read all three logs side by side, not each one alone. The pattern isn’t in any single entry, it’s in what repeats across entries, the way a repeated support ticket points somewhere real underneath.
