Supporting article · 8 min · Updated 30 Aug 2026
Session design (20 / 40 / 60)
Quick answer
A session has one constraint, one song fragment, and a stop while form is still good. Time of day matters less than whether you can name what failed. Use the templates below instead of “play until I feel done.”
Rules that do not change with length
- One constraint per session (mute bounce, outside crossings, downpicking duration, a landing note). Not five.
- Work the constraint with the 1-bar protocol.
- Song time is a loop of the bar that breaks, not a full play-through.
- If form changes, the block is over. Rotate or stop. Speed without tension.
20 minutes
- 2 min — open-string even 8ths (are you here today?).
- 12 min — constraint only.
- 6 min — one riff fragment at floor BPM.
Skip warm-up songs. Twenty minutes cannot afford them.
40 minutes
- 5 min — check-in + current path stage exit test.
- 15 min — constraint.
- 12 min — song fragment.
- 8 min — one lead constraint (target, pinch, or a three-note cell). Optional if the path stage is still mute/pick.
60 minutes
- Same as 40, plus 15–20 min on a second fragment or a second constraint after a 2-minute break.
- Last 5 min: play the fragment once “as music,” no debugging. If it falls apart, you learned where tomorrow starts—do not start a third project.
What this is not
It is not a content calendar of new licks. Repeating yesterday’s failed bar is the session. Spacing across days beats one heroic Saturday: distributed practice.
Related
Sources: session structure from deliberate-practice logic applied to guitar blocks. Not a lab schedule. Updated 30 Aug 2026.