Anggriawan Sugianto

An injury doesn't appear overnight.

It builds. Slowly. Quietly. Usually while you're ignoring the warning signs.

You feel a twinge. You think, "It's nothing, just a little soreness." You keep training.

Two weeks later, the twinge becomes a persistent ache. You think, "Hmm, I should probably address this." You keep training.

Four weeks later, you can't run at your target pace. You think, "Okay, this is a real problem." You finally see someone.

By then, you've lost 6 weeks to deconditioning because you didn't address it when it was a twinge.

Learning to identify red flags—the early warning signs of injury—is how you stay healthy through 170 kilometers of training.

ASICS Running Club 2024

Cardiovascular and Structural Red Flags

There are two categories of red flags: ones that signal overtraining or inadequate recovery, and ones that signal structural problems.

Overtraining Red Flags:

These are signs that your nervous system is fried, your recovery is insufficient, or your training load is too high:

• Elevated resting heart rate: Your baseline RHR is 58 bpm. If it climbs to 64+ bpm consistently over 3+ days (not just one elevated morning), this signals overtraining.
• Crashed HRV: Your baseline HRV is 39. If it drops below 30 for consecutive days, your nervous system is stressed.
• Persistent fatigue: You feel tired even after rest days. Your legs feel heavy. Your motivation is gone.
• Elevated morning heart rate after hard workouts: After a tempo run, your morning HR should return to baseline within 24 hours. If it's still elevated on the second day, you didn't recover.
• Elevated resting heart rate during runs: Your heart rate during easy runs is creeping up. What used to be 145 bpm now requires 155 bpm to maintain the same pace. This signals fatigue accumulation.
• Sleep disruption: You're lying awake. You're waking up frequently. You're not sleeping deeply even though you have 8 hours in bed.
• Mood changes: You're irritable. You're anxious. You're having trouble concentrating.

When I see 3+ of these signs simultaneously, I immediately reduce training intensity (not volume) and prioritize sleep and recovery.

Structural Red Flags:

These are warning signs that something is biomechanically wrong and injury is developing:

• Pain that appears in the same spot consistently: Sharp pain in your left knee on descents, aching in your right shin on long runs—these are structural problems, not just soreness.
• Pain that gets worse over the course of a run: You feel fine at kilometer 10, but by kilometer 25 the pain is significant. This suggests a mechanical problem that accumulates with volume.
• Asymmetrical pain: One leg hurts, the other doesn't. This suggests either an injury on that side or a compensation pattern.
• Pain that doesn't improve within 2 weeks of rest: Normal training soreness should resolve with 2–3 days of reduced intensity. If it persists beyond 2 weeks, it's structural.
• Swelling or visible inflammation: Puffiness around your ankle, knee, or hip. Warmth in the joint. Visible bruising.
• Altered running gait: You're limping slightly. You're shifting weight to one side. You're shortening stride on one leg.
• Pain that wakes you at night: Sleep is usually when inflammation decreases. If pain wakes you, the inflammation is significant.

For me, the most relevant red flag is right plantar fasciitis. I experienced this after the BDG Ultra 64K in 2024, when I ran macadam downhills. The repetitive impact on descent caused heel pain.

My approach to this vulnerability:

When I feel even mild heel pain, I:

1. Reduce impact volume (fewer long runs on hard surfaces)
2. Focus on technical trail running (softer landings, better technique)
3. Do calf stretches and plantar fascia release work
4. Ice if needed

When I see structural red flags, I immediately:

1. Stop running if pain is sharp or worsening
2. Reduce volume if pain is stable but present
3. Get professional assessment if pain persists beyond 2 weeks
4. Follow rehab protocol precisely

I don't ignore it. I don't "run through it." I acknowledge it and adapt my training.

Before you train for 170 kilometers, you need to understand how your body actually moves.

Not how you think it moves. Not how it looks in the mirror. How it actually moves under load, on fatigue, on mountains.

Most runners skip this step. They see a training plan, they start running, and they wonder why they get injured 12 weeks in.

The reason: they never did a baseline assessment.

In 2024, I spent time understanding my movement patterns. Not in a gym. In the real world: on roads, on trails, on mountains, under different conditions.

What I discovered surprised me. I had physical characteristics and movement tendencies I wasn't fully aware of. Asymmetries that would eventually matter if I didn't account for them.

