LOGIN
BECOME A MEMBER

THE BLOG

Episode 101 - "Nobody Plays in Perfect Conditions" (July Monthly Catch-Up) — Kajabi Plain-Formatting Guide

Aug 06, 2026

Ian Renshaw & Keith Davids · Monthly Catch-Up · July 2026 · The Constraints Collective


You've probably heard a version of it from your own group: "we're rubbish in the wet." Not because the skill isn't there on a dry night, but because it was never trained any other way. Ask why, and the answer is almost always logistical rather than technical — the team trains somewhere warm and dry, so wet-weather handling simply never gets rehearsed. Then a wet Saturday arrives, the skill disappears, and everyone calls it bad luck.

That exchange — a real one, between an AFL player and his coach — was one of several threads Ian Renshaw and Keith Davids picked up in July's Constraints Collective monthly catch-up. Across an hour of conversation the two returned to a single question from several directions: how do you prepare an athlete for the conditions you can't control, the schedule you can't shorten, and the pressure you can't rehearse away?


We're Rubbish in the Wet

Ian's fix for the AFL player was almost embarrassingly simple: dip the ball in a bucket of water before a drill. Keith went a step further — sprinklers on the training pitch, timed to whatever the away fixture's forecast actually says. Neither idea depends on the weather cooperating on a Tuesday night in Brisbane. Both make an uncontrollable environmental constraint something the team has already handled once, in miniature, before it matters.

"You can use sprinklers on the pitch to simulate it... if it looks like the weather patterns are going to be wet in the area you're travelling to, these are the typical conditions — you can simulate those to an extent in training."

The point isn't the bucket. It's the principle underneath it: skill adaptation, not skill acquisition, is what a constraints-led approach is actually training for. You cannot coach the rain away. You can coach a team that has already felt a wet ball in its hands.


The Bench Is Not a Backup Plan

Keith's second thread came from an unlikely place — the NBA's fixture list. Eighty-two games in roughly a hundred and seventy days works out to a game every two days once travel is added in, and the data shows win probability rises measurably whenever a team gets at least 48 hours between fixtures. Some weeks, they don't get it.

"Sometimes they play two games adjacent night after night. And that is insane. That's an insane schedule."


 An illuminated basketball court at night. Caption if the editor supports one: "Eighty-two games, roughly a hundred and seventy days — the NBA calendar leaves little room for recovery."

The response Keith has been hearing from NBA staff, filtered through conversations with coach Noah LaRoche, isn't longer training blocks. It's shorter, sharper ones — fifteen to twenty minute pockets built around the specific opponent coming next, rather than generic repetition. Ian's read on it was blunt: a squad's depth isn't insurance against a brutal schedule, it's the actual plan for one. "You're only as strong as your weakest player" — never truer than when the calendar won't let your best one rest.


You Only Get One Session

The same time pressure runs through a piece Ian has been developing away from the podcast — single-session design, borrowed from psychology and psychiatry literature rather than sport. The finding that reframed his thinking: a large share of clients who attend a single session never return for a second, and most of them still say that one session made a real difference.

"If we've only got one session... the underpinning mindset is we can make a significant change and significant difference in this one session."

It's a direct answer to one of the oldest complaints about constraints-led and game-centred coaching — that it's a slower road to competence than simply telling a player what to do. Ian's counter isn't an argument, it's a design constraint: if you genuinely believed you had one session to work with, what would you actually change about how you ran it?


Afford Is Not Potentiate

The theoretical core of the conversation returned to a distinction Ian and Keith have been refining for years: constraining to *afford* versus constraining to *potentiate*. The first is a perceptual problem — a beginner often doesn't know what to look for, so the coach manipulates constraints to make the right opportunity more visible. The second goes further, into whether the athlete can actually act on what they've now seen, by reshaping the coordinative structures that make a movement possible in the first place.

"What I like about the constraint-to-potentiate idea is that it recognises the individual has onboard sources of energy — intentionality, agency, autonomy as a player."

It's a useful corrective to a criticism both hosts hear often: that constraints-based coaching isn't really coaching, because it isn't built on instruction. The reply is that constraints are invitations, not commands — and an athlete who ignores one isn't malfunctioning, they're exercising exactly the agency the approach is designed to respect.


Stay in the Green

The clearest illustration of all of it came as a story, not a framework. Sport psychologist Bill Beswick's traffic-light model — green for composed, red for lost control, amber as the zone where either is still possible — sat behind a moment from England's Under-21 side. In one leg of a tie against Eastern European opposition, defenders fouled Michael Owen off the ball until he retaliated and was sent off. In the return leg, a substitute forward faced the same treatment and started to react the same way — until a teammate's voice reached him from the far end of the pitch: "stay in the green, stay in the green.'

That cue wasn't improvised. The team had planned for the scenario before it happened, which is the entire argument in miniature. You don't remove the amber zone — Keith connects it to what dynamical systems theory calls the region of metastability, a genuine window where performance could tip either way. You rehearse what happens inside it, so that when the moment arrives, someone already knows what to say.


Whether it's a wet ball, a compressed fixture list, one shot at a session, or a defender determined to provoke a red card, the throughline is the same: conditions won't hold still, and neither will performers. The job isn't to engineer the uncertainty out. It's to make sure the athlete has already met it once before it counts.

This piece draws on July's Constraints Collective monthly catch-up between Ian Renshaw and Keith Davids. Members can watch the full recording, read the monthly newsletter, and get the clip library inside the members area.