The Complete Guide to Interpreting Power Data: What NP, IF, and VI Really Mean, and How to Spot Problems from a Single Ride

Two riders complete the same route on the same day, upload their files at home, and both have an average power of 180 watts over the same three-hour duration. At first glance, these look like two identical training rides. But one of them cruises through an easy recovery ride the next day, while the other lies around for two days and still feels like their legs are empty.

The difference isn’t in the average power—it’s in how those 180 watts were produced. One rider held a steady output between 170 and 190 watts the whole way; the other did ten three-minute 300-watt efforts to chase wheels, punctuated by long coasting stretches. The power meter records both as the same number, but the body completely disagrees.

Normalized Power (NP), Intensity Factor (IF), and Variability Index (VI) are three metrics designed specifically to address this problem. They aren’t numbers for showing off—they’re a set of diagnostic tools that let you look at a single FIT file and see what actually happened during the ride, where things went wrong, and what to adjust next time.

This article will break down the logic behind these three metrics, then spend the bulk of its length on the genuinely useful part: how to spot problems in a ride from its data.

---

1. Why Average Power Lies

Power is an “instantaneous value,” and it fluctuates violently

Heart rate is a physiological response—it has inertia and changes smoothly. Power is not. Power is your mechanical output at the pedal at any given moment, and it can jump from 0 to 600 and back to 0 within a single second. Coasting downhill is 0 watts, braking through a corner is 0 watts, stopping at a red light is 0 watts, and a hard out-of-the-saddle surge can momentarily spike to six or seven times your body weight in watts.

When you take the arithmetic mean of such a wildly fluctuating series, you get a number that is “mathematically correct but physiologically meaningless.” The arithmetic mean assumes every watt is worth the same—that the 100th watt and the 400th watt cost the body linearly equal amounts. That assumption is completely wrong.

The physiological response to power is nonlinear

This is the core of understanding NP. Here are several well-established physiological principles (individual variation is large; we’re only talking about direction here, not precise numbers):

First, the recruitment ratio of energy systems rises steeply with intensity. At low intensity, fat can contribute a significant share of energy. As intensity rises, the proportion of glycogen use increases rapidly. This increase isn’t proportional—it accelerates. Producing the same extra 50 watts, going from 120 to 170 versus from 280 to 330, has vastly different metabolic implications.

Second, lactate production and clearance are a dynamic balance. Below the lactate threshold, the lactate produced can largely be cleared, and you can sustain that effort for a long time. Once you cross the threshold, the production rate exceeds the clearance rate, blood lactate begins to accumulate, and the rate of accumulation accelerates sharply with how far you exceed it. That’s why you can ride for three hours just below threshold but only manage twenty minutes just above it.

Third, oxygen uptake has a “slow component.” Holding a fixed power at high intensity doesn’t keep your oxygen consumption at the theoretically corresponding value—it keeps creeping slowly upward. In other words, holding a high power output gets progressively more expensive over time.

Fourth, recovery isn’t free. Coasting after a hard surge doesn’t return you to your pre-surge state. Phosphocreatine resynthesis, lactate clearance, and restoration of the muscle’s internal environment all take time, and during that recovery period your body is still paying the bill.

Add these four points together and the conclusion is clear: high-intensity segments impose a metabolic cost on the body far greater than their weight in the arithmetic average. The brief high-power spikes in a ride contribute far more fatigue than they contribute to the average.

A concrete comparison

Suppose two one-hour rides:

Scenario	Content	Average Power	How It Feels
A: Steady cruising	Holding a constant output just below threshold the whole time	200 W	Tired, but manageable and repeatable
B: Chasing and coasting	Half an hour of repeated surges around 350 W, half an hour of coasting at 50 W	200 W	Legs destroyed, noticeable residual fatigue the next day

The average power is identical, but the training stimulus and fatigue cost are completely different. Average power only answers “how much work did you do,” not “how much does that work cost.” NP exists to answer the second question.

---

2. Normalized Power (NP): What It’s Actually Calculating

The calculation process

NP is calculated in four steps, and the order can’t be changed:

1. Take a 30-second rolling average of the power data, producing a smoothed curve.
2. Raise each smoothed value to the fourth power.
3. Average all the fourth-power values.
4. Take the fourth root of the result, giving you NP.

Each step is designed to model something specific.

Step 1: What the 30-second rolling average models

The body doesn’t respond to power on a second-by-second basis. When you jump power from 150 to 300, your oxygen uptake, cardiac output, and muscle blood flow don’t catch up in the next second—they have a rise time constant on the order of tens of seconds. Conversely, when you back off and coast, those physiological responses don’t drop back down immediately either.

The 30-second rolling average is a rough proxy for this “physiological inertia.” What it does is smooth out the ultra-short-term fluctuations the body barely registers. A three-second surge through a corner barely registers with the body; a 40-second climb effort is fully felt. The rolling average lets the latter survive while diluting the former.