This post is about how to do the same for yourself.

Pocari Sweat Pacers & Sport Science Team 2024

Finding Your Natural Stride and Biomechanical Biases

There's no "perfect" running form. There's your running form. Your unique way of moving based on your body structure, your anatomy, your neuromuscular patterns, and your movement tendencies.

A biomechanical bias is a natural tendency in how you move. For example:

• You might naturally land more on your forefoot even when running easy
• You might have a tendency to overstride on descents
• You might lean forward from your ankles instead of your hips
• You might rotate your hips excessively when climbing
• You might externally rotate one leg more than the other

None of these are "wrong." They're just how your body is built. But if you don't understand them, they can become injury vulnerabilities.

In 2024, I asked for feedback on my running form from the Pocari Sweat Sport Science team when I was pacing in a race. They gave me valuable insights about my movement patterns. 

Later, I also learned that some runners in the community ask Dr. Maria (on Threads) for running form analysis, which is another great resource.

My own patterns:

• My natural cadence: I run at 173–177 steps per minute depending on the distance and effort. In 2025, my road marathons had a cadence around 173 spm (slightly below the often-recommended 180 spm, but efficient for my body). On my 10K race, it was 177 spm (faster pace, naturally higher cadence). This tells me my stride adjusts appropriately to effort level.
• My foot asymmetry: My right foot is 27.1 cm long, while my left foot is 26.9 cm—a 2 mm difference. My left foot is slightly wider than my right. This 2 mm difference might seem tiny, but it can create asymmetries in how I land and propel myself.
• My strength symmetry: I don't know if one leg is significantly stronger than the other. Both feel similarly strong. But I'm aware that I need to address strength training more consistently.
• My descent pattern: I have a tendency to brake excessively on downhills. This is where I see the most room for improvement in my form.

How to find your own patterns:

1. Film yourself running (from the side, from behind) on flat ground, on a hill, on a descent
2. Look for asymmetries (does one leg land differently? does one foot point differently?)
3. Check your foot characteristics (measure your feet; notice width, arch height, toe flexibility)
4. Ask the running community (post videos to group or submit to coaches like Dr. Maria for analysis; others see things you miss)
5. Note what feels easy vs. hard (climbing feels hard, descending feels easier—or vice versa?)
6. Get professional feedback (race organizers sometimes have sport science teams; use them)

Your movement patterns aren't good or bad. They're just data. And data helps you prevent injuries and move efficiently.

The hardest part of being self-coached isn't the training plan.

It's seeing yourself clearly.

You're terrible at this. We all are. We're biased toward believing we're working harder than we are, faster than we are, and smarter than we are.

I completed three 100K races in 2025 and felt like a genius. I told myself: "I've figured it out. I'm ready for 170K."

Then I discussed my data with an AI analysis tool and got honest feedback: "Your pace is inconsistent across the three races. Your fueling strategy showed improvement but still has fragile points. And you've never run sleep-deprived for 30+ hours, which is 50% of the 170K experience."

It stung. But she was right.

I had achieved something real (three 100Ks in eight weeks: BDG 100K in 30h 17m, Trans Jeju 100K in 23h 37m, BTS 100K in 27h 24m), but I'd overestimated my readiness for 170K. My ego had inflated my assessment.

This is why you need external perspective. Not necessarily a coach. A support system.

One of my support systems: CodeRunners IA-IF ITB 2025

Self-Assessment Without Self-Deception

As a self-coached athlete, you can't eliminate bias. But you can manage it by surrounding yourself with people and tools that give you honest feedback.

I built a personal support system for my ultra training. Not a full-time coach. An ecosystem of resources:

The Technology: I use AI tools to analyze my training data, race data, and decisions. AI doesn't have ego or emotional attachment. When I ask, "Is my current training plan realistic for BTS Ultra 170K on November 8?", it gives me objective feedback based on my actual performance metrics. It's like having a wise coach who never sleeps and never gets tired of answering questions.

When I was considering running four 100Ks in 2025, I ran the scenario through AI: training load, recovery capacity, injury risk. The feedback was clear: "Three races is optimal. Four introduces 23% higher injury risk with only marginal fitness gains." I did three instead. Better decision.

