Training
A capable person sits down with a tool she uses every day. What should take ten minutes takes forty-five. She is not confused about the goal and she is not distracted. She does not know how the tool works, so she routes around it, approximates, and backs up to try again.
Multiply that by eight people across a working week and it stops being a training gap. It becomes a structural drag on everything the team produces. Nobody reports it, because from the inside it feels like the work simply taking as long as the work takes.
Both products came out of the article Training as a Productivity Multiplier.
Free Asset
Fifteen minutes, one tool, twelve questions, and a number you can act on.
Pick one tool your team uses every day. Not the most complex one, and not the one already scheduled for replacement. Answer twelve yes or no questions from what actually happens rather than from what the process document says. Count the yes answers.
The count puts you in one of three bands. Contained, structural, or compounding. Each band carries an estimated weekly loss per person, so you can size the problem before you spend anything on it.
Grouping your yes answers sorts the loss into four friction types. Transition, format, translation, and workaround. A four level fluency ladder shows you where your team sits and how far one session can move it. The paid workbook reuses every one of those terms, so nothing you write down gets thrown away.
The weekly loss ranges are calibration estimates, not measurements. They exist to help you decide whether the problem deserves attention this quarter. Measuring the real figure means timing a fixed set of tasks before and after a change.
the-tool-friction-scan.pdf, eight pages. Why capable teams run slow, the four kinds of friction, the fluency ladder, the twelve question scan, how to read your score, and what the scan deliberately leaves undone.
Priced pay what you want with a zero minimum. Take it for nothing.
The Path
The scan produces a diagnosis. It does not produce the fix. Knowing your band and your dominant friction type tells you the size and shape of the problem. It does not tell you which moments in the workflow to target, how to build practice that changes behavior instead of delivering information, or how to prove the change happened once you made it.
The sprint is that work built out in full. Same tool, same team, same vocabulary, with the observation protocol, the baseline tracker, the lesson builder, the session deck, and the before and after scorecard.
Run the scan first. It takes fifteen minutes and it is free. Without a score you have no dominant friction type to aim at, no band to size the effort against, and no before number for the retest to compare against.
Same vocabulary, same tool, same team. The sprint is the second half of one piece of work.
Paid Product, $97
A thirty day sprint that turns the friction you found into hours you can measure and defend.
Five phases, each one producing a single output that the next phase consumes. Thirty days of elapsed time and far less than thirty days of work. Most of the calendar is the gap between the session and the retest, which exists so the new behavior gets used on real work before anyone measures it.
| Phase | What You Do | Days |
|---|---|---|
| Observe | Watch two or three people do real work and time a fixed set of three to five tasks | 1 to 7 |
| Isolate | Turn the notes into three or four ranked pattern statements and cut the rest | 8 to 10 |
| Build | Turn each pattern into a practice task drawn from real work with a correctness check | 11 to 16 |
| Run | One session of thirty to sixty minutes, everyone on their own machine | 17 |
| Prove | Time the same tasks again, compute the delta, write the one page result | 28 to 30 |
Eight pages. The free diagnostic the sprint starts from, bundled here so the sprint is self-contained. If you already ran the scan and have your score, skip it. If you did not, run it before Phase 1 rather than guessing which friction is doing the damage.
Thirty-five pages, editable in Word. The spine of the product. It carries the observation protocol, the shortlist test, two fully worked micro lessons, the facilitation method, the arithmetic behind the annual figure, the thirty day calendar, and the failure modes for every phase.
Five sheets. Setup holds the tool, the team size, the hourly cost and your scan score. Baseline holds one row per observed task run. Retest holds the same tasks timed again. Result computes the delta, the weekly hours and the annual figure. Reference holds the dropdown lists, so your entries stay sortable.
Five sheets. Shortlist ranks the patterns from Phase 2. Lesson Plan turns each one into a runnable micro lesson. Worked Examples shows two finished lessons in the same columns. Session Plan lays the lessons out against the clock. Checklist is the quality gate you run before you book the room.
Nineteen slides. The slides carry only what the room needs to see. The speaker notes carry the facilitation script, including what you say, when you stop talking, and what to do when the practice goes sideways. You present from the notes.
A calibration estimate, straight from the workbook worked example. Nine minutes saved per run, two runs per person per week, five people, gives ninety minutes a week for the team. Across forty-six working weeks that is sixty-nine hours a year, against about eleven hours of your time and seven and a half hours of team time to run the sprint. The workbook invents those inputs to show the arithmetic. They carry no benchmark and they say nothing about what your sprint will produce.
A measured hour is worth more than an impressive session.
Fit
The sprint asks for real access to real work. Read both lists before you buy.
Start Here
Run the free scan on one tool this week. If your score lands in the structural or compounding band, the sprint is the next thirty days.
