When Should Leaders Teach Playing To Win In Training?

I still get a rush thinking about how a single shift in mindset remade the whole way I approach training. When 'playing to win' becomes the lodestar, the daily design of practices tightens up — every drill, warm-up, and scrimmage is framed by measurable outcomes. That means less free-form play and more situational reps that mimic late-game pressure, set-piece sequences, and opponent-specific problem solving. It also changes communication: feedback is crisper, with clear KPI-like checkpoints (decision speed, conversion rate, defensive transitions) instead of vague encouragement. I found this makes athletes adapt faster tactically, but it can also thin patience for long-term skill cultivation if you don't protect space for experimentation. Beyond sessions, selection and squad management shift dramatically. Playing to win nudges coaches toward shorter leashes on development projects, faster rotations of personnel, and sometimes morally gray tradeoffs—minutes for veterans who help secure results over nurturing a raw talent. I've seen teams win more short-term, but sometimes lose the culture that keeps players engaged for years. For me, the takeaway is balance: you can harness the competitive edge of winning-focused coaching while carving out explicit time and permission to fail, so the team doesn't become a factory of outcomes at the cost of growth.

One of my favorite recurring moments in the Pokémon world is when a protagonist actually gets coached or straight-up trained by a gym leader — it feels like a real mentor arc, not just another battle. In the anime, the clearest and longest-running example is Ash with Brock. Brock is the Pewter City Gym Leader and he spent years traveling with Ash, acting as cook, medic, and tactical adviser. He taught Ash fundamentals: how to care for Pokémon, how to think about team composition, and gave him battle strategy hints that Ash used through the original series and beyond. Later on, in Kalos, Ash gets hands-on help from Korrina (the Shalour City Gym Leader) around Mega Evolution; she’s not just a namesake you fight once and forget—Korrina helps Ash understand aura and the mechanics behind Mega Evolution for Lucario in a way that’s explicitly instructional. Clemont (the Lumiose Gym Leader) is another example: he travels with Ash in 'XY' and constantly provides technical help, training ideas, and even devices that change how Ash approaches battles. Those relationships are textbook “protagonist trained by a gym leader” in the anime space. May’s arc is another one that jumped out to me, because it’s more familial and personal. May is the daughter of Norman, the Petalburg Gym Leader, and that home connection means she has a mentor, parent, and Gym Leader in one person. Norman gives her critiques, advice on contest and battle technique, and that shapes how she grows into her role as a trainer and coordinator. That’s a neat dynamic because the training comes from someone with official standing in the Gym system, not just a casual mentor. Serena, while not trained in battle by a gym leader in the same formal way, receives mentorship from Clemont and other friends during her journey — it blurs the line between coaching and formal Gym-style training, but you can see the influence of gym-leader-level expertise on her development, especially in performance and battle pacing. If you nudge over to the games and manga, the idea still shows up but often in different flavors. In games the player character rarely has a long-term travelling Gym Leader coach the way anime protagonists do, but familial links exist — Norman is not just an anime dad; he’s the Hoenn Gym Leader in the games too, and that creates moments of mentorship for his child (and rival) characters. In the manga 'Pokémon Adventures' (which treats Gym Leaders and rivals differently than the show), you’ll also find protagonists learning from and clashing with Gym Leaders in ways that force growth. Overall, the best places to watch this play out are the early 'Indigo League' episodes for Brock-and-Ash mentorship, the 'Advanced Generation' arcs for May-and-Norman family training beats, and the 'XY' arc for Korrina and Clemont’s direct influence on Ash (Korrina’s episodes around Mega Evolution are especially satisfying). If you like mentor-style growth, those arcs hit that sweet spot where a Gym Leader isn’t just an obstacle — they’re a teacher, and the protagonists come out measurably better for it.

I've come to think of a playing-to-win strategy as less about clever hacks and more about courageous choice. For me that starts with deciding where you will play and, just as importantly, where you won’t. You can't be everything to everyone; the winning moves are born from ruthless focus and relentless customer empathy. I often tell myself that the sweet spot is where customer pain, your unique capabilities, and attractive economics overlap. After that, it’s about constructing a coherent system: clear value proposition, a repeatable way to reach customers, a set of capabilities you protect and invest in, and metrics that tell you if your choices are actually working. I learned a ton from reading 'Playing to Win' and then watching teams try to implement it—the theory is elegant, the practice messy. You need governance to keep trade-offs visible and a culture that tolerates experiments but also commits to bets when the data lines up. Personally, I sleep better when strategy is a set of deliberate trade-offs rather than a wish-list, and I love the clarity that comes with a real plan to win.

