Chapter 5: The Wolf in Trainer's Clothing
The email from Ken’s office arrived just after the morning stand-up. It was addressed to Bell, cc’d to David, Mike, Maya, and Anne. The subject line was benign: ‘Cross-Functional Initiative: Second Team Mentorship’. The body was a model of corporate prose, outlining a temporary but critical assignment to onboard and train the newly formed second team on the legacy codebase and current agile protocols. It emphasized knowledge transfer and leadership development. It was, in essence, a significant pile of extra work.
Non wasn’t on the thread.
He found out because Bell, ever transparent, forwarded it to him immediately with a note: “Seen this? Looks like a big opportunity. Happy to lead the charge.”
From his glass-walled office, Non watched Bell’s face. He saw not dread, but a spark of focused interest. Non’s own interpretation snapped into place, clean and self-serving as always. He stood up and walked onto the floor, a general surveying his troops.
“Team,” he announced, clapping his hands once. David and Mike looked up from their monitors. Maya paused her typing, her expression blank. Anne sipped her coffee, waiting.
“You’ve all seen the directive from leadership,” Non said, puffing his chest slightly. “The mentorship of the second team. A substantial undertaking.”
He paced slowly, hands clasped behind his back. “Now, I want you to see this for what it is. An investment in your… development. Bell, you’re a hard worker, but there are clear gaps in parallel task management. This will force you to improve. David, Mike—your technical skills are good, but your soft skills, your ability to articulate process? This will grind that edge. Maya, Anne, this is about scaling your operational precision.”
He stopped, offering a smile that felt like a dental inspection. “I, of course, was not assigned this extra workload. My portfolio is strategically focused. Leadership recognizes mastery when they see it. They need me clear-headed for the high-level directives. This task for you all? It’s a lesson. A chance to reflect. To grind. I expect you to absorb every scrap of learning from this so that when you return to our core projects, you bring more value to my team. Understood?”
The silence was thick. David stared at his keyboard, his jaw tight. Mike’s placid face remained unchanged, but he stopped spinning his pen. Maya slowly adjusted the frame on her desk. Only Bell nodded, earnest and accepting.
“Understood,” Bell said. “It’s a challenge. Juggling our core sprints with proper training for the new team… it’ll be a test of systemizing knowledge transfer. I’m looking forward to it.”
Non beamed, mistaking Bell’s enthusiasm for submission. “Good. That’s the spirit. Learn. Grow.” With a final, magnanimous nod, he retreated to his office, closing the door on a job well done.
The moment it clicked shut, David leaned over to Mike. “Grind? He thinks this is a punishment?”
Mike shrugged. “He thinks a spreadsheet is a database. His perceptions are not relevant.”
Maya and Anne exchanged a glance. They had been in Ken’s office the day before, along with David and Mike. The conversation had been starkly different from Non’s patronizing speech.
“We’re restructuring the reporting lines, but quietly,” Ken had said, his fingers tapping the polished wood. “This second team project is the vehicle. It’s real work, critical work. But its primary function is to create a formal, documented separation. Bell will be its de facto lead. You four will be its core. Your ‘extra work’ is the foundation of a new, competent team. Non will be left with the shell of his old one.”
“He won’t see it coming?” David had asked.
Anya, leaning against the window, had answered. “He’ll see what he always sees: his own superiority. He’ll think you’re all in remedial class. By the time he realizes he’s alone in an empty room, the door will be locked.”
Now, executing the plan, they moved to the training room. It was a fishbowl of glass and light. The second team—three new hires fresh from campus and two nervous transfers from marketing—sat in a semi-circle, their faces a mix of eagorship and terror.
Bell stood at the front, at ease. He hadn’t prepared a PowerPoint. He had a live code editor projected on one screen and a simple flowchart on the other. “Alright, welcome. The best way to learn this is to break it,” he said, smiling. “So let’s break something. Who wants to volunteer their machine to run the test suite?”
A hesitant hand went up. A young woman named Priya.
“Perfect. David, can you shotgun the legacy deployment script to her terminal? Mike, watch the network log. Let’s see what smoke we get.”
It wasn’t a lecture. It was a collaborative dissection. Bell narrated as David fired commands, as Mike called out anomalies. When the test failed—as it was meant to—Bell didn’t frown. He looked energized. “Okay! There’s our first lesson. The error is about missing dependencies. But look at the date on the error. That tells us this isn’t about her machine. This is about the artifact repository from two years ago. The problem is historical. Your first skill isn’t fixing code; it’s archaeological debugging.”
The trainees leaned forward. This was not the corporate onboarding they expected.
Non made his grand entrance twenty minutes in. He swept into the room, offering a broad, stagey smile. “How’s the boot camp proceeding?” he boomed.
Bell, mid-sentence explaining a version control branch strategy, paused. “It’s going well. We’re just digging into the dependency chain.”
“Excellent, excellent,” Non said, placing a hand on the back of Priya’s chair. She stiffened. “Remember, team, the big picture! Don’t get lost in the weeds of code. Think about synergies! Think about user stories!” He waved a hand vaguely. “The trees are important, but I am here to show you the forest!”
He stood there for an awkward minute, waiting for a question. The trainees looked from him to Bell, who was waiting politely. The only sound was the hum of the projectors.
“Right. Carry on,” Non finally said, his smile stiff. He strode out, his parting line hanging in the air, meaningless and hollow.
The second the door swished shut, a trainee named Ben whispered, “What’s a user story in this context?”
David snorted. “In his context? A bedtime story. Ignore it. Bell, show them the actual Jira mapping you made.”
Bell resumed, and the flow of practical knowledge swallowed Non’s interruption whole. By lunch, the second team had a shared Slack channel. Someone renamed it from ‘Second-Team-Onboarding’ to ‘Bell’s Brigade’. A meme appeared, crafted by David: a photo of Non from the company website with a cartoon thought bubble filled with floating buzzwords like ‘paradigm’ and ‘leverage,’ and a caption that read: ‘My manager when I ask a technical question.’
It was shared only within the brigade and the conspirators. Laughter was quiet, cathartic, and binding.
Across the room, Maya and Anne worked not on training, but on documentation. Maya compiled a list of every substantive question asked by the trainees, and next to it, who answered. Bell’s column was dense with checkmarks and brief, accurate summaries of his solutions. Non’s column had two entries: “Think about the forest,” and “Synergies.” Anne meticulously logged the time allocations, showing Bell and the others spending 90% of their scheduled hours on the new initiative, their core project work being seamlessly completed in the margins, through sheer efficiency.
Non, in his office, drafted a status email to Ken. “Mentorship initiative underway. My team is absorbing the challenge, though visibly strained by the extra workload. My guidance is ensuring they focus on strategic takeaways rather than minutiae. Their progress will reflect well on my leadership.”
He sent it, proud. He was steering the ship, even from a distance.
In the training room, Bell was helping Priya rewrite a configuration file, his focus complete. He felt the stretch of managing two teams, the pressure of new responsibility. It felt like growth. It felt like trust. The idea that it was a carefully laid trap to spring him from a sinking superior never once crossed his mind.
Ken read Non’s email, then opened the shared document Maya and Anne were updating in real-time. He compared the two realities side-by-side on his massive monitor. He allowed himself a small, private smile. The plan was not just working; it was accelerating.
Non was bragging about a burden he didn’t understand.
Bell was thriving under a responsibility he saw as a gift.
And the team that was silently, officially, becoming Bell’s was documenting every second of the divergence.
The rope, as requested, was now neatly coiled on Non’s desk. He was admiring its texture, believing it to be a trophy. He had begun, entirely on his own, to fashion one end into a noose.
He had begun, entirely on his own, to fashion one end into a noose. The chime of a priority email broke his self-satisfied reverie. It was from Ken. The subject line, ‘URGENT: Leadership Eyes Only’, made his pulse jump pleasantly.
“Non,” the message began, crisp and direct. “Need a discreet but critical analysis. The quarterly board deck has a data visualization on slide twelve that’s drawing questions. The underlying source files are a mess—merged cells, broken links, inconsistent formatting. I need someone with a strategic eye to untangle it, clean the data, and validate the narrative. I believe you’re the only one who can see both the big picture and the granular details required. This stays with you. Time-sensitive. Ken.”
Non read it twice. A warm flush of pride spread through his chest. Leadership eyes only. The only one. The phrasing was a potent balm, a direct affirmation of the very mastery he’d just been preening over. He was being personally tapped by the CEO for a sensitive, high-stakes fix. This was his moment to demonstrate the strategic value he was always touting.
He straightened his tie, a general receiving his orders. His reply was swift and confident. “Ken, consider it done. The task is in my hands. You don’t have to worry about a thing. I’ll have clean data and a coherent narrative for you by end of day.” He hit send with a flourish, the click of the mouse sounding like a lock snapping shut.
Across the building, Ken read the reply in his sunlit office. A slow, knowing smile touched his lips. He knew the second team was deep in a simulated deployment crisis, Bell wholly engrossed as David and Mike orchestrated a controlled server meltdown for the trainees. Non’s department was a ghost town. He was utterly, blissfully alone with the task.
Ken picked up his phone, speed-dialing Anya. “The bait is taken. Deploy the parallel track. Exactly as we discussed.”
In the glass-walled training room, Anya entered with a clipboard, the picture of officious calm. The air was thick with the smell of pizza boxes from a working lunch and the electric hum of focused problem-solving. Bell was sketching a network diagram on a whiteboard, a trainee named Leo tentatively suggesting a alternate routing path.
“Group, a small pivot,” Anya announced, not raising her voice. All heads turned. “A live-fire exercise just landed. Consider it your practical exam after today’s training.”
She explained the task, identical to the one Ken had sent Non: the corrupted board deck data on slide twelve. “Your objective is to diagnose, clean, and validate. Bell, David, Mike, Maya, Anne—your role is advisory only. You must let the trainees drive. Priya, Leo, Ben, Sara, and Mark—this is now yours. The files are in the shared drive, folder ‘Omega’. You have four hours.”
Anya caught Maya’s eye for a fraction of a second, a flicker of understanding passing between them. This was the examination.
Meanwhile, Non opened the ‘Omega’ folder. He expected a few spreadsheets. What he found was a digital rat’s nest. There were seventeen different files, some dating back three fiscal years, with naming conventions that seemed deliberately cryptic: ‘Q4_FINAL_v2_ACTUAL_rev5.xlsx’. Pivot tables linked to sources that no longer existed. Macros written in a deprecated version of the software that now threw silent errors.
His confidence curdled, just slightly. He cracked his knuckles. “Alright,” he muttered to his empty office. “Strategic eye. Granular details.” He opened the most recent file and stared at a galaxy of colored cells.
Back in the training room, the trainees huddled around two large monitors. “Okay, first, don’t touch anything original,” Priya said, her voice gaining steadiness. “Mike, is making a copy of the entire folder structure the right first move?”
“It’s the only move,” Mike said, his placid tone reassuring. “Corner the chaos before you try to tame it.”
“David, can you check if there’s version control on these?” Ben asked.
David shook his head, already navigating. “Nope. This is prehistoric. It’s like they used carrier pigeons. I’ll write a quick script to checksum everything so we know if anything changes during cleanup.”
Bell watched, arms crossed, a quiet coach on the sidelines. “Good. Leo, what’s your first analysis step? Don’t look at the graphs yet.”
Leo zoomed in on the raw data tabs. “Find the source truth. There are three columns labeled ‘Revenue’ with different numbers. I need to trace which one the final chart actually used, then see if it’s mathematically sound based on these other tabs.”
“Solid,” Bell nodded. “Sara, Mark—you’re on data hygiene. Scan for duplicates, nulls, and format inconsistencies. Use the tools Maya showed you.”
The room fell into a rhythm of focused calls and responses, the clatter of keyboards a staccato soundtrack. It was collaborative, systematic. They were a unit.
In his silent office, Non was sweating. He had decided to start with the final, presentation-ready chart and “work backwards.” But the chart was linked to a pivot table, which was linked to a defined range that, when he clicked it, took him to a cell reference that said ‘#REF!’. Error. He tried to trace precedents. The lines skittered across the screen like spilled ink, leading nowhere.
He grunted in frustration. This was beneath him. This was data janitor work. But Ken had asked him personally. The only one. He googled the error. The solutions were technical, involving named ranges and workbook connections. His understanding was superficial, a veneer. He fumbled with the toolbar menus, clicking options at random.
An hour in, the trainees had isolated the core discrepancy. “Found it!” Priya announced. “The chart uses ‘Revenue_Stream_A’ from the 2022 file, but that file was updated in March 2023. Someone linked to the old path. All the numbers from last Q4 are off by eighteen percent.”
“Can we fix the link or rebuild the table from the clean source?” Ben asked.
“Rebuild,” David and Mike said in unison.
“Always rebuild from clean truth,” Mike added. “Never trust a broken link.”
Maya and Anne observed, making notes on a tablet. Their log now had entries: ‘Trainee Priya identified source-of-truth corruption.’ ‘Trainee Ben proposed version-control protocol for legacy files.’ Each entry was a stone in a foundation.
Non’s screen was a constellation of open windows. He’d somehow managed to corrupt the one clean visualization he had. The chart now showed revenue as a flat line zero. Panic, a cold wire, tightened in his gut. He checked the clock. Two hours gone.
He drafted an email to Ken. “Making strong progress. The data intricacies are deeper than expected, validating your need for a high-level review.” He deleted it. It sounded weak. He needed a deliverable.
He thought of Bell. A sour resentment bubbled up. This was Bell’s kind of work. The granular, tedious junk. But he couldn’t ask. That would be an admission. Ken said it stayed with him.
He decided to manually re-enter the numbers from the final PDF of the old board deck into a new spreadsheet. It was brute-force, stupid, and prone to error, but it would look clean. He began typing, his fingers clumsy with agitation.
In the training room, with thirty minutes left, the new, clean slide was built. The trainees had scripted the data pull, documented every assumption, and created a one-page summary explaining the original error and the correction. Leo presented it to the group, his voice clear.
“So the narrative was wrong because it was built on abandoned data,” he concluded. “The corrected story shows a steeper dip in Q4, but a stronger recovery this Q1. The board’s old question about the ‘blip’ was actually a question about a ghost.”
Bell smiled, a real, warm expression of pride. “Excellent work. That’s not just cleaning. That’s forensic accounting. You just provided real value.”
Anya reappeared to collect the results. She took the trainees’ file and the detailed log from Maya. “Thank you. The board will be pleased.”
As the trainees exhaled, shared grins of exhausted triumph on their faces, Non was proofreading his manually typed numbers, his vision blurring. He had three columns done out of fifteen. The task was a suffocating quilt. His earlier pride was a distant memory, replaced by the gritty taste of impending failure.
He finally sent a short, strained email to Ken as the clock hit 5:00 PM. “Task is more complex than initial assessment. Requiring additional time to ensure strategic alignment. Will have a full report tomorrow EOD.”
The reply from Ken was instantaneous and neutral. “Understood.”
Non sat in the dying light of his monitor, the ‘Omega’ folder a gloating presence on his screen. The silence of his department was no longer peaceful; it was accusatory. Across the building, the second team and their mentors were packing up, the easy buzz of their conversation leaking into the hallway. They had passed their exam.
He had not. And for the first time, a sharp, naked fear cut through his arrogance. He was alone with the proof of his own limitations, and a request for more time felt like the first, tremulous confession of a lie he could no longer sustain.