This also explains a common question: why doesn’t a sprinter’s 1200-watt, ten-second sprint boost NP nearly as much as you’d expect? Because those ten seconds get flattened across the 30-second window. NP isn’t trying to capture instantaneous explosive power—it’s capturing metabolic load on a medium-to-long timescale.

Steps 2 and 4: What the fourth power and fourth root do

This is the most misunderstood part of the entire formula. The fourth power isn’t some mysterious physiological constant—it’s a weighting amplifier.

The effect of raising to the fourth power is: the higher the power segment, the greater its weight in the final average, and that weight grows at a fourth-power rate. Doubling the power becomes sixteen times the weight after the fourth power. This corresponds directly to the “disproportionate metabolic cost of high intensity” discussed earlier.

The final fourth root brings the number back into watts, so it can be compared directly with average power and FTP. Without the root, you’d get an astronomical number with no readability.

So the whole of NP can be understood this way: NP is a hypothetical steady power—if you rode the entire ride at that fixed power, the metabolic cost would be roughly the same as your actual ride’s up-and-down effort.

NP’s limits of applicability

NP isn’t universal. It distorts in the following situations:

• Very short efforts: With less than 20 minutes of data, the 30-second rolling average window takes up too large a share, and NP’s meaning weakens.
• Descents dominated by pure coasting: A long downhill section pulls NP down, but your body is actually resting—NP instead underestimates the cost of the preceding climb. This is why, for rides like Wuling where “the climb is long and the descent is also long,” you should isolate the climb segment and look at its NP separately rather than the whole ride.
• Extremely steady indoor trainer efforts: Here NP is nearly equal to average power, so NP adds no extra information.
• Power meter dropouts or zero-offset anomalies: A spurious high-power spike, amplified by the fourth power, can seriously contaminate NP. Before analyzing, check for unreasonable spikes.

---

3. Intensity Factor (IF): How Hard This Ride Is for You

Definition and meaning

IF = NP ÷ FTP.

It’s a unitless ratio that personalizes NP. The same ride with an NP of 220 watts is completely different in difficulty for someone with an FTP of 200 versus someone with an FTP of 300. IF answers: where does this ride’s intensity fall relative to your own ability?

An IF of 1.0 means the ride’s metabolic intensity is roughly equivalent to riding at FTP the entire time. By the definition of FTP, you can only sustain that for about an hour.

Where Should IF Fall for Different Durations

This requires great care: any precise table claiming “X hours corresponds to IF X.XX” is false, because it depends heavily on individual endurance profile, terrain, group dynamics, and whether FTP is set correctly. Only directional general rules can be stated:

• The longer the duration, the lower the sustainable IF must be. This is the most solid rule. You cannot sustain the same IF for a five-hour ride as for a one-hour time trial.
• For short time-trial efforts, IF will be close to or slightly above 1.0; the shorter the effort, the more likely it exceeds 1.0, because anaerobic capacity can temporarily boost output.
• For a one-hour all-out time trial, IF will be right around 1.0 — that is, by definition, what FTP represents.
• For mid-distance high-intensity group rides or climbing races, IF is typically clearly below 1.0, but still high.
• For long-distance events or endurance rides, IF will be significantly lower, and the longer the ride, the lower it goes. On a long, high-climbing ride like Wuling, if your overall IF is absurdly high, it usually doesn’t mean you’re strong — it means your FTP is set too low, or you rode too aggressively and will pay for it later.
• Recovery rides should have an IF so low that you wonder “did I even train?” — that’s exactly what a recovery ride should feel like.

The most practical use of IF is not comparing it to someone else’s chart, but comparing it to your own past records. On the same route, with the same riding style, if your IF goes from 0.72 to 0.78 with the same perceived effort, that’s a signal of improvement or that your FTP needs retesting. Conversely, if IF stays the same but you feel completely exhausted, that’s a warning sign about your recovery status.

The Biggest Trap with IF

IF is built entirely on FTP. If FTP is set wrong, IF breaks entirely — and it breaks convincingly, because the numbers still look reasonable. This will be covered in detail later.

---

IV. Variability Index (VI): What Your Riding Style Looks Like

Definition

VI = NP ÷ Average Power.

VI doesn’t address intensity; it only addresses how smooth your output is. The closer VI is to 1.0, the more stable your power; the higher the VI, the more your power surges and fluctuates.

Its beauty lies in this: VI is almost unaffected by FTP settings. Even if your FTP is completely wrong, VI remains trustworthy. When you suspect all your data is wrong, VI is the last thing you can still believe.

VI Characteristics by Riding Type

