A repeated behaviour usually happens somewhere, after something and for a reason. If you want to change it, those details can be more useful than a stronger declaration that tomorrow will be different.
- 01Observe one instance
- 02Alter the environment
- 03Choose a substitute
- 04Review without drama
Observe one instance
Record what happened immediately before the behaviour, where you were and what you were trying to obtain or avoid. Keep the description factual. A notification, an unclear task or a difficult transition may be part of the sequence.
Do not assume every behaviour has one simple cause. The point is to identify a plausible intervention, not to diagnose yourself from a short checklist.
Alter the environment
If a notification repeatedly interrupts writing, change the notification setting during that work. If you open a distracting application when a task becomes unclear, leave a specific next action in the document before the work block begins.
Make the desired action easier to reach and the unwanted action less automatic. Small changes can be worth testing when they match the actual sequence.
Choose a substitute
Removing an action may leave the original need untouched. A short break, a question to a colleague or a clearer task boundary may serve that need more effectively. Decide what you will do at the familiar cue rather than relying only on what you will stop doing.
Review without drama
Compare a few instances and adjust. Some habits involve needs that deserve professional support; a workflow tweak is not a universal remedy. For ordinary work routines, the practical goal is a setting that supports the intended behaviour more reliably than a resolution alone.