The Community: My running community from EPIC Trail. These are people at similar fitness levels running similar races. We share training updates, compare notes, celebrate wins, and most importantly, commiserate about struggles.

When I was discouraged after a mediocre training run, someone from the community said: "One bad run is data. Five bad runs in a pattern. One bad run means nothing." Exactly what I needed to hear.

The Nutritionist: I use telemedicine (Halodoc/GoodDoctor) to consult with nutritionists when I need specific guidance. We've designed my race-day food plan together. I check in occasionally to update it.

When I complained that my stomach couldn't handle real food during runs, she said: "You're trying to eat too much too fast. Practice eating 200 calories per hour, not 400. Train incrementally." Changed everything.

The Strength Coach: I work biweekly with a strength coach from the ASICS Running Club. In a 90-minute session, they assess my movement, identify weaknesses, and prescribe specific exercises. Then I implement them on my own.

When I showed them my ankle instability, he said: "This is your limiting factor, not your aerobic capacity. Fix this first." I did single-leg work for few weeks. My ankle got stronger. My running improved.

Everyone has 24 hours.

But not everyone has the same energy budget.

Energy is different from time. You can have 4 hours free but be mentally exhausted. Or you can have 2 hours free but be completely fresh.

Most busy professionals understand this intuitively. They manage their calendar, they schedule meetings, but they never actually account for the energy cost of those meetings.

Then they try to add 10 hours of ultra training per week on top of it.

And they wonder why they're tired all the time.

As a CEO training for a 170-kilometer ultramarathon in November 2026, this is my central constraint. Not time. Energy.

Sharing Session @ CodeRunners

Time Blocking: Fitting Ultra Training into a 60-Hour Work Week

I run a company with ~200 employees. And I train for 170-kilometer ultramarathons.

People ask me: "How do you find the time?"

The honest answer: I don't find it. I create it. And I do this by treating training like a business priority, not a leisure activity.

Here's my weekly time block:

• Monday: Strength Training
• Tuesday: Easy Run
• Wednesday: Interval Run
• Thursday: Strength Training
• Friday: Threshold Run
• Saturday: Long Trail Run
• Sunday: Back-to-back Run

This is about 10% of my available waking hours. But it's concentrated in early mornings (or late evening) and scheduled like meetings.

The key insight: Most people don't lack time. They lack the willingness to treat training as non-negotiable.

If you told your boss, "I can't make that 5:30 PM meeting because I'm going to the gym," they'd be annoyed. But if you tell yourself, "I'm not running my planned long run because I had too many meetings," you just accept it.

As a self-coached athlete, you are the boss. You have to hold yourself to the same standard you'd hold an employee.

But here's what's actually going on: it's not about time. It's about energy. Let me explain.

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.

Organizing ITB Ultra Marathon 2025

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.

You don't need to read these posts in order. You also don't need to read all of them.

This isn't a book: it is a documentation of a system written as standalone observations about ultramarathon training. Think of it as a collection of field notes rather than a narrative arc. There are specific paths through the content depending on what you want to understand.

BTS Ultra 100K - 2025

If You Want to Finish Your First 100K

If you want to understand the minimum viable system to finish a 100 kilometer ultramarathon, here is your reading path:

Foundation:

• The Algorithm of Endurance: Why I run.
• The Architecture of Endurance: What you're learning (the system I built).
• Bio-Structural Audit: Understand your body before training.
• Red Flags & Screening: Prevent injury before it happens.

Then Skip Straight to Ultra:

• The Mindset Shift: Why 100K is different from marathoning.
• Strategic Periodization: How to structure 6 months of training.
• Ultra-Specific Work: Building durability and vertical climbing.
• The Ultra Stomach: How to fuel for 20 plus hours.
• Psychology & Grit: Mental frameworks for the hard moments.
• Crew Management: How your support team makes or breaks your race.
• Problem-Solving: What to do when things go wrong.

Then (Optionally) Understand Why:

• Bioenergetics: How your body actually produces energy.
• Fuel Selection: Understanding metabolism and fat adaptation.
• Threshold Diagnostics: Measuring your actual fitness.
• Data Integration: Knowing what your watch is actually telling you.

This path takes you from identity → understanding your body → building ultra-specific fitness → executing a race → understanding why it works.

