Anggriawan Sugianto

Your ego wants to run fast today.

Your system says run easy. Heart rate below 150 bpm. You should be able to have a conversation. Pace around 6:10–6:40 per kilometer.

Guess which one feels better?

The fast run feels good. You're breathing hard. You feel like you're "working." Your watch shows a nice pace. You can screenshot it for Strava.

The easy run feels like wasted time. Your pace is embarrassing. You're barely sweating.

As someone training yourself without a coach, this is your fundamental problem: Your ego and your system are in constant conflict.

When you have a coach, they resolve this conflict for you. The coach says, "Easy run today. I don't care how you feel." You do it because you paid them money and you respect their authority.

But when you're coaching yourself? You have to resolve that conflict internally. And if you're not ruthless about it, your ego wins. And when your ego wins repeatedly, you overtrain, get injured, or burn out.

This post is about learning to decouple your ego from your training decisions.

The Psychology of the Self-Coached Athlete

Here's what I learned in 2024: Your feelings about your training are not data.

You might feel like you need a hard run. Your body might actually need recovery.

You might feel strong today, but your HRV (heart rate variability) score tells you that your nervous system is fried.

You might feel like you're not working hard enough, but your training stress is already at critical levels.

You might feel energized, but your resting heart rate is elevated, suggesting overtraining is accumulating.

Most runners make training decisions based on feels. "I feel good, so I'll do a workout." "I feel tired, so I'll rest." This seems logical, but it's actually just your ego talking.

Here's the problem: your feeling is a lag indicator. By the time you feel tired, you've already been accumulating fatigue for days. By the time you feel strong, you might already be pushing into overtraining.

Data is a lead indicator. Your HRV drops before you feel tired. Your resting heart rate rises before you feel fatigued. Your sleep quality declines before your mood crashes.

In January 2025, I was scheduled for an easy run. 8 kilometers, heart rate around 145 bpm. I woke up feeling incredible. I'd slept well, I felt strong, I wanted to run hard.

My ego said: "Skip the plan, run hard today, you'll feel amazing."

My data said:

• HRV: 32 (below my baseline—indicates high stress)
• Resting heart rate: 62 bpm (elevated from my baseline of 58)
• Previous 5 days: All moderate-to-hard intensity
• Sleep last night: 6 hours (below my 8+ target)

My system said: "Run the easy run."

I ran the easy run. My watch showed I did 8 km in 52 minutes (6:30/km pace), which for an "easy" run felt slow. My heart rate stayed at 145–150 bpm the whole time.

And crucially, my HRV recovered to 42 by the next day.

If I'd run hard that day, I would have felt great for 1 hour. Then I would have paid for it with elevated HRV and higher injury risk for the next 3–4 days.

This is ego decoupling: choosing the data over how you feel.

Separating Ego from Data: Learning to Listen to Your Body

Here's the paradox: Learning to "listen to your body" is actually about learning to ignore what your body wants and pay attention to what your body needs.

Your body wants to sprint when it's rested. Your body needs steady easy running to build aerobic base.

Your body wants carbohydrates after a run. Your body needs adequate protein for recovery.

Your body wants sleep. Your body needs 8+ hours of it, not 6.

The self-coached athlete learns to distinguish between wants and needs. And the only way to do that is through data.

In 2024, I decided to track everything obsessively. Not for Instagram. But for clarity.

Every morning, before I ran, I measured:

• HRV (Heart Rate Variability) — How recovered is my nervous system?
• Resting Heart Rate — Is my heart having to work harder to maintain baseline?
• Sleep Quality — How many hours? How deep?
• Body Weight — Am I retaining water? (Sign of overtraining)
• Subjective Fatigue — 1–10 scale, how tired do I feel?

Every run, I tracked:

• Distance and Pace — What I actually did
• Heart Rate Zones — Did I stay in my target zone?
• Perceived Exertion — How hard did it actually feel?
• How I Felt Afterward — Crashed or energized?

