9.3: The Champion Who Was Right About Everything... Almost!

NorthStar Logistics: The Training That Promised Everything

The training was excellent, three days for every team in engineering, and by the end of it NorthStar Logistics was officially trained on Scrum. Sarah Chen, who had been hired six months earlier to lead the transformation, had ten years of Agile coaching behind her, certifications, and two successful transformations on her resume, and she had come in with a clear mandate from CTO Rebecca Martinez to make the company Agile because it was moving too slowly and competitors were eating its lunch. On Monday morning the ceremonies started, the boards went live in the tool, the velocity dashboards were configured, and Sarah, having drafted a one-page Agile Operating Model and emailed it out Sunday night, felt ready and certain she was right. Within ten minutes of sitting in on the platform team's first Sprint Planning, she knew something was already wrong.

Marcus Reilly had been at NorthStar twelve years and had built most of the platform himself. He'd sat through the training, taken notes, nodded politely, and said almost nothing, and in Sprint Planning he simply ran his old meeting under a new name: estimates, assignments, deadlines. When Sarah gently suggested they start with the Sprint Goal and think about what value they were delivering, Marcus said the goal was to finish the database migration, and when she told him that was a task and asked him to think from the user's perspective, he paused and offered that customers should be able to keep using the platform without performance problems, then turned right back to the team and walked through the same task list as before. Sarah noted that night that the platform team was going through the motions and that Marcus was resistant. She wasn't wrong, exactly, but she misread the shape of it. Marcus wasn't opposed to Agile. He was reacting, in a way he couldn't quite have named even to himself, to being told that twelve years of judgment were now wrong, and what came out looked like polite compliance instead of the quiet refusal it actually was.

James Okonkwo, an engineer until a month earlier, had been nominated by Sarah for Product Owner because he was thoughtful and willing to learn, and because he had never once said no to anyone in his life. In the first Sprint, stakeholders called him constantly: sales needed a demo feature, customer success needed bug fixes, marketing wanted analytics, and James said yes to all of it, with no real sense of how to prioritize and no authority that felt real to him four weeks removed from being an engineer himself. The Sprint Goal was missed the first week and missed again the second. Sarah told him he needed to push back, that the Sprint Goal was sacred, and James said sales had a major customer demo coming, so Sarah told him he had to choose, the Sprint Goal mattered or it didn't. James went back to his team and told them they had to deliver the demo feature, and the Sprint Goal was missed again. By week six he was deferring every hard call to Sarah, who was now making product decisions herself and calling it coaching, while James learned nothing about being a Product Owner except how to do what Sarah told him. He started telling friends he wanted to go back to engineering. One of those friends mentioned it to Marcus, who filed it away.

Theresa Park led the data integration team, which handled real, high-stakes work across three shipping providers and two million orders a day, with compliance reporting that had to be flawless. She'd read the books Sarah recommended and understood Scrum well enough intellectually, but she didn't believe her team had the slack to learn a new way of working while keeping the pipelines running. So she built a Scrum board, held Daily Scrums when Sarah was around, and kept the dashboards looking exactly as green as they should. Underneath that, her team ran an 8 AM call before the official 9 AM Daily Scrum where the actual coordination happened, along with a private task tracker and a Slack channel no one outside the team saw. She wasn't sabotaging anything. She believed Sarah didn't understand the risk her team carried and was protecting it accordingly, but the effect was the same either way: Scrum wasn't actually being adopted there. Sarah, seeing only the green dashboard, told Rebecca that Theresa's team was doing well, and Rebecca, who had worried most about the team handling the most critical work, felt relieved.

Three months in, Sarah went to Rebecca with a firm assessment: Marcus was openly resistant, James was too soft to be a real Product Owner, the platform team was performing Scrum theater, and Marcus, in her view, needed to move into an individual contributor role so someone who actually believed in the change could take his place. Rebecca pointed out that Marcus had been there twelve years and knew the platform better than anyone, and Sarah said that was part of the problem, that he was invested in the old way. Rebecca said she'd think about it, without saying aloud that she'd hired Sarah to fix problems, not remove people, and that she was starting to worry Sarah was right about the diagnosis and wrong about the cure. Sarah didn't wait for an answer. She booked a one-on-one with Marcus the next week and told him directly that she didn't think he was really adopting Scrum, that he was going through the motions. Marcus, who had outlasted plenty of process changes before her, asked calmly for specific examples, and when she gave them, Sprint Planning as task allocation, standups as status updates, the Sprint Goal as an afterthought, he told her that she was asking him to change coordination patterns that had evolved for good reasons over years, that he was doing his best with what the training had given him, and that he wasn't opposed to it even if his execution wasn't perfect. Sarah pressed for a real commitment, telling him the team took its cue from him and that if he wasn't all in, they wouldn't be either. Marcus just said he was doing his job and wasn't sure what else she wanted. The conversation ended without resolution, Sarah convinced Marcus had lied about buying in, Marcus convinced Sarah didn't respect his experience. That evening he told two colleagues she wanted changes that didn't fit their work and clearly didn't understand what they did. Within a week the story circulating across half of engineering was that Sarah had told Marcus to get all in or leave, which she had never actually said, but which was now simply believed.

By month eight, Rebecca's confidence had worn thin. Sarah's reports still said the transformation was progressing, and the dashboards still looked reasonable, but Rebecca kept hearing things in hallways: Marcus had gone quietly cold toward Sarah, James looked worn down, and Theresa's team kept missing handoffs in ways that suggested real coordination gaps despite metrics that looked fine. Without telling Sarah, Rebecca hired an outside consultant, David Whitfield, for a four-week assessment, framing it to Sarah as a fresh pair of eyes to validate their progress. Sarah, mildly annoyed, assumed he'd simply confirm what she'd already been saying. David spent his first week only listening, interviewing Marcus, James, Theresa, Sarah, Rebecca, and a dozen others, sitting silently through ceremonies, reading memos and notes, and looking at what was actually being delivered rather than what the dashboards claimed. By the end of week two, the picture he'd assembled looked nothing like what Sarah had reported.