Riding Type	Typical VI Direction	What It Represents
Indoor trainer ERG mode	Extremely close to 1.0	Power is locked by the machine, almost no fluctuation
Flat solo effort, individual time trial	Very close to 1.0	Good pacing control — this is what a time trial should look like
Steady long climb (e.g., Provincial Highway 14A)	Close to 1.0, slightly higher	Small fluctuations from gradient changes and corners
Rolling-terrain endurance ride	Moderately low	Natural differences caused by climbs and descents
Group road race	Clearly elevated	Repeated surges from starts, position fighting, drafting, and attacks
Urban commuting, stop-and-go	Very high	Traffic lights, intersections, pedestrians, acceleration from stops
Riverside path interrupted by gates	Elevated	Frequent deceleration and re-acceleration

How to Use VI

VI is an “intent checklist.” The key question is always: Does what you intended to train today match the VI you actually produced?

• Your workout today was “two hours of steady endurance riding,” but VI came out high → you weren’t steady at all; you were stop-and-go. The quality of this ride is not what you thought it was.
• Your workout today was “time trial simulation,” but VI came out high → you have a pacing problem, possibly pushing too hard on climbs and completely letting off on descents.
• You did a group race today — a high VI is expected. Looking at VI in this case is meaningless; what you should look at is your power distribution within the group and the number of sprints.
• You’re climbing Wuling but see an elevated VI → your power control is unstable across gradient changes, meaning you’re likely grinding by feel rather than pacing.

VI has no absolute good or bad — only “does it match your training intent.” A high VI in a group race is normal; a high VI in a steady endurance ride is a failure.

---

V. TSS: Compressing Intensity and Time into a Single Number

Concept

TSS (Training Stress Score) aims to do something simple: combine “how hard” and “how long” into a single overall load metric, allowing you to compare across different rides.

Its logic uses IF as the intensity weight, multiplied by time, then normalized. The anchor point is clear: one hour at FTP equals 100 TSS. From this anchor, the higher the intensity and the longer the duration, the greater the TSS; and because the intensity term is weighted in squared form, intensity affects TSS more steeply than time does.

Accumulated TSS can then derive trend indicators of training load: long-term chronic load (often called fitness), short-term acute load (often called fatigue), and the difference between the two (often called form). The value of this framework lies in looking at trends, not at single-day numbers.

Limitations of TSS (Important)

First, TSS is a proxy for purely mechanical load; it does not include muscle damage or neural fatigue. The same 200 TSS — one flat steady cruise versus one high-intensity climb with fast descents — has completely different actual impacts on the body. The eccentric load of long descents and the tension of bike handling stress are entirely invisible to TSS.

Second, TSS does not include environmental cost. Three hours baking on a riverside path at noon in a Taiwanese summer, with extreme humidity and soaring body temperature, versus the same workout on an indoor trainer in air conditioning — TSS may be identical, but the actual cost is vastly different. Heat, wind, road conditions, sleep, work stress — TSS knows none of it.

Third, cross-sport comparisons are almost meaningless. Running TSS uses a different model, and swimming yet another. Forcing 100 TSS of cycling and 100 TSS of running to be equivalent loads will seriously underestimate the impact load of running.

Fourth, TSS fully inherits FTP errors. If FTP is set too low, all TSS inflates across the board. You’ll think you’re training hard every week, when in reality it’s just numerical inflation.

Fifth, chasing TSS distorts training behavior. Adding an extra hour of ineffective moderate intensity just to hit a number is why many people get stuck in plateaus. TSS is a result of training, not a goal of training.

---

VI. Key Section: How to Spot Problems in a Single Ride’s Data

This section is the core of the entire article. Each case below follows the format: data symptom → possible causes → what to adjust. Note that the same set of symptoms often has multiple possible causes, and must be interpreted together with that day’s subjective feel, weather, nutrition, and sleep records — never draw conclusions from numbers alone.

Case 1: Power Sliding Downhill Throughout a Climb

Data Symptoms: Split a long climb (e.g., Provincial Highway 14A toward Wuling, or the continuous Fengguizui section) into three segments—beginning, middle, and end. Average power drops in a stepwise fashion, with the final third clearly falling off a cliff. Heart rate may hold steady or rise slightly, and cadence usually drops along with it.

Possible Causes:

1. Starting too hot. This is the most common cause, especially when starting a climb in a group ride or when someone sets a hard pace up front. Energy spent early cannot be paid back later—climbing has no compensation mechanism. Every extra bit of effort you use early on must be repaid many times over later.
2. Insufficient fueling. Glycogen consumption on long climbs is severely underestimated, and it’s easy to forget to eat when focused on climbing. A power drop accompanied by fading concentration, shaky hands, and unexplained low mood is a classic sign of energy depletion.
3. Core temperature too high. In Taiwan’s summer, high heat and humidity at lower elevations (e.g., Puli to Wushe) raise core body temperature, causing blood flow to the skin to compete with cardiac output, forcing power down.
4. Dehydration. This often occurs together with the heat issue, and the two worsen each other.
5. Simply insufficient fitness. If all of the above are ruled out, your endurance base hasn’t been built yet. That’s not a problem—it’s just where you are right now.

What to Adjust:

• Deliberately hold back for the first ten to fifteen minutes of the climb, going slightly lower than what you “feel” you should be doing. The correct strategy for a long climb is conservative at the start, steady in the middle, and only if you still have something left in the tank, let it out at the end.
• Establish a time-driven fueling rhythm—don’t wait until you’re hungry to eat. Set a watch reminder to take in carbs and fluids at fixed intervals.
• Adjust your targets on hot days and accept that power will be lower than on cool days. Don’t use cool-weather numbers as the standard and chase them hard.
• Do a segment comparison next time on the same climb: if the power gap between the beginning, middle, and end segments narrows to a very small margin, your pacing has improved.

---

Case 2: “Junk Training” with High VI

Data Symptoms: You rode for three hours, average power wasn’t high, but NP was much higher and VI was clearly elevated. The power distribution chart shows a “polarized” pattern—large amounts of very low power (coasting, stopped at lights) mixed with scattered high-power spikes, with the moderate-intensity zone almost empty.

Possible Causes:

1. Wrong route choice. Urban roads, sections dense with traffic lights, or riverside bike paths with numerous gates and mixed pedestrian/bike crossings—you’re not training, you’re doing interval starts.
2. Poor group-riding habits. Hiding in the pack and not contributing at all, then falling off the back and chasing back on at full effort, repeating the cycle. The time is long, but the effective training stimulus is very thin.
3. No workout plan, riding by feel. Sprinting at every climb, coasting on every flat—there’s no stable target zone for the entire ride.

What to Adjust:

• Clarify the purpose of the training. If the goal is building an aerobic base, you need continuous, uninterrupted low-to-moderate intensity output. Those high-power spikes don’t help; they only add unnecessary fatigue.
• Change your route. In Taiwan, finding continuous, uninterrupted roads usually means heading to the suburbs or long climbs. It’s very hard to raise the quality of endurance rides within the city.
• Evaluate using “time spent in power zones” rather than average power. Look at how many minutes you actually spent in the target zone—that’s the real output of the ride.
• Accept a fact: three hours of stop-and-go riding may have less training value than ninety minutes of continuous, steady output.

---

Case 3: Heart Rate Rising, Power Falling in the Second Half

Data Symptoms: Split the ride into two halves. In the first half, power is high and heart rate is low; in the second half, power drops but heart rate rises or holds steady instead. The relationship between power and heart rate has become “decoupled.” This phenomenon is often called cardiovascular drift or power-heart rate decoupling. A common interpretation convention is to compare the “power/heart rate ratio” between the two halves; a change within a small range is considered normal, while a larger change warrants attention—but this threshold is an empirical convention, not a physiological law.

Possible Causes:

1. Dehydration. Plasma volume drops, stroke volume decreases, and heart rate must rise compensatorily to maintain the same cardiac output. This is the classic explanation.
2. Heat load. Core temperature rises, a large amount of blood flow is diverted to the skin for cooling, and blood flow available to working muscles decreases. In Taiwan’s summer, this is the main cause.
3. Insufficient aerobic endurance. If decoupling is still significant under cool conditions with adequate fueling, it means your aerobic base cannot sustain that intensity for that duration.
4. Pacing too hard in the first half. Overspending forces the physiological systems to work overtime compensating in the second half.
5. Energy depletion. When glycogen is nearly empty, the physiological cost of maintaining the same power rises.

What to Adjust:

• Rule out environmental and fueling factors first, then talk about fitness. Decoupling in extreme heat or a dehydrated state does not mean your aerobic system is weak.
• If it’s insufficient training, the prescription is to add more steady, long aerobic rides to let your body adapt to sustaining output over time.
• If you frequently experience significant decoupling under cool conditions, with normal fueling and moderate intensity, accompanied by abnormally high heart rate, chest tightness, or dizziness, this is not a training issue—please seek medical evaluation.
• Track changes in decoupling over time on the same route and at the same intensity target. This is one of the most practical indicators of endurance improvement.

---

Case 4: A Dip in the Power Curve at a Certain Duration

Data Symptoms: Plot your recent “best power curve” (maximum average power for each duration). Normally, it should be a smooth curve descending from high power at short durations to lower power at long durations. If there’s a clear dip in a certain duration range, it means your ability at that duration is relatively underdeveloped.

Interpretation Guide:

Dip Location	Typical Ability Gap	Possible Training Direction
Very short (a few seconds)	Insufficient neuromuscular explosive power	Short sprints, strength training
30 seconds to 1–2 minutes	Insufficient anaerobic capacity, can’t sustain short high-output efforts	Short intervals, lactate tolerance workouts
3–8 minutes	Weak VO₂max-related ability	Interval training in that range
20 minutes to 1 hour	Insufficient threshold ability	Sustained or long intervals in the threshold zone
Over 2 hours	Insufficient aerobic endurance and fatigue resistance	Extend ride duration, train under fatigue

