Why Accepting Reality — Not Setting Expectations — Is the Key to Athlete-Centered Coaching
Most coaches walk into a season with a list of expectations. Win percentage targets. Defensive ratings. Development benchmarks. And then — almost inevitably — reality doesn't match the list. Players underperform. The team loses five in a row. Nobody's meeting the standard. And what happens next? Frustration. Finger-pointing. A locker room where everyone's looking outward instead of inward. I heard a conversation recently that stopped me cold, because it named something I've felt for years but never quite articulated: expectations might actually be the enemy of growth. Not goals. Not standards. Expectations. And the difference is more significant than it sounds.
The Problem With Coaching for Outcomes You Can't Control
When I heard the point made in this conversation — that 24 out of 25 teams in a professional league are going to fail if "winning is the only thing that matters" — I immediately thought: we say this all the time, and nobody really believes it. Coaches nod along, and then they go back to measuring everything by results. It's almost automatic. The culture of competitive sport makes it feel irresponsible to think any other way.
But here's the thing. That framing isn't just philosophically shaky — it's practically counterproductive. If your definition of success is a result you share with opponents, external conditions, and a thousand variables outside your control, you've already lost before the opening tip. The coaches in this conversation were refreshingly direct about it. You're not measuring progress. You're measuring variance. And then you're calling it development.
What I found most compelling was the reframe around where progress actually lives. It's not "did we win?" It's "where were we in step one, and where are we now, two months later?" That shift sounds simple. It is not simple. It requires a coach to genuinely release attachment to the outcome — and that's a psychological ask most of us aren't trained for. Which is exactly why one of the speakers brought up their background in counseling. A good therapist doesn't prescribe answers. They create conditions where a person can discover their own way forward. I think that parallel is dead accurate. Athlete-centered development in basketball asks coaches to make that same shift — from answer-giver to environment-designer — and it's genuinely hard to do if your identity is tied to being the person with all the solutions.
Acceptance as a Coaching Tool (Not a Surrender)
This is the section I keep coming back to. Because when I first heard the word "acceptance" used in this context, I bristled a little. I'll be honest. My gut reaction was: isn't acceptance just giving up? Isn't that how you get a team that stops holding itself accountable?
But the argument here is more nuanced than that, and once I sat with it, it clicked.
The example used was beautiful in its simplicity. You're working on transition offense. You constrain the shot clock to eight seconds to force faster decision-making. The players are struggling — the success rate is low, almost nothing is working. Now what? The old-school instinct says: run harder, be more disciplined, you're not meeting the standard. The acceptance-based approach says: I'm going to look at what's actually happening in front of me, acknowledge that this constraint is too severe right now, and adjust the shot clock to fourteen seconds. Not because standards don't matter. Because I'm working from reality, not from what I wished reality would be.
That's the distinction. Acceptance doesn't mean you abandon expectations entirely. It means you stop using the gap between expectation and reality as a reason to punish or blame — and start using it as data. This connects to something I think about a lot when it comes to the problem with punishing players for failure rather than understanding what that failure is telling you about your practice design.
What's philosophically interesting — and the conversation went there, which I appreciated — is that frustration itself is a byproduct of unmet expectations. Not of failure. When players blame each other after a turnover, when a coach loses composure after a bad possession, that emotional reaction isn't really about the turnover. It's about the gap between what they expected and what happened. Close that gap — not by lowering standards, but by accepting present reality — and suddenly there's space to actually problem-solve instead of panic.
Meeting Players Where They Actually Are
There was a line in this conversation that landed differently than I expected. The idea that you'd never have expectations for a coach or a player to "be a certain thing or be a certain way or be at a certain level." At first that sounds almost passive. Like you're letting people off the hook.
But the follow-up reframe is everything: it's not about lowering the bar. It's about coming to where the person is in their path, and then helping them take one step forward. Not twenty feet. One step. That approach requires a completely different skill set from a coach. You have to actually see the player in front of you — not the player you wish they were, not the player the scouting report said they'd be. The real one. Right now.
I've seen this play out personally in grassroots settings. The coaches who make the biggest impact on young players aren't always the ones with the most intricate systems. They're the ones who have a genuine read on where a player is emotionally and technically, and they build from that. No judgment. No frustration that the player isn't already further along. Just: here's where you are, here's one thing we can work on today. That kind of coaching is underrated precisely because it's invisible. There's no dramatic clipboard moment. There's just quiet, consistent, sustained development that compounds over time when a coach commits to this kind of approach.
What struck me most was the connection made between this approach and agency. When you meet players where they are and allow them to set the pace of their own growth, you're giving them ownership of the process. That's not soft. That's arguably the hardest thing to build — because it requires the coach to give up control. And as the conversation pointed out, that requires a level of self-assurance that many coaches haven't cultivated yet. The insecurity that drives micromanagement, that drives expectation-setting as a control mechanism — that's real, and it's worth naming. Because until a coach confronts that in themselves, they can't genuinely put the learner at the center. Modern basketball demands exactly this kind of shift — from choreographed systems designed to make the coach look smart, toward environments designed to make the player capable.
Are We Actually Allowing Learning to Happen — Or Just Saying We Are?
Every coach I've ever met says the same thing. "Learning is messy." "It's nonlinear." "You have to trust the process." And I believe most of them genuinely mean it. But when I heard this part of the conversation, I stopped and asked myself — do we actually live that, or do we just say it?
Because there's a massive gap between believing learning is nonlinear and actually sitting with the discomfort of watching a player struggle without jumping in. That gap is where most coaching breaks down.
What struck me most was the framing around mistakes and errors. The idea that when you see something go wrong, the first question shouldn't be "how do I fix this?" It should be "is this actually an error — or is this the player adapting?" That's a profound reframe. And honestly? It's one I've had to actively work on myself. We're trained — almost instinctively — to be deficit detectors. See a problem, solve a problem. It feels productive. It feels like coaching.
But sometimes the most important thing you can do is nothing. Step back. Watch. Let the player negotiate the environment on their own terms. Because if we keep interrupting that process, we're not developing problem-solvers. We're developing players who wait for the answer.
This connects directly to something I've thought about a lot around how skills actually emerge through interaction with the environment rather than being drilled in through repetition — and it's a perspective that completely changes how you interpret what you see on the court. An awkward decision, a hesitation, a missed read — these might not be failures at all. They might be exactly what learning looks like in real time.
The coaching spectrum described here — from "tell them what to do" all the way to "observe and let them self-solve" — is something I think coaches need to revisit constantly. Not just in theory. In actual practice. Where are you sitting on that line right now, in this drill, in this moment? Are you intervening because it's necessary, or because the silence makes you uncomfortable?
I don't fully agree that you should always step back, by the way. There absolutely is a line. Some errors do need correcting before they get reinforced. But the key word is sometimes. Not reflexively. Not every single rep. The default shouldn't be to stop and fix — it should be to observe and trust, and only intervene when you've genuinely determined the player can't self-solve.
Self-Regulated Learning Is the Real Goal — And Coaches Need It Too
This is something I think about a lot. We spend enormous energy trying to develop skilled players, but how much time do we spend developing learners?
The self-regulated learning framework laid out here — plan, monitor, evaluate, adapt, repeat — isn't complicated. But it's rare. And I think it's rare because it requires players to take genuine ownership, and it requires coaches to relinquish a degree of control that feels uncomfortable. Most coaching cultures aren't built for that. They're built on the coach as the all-knowing authority and the player as the receiver.
When I heard this, I immediately thought about how different the game looks when you have a player who's genuinely proactive about their own development versus one who only improves when someone tells them to. The self-regulated learner shows up differently. They're curious. They ask better questions. They recover from setbacks faster because they have a process — not just a result to chase.
And the point that really landed for me? This applies to coaches just as much as players. If I'm not planning what I need to work on, monitoring my own practice, evaluating whether it's working, and adapting accordingly — then I'm asking something of my players that I'm not doing myself. That's a credibility problem. The athlete-centered development philosophy in basketball only works when the coach is also genuinely committed to their own growth as a learner.
What I also appreciated was the honesty around "toughness." That word gets thrown around so casually. Be tougher. Play harder. Grind more. But what does that actually mean? The argument here — that true toughness is being proactive, strategic, and persistent in your own learning cycle — is a far more useful definition. Show me a player who can honestly evaluate their own performance, identify what needs to change, make a plan, and stick to it. That player is tough. That player is resilient in a way that actually transfers.
I've seen this play out personally — players who look physically dominant but fall apart the moment things don't go to plan, because nobody ever taught them how to make quick decisions under pressure without a coach in their ear. And then there are players who maybe aren't the most gifted but adapt constantly, adjust constantly, and just keep finding solutions. That second player is the one you want when the game is on the line.
The Plan-Do-Review Cycle — And Why "Do" Is Eating Everything Else
This part of the conversation hit close to home. The Plan-Do-Review cycle isn't a new idea. It's been used across education, business, medicine — for decades. But the observation here is painfully accurate: coaching culture is almost entirely consumed by the do.
We plan (sometimes). We do (always). We review (almost never).
Why? Because reviewing feels like extra work. Because there's always another session, another game, another drill to run. Because the "do" phase is visible and active and feels like progress, while reflection feels passive and slow. But that's exactly backwards. The review is where the learning actually gets locked in — for coaches and players alike.
I found it genuinely refreshing to hear a coach admit that the review section of their own practice plan is the hardest part to actually complete. Not because they don't believe in it, but because time and habit work against it. And honestly, that resonates. It's easy to be philosophical about reflection when you're talking about it. It's a lot harder at 9pm after a draining practice when you just want to go home.
But here's what I keep coming back to: if we're asking players to evaluate their performance, to be honest about what's working and what isn't, to adapt their approach — then as coaches, we have to model that exact behavior. You can't just preach the cycle. You have to live it. Even if it's a voice note on the drive home. Even if it's two minutes of honest thought before you write tomorrow's practice plan. The coaches who've genuinely transformed their approach seem to share this in common — they became ruthlessly honest evaluators of their own sessions, not just their players' performances.
And if you want a practical starting point? Start with your coaching. Not the drill design, not the game plan. Look at how you behaved during the session. Did you intervene too much? Did you give players space to self-solve? Did you ask questions or just give answers? That's where the real growth is hiding.
Planning Connections Is Just As Important As Planning Drills
Something shifted for me when I heard this part of the conversation. The coach talked about reserving three spaces on his practice plan — not for drills, not for objectives — but for connections. Three players. Three check-ins. Written down in advance, intentional, deliberate. When I heard this, I immediately thought about how many coaches would consider that soft, unnecessary, maybe even a waste of planning time. And honestly? I used to be one of those coaches.
But think about it. You already know who's carrying something heavy into practice. You already noticed the player who looked drained last session, or the kid coming back from injury who's mentally somewhere between confident and terrified. The question isn't whether you see those things — it's whether you actually plan to act on them. Writing down "check in with Adam about his energy" is the difference between a coaching intention and a coaching action. That gap matters more than most of us admit.
I've seen this play out personally. The players who respond best to you aren't always the most talented ones. They're the ones who feel like you actually see them as a person. And that doesn't happen by accident — it happens because you made space for it. If you're thinking about how to build that kind of environment systematically, athlete-centered development in basketball is the broader philosophy that underpins everything being discussed here, and it's worth diving into if this resonates with you.
What struck me most was the framing. The coach said planning those connections is just as important as planning the targets of the session — what you're introducing, developing, performing. Not more important. Equal. That's a subtle but huge reframe. Most of us treat the human stuff as a bonus if we have time. He's saying it belongs on the same sheet of paper, in the same planning block, with the same level of intention.
Gratitude Isn't Soft — It's How You Stay Connected to Your Why
This is something I think about a lot, and I'll be honest — hearing this section made me a little uncomfortable in the best possible way. The coach described sometimes having to reach to fill in three lines of gratitude after a practice. Really reach. And rather than framing that as failure, he framed it as the whole point. Because the act of reaching — of forcing yourself to find something you appreciated about that session — pulls you back toward your why.
We talk about the do-do-do mentality in coaching all the time. The relentless grind of preparation, execution, next practice, next game, next season. And somewhere in that loop, a lot of coaches quietly lose the thread of why they started. Not dramatically. Just gradually. The joy gets buried under logistics and results and parent emails and lineup decisions. The gratitude section of the Plan-Do-Review model is, at its core, a circuit breaker for that drift.
What I found genuinely powerful was the connection the coach drew between gratitude and values. He asked — and this one landed hard — not just what are your values as a coach, but how do you demonstrate them? Those are two completely different questions. I can tell you my values in thirty seconds. But showing you how I actually demonstrate them in practice? That requires me to have been paying attention to myself. That requires reflection. And the more I heard him connect gratitude to the kind of intentional coaching shift that actually changes careers, the more I understood why it belongs in a structured review process rather than just left to chance.
There's also something deeper here about adaptation — the coach made the link himself, almost cautiously, connecting gratitude to the broader idea of skill adaptation and perceptual learning. He didn't fully draw the line, but I think the intuition is right. When you consistently review what you felt, noticed, and appreciated in a session, you're not just journaling. You're refining your own perceptual system as a coach. You're becoming more attuned to the environment you're working in. That's not separate from the ecological approach to learning — it's basically the same principle applied to the coach instead of the player.
Final Thoughts
I came away from this podcast feeling like I'd been handed a mirror. The Plan-Do-Review framework isn't complicated. It doesn't require a philosophy degree or a research background. It just requires honesty — about your preparation, your energy, your communication, who you're showing up for and whether you actually know why. The coaches who'll benefit most from this aren't the ones who are doing everything wrong. They're the ones doing everything right on the surface but running on fumes underneath, disconnected from the reason they ever picked up a clipboard. If that's you — and at some point it's been most of us — this framework is worth trying. Not because someone told you to. But because you already know the reflection is overdue, and sometimes all it takes is a structure that makes it feel safe enough to start.