One scene in 'How to Train Your Dragon 2' that always sticks with me is the moment Astrid steps up in the dragon rescue — she doesn't just fight, she organizes. Watching her coordinate the other riders, send Stormfly into precise maneuvers, and make split-second calls made me realize her growth: she transitions from competitive sidekick to a leader people follow because she earns that trust through competence. Visually and narratively, the movie supports that shift. Her armor and posture are more deliberate, her dialogue sharper, and she takes initiative without stealing the spotlight from Hiccup. The raid on the training grounds and later the infiltration of Drago's stronghold show different sides of leadership — tactical planning, reading people and dragons, and keeping morale up when things go sideways. I especially love how she balances assertiveness with empathy; she can be blunt and fierce, but she also listens to Hiccup and accepts his ideas, which is rare in fantasy tropes. For me, Astrid's arc in this film feels like a masterclass in leading by example. She leads from the front, she protects the team, and she knows when to step back and trust others. It’s the kind of leadership that works in real life too — competence plus care — and it’s part of why I keep rewatching 'How to Train Your Dragon 2' with friends and pointing out little moments where she quietly holds everything together.

There’s something a little ritualistic about how I teach quotes about winners — it’s part storytelling, part workshop, and part locker-room nonsense that somehow sticks. After practice I’ll scribble a line on the whiteboard, something like ‘Winners focus on the next play,’ then we don’t just nod and move on: I ask players to tell a two-sentence story where that line mattered. That forces the quote out of platitude territory and into memory. I like breaking the quote down: what words are literal, which are metaphor, and what behaviors would prove it true. We turn it into drills — five reps where the person who makes the mistake must finish the next rep with extra effort, or film one play and annotate how someone acted like a ‘winner’ or didn’t. I also encourage personal variations: a player might tweak the quote into a tiny mantra they can whisper under pressure. Sometimes I bring in a book like 'Mindset' to show the science behind praise and effort, other times we laugh at a meme and still learn. The key is repetition plus meaning — the quote becomes a habit because it’s been argued, practiced, and owned. That’s when it stops being words on a wall and becomes part of how we play.

I love how 'Leaders Eat Last' flips the usual power script — it insists leadership is about guaranteeing a safe space for people to do their best, not about bossing people around or chasing short-term wins. Simon Sinek breaks down how biology and trust shape teams: when people feel secure, oxytocin and serotonin reward cooperation; when they're scared, cortisol wrecks focus. For a new manager, that translates into a simple but radical idea: prioritize your team’s wellbeing and the work follows. The book isn't just fluffy inspiration — it gives a framework for why protecting people from unnecessary stress and aligning everyone around a shared purpose actually pays off in resilience and creativity. The practical lessons that stuck with me are refreshingly actionable. First, build a 'circle of safety' — make your team feel like they belong and are protected from pointless politics or outside panic. That means shielding them from disruptive top-down pressure when possible, sharing context honestly, and being the person who absorbs the heat rather than passing it on. Second, lead by sacrifice: give credit liberally and take responsibility for mistakes. Give your team autonomy instead of micromanaging and watch trust compound. Third, hire for character and values, not just CVs; skills can be taught, but a cooperative mindset is rarer. Sinek’s focus on long-term thinking also warns against optimizing purely for quarterly metrics — that’s where culture gets hollowed out. For practical daily habits, I picked up things like running short one-on-ones, celebrating small wins publicly, being consistently available for questions, and creating tiny rituals (weekly check-ins, shared retrospectives) that reinforce connection. I've tried applying these ideas at work and in hobby groups, and the difference is real. When I started protecting my team from frantic executive emails and instead fed them context and realistic priorities, people experimented more and actually shipped better features. Owning up when I screwed up — even in small ways — made it easier for teammates to speak up when something was broken. It’s also helped me avoid the trap of hero-leadership: trying to be the lone superstar who saves the day. Instead, the wins feel communal, and morale stays higher even when the project schedule is brutal. The book pairs nicely with stories from games and comics where teams succeed because members trust each other and protect the vulnerable — the healer who stays alive in a raid only because the tank creates space, for example. That kind of mutual care is what 'Leaders Eat Last' champions, and honestly, it’s made me rethink how I want to lead: more steady, more human, and a lot less about timing the perfect victory pose.