Important Notes:

• A dip in the curve may simply mean “you haven’t trained that duration recently” rather than a true ability deficit. If you haven’t done any five-minute all-out efforts in three months, that segment will naturally be depressed. Check data density first, then talk about ability gaps.
• The curve only reflects the maximum effort you’ve ever produced—it’s a floor, not a ceiling.
• When addressing a “dip,” progress gradually; individual variation is large. Suddenly adding a large volume of high-intensity intervals significantly raises the risk of injury and overtraining.
• Match needs to goals. If you only ride long-distance events, a dip at the few-second level is irrelevant—no need to spend time fixing it.

Case 5: How to Read Left/Right Power Balance and Cadence

Left/Right Balance

Data Symptom: The power meter shows a left/right ratio deviating from 50/50, e.g., 46/54.

How to Interpret It:

• First, confirm how your power meter measures. A single-sided power meter (only installed on one side) measures one side and multiplies by two—it has no real left/right data at all, so any balance number it displays is meaningless. Only true dual-sided devices (dual-sided pedals, dual-sided crank arms) are worth discussing.
• Slight asymmetry is common. The vast majority of people are not perfectly symmetrical, and this alone requires no action.
• Watch for “changes” rather than “values”: If you’ve been 49/51 for a long time and one day it shifts to 44/56, or the asymmetry widens sharply as fatigue accumulates, that’s the signal—it could indicate a unilateral injury, a bike fit that has drifted, a cleat adjustment, or compensatory movement patterns.
• Asymmetry accompanied by pain needs attention. Pure numerical asymmetry with zero discomfort usually doesn’t need to be addressed. Do not deliberately alter your pedaling motion to chase a 50/50 split—that tends to create compensatory injuries instead.

Cadence

Data Symptom: Average cadence is very low for the entire ride (e.g., grinding a low cadence for extended periods on climbs), or cadence drops noticeably in the second half.

How to Interpret It:

• A drop in cadence is often an early indicator of fatigue, usually appearing before power drops. When you notice your cadence naturally falling in the second half, that’s your body telling you your reserves are running on empty.
• There is no single “correct cadence.” Optimal cadence is highly individual, depending on muscle fiber composition, gear selection, gradient, and riding style. Forcing yourself to mimic someone else’s cadence is pointless.
• On long climbs, insufficient gearing forces you into low-cadence grinding, increasing knee joint load. On long climbs like Taiwan’s Wuling, Beiyi, and Yangjin P-shaped mountain roads, inadequate gearing is a common equipment mistake that shows up directly in your cadence data.
• The most useful way to use cadence data is together with power: if cadence drops at the same power output, it means you’re using greater pedal force to maintain output, and muscle fatigue will accelerate.

---

Case 6: Power Spikes in the First Ten Minutes, Then the Whole Ride Falls Apart

Data Symptom: Power in the first ten to twenty minutes is clearly above the ride average, but heart rate hasn’t caught up yet (heart rate lags), then power gradually declines, and subjectively you start suffering from the 30-minute mark onward.

Possible Causes:

1. No warm-up before going straight into intensity. Your body isn’t ready, and you force out high power through willpower—the price comes later.
2. Sucked into the group ride pace. Everyone is energetic at the start, and you follow along, but that isn’t your pace.
3. The pitfall of pacing by heart rate. Heart rate is low at the start, so you mistakenly think “this is still easy” and keep pushing—but heart rate lags, and by the time it catches up, you’ve already overspent.

What to Adjust:

• Pace the start with power, not heart rate. Heart rate is unreliable at the beginning.
• Build a warm-up habit: ten to twenty minutes of low intensity before entering the main workout.
• The golden rule for long-distance events: the first third should feel “too easy.” If it feels just right at the start, you will blow up in the latter part.

---

Case 7: Interval Workout Completion Rate Collapses in the Latter Sets

Data Symptom: Planned five intervals—the first two hit the target, the third is barely managed, and the fourth and fifth show clearly insufficient power or are cut short.

Possible Causes and Adjustments:

1. Target intensity is set too high—possibly an overestimated FTP. If the same collapse pattern happens two or three times in a row, suspect FTP first.
2. Insufficient recovery between intervals—not enough rest time or recovery segments at too high a power. Recovery segments should actually be recovery.
3. Accumulated fatigue hasn’t cleared—check the training load and sleep from the previous days. What you need then is rest, not pushing through.
4. The workout design itself is unreasonable—the combination of set count and intensity exceeds current capability. Reducing the number of sets is usually a better first step than reducing intensity.

Judgment Criteria: Failing to complete a workout once might be a bad day; if the same collapse pattern repeats multiple times in a row, the setup is the problem—go back and check your FTP or workout structure.

---

7. FTP: The Foundation of All Your Numbers, and the Most Common Source of Errors

The Definition Itself Is Debatable

FTP (Functional Threshold Power) is most popularly defined in plain terms as “the maximum average power you can sustain for one hour.” But this definition has several practical problems:

• Very few people actually do a full one-hour all-out test, because it’s extremely painful and requires good pacing skills to avoid getting a value that’s too low.
• It is not exactly equivalent to physiological threshold concepts (such as maximal lactate steady state or critical power). These concepts are related but not synonymous, and different methods yield different numbers.
• Individual variation is large: some people can hold FTP for over an hour, while others can’t last 45 minutes. This depends on endurance profile, muscle fiber composition, and training background.

A healthier practical attitude is: treat FTP as “a reference anchor for setting training zones,” not a precise physiological constant. Its value lies in consistency—as long as you use the same method each time and compare it to yourself, it’s useful.

Common Testing Methods and Their Respective Biases

Testing Method	Procedure	Advantages	Biases to Watch For
20-Minute Test	After a full warm-up, go all-out for 20 minutes, take the average, then apply a coefficient (conventionally subtract ~5%)	Relatively executable, widely used	The coefficient is a general rule, not a law; people with strong anaerobic capacity tend to overestimate, endurance types tend to underestimate
Ramp Test	Power increases in steps until exhaustion, take a certain percentage of the last minute’s average (common protocols use ~75%)	Short, less suffering time, easy to repeat	Particularly prone to overestimation for those with strong anaerobic capacity; conversion percentages differ across platforms and must not be mixed
One-Hour All-Out	Directly measure the definition itself	Closest to the definition	Extremely painful, pacing errors have a big impact, hard to perform frequently
Race Estimation	Back-calculate from actual power in a time trial or hill climb race	Close to real performance, high motivation	Requires an event of appropriate length; group race data is not applicable
Critical Power Model (CP/W’)	Fit a curve using multiple all-out efforts of different durations	Most informative, also yields anaerobic work capacity	Requires many tests, high demands on execution quality

Key principle: numbers from different methods cannot be compared with each other. If you get 260 from a ramp test and 245 from a 20-minute test next time, that doesn’t mean you’ve gotten worse—it just means the method changed. To compare, use the same method.

What Happens When Your FTP Is Set Wrong — A Chain Reaction of Contamination

This is the most critical point of this article: Both IF and TSS use FTP as the denominator. If FTP is wrong, both numbers are wrong together.

What happens if FTP is set too high:

• IF is underestimated — you think a ride was moderate, but it was actually very hard.
• TSS is underestimated — you think your training load isn’t enough, so you add more.
• Training zones shift upward across the board — your “aerobic endurance zone” actually sits near your threshold. You think you’re doing low-intensity work, but you’re actually doing moderate intensity the whole time. This is the most common reason polarized training fails.
• Interval workouts repeatedly go unfinished, and then you blame your own lack of willpower.
• The end result: chronic fatigue accumulates, progress stalls, and you lose confidence in your training.

What happens if FTP is set too low:

• IF and TSS inflate across the board — the numbers look great but are meaningless.
• You ride in the “deliberately easy” zone and never touch the training stimulus you actually need.
• Workouts are all completed easily. You think you’re in great shape, but race performance doesn’t improve.
• The long-term fatigue trend chart shows you training hard, but the actual training stimulus is insufficient.

How to tell when FTP should be retested:

• Subjective workout difficulty systematically deviates from expectations (multiple consecutive sessions too easy or too hard).
• You’ve trained for six to eight weeks and feel clear improvements.
• After a long rest period or illness.
• You’ve changed power meters, or the power meter has been moved to a different mounting position.
• Before starting a new training block.

Don’t test every two weeks. An FTP test itself is a high-load workout; testing too frequently disrupts your training rhythm.

---

8. Common Mistakes Checklist

Mistake 1: Treating TSS as a Goal

Symptoms: Adding meaningless rides just to hit a weekly TSS target; or choosing high intensity over appropriate intensity just to make the numbers look good.

Problem: TSS measures load, not training quality. The same TSS can come from completely different qualities of training. A structured week of 600 TSS can far outperform a random week of 800 TSS.

Mistake 2: Staring at Long-Term Trend Metrics Every Day

Symptoms: Opening your software daily to watch the fitness/fatigue/form curves, getting anxious when numbers drop, and changing your plan for the day because of it.

Problem: These metrics are exponential moving averages, designed to be read as weekly and monthly trends. Daily fluctuations carry almost no information. Use them for direction, not for single data points.

Mistake 3: Treating NP as a Race Target

Symptoms: During a time trial, staring at the NP on the head unit and thinking, “I need to push NP to a certain number.”

Problem: NP is a post-hoc calculated result, not a target you can control in real time. Chasing NP during a race will make you push on descents and blow up on climbs, ruining your pacing. During the race, watch instantaneous power or 3-second/10-second averages. Leave NP for post-race analysis.

Mistake 4: Power Meter Not Zeroed or Calibrated

Symptoms: Power readings suddenly run uniformly high or low on a given day, or numbers on a familiar route look inexplicably off.