Every week, I reviewed:

• Total Training Stress — Cumulative load from all workouts
• Fatigue Level — Is it trending up or down?
• Fitness — Are my times improving or declining?
• Easy/Hard Ratio — Am I doing 80% easy and 20% hard?

By January 2025, I had 9 months of data. Patterns emerged:

• When I ran too many hard days in a row, my HRV crashed 3–4 days later
• When I prioritized sleep over training, my fitness actually improved
• When I ate processed carbs after a run, my recovery was slower than whole grains
• When I did back-to-back long runs, my body responded better with one easy day between them
• When I ran fasted, my aerobic pace was slower, but my fat adaptation improved

None of this was obvious from "how I felt." It was only visible in the data.

This is what "listening to your body" actually means: collecting enough data that you can see what your body is actually telling you, beneath the noise of daily feelings.

The Pre-Mortem: Inverting Failure to Build Resilience

You know how most training plans work? You follow them perfectly, and then something breaks.

You get injured. You get sick. Your work stress spikes and you can't train. You go on a business trip and your schedule disappears. Suddenly, the plan falls apart.

But you didn't account for this. The plan assumed you'd follow it perfectly.

As a self-coached athlete, I use a technique from project management called a pre-mortem. Instead of waiting for something to go wrong, I imagine it has already gone wrong, and I work backward to prevent it.

Here's how it works:

Imagine it's November 8, 2026, 00:01. You're starting BTS Ultra 170K. The course is 170 kilometers with 7,439 meters of elevation gain. The cut-off is 42 hours. But you DNF (Did Not Finish) at 120 kilometers.

Now, ask: How did we get here?

Common failure modes:

• "I got injured in month 3 and lost 6 weeks of training."
• "I had a work crisis in August and couldn't train for 4 weeks."
• "I never figured out my fueling, and I bonked around 100 kilometers."
• "I didn't do enough vertical climbing training, and the mountains broke me."
• "I got sick twice during peak training and never recovered my fitness."
• "I over-raced early and was burnt out by November."

Once I identify the potential failure modes, I design my system to prevent them:

Failure Mode 1: Injury During Training

Prevention System:

• Strength training 2× per week
• No more than 10% volume increase per week
• Mandatory rest weeks every 4 weeks
• One rest day every week, non-negotiable
• Dynamic warm-ups before every run
• Foam rolling and mobility work 5× per week

Failure Mode 2: Work Stress Derailing Training

Prevention System:

• Training time is calendar-blocked (non-negotiable)
• If I miss a run for work, I do it the next day (no skipping entirely)
• During high-work periods, I reduce intensity (easy runs only) but maintain volume
• One long run per week minimum, even if work is chaotic

Failure Mode 3: Fueling Strategy Fails on Race Day

Prevention System:

• Practice fueling protocol on every long run (no exceptions)
• Try 3 different fuel options before settling on one
• Have a backup if your primary fuel isn't available
• Train your stomach with varying food, not just gels

Failure Mode 4: Insufficient Vertical Climbing

Prevention System:

• 3,000+ meters of elevation per week during peak phase
• At least one climbing workout per week
• Practice descending on technical terrain weekly
• Do a long run on mountains at least once per month

Failure Mode 5: Illness During Peak Training

Prevention System:

• Sleep non-negotiable (8+ hours every night)
• Immune support (zinc, vitamin D, probiotics)
• Manage stress aggressively
• Reduce training volume slightly when you feel a cold coming on

Failure Mode 6: Burned Out from Over-Racing

Prevention System:

• Race only 2–3 times before BTS Ultra 170K
• Each race serves a specific purpose (test nutrition, build confidence, practice pacing)
• Not every run is a workout; most are just easy miles
• Take 2 weeks off after each race before hard training resumes

By working backward from failure, I've designed a system that anticipates problems rather than reacting to them.

The pre-mortem isn't about catastrophizing. It's about being realistic. Something will go wrong. The question is: did you plan for it?