Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More

Owned by Keith

100 Days to Fit

1 member • Free

100 days. Real habits. Real results. Build momentum and create lasting change that sticks.

Ruth Performance Lab

353 members • Free

1 contribution to Ruth Performance Lab
What actually eats most of your programming time?
For the last few months, I’ve been paying closer attention to how I spend my programming time and I’ve been trying to answer one simple question: What task or problem eats the most time? The more I paid attention to what I was doing, the more I noticed it wasn't high-level planning or deciding whether to progress an athlete or pull-back. It was rebuilding things I’ve already built! Writing a week without a well-defined mesocycle or template immediately turns it into a crippling blank-page exercise. Then I find myself trying to invent a new week layout or progression for a problem I’ve already solved dozens of times. Sometimes this is because the solutions I've built aren't organized well enough to find and sometimes because I'm focused getting the week layout right rather than building the actual week. The physical process of building the program often takes significantly longer than deciding what the program needs to accomplish. Reading an athlete’s feedback, understanding how they’re adapting, and deciding whether to continue progressing, back off, or make a structural change takes time. However, that’s also the part of the coaching process where we deliver the most value to the people we're guiding, so I'd rather focus my time there than re-typing the same solution to a problem over again. The distinction I keep coming back to is this: Individualized coaching doesn’t require inventing a new solution every week. It requires: - A well-defined plan - A library of proven progressions - Clear rules for selecting and adapting them - Enough attention to athlete feedback to know when the plan needs to change Interestingly, I looked back through several of my mentorship conversations, and this same problem appeared over and over again. The most common recommendation I’ve made to other coaches is to stop programming from a blank page and start building a searchable library from the work they’re already doing. Write it once, save it in a place you can access it again, organize it, then adapt it for a client's unique situation.
1 like • 3d
Really resonate with this. I find in particular that programming for competitive CrossFit is the most time intensive as I'm also second guessing myself and my program to understand if I'm doing enough of this or too little of that - I suppose this would be imposter syndrome sneaking into my process due to lack of experience?
1-1 of 1
Keith Stillman
1
4 points to level up
@keith-stillman-6758
Gym owner in Kobe, Japan. I used to hate fitness. Now I help people love it — and change their life in 100 days.

Active 2d ago
Joined Feb 27, 2026
Powered by