He sat down with Rebecca privately first, warning her some of it would be uncomfortable. The transformation had a vision problem, he said, but not the one Sarah assumed: leadership was clear about the destination, but nobody doing the actual work understood why they were heading there, since no one had ever explained what problem the change was meant to solve, which left Marcus treating it as a passing initiative he'd simply outlast. There was a skills problem too, in a different place than Sarah was looking, because she was treating training as equivalent to skill when they weren't the same thing at all: James lacked the skills to be a Product Owner, Marcus lacked the skills to facilitate a real Scrum team, Theresa lacked the skills to adapt Scrum to her context, and Sarah herself lacked the coaching skills the moment required, since coaching and teaching aren't the same craft. Beyond that, the organization's own incentives were fighting everything Sarah was trying to build: budgets still locked to fixed scope a year out, finance still wanting Gantt charts, sales commitments still overriding Sprint plans midstream, Marcus's bonus still tied to system reliability, Theresa's team still judged on uptime, James promoted on paper while the people who used to give him orders still expected to. The system was rewarding exactly the behavior Sarah was asking people to abandon, and the system, David said flatly, always wins that fight. On top of it, there wasn't enough capacity anywhere: Sarah alone coaching four teams while also setting strategy, James doing Product Owner work part time while still pulled into engineering fires, no Scrum Master for Marcus or Theresa at all, no room in any Sprint to actually act on a retrospective's own findings. And underneath all of it, there was no real plan, only a target state of "we are Agile" and a starting state of "we are not," with ceremonies and dashboards standing in for an actual path between the two. Rebecca, taking it all in, finally asked what to make of Sarah herself, and David chose his words carefully: she was right about nearly everything she'd diagnosed, the platform team wasn't really doing Scrum, James was struggling, the data team was running its own parallel system, but her certainty had generated resistance she couldn't see, the one-on-one with Marcus had done damage still spreading through the org, and her recommendation to remove Marcus would have been close to catastrophic, since losing the one person who actually understood the platform would have cost the company six months of crisis.

What David proposed instead was slower and less satisfying than anything Sarah had offered. The organization needed to name its actual problems in measurable terms, cycle time, quality, missed customer commitments, rather than chase a framework for its own sake, so that everyone from Rebecca down could say plainly what the change was for. It needed real skill-building instead of training, months of pairing with experienced coaches rather than days in a room, an outside mentor for James, and Sarah stepping back from day-to-day coaching into strategy so other coaches could work with teams without her authority distorting the relationship. The incentive system had to change before behavior could, meaning finance, sales, and performance reviews all needed to measure something different, or every new practice would keep fighting the system it lived inside. The organization needed real capacity, fewer teams transforming at once, more coaches, or less demanded of people during the transition, instead of asking everyone to rebuild the plane mid-flight with no extra fuel. There needed to be an honest, phased plan with real checkpoints and the willingness to slow down when something wasn't working, not a roadmap that simply promised Agile by year's end. Sarah needed an entirely different conversation with Marcus than the one she'd already had, something closer to admitting she'd made assumptions worth revisiting and asking what would actually help his team. And the relationship between Sarah and Rebecca itself needed to change, since both of them had spent months protecting each other from bad news instead of trading it honestly.

David sat down with Sarah in week four and told her directly that her diagnosis of the organization was largely right but incomplete, and that some of what she'd done had made the resistance worse rather than better. Sarah was defensive at first, citing her years of experience and the organizations she'd seen before this one. David told her he wasn't saying she was bad at her job, only that she'd walked into a complicated system and treated it like a simple one, diagnosing the people as the problem when they were responding rationally to a system that rewarded exactly what she was asking them to stop doing. Marcus wasn't resisting Agile, he said. He was responding to being told his experience didn't count. Theresa wasn't faking compliance, she was protecting her team from what looked, from where she sat, like genuine risk. James wasn't too soft, he was doing a job he'd never been prepared for inside a system that had never actually given him authority. Sarah sat with that for a long time before asking what David wanted her to do. He said he didn't want anything from her, that the decision belonged to Rebecca, but that if she wanted his honest advice, her next conversation with Marcus should look nothing like the last one, and her next memo to Rebecca should say more plainly what she didn't yet know.

Rebecca read David's full report on a Friday night, read it again Saturday morning, and by Sunday had highlighted three sections with notes in the margins. By Monday she had decisions in front of her that none of them were easy: accept David's plan and slow everything down at real cost, both in money and in the argument she'd have to make to an already impatient board; let Sarah continue as she had been, a path David had called unlikely to produce real transformation and likely, eventually, to cost them Marcus; replace Sarah outright and absorb another six months of disruption while signaling to the whole organization that the transformation was failing; or find something in between that she hadn't yet figured out how to define. She had a one-on-one scheduled with Sarah for Tuesday and didn't know yet what she was going to say. In the meantime, the ceremonies kept happening exactly as before. The dashboards stayed green wherever they'd already been green. Marcus kept running his planning meetings the way he always had. James kept saying yes. Theresa's team kept its parallel system quietly humming along beneath the official one. And the actual problems that had started the transformation in the first place, cycle time, quality, the competitors who kept moving faster, were all still sitting there, untouched, eight months into a transformation that wasn't yet one.