Chapter 14 / 9 min
Build Your Rules of Engagement
Replace vague intentions with specific rules across access, timing, format, and stopping.
A rule is useful only if it tells you what happens at the moment of temptation.
Four dimensions
Access asks where and on which devices the activity may happen. Timing asks when it may happen. Format asks which version is permitted. Stopping asks what ends the session. Together they turn intention into operating instructions.
A weak rule says, 'Use YouTube responsibly.' A useful rule says, 'YouTube is available on the television after 7:00 p.m. I select the video before opening the app. Autoplay remains disabled. The session ends after two videos.'
Rules are not identity statements
You are not declaring what kind of person you are. You are defining what happens when a predictable situation appears. Rules should be reviewed and edited when evidence changes. If a rule is too strong to follow, weaken it until it works. If it fails repeatedly, strengthen the environment around it.
Start with the primary defense target from your audit. One strong rule for one activity is more useful than twelve vague hopes.
Rules need enforcement points
A rule should answer the question that appears at the moment of temptation. Where is the device? What time is it? Which version is allowed? What counts as done? If the rule does not answer those questions, it will be replaced by mood.
Rules also need enforcement points outside the moment itself. Autoplay is disabled before the session. The phone charges outside the bedroom before fatigue. The shortcut is removed before the task transition. The device rule is made while you are calm.
Review evidence, not vibes
After a week, review the rule by evidence. Did it reduce unplanned starts? Did it protect sleep? Did it make task initiation easier? Did it create resentment so strong that you abandoned it? Did it need more friction or less ambition?
A rule is not a vow. It is an operating instruction that can be revised when the evidence changes. The best rules are stable enough to trust and humble enough to edit.
Smallest useful first step
Write one complete rule for the primary defense target. It must include access, timing, format, and stopping. If any dimension is missing, the rule is not finished.
Field application
Test each rule by imagining the exact moment it will be used. You are tired, the device is nearby, the task is uncertain, and the old behavior is available. Does the rule tell you what to do without further interpretation? If not, it needs more operational detail.
A complete rule usually contains one sentence for access, one for timing, one for format, and one for stopping. Access defines where the activity may happen. Timing defines when. Format defines which version is allowed. Stopping defines the end. If the rule has all four, it can function under pressure.
Rules should be few enough to remember and strong enough to matter. Begin with the primary defense target and one vulnerable window. Expand only after the first rules become ordinary.
- Access: where and on which device.
- Timing: when and when not.
- Format: selected version, not open-ended entry.
- Stopping: the exact endpoint.
Write one complete rule
Diagnostic question: Which current rule is too vague to enforce?
- Choose one target activity.
- Define access, timing, format, and stopping.
- Test whether another person could follow the rule without knowing your intentions.
Key takeaways
- Good rules are concrete, narrow, and editable.
- Access, timing, format, and stopping cover most digital risk.
- The plan builder turns audit results into a one-page operating plan.