Plan a marathon base without the fluff

Plan a Marathon Base fails when the plan depends on willpower alone. These steps remove willpower from the equation.

What you need

• A notebook or notes app
• One hour of setup time
• A weekly review reminder

Step by step

1. Track for two weeks using a method you will actually keep.
2. Choose the smallest recurring action that moves the number.
3. Attach the action to something you already do daily.
4. Review at the checkpoint: keep what worked, shrink what did not, delete what you skipped twice.
5. Collect your current baseline numbers without judging them.

Tips

• Set a timer; scope grows to fill available time.
• Keep a 'problems' list while working instead of fixing mid-flow.
• The second rep is always faster — plan for it.

Common mistakes

• Skipping the verification step because the first attempt looked fine.
• Changing multiple variables between attempts, which makes failures unlearnable.
• Using the wrong tool 'just this once' and damaging the part.

FAQ

What if I get stuck?

Return to the last verified checkpoint and redo the failing step slowly. If it still fails, search for the exact error or symptom rather than the general task.

Do I need special equipment?

No. The lists above stick to essentials. Upgrade only after the basic version works and you know which limitation actually bothers you.

How do I maintain the result?

Add the final maintenance step to a calendar. Ten minutes monthly prevents most regressions.

Related guides

[[how-to-plan-trail-running]] [[how-to-plan-hill-repeats]] [[how-to-plan-race-day-fueling]] [[how-to-plan-recovery-weeks]]

That is the whole loop: prepare, change one thing, verify, repeat. Mastery is just reps with feedback.