Principle: Strain-gauge power meters are sensitive to temperature changes, and the zero point drifts with temperature. Bringing the bike out of an air-conditioned room, or riding from sea level to high altitude (e.g., Wuling, where temperature differences can be extreme), can both cause the zero point to shift.

What you should do:

• Perform a zero/offset calibration before every ride — it only takes a few seconds.
• On long climbs with large temperature swings, find a chance to re-zero mid-ride (follow your device’s specific procedure).
• Regularly check battery level and mounting torque.
• If your device supports static weight calibration, perform it periodically per the manufacturer’s instructions.
• When data looks unreasonable, suspect the equipment first, then yourself.

Mistake 5: Directly Comparing Numbers from Different Power Meters

Principle (general principles only, without referencing any brand’s accuracy figures; official specifications per manufacturer announcements):

• Different measurement locations: Pedals, cranks, crank spiders, rear hubs, and trainers measure progressively further down the drivetrain, with drivetrain losses in between. Numbers measured further downstream are typically lower.
• Single-sided vs. dual-sided: Single-sided measurement doubles one side as an estimate. If you have left-right asymmetry, the error is amplified directly.
• Different temperature compensation strategies: Each brand handles thermal drift differently.
• Different sampling and filtering: Short-duration high-power readings can differ.

Practical conclusion: Switching power meters is like switching rulers — FTP must be retested. Don’t mix trainer numbers with outdoor numbers in the same zone system. If you use two devices simultaneously, establish two separate FTPs and note the source in your analysis.

Mistake 6: Analyzing Before Checking Data Quality

Before drawing any conclusions, check:

• Are there data gaps from signal dropouts?
• Are there absurd spikes (e.g., false signals when standing to sprint, or magnetic interference)?
• Are the start and end times correct? Did you include time spent stopped at lights or packing up equipment?
• Did you use auto-pause? Auto-pause affects the basis for average power calculations.

A corrupted FIT file will produce a set of conclusions that look professional but are completely wrong.

Mistake 7: Watching Only Power, Not the Body

Power is external load (how much work you did); heart rate, perceived exertion, sleep, and mood are internal load (how much it cost you). Watching only external load misses the most important signals. Spend thirty seconds after every ride recording a 1-to-10 rating of perceived exertion. Over the long term, its value rivals any advanced metric.

---

9. Taiwan Local Context: How to Read These Numbers Here

Wuling (Provincial Highway 14A) Long Climb

• Analyze it in segments. Full-ride NP and IF get diluted by the relatively flat early sections and the high-altitude later sections, hiding the true load. At minimum, split it into several major segments and examine each separately.
• Power decline at altitude is a normal physiological response, not a sign of regression. Lower partial pressure of oxygen directly reduces sustainable power output, becoming more pronounced at higher elevations, with large individual variation. Demanding that you hit your sea-level power targets on the highest section is the standard recipe for blowing up your pacing.
• Extreme temperature differences: hot at the base, potentially very cold at the summit. The risk of power meter zero drift is high, and your nutrition and clothing strategies need to adjust accordingly.
• Treat descent data separately. Long descents severely drag down full-ride average power and distort the meaning of VI. The focus and bike-handling stress of descending is something TSS cannot reflect at all.

Fengguizui

• One of the most commonly used fixed test segments in the Taipei area. Its value lies in repeatability: the same stretch, the same effort, different time periods, directly comparing power and heart rate.
• For analysis, isolate only the climb segment. Don’t include the urban out-and-back sections, or VI and IF will be contaminated.
• Be aware of wind. Power-to-speed relationships on the same stretch can vary dramatically under different wind conditions, so compare power, not time.

Beiyi Highway and Yangjin P-Style Mountain Road

• These routes are characterized by rolling terrain and many corners, so VI is naturally higher than on a pure long climb. Don’t directly compare their VI to Wuling’s.
• Traffic safety comes first: these are open roads with heavy vehicles and tourist traffic, and poor visibility around corners. No data target is worth the risk — don’t race on open roads. When chasing numbers, leave a generous safety margin and obey speed limits and traffic signals.

Riverside Bike Paths

• Riverside paths in Taiwanese cities are the easiest place to accumulate hours, but gates, under-bridge turns, pedestrians, and other path users cause constant slowing and re-accelerating, making VI prone to inflation.
• For steady endurance riding, choosing a longer continuous stretch and riding out-and-back is far more effective than wandering through complex sections.
• Riverside areas are mostly open spaces, so the power-to-speed relationship differs enormously between headwind and tailwind sections. Pace by power, not by speed.

Summer Heat and High Humidity

• Humidity in Taiwan’s summer severely impairs evaporative cooling efficiency, making the same temperature feel much more uncomfortable under high humidity. This directly lowers the power you can sustain and amplifies heart rate drift.
• The sensible approach is to accept a downward adjustment of your power targets in summer, and focus on hydration, electrolytes, timing (early morning), and shaded routes.
• Directly comparing summer data with winter data will lead to a false “I’ve gotten worse” conclusion. Look at trends separately by season.

