Fiction: This is an original fictional story. Characters and events are invented.
The hum of fluorescent lights blended with the clatter of keyboards as Jordan Polk navigated the open-plan office floor, coffee in hand and anxiety simmering beneath his carefully composed expression. On the muted screens around him, the RelayPath Solutions logo glowed—a familiar comfort from his seven steady years here—but today, the atmosphere buzzed with new uncertainty. Just last week, their biggest client had abruptly withdrawn a seven-figure contract, leaving project leads scrambling and upper management in a state of barely concealed panic. Whispers of layoffs had circulated, but instead of pink slips, the board had brought in Leslie Harriman, a director with a reputation for shaking things up.
“She’s from California—ran three launches at Dataverse,” someone had murmured in the break room. “Like a shot of reality through the heart of the place.”
Now Leslie stood at the front of a hastily organized Monday morning meeting, her dark suit crisp against the washed-out gray of the company conference room. Her voice carried with confident warmth as she introduced herself—but her eyes, Jordan noted, swept the room with clinical focus. “RelayPath is at an inflection point. We need radical transparency and radical accountability.” She clicked a remote. A slide titled Blue Monday Protocol appeared, five bullet points glowing in RelayPath’s signature teal.
Jordan’s pulse ticked up as she explained: weekly public rankings of teams and individuals on key performance metrics—tickets closed, response times, feature releases. The lowest quartile, Leslie promised, would be reviewed for fit and improvement plans. Faces around him shifted: worry, disbelief, muted bravado. Jordan felt the eyes of his product team swing his way. He’d been trusted to advocate for them—a steady hand in storms, but never the one steering the ship.
After the meeting, as the crowd dispersed in knots of quiet, Leslie intercepted him by the coffee machines. She smiled—a little too practiced—and leaned closer. “We need this, Jordan. I’d like you to be our pilot manager. You roll this out quietly, keep the team on board, and I’ll put your name forward to lead the new client solutions task force. Think of it as your shot.” A pause. “Can I count on you?”
Her words lingered as Jordan made his way back to his pod, passing Marcus Choi hunched over his monitor, headphones askew and jaw set. Marcus was talented—one of the sharpest full-stack developers in the office—but worn thin after months of late nights patching legacy code. Jordan perched on the edge of Marcus’ desk and dropped his voice. “Want to grab lunch later?”
Marcus gave a tired smile. “Depends if Leslie’s leaderboard has me at the bottom by noon.” He peeled off his headphones, sighing. “This… protocol. It’s just going to make the team more stressed.” He let the words hang, knuckles white around his stress ball. “People are already fried. Another metric, more pressure. Not sure I have it in me.”
Jordan felt the weight of responsibility settle heavier on his shoulders. “We’ll talk it through,” he promised, but his own certainty wavered.
He slipped away before his doubts showed, making a beeline for the HR office, where Vivian West’s lights were always on. Vivian—silver-haired and measured—looked up, reading his tension immediately. Jordan closed the door softly and slumped into a chair.
“You don’t like what’s coming either,” he said.
Vivian gave a small, rueful chuckle. “Forced transparency breeds anxiety. When people know they’re being measured and compared, trust evaporates. They retreat. You remember the last new tool they tried—half the staff started job-hunting before the month was out.” She folded her hands. “But Leslie’s hired to drive results. She’ll expect you to get in line. Are you ready for that heat?”
He shook his head, uncertain. “I want my shot, Viv. But not like this.”
Vivian’s eyes softened. “Just remember, sometimes safeguarding people is more important than climbing ladders. Especially when the ladders keep shifting under our feet.”
As he left her office, Jordan paused in the hallway, staring at a laminated poster extolling the virtues of collaboration and respect. The words felt oddly hollow now. In the bullpen, he glanced toward Marcus again—the tired eyes, the tremor in his hands—and then to the corner where product analysts whispered behind screens. The office felt changed already, as if the Blue Monday Protocol was rearranging gravity itself. Jordan squared his shoulders and walked back to his desk, caught between principle and ambition, knowing that the next move might fracture the team—or save his own future.
The first Blue Monday scores hit the company Slack channels before noon, bright bars and numbers ranking each RelayPath employee by their weekly throughput. People’s reactions ranged from forced jokes—”Guess I should’ve skipped lunch!”—to a brittle silence that settled in desk clusters. Jordan watched the chat scroll, feeling more like a referee at a boxing match than a product lead. The high scorers flashed green badges beside their avatars, a digital gold star; the bottom quartile lit up in anxious orange. Marcus was third from the bottom, his name uncomfortably visible.
Jordan tried to project normalcy, tapping out supportive comments in public chats. But in their product channel, the mood soured quickly.
#prod-team
JessieH: “So if you have a kid or sick parent, you’re just… toast?”
YusufM: “I did client work that’s not tracked. Where’s that count?”
AmberL: “Why even do help tickets if they drag your average down?”
He started writing a reassuring response, then deleted it, fingers clenched. The gulf between Leslie’s directives and what his team needed seemed to widen with every ding of a notification.
By Tuesday, the competitive hum curdled into backstage grumblings and private DMs. Marcus, usually quick with a meme or code suggestion, barely spoke. He was late for the daily standup, eyes rimmed red, muttering about API failures that weren’t his fault. At 11:30, a fresh leaderboard pinged the team’s shared monitor. His score—already low—had slipped further, thanks to a bug in the reporting tool that failed to log his overnight deploy.
Jessie shot Marcus a sympathetic look as the room fell quiet. Someone coughed. Jordan tried to redirect: “Numbers will be up to date after we debug the tracker. Let’s focus on blockers.” But the damage lingered; Marcus kept his gaze glued to the table.
The hour after lunch, Jordan’s calendar pinged. Leslie again, this time in her glassed-in office. She waved him in, blue graphs already glowing on her wall monitor, posture sharp as ever.
“There’s churn in the numbers,” she said, voice clipped. “People second-guessing, gaming the KPIs. You need to clamp down, Jordan. A few folks are undermining the dashboard in group chats. Some, including Marcus, don’t get that underperformance has consequences now. You’re supposed to be setting the tone.”
Jordan’s jaw tightened. “We’re tracking the wrong things, Leslie. Quiet contributors are being left out. Marcus pulled a twelve-hour fix last weekend and still went down the board—because the tool missed his commits.” He risked a glance at her—no softening in her eyes.
“That’s noise,” Leslie replied. “We need bias for action. And you, Jordan, can’t afford to have your team seen as resistant. You want the client-facing lead role? Show me you can command—not coddle.”
He left her office feeling scorched, uncertainty tightening into something closer to guilt. He caught Marcus by the staircase, pale and distracted, twirling his badge between his fingers.
“You okay?” Jordan asked.
Marcus shrugged. “Jessie and I helped QA all weekend, but Jessie’s still orange too. I get it—metrics matter. But this just… makes me want to hide.” He offered a weak smile. “Suppose that counts as lack of transparency.”
Jordan hesitated. “Let’s get through this sprint. We’ll figure something out, I promise.” But he didn’t know if he could make good on that promise—or if Leslie’s expectation was just setting them all up to fail.
In HR, Vivian tracked the rising complaints with a weary efficiency. At her desk, a sticky note marked every new DM and anxiety-fueled email—most anonymous, all worried. That afternoon, she stopped by Ava Li’s office, closing the door behind her.
“We’ve been down this road before, Ava,” Vivian said, voice low. “People are burning out. The board wants transformation, but this kind of ranking damages trust.”
Ava nodded, her brow furrowed. “Leslie’s mandate is results, but culture is my lane. Let’s not wait for collateral damage.” She tapped her desk thoughtfully. “Set a private all-hands for Friday morning. I want to hear what people aren’t saying in metrics.”
By day’s end, the group chat pings had escalated to open sarcasm, and Marcus was nowhere to be found. Watching the fading activity lights on his team’s profiles, Jordan realized splintering was well underway—and the deadline for picking his path was coming faster than he liked.
Jordan arrived early Friday, hoping the quiet would give him space to think before the all-hands Ava had called. Instead, even the empty office felt weighty—the common areas deserted, the overflow fridge humming, faded conference swag tossed aside. The Blue Monday dashboards flashed on wall screens in mute accusation, their neatness a mockery of the mess underneath.
He settled at his desk, opened his laptop, and reread the barrage of overnight Slack messages. Overnight customer complaint. Two missed deliverables. Now a high-priority integration bug had cost their only remaining mid-level client a day’s worth of shipment tracking. The error had started with a misconfigured API—an easy mistake under normal conditions, but this week, Marcus hadn’t updated the reference code, trusting that Amber’s module was current. Amber assumed Jessie had QA’d. No one had double-checked. Everyone was sleep-deprived, anxious, eyes on the leaderboard instead of their actual shared work.
Emails had already arrived from Ops and Sales. Subject lines: “Urgent: Root Cause Analysis Needed” and “Client Wants Update – Escalating.” Above those, a terse note from Leslie: Need to discuss—come by 8:45 sharp.
A cold dread formed in Jordan’s gut. In the meeting room, Leslie was already pacing, lips pressed thin. As soon as he entered, she started: “How does this happen, Jordan? That tracking API feeds right into the delivery dashboard. The client goes dark, their customers freak out, and suddenly this is all our problem.”
He tried to steady himself. “I’ve dug through the logs. It was a simple miscommunication—the team’s tired, juggling too much, worried about rankings…”
“Enough about feelings,” Leslie snapped, her voice echoing off the glass. “We’re talking accountability. Marcus wrote bad code. Amber and Jessie missed QA. But you, Jordan, should’ve caught it as product lead.”
He felt the accusation settle. The conversation was over before it began: Leslie needed someone to blame. “It’s not that simple. Blue Monday has everyone overworked and distracted, worried more about metrics than solving actual problems. We—”
Leslie cut him off. “If people can’t cut it, we find people who will. I need you to run a postmortem at noon. Own it, Jordan. Be visible, take the heat. I’ll talk to Ava. And if Marcus isn’t prepared with a full incident report, I want him off core deliverables. Understood?”
Jordan bit back an answer. He left, chest tight, the promised promotion now receding behind a wall of recrimination.
Back at the bullpen, Amber and Jessie sat together, speaking in low voices. Marcus hadn’t come in. A new message appeared—Marcus, working from home: Sorry about the deploy. Will send the report by 11. Not sure how much more I can do like this.
The chat fell silent. Amber looked at Jordan, expression drawn. “If Marcus leaves, we’re sunk. Nobody knows core legacy code like he does. But every time that leaderboard comes out, we all feel like it’d be easier not to show up.”
Jessie nodded, voice thick: “I’m tired of competing with my own team for who keeps their job. What are we even tracking?”
Jordan should have had answers, but the words stuck. How much of this job was he willing to trade for that next rung up the ladder?
Vivian stopped him by the kitchen, away from the monitors and prying eyes. She glanced up kindly, but the heaviness in her own posture matched his. “It’s not your job to be a scapegoat, Jordan. And it’s not right to hang Marcus out to dry—everyone knows he’s not failing, the system is.”
He stared at his coffee. “But repercussions come for whoever stands up first.”
Vivian’s eyes narrowed. “You can’t lead a team by hiding behind someone else’s blame. And Ava’s watching—don’t forget that. She asked me outright what’s really going on.”
The postmortem was a stilted affair. Jordan forced himself to take ownership before heads could turn to Marcus or anyone else. As soon as the call ended, his DMs filled with supportive messages—but also more confessions of burnout, anger, even plans to start looking elsewhere. Jessie’s last note echoed: We need you to fight for us, not just for yourself.
By late afternoon, Vivian flagged him into her office. “Jordan, HR’s gotten five formal complaints just today. Anonymous, but I can guess the authors. Marcus has asked for FMLA time if things don’t change. Jessie’s circulating a petition. Leslie’s deflecting up to Ava. If you have something to say to leadership, now’s when it’ll matter.”
Jordan glanced at the stack of open tabs, his self-evaluation form flashing in an unopened window beside the Blue Monday leaderboard. His next step—support his team at his own risk, or try to save himself and hope things changed anyway. No outcome seemed safe. But the only thing worse than taking a side, he realized, was not taking a side at all.
Jordan spent that long Friday night hunched over his laptop, the glassy blue flicker of the leaderboard glaring in the dark. After a fitful nap, he woke early Saturday with a clarity he hadn’t felt in months. The numbers and badges meant nothing if they left the company hollowed out: burned-out colleagues, good people pushed away. What would RelayPath even be if it lost what made it worth working for?
By Monday morning, he had a plan—and for once, it didn’t begin with asking permission. With Vivian’s help, he scheduled an emergency team forum, inviting Ava and key product staff for an open discussion on the protocol’s real impact. To his surprise, people joined, even some who’d never spoken up before. Marcus dialed in, camera off but listening. Jessie and Amber, voice shaking, described feeling invisible unless they were “on top.” Junior analysts shared how they’d stopped asking questions, afraid it’d hurt their metrics. Even team members who’d scored well admitted the new ranking had them anxious—isolated, always looking over their shoulder.
Vivian prompted gently, and Jordan shared what he’d tracked: turnover in the last two months up by a third, anonymous HR complaints tripled. Four team members on medical leave had cited work stress. Product velocity hadn’t improved—if anything, it had fallen, as people spent time tracking scores and worrying about faults instead of collaborating. Jordan laid the facts out in front of everyone, no blame, just reality. Marcus, after a pause, finally unmuted his mic. “I want to do great work, but not if it means competing against my own team. That’s not why I joined.” The Zoom chat filled with nods and heartfelt, nervous agreements.
The next day, Ava swept into the office earlier than usual. Her presence, usually calm, was now edged with urgency. She tapped Jordan on the shoulder. “I read the transcript. Thank you for showing us the full picture. I need you and Vivian upstairs at noon.”
The meeting in the executive suite was tense. Leslie defended the Blue Monday Protocol with energetic precision: “Early resistance is normal. We just need to push through, set clearer consequences.” But Ava, with a file of charts and a handful of employee testimonials from Vivian, cut in. “When the process is this painful and staff want to leave, that’s not healthy transparency. That’s instability.” She read out Marcus’s comment and cited drop-offs in cross-team project quality. “We need to pause before RelayPath turns into what we’re trying to fix.”
The outcome came in just after lunch: Ava announced an immediate suspension of Blue Monday. All performance tracking would be moved back to private manager reviews until a better alternative emerged. Ava named a task force to evaluate future approaches, led jointly by Vivian and—somewhat to his surprise—Jordan himself.
Later, Leslie was called into a separate leadership review. The details weren’t public, but her directives were now subject to Ava’s oversight. For the first time in weeks, the tension on the office floor eased tangibly—even if a few worried looks lingered.
Jordan was called to Ava’s corner office that evening. She regarded him with genuine respect. “You didn’t get the client-facing promotion,” she said, “but you didn’t walk away from your values either. I want you to spearhead a healthier culture initiative as part of the new task force. Help us find a way to hold people accountable and support them at the same time.”
The title wasn’t the one he’d hoped for, but sitting with his team later, watching Marcus smile for the first time in weeks, Jordan realized the work and the trust mattered more than any shiny new badge. Jessie caught his eye as they packed up. “You did right by us. That’s more than most would risk.”
Over the next weeks, RelayPath shifted course: smaller forums replaced mass rankings, burnouts dropped, and staff found their voices again. Jordan helped draft a new set of collaborative goals, this time actually listening to every rung of the ladder—finally living up to the poster by the hallway. Ava and Vivian coached him as he grew into a quieter, steadier kind of leadership. By spring, turnover slowed, and product quality rebounded. The company hadn’t solved every problem, but the old sense of shared mission flickered back to life. For once, Jordan felt not just useful or respected—but truly at home.