Total time: 6-7 hours of reading + 24 weeks of training.

In late 2024, I made a decision that seemed insane at the time: I was not going to hire a running coach.

Not because I couldn't afford one. Not because I didn't believe in coaching. In fact, I have seen the value of professional guidance firsthand. I was coached as part of the ASICS Marathon Team in 2023 and influenced by the Pocari Sweat Sports Science team while serving as a Pocari Sweat Marathon Pacer in 2024.

However, I realized something about myself: I think better when I understand the system, not just the directives.

A coach would tell me: "Run 10 kilometers easy on Tuesday. Do four repeats of 1600 meters hard on Wednesday."

I would follow the plan. If it worked, great. If it did not, I would blame the plan or myself, but I wouldn't actually understand what happened.

Instead, I decided to reverse-engineer my own training system from first principles, synthesizing methodologies from foundational texts like Daniels’ Running Formula, 80/20 Running, and Advanced Marathoning.

Trans Jeju 100K - My first UTMB World Series

Why You Don't Need a Coach (But You Need a System)

I'm not anti-coach. Good coaches are valuable. But most runners don't need a coach. They need a system. Here's the difference:

A coach is a person who:

• Knows your history, injuries, and psychology.
• Adjusts your plan in real-time based on how you're responding.
• Provides accountability and motivation.
• Costs $30 to $300 (Rp5.000.000) per month.

A system is a framework that:

• Is replicable and teachable.
• Removes guesswork from training decisions.
• Can be personalized without external help.
• Costs $0 (or the price of understanding it).

As a busy professional, I don't have the bandwidth for a coach. But I have the intellectual capital to understand training systems. I have the time to document what works. And I have the obsession to test it rigorously.

This is what a system gives you: the ability to adapt to your reality.

Because life isn't static. Work stress spikes. You get injured. You travel. Your schedule changes. A fixed training plan breaks under this complexity. But a system you understand can flex.

When my work spiked in August 2025, I didn't abandon training. I reduced intensity while maintaining volume. I ran 80% easy runs instead of 60%. My fitness didn't decline. It actually improved because I managed stress better.

A coach's plan would have said: "Follow this or don't." My system said: "Adapt while maintaining the principles."

There is a moment that happens around kilometer 80 of an ultra trail race. Your legs feel like concrete. Your mind is screaming. The pain isn't sharp anymore; it is dull and omnipresent, as if your body is slowly surrendering to physics.

I hit that moment three times in 2025.

Three ultra trails in eight weeks. Three 100-kilometer races. Three times I convinced myself that my legs would keep moving when my brain insisted they were finished. Three times I discovered something I did not know about myself.

But here is what surprised me most: it was not the ultramarathon that changed me. It was the realization that everything I had learned as a business technologist, including every framework, system, and principle I built while running my company, applied directly to running 100 kilometers through mountains.

This is my origin story in running.

BDG Ultra 2025 - My first 100K

The Desk-to-Trail Transition

My name is Anggriawan Sugianto. I am the Chief of Suitmedia, a digital consulting firm in Jakarta with over 200 employees. I spend most days in optimizing workflows, analyzing spreadsheets, and making decisions that affect growth.

I also run 100-kilometer races through mountains.

These two facts may seem disconnected, but they are not. They represent the same skill applied to different domains.

In 2023, I started running seriously. I do not mean the casual 10-kilometer runs often seen on social media. I mean distance: the kind that takes hours, demands total consistency, and reveals your true character.

At first, it was for health. Then it became a test. Finally, it became an obsession with understanding how systems work.

Most people who run endurance distances follow one of two paths:

1. Outsourced: Hire a coach, pay the fee, and follow the plan.
2. Amateur: Download a generic plan from the internet and hope for the best.

Both approaches assume you need an external structure or that you cannot think for yourself. I rejected both.

As a strategist, I have spent a decade learning to think in systems. I build products using frameworks. I make hiring decisions using matrices. I structure companies around principles rather than hunches.

It seemed illogical to abandon that mindset the moment I wanted to run 100 kilometers.

In late 2024, I decided to become my own coach.

This was not due to arrogance, but because I had a unique advantage: the ability to reverse-engineer the system. I had the time to test hypotheses and document what actually works.

By 2025, I had proven the system works.