Reading 'Playing to Win: How Strategy Really Works' felt like uncovering a playbook for life, not just business. The authors, Lafley and Martin, break down strategy into something tangible—no vague corporate jargon, just clear steps. One of the biggest takeaways for me was their 'cascading choices' framework. It starts with defining what winning looks like (your goal), then moves through where to compete, how to differentiate, and what capabilities are needed. It’s like building a puzzle where every piece locks into place logically. I used this framework to rethink my own goals, and suddenly, decisions felt less overwhelming. Another lesson that stuck with me is the idea of 'reverse engineering' success. Instead of starting with what you’re good at, you start with the end goal and work backward. It’s counterintuitive but powerful. The book uses P&G’s turnaround as an example—they didn’t just improve existing products; they asked, 'What would it take to dominate this market?' and then built the systems to make it happen. It made me realize how often we get stuck in incremental thinking instead of aiming for breakthroughs. The book’s practicality is its strength—it’s not theory; it’s a toolkit.

I’ve always loved the gritty bits of backstory, and Raven’s origin is one of those deliciously rough edges. From everything shown in 'RWBY', Raven Branwen didn’t polish her leadership in a classroom — she earned it in the tribe. She trained within the Branwen Tribe itself, living the nomadic, raid-centered life that shaped their code: survival, stealth, and brutal efficiency. The training was practical and relentless — hand-to-hand combat, guerilla tactics, and the kind of fieldcraft you only learn by doing under pressure. Elders and seasoned warriors tested recruits constantly, and Raven climbed that ladder by being sharp, ruthless, and fiercely independent. You can see that reflected in the way she moves and leads: quiet, economical, and dangerously confident. Her Semblance and unique fighting style were honed in real encounters rather than drills; leadership came as much from proving herself in raids and disputes as from any formal rites. The tribe’s culture emphasized adaptability, so she became a leader who trusts instinct and quick decisions more than protocol. That’s why when she shows up in the canon moments of 'RWBY', she feels like someone forged in the wild — not a polished commander but a predator who knows her flock and the landscape. I find that kind of origin incredibly compelling. It makes Raven messy and human, a leader whose authority is raw and earned, and it explains why she’s such a wild card in the story.

I've noticed that some companies wear 'playing to win' like a second skin, and you can spot them by how ruthlessly they choose where to play and how to win. Take Procter & Gamble — the company behind the authors of 'Playing to Win' — which used that framework to simplify portfolios and double down on brands and capabilities that actually moved the needle. P&G's choices were about focus: pick the battlefields and commit resources, then build the capabilities to sustain the fight. Amazon follows a similar script in its own way: pick customer pain points, reinvent the model (Prime, AWS) and accept short-term margin pain for long-term market control. I also see this in companies like Netflix and LEGO. Netflix decided it would own the content and the delivery experience; that was a clear where-to-play and how-to-win decision that rewired the whole company. LEGO returned to the core toy-and-imagination play space and layered partnerships and digital experiences on top. What makes these examples feel like actual wins is the discipline to align leadership, capabilities, and metrics — not just a flashy product launch. Personally, I love studying these moves because they feel like puzzle pieces snapping into place, and they teach more than any textbook ever could.

I've always found the real talk in 'The Hard Thing About Hard Things' cuts through the usual leadership fluff. It isn't about vision statements; it's about the visceral, daily panic of keeping a company alive when everything's on fire. For me, the most crucial lesson was about embracing the struggle without a playbook—Horowitz framing it as there being no rules when you're in the thick of it. You have to accept that you'll be making calls based on incomplete, often terrifying information, and that self-doubt is just part of the job, not a sign you're failing. Another huge takeaway is the brutal honesty required with your team. The book pushes you past wanting to be liked. You have to lay out the ugly truth, like when you're considering layoffs or a complete strategy pivot, because that transparency, as harsh as it feels, is what builds the trust needed to survive a crisis. It's less about inspirational speeches and more about saying 'Here’s the mess, we probably won't all make it, but this is the plan.' That shift from cheerleader to clear-eyed commander was a perspective I needed. He also gets into the psychological toll in a way few business books do. The 'struggle' isn't a metaphor; it's sleepless nights and feeling completely alone. His advice to find peers who get it—not to solve your problems, but just to listen—is practically a survival technique. The lesson isn't to overcome these feelings, but to manage them so they don't paralyze you while you're still expected to make payroll. It's a manual for resilience, not success, and that distinction is everything.