Northeast Monsoon

• The northeast monsoon in autumn and winter creates extreme contrasts between headwinds and tailwinds for rides in northern and northeastern Taiwan.
• Power will be high but speed slow on headwind sections, and the opposite on tailwind sections. VI will also be inflated in this situation, because your output fluctuates greatly with the wind.
• When analyzing such rides, power is the only reliable measure of effort; speed, time, and even heart rate will all be distorted by wind conditions.

---

10. Safety and Health Reminders

Data analysis always comes after health. In the following situations, stop riding immediately and seek medical evaluation—do not try to explain it away with data:

• Chest tightness, chest pain, or a feeling of pressure in the chest, or discomfort radiating to the arms, neck, or jaw.
• Abnormal heart rate: a response clearly deviating from your usual pattern, such as heart rate spiking abnormally at low intensity, or failing to rise as expected at high intensity, accompanied by discomfort.
• Palpitations, a clear sensation of arrhythmia, dizziness, blurred vision, or feeling close to fainting.
• Signs of heat illness: cessation of sweating, hot dry skin, confusion, nausea or vomiting, extreme weakness, or a clearly elevated body temperature. This is a medical emergency requiring immediate cooling and medical attention.
• Unusual shortness of breath disproportionate to exercise intensity.

Additional reminders:

• All training recommendations involve enormous individual variability and must be progressed gradually. Sudden large increases in training volume or intensity are a primary cause of injury and overtraining.
• Those with cardiovascular disease, chronic conditions, long-term medication use, or who have been inactive for a long time should consult a medical professional before starting or significantly adjusting training.
• This article is a general explanation of training data interpretation and cannot replace professional medical evaluation and diagnosis.
• When riding outdoors, obey traffic rules, wear a certified helmet, and pay attention to road conditions and other road users. Do not take risks on open roads in pursuit of data.

---

11. Key Takeaways and Action Checklist

Core Concepts in One Sentence

Metric	One Sentence	Primary Use
Average Power	How much work you did	Total mechanical output
NP	The “metabolic” equivalent of a steady power for this ride	True load of a variable ride
IF	How hard this ride was relative to you	Comparing intensity across rides
VI	How smooth your output was	Checking whether your riding style matches training intent
TSS	Combined load of intensity multiplied by time	Tracking long-term training load trends
Power Curve	Your capability profile across durations	Identifying capability gaps

Five-Minute Check After Every Ride

1. Check data quality first: any dropouts, absurd spikes, or timing issues.
2. Check VI: does it match today’s training intent? If not, the quality of this ride is questionable.
3. Check split power: divide the ride into beginning, middle, and end segments—is power holding steady or declining? How much is it declining?
4. Check the power–heart rate relationship: is there a clear decoupling in the latter half? If so, first ask about environment and fueling, then about fitness.
5. Record a subjective effort score (1 to 10), and briefly note weather, sleep, and diet. Thirty seconds of effort, extremely valuable over the long term.

Monthly Checks

1. Review your power curve, identify weak segments, and confirm whether they are genuine capability gaps or simply undertrained.
2. Review workout completion rates: if you repeatedly fail to complete sessions or find them too easy, it’s time to retest FTP.
3. Look at training load trends, not single-day numbers. Confirm whether load is rising progressively or spiking.
4. Compare against a fixed test segment (e.g., the climb on Fengguizui), using the same segment and similar effort for long-term tracking.

Five Habits to Change Immediately

1. Zero your power meter before every ride—make it a habit.
2. Don’t stare at NP during races or tests; look at real-time power or short-term averages.
3. Don’t pace the start with heart rate—heart rate lags and will deceive you.
4. Don’t ride just to hit a TSS number—training purpose comes before the metric.
5. Retest FTP when you change devices—don’t use two different rulers with the same set of zones.

---

The value of data lies not in how precise it is, but in that it lets you see what you couldn’t see: the steadiness you thought you had is actually fluctuating, the effort you thought you were giving is actually collapsing in the latter half, and the progress you thought you made is actually just an FTP set too low.

NP, IF, VI, and TSS are all just tools—tools alone won’t make you stronger. What truly makes you stronger is using these tools to honestly examine every ride, finding one thing to improve, and then changing it on the next ride. Change one thing at a time, and that’s fifty things in a year. That’s worth more than any impressive number.

Related Reading

• Complete Guide to Cycling Power Data: Making Every Ride Meaningful with NP, IF, and TSS
• How to Interpret Training Data: What Are Power, Heart Rate, and TSS Really Telling You?
• Post-Race Power Data Analysis Guide: How to Find Room for Improvement in Your Race Files
• Power Meter Data Analysis: Interpreting Key Metrics in Strava and TrainingPeaks