+Cue
✓Tiny Start
+Completion
▦Visible Win
+Repeat
◎Identity
?Momentum Builders
↔Two Engines
▦Small Wins
?Friction Audit
▶Weekly Reset
✓Common Traps
+Caveats
◎Takeaway
✓TodayA cue answers one question: When does the behavior begin? Strong cues are specific, observable and connected to something that already happens.
What existing event in your day could trigger the new behavior?
Reduce the first action until beginning feels easy. The minimum version should be small enough to survive low-energy days.
Write your current goal. Then shrink the first step until it feels almost too easy.
Completion creates a clear endpoint. A small completed action often provides more useful feedback than a large unfinished intention.
Tracking makes behavior observable. A simple check mark, tally or streak can make progress visible before the larger outcome appears.
Monitoring is useful, but it does not guarantee success in every context.
Repetition in a stable context reduces repeated decision-making. Consistency of context can matter as much as intensity.
Treat one miss as information. Repeated misses indicate that the system needs revision.
The system generates observable behavioral data.
Each completion becomes a small piece of evidence that the behavior can occur.
Repeated successful execution can strengthen confidence in the process.
Over time, repeated evidence can contribute to identity-related beliefs.
Rate each factor mentally from 1 to 5. Start with the lowest score.
Creates energy, meaning and willingness to begin.
Shapes the conditions under which behavior occurs.
Small wins can reduce resistance, make progress visible and create opportunities for reinforcement.
Open the item that sounds most like your situation.
Likely issue: Start friction. Return to Tiny Start.
Likely issue: Time friction. Return to Cue.
Likely issue: Visual friction. Make the cue obvious.
Likely issue: Social or environmental friction. Redesign the surroundings.
Likely issue: Recovery friction. Use a restart rule and return to Repeat.
Tap each step in order.
Choose one priority for the coming week.
Set the cue and arrange the environment before action is required.
Perform the minimum version of the behavior.
Record whether the behavior occurred.
Look for patterns, obstacles and helpful conditions.
Change the system, then begin the next cycle.
Define a minimum version. Partial success still gives useful behavioral data.
Rewrite the goal as an observable action with a cue or time.
Choose one priority habit for seven days.
Attach the behavior to a reliable existing event.
Use one visible check mark per completed action.
Resume at the next available cue. Do not wait for a new week.
This framework is a practical behavior-design tool. It is not a claim that every outcome is fully under personal control.
Use the model for experimentation, not self-judgment.
The loop lowers the difficulty of beginning, makes progress visible and creates repeated evidence over time.
Use this fill-in structure.
Behavior: ____________________
Cue: After ____________________
Minimum action: ____________________
Tracking method: ____________________