Why static plans fail when life happens
The standard playbook for mountain athletes is brutal: a coach writes you a 12-week plan in a spreadsheet, you grind through it, you check off boxes. The plan does not know that Tuesday's intervals were impossible because you flew red-eye, or that Saturday's hike turned into a six-hour scramble with 1500 metres of vertical, or that you caught a cold and wrote off a week.
A static plan keeps prescribing as if none of that happened. The athlete either feels guilty for falling behind, or grinds anyway and arrives overcooked. Both outcomes are worse than the plan having no business being followed.
An auto-sync wearable training plan solves this differently. Every session your watch records is read into the algorithm within minutes of syncing. The next session, the next week, the next phase - all reshape around what you actually did, not what the spreadsheet said you should have done.
What TTM reads from your wearable
Whatever you train with - Garmin, Apple Watch, Coros, Suunto, Polar - your wearable records the same core signals, and most sync them automatically into Strava, which is the connection point TTM reads. Five of those signals feed the algorithm. Each one drives a different part of the plan.
How the plan adapts: four scenarios
Concrete examples are easier than abstract rules. Here are four common situations and what the algorithm does in each.
The plan you complete shapes the plan you get. That is the difference between a static spreadsheet and a connected training app.
What your wearable cannot show
Honesty matters. A wearable is excellent for what you did - duration, intensity, vertical, type. It is silent on three things that still matter for training:
- Perceived effort. A session that reads as Z2 but felt like Z4 - because of heat, dehydration, poor sleep, or illness - is more fatiguing than the numbers suggest. The watch records the heart rate, not the struggle behind it.
- Pain, niggles, and injury risk. A knee that is starting to complain does not show up in heart rate data until it is too late. No wearable flags the early warning.
- Life context. Your wearable logs that Tuesday's session did not happen. It does not know it was a red-eye flight, a sick child, or a brutal work week. The reason changes what next week should look like.
TTM's AI coach (Ridge) covers this gap with short conversational check-ins, not with another device to buy. After key sessions, Ridge asks how it felt, and that perceived effort is added to the data the algorithm sees. It is a deliberate hybrid: machine-readable data for the bulk of the picture, human-readable input for what the sensors miss.
Connecting your wearable
Most wearables - Garmin, Apple Watch, Coros, Suunto, Polar - sync your activities automatically into Strava, and TTM connects there with a one-time authorisation. We read your activities; we never publish back to your feed. Activities going back several months are read in on first connection, which means the algorithm has historical context from day one - it does not start from zero.
One honest setup note: wrist-based optical heart rate can drift during hard intervals or in cold conditions, where accurate zone data matters most. If your training leans heavily on precise intensity work, a chest-strap heart rate monitor pairs with every major wearable and gives the algorithm cleaner data to work from.
For the deeper rationale on why heart rate zones (and therefore your wearable's HR data) matter so much for mountain athletes specifically, see our heart rate zones for mountaineering guide.
How TTM uses your wearable data, in one paragraph
The short version
- Each synced session is read by the algorithm and converted into a Mountain Training Score that captures cardiovascular load plus mountain-specific factors (vertical, activity type).
- Your fitness and fatigue trends (MF, MFat, MForm) update with every session, exponentially weighted so recent training matters more than ancient history.
- Next week's plan is recalculated from that updated state - protecting the aerobic base, reshaping intensity, advancing or holding phase as needed.
- Ridge's check-ins add perceived effort and recovery context the data alone cannot show.
The result is a plan that earns its name. Not a 12-week spreadsheet you tried to keep up with - an actual coach that read your week and adjusted.