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.
![Why Does Your System Only Work When You Feel Like It? (The Two Parts Every System Actually Needs) Every system that holds has the same starting point: a fixed trigger and one small, defined action. The Trigger-Action Designer builds both in about 7 minutes, the two parts most plans skip in favor of just deciding to try harder. A system is a structure, not a feeling At IBM, we didn’t manage large accounts by hoping the team felt inspired on a given Tuesday. We built fixed checkpoints, specific and repeatable. I didn’t think of that as a life skill at the time. It is one. A trigger has to be fixed, never “whenever I feel like it,” and an action has to be small enough to do without deciding. Who this is for, and how long it takes About 7 minutes. For anyone who has an intention but no system carrying it yet. What’s inside A trigger field. An action field. A worked example. How to get the most out of it Resist making the action bigger than it needs to be. Small enough to do without deciding is the whole point. What changes if you actually do this The output is one designed system start. The outcome is that the action becomes something you don’t have to decide on. The impact is that your intention gets a structure to run on. Download The Trigger-Action Designer [Download button placeholder, to be added.] Next step: The Follow-Through Tracker, which adds the part most systems skip and runs the whole thing for the first time. FAQ How is this different from the full Continuity Design Template? The full template includes the follow-through step too, in one sitting. This is the first half, for a quick start. What if I can’t think of a good trigger? Anchor it to something that already happens every day, closing your laptop, making coffee, a specific time. Consistency matters more than cleverness. Does this work for team systems, not just personal ones? Yes. The same trigger-and-action logic applies to a team habit as much as a personal one.](https://yassinebentaleb.com/wp-content/uploads/2026/07/Why-Does-Your-System-Only-Work-When-You-Feel-Like-It-The-Two-Parts-Every-System-Actually-Needs-350x250.png)
