Cover of The Subordinates' Game

The Subordinates' Game

Read the story

72 chapters · 198329 words · Read 0 times

Non is an ambitious and overconfident guy in early 30s. He always talks big, yet the outputs of his works are small. He doesn’t understand much of what his responsibilities and what he has to actually do. On the contrary, Bell, a brilliant, good looking, and smart guy in late 20, is very cheerful and hardworking. Bell understands the whole workflow and all details of his work, yet he never bossy anyone. While Non acts like a boss, Bell tries to bring the whole team move forward together and nice to all people including his subordinates. Due to this, Non feels that Bell is taking his spot. However, Bell doesn’t even notice how Non actually feels about him. All other employees and executives feel the same that Non is really annoying and love to secretly support Bell. Bell is unaware that all of them maintain good environment of the workplace while plotting the way to humiliate Non every time they find a chance.

Chapter 4: The Emperor's New Slides

The morning of the quarterly executive sync dawned with a particular, crackling energy in the bullpen. Anya moved through the cubicles not with her usual sharp clicks, but with a silent, predator’s grace. She didn’t need to give orders. A glance at David, a raised eyebrow at Maya, a subtle tilt of her head toward Bell’s workstation was all the instruction required.

The plan was simple: ensure Bell’s relentless helpfulness became his cage for the next ninety minutes.

“Bell, man, I’m hitting a wall with this integration script,” David called out, genuine frustration in his voice made sharper by his secret purpose. “The API is throwing a 429 error, but the retry logic you suggested is just eating it. Can you eyeball it for two seconds?”

“Of course,” Bell said, already swiveling his chair over. He was in his element.

As he began tracing through lines of code, Maya appeared at his other shoulder, a printed spreadsheet in her hand. “Bell, sorry to interrupt, but the quarterly figures from Finance… there’s a variance in the projected cloud costs. Miriam’s team is asking for a sanity check before the meeting. It’s probably nothing, but you have the best context.”

“Let’s see,” Bell said, not looking up from David’s screen, his mind already partitioning itself. “Is it the data warehouse compute or the legacy VM cluster?”

While he was triangulating between the two problems, Mike wandered over, holding a server schematic. “The new architecture for the payment module. The redundancy path. I have a concern.”

Bell, now the center of a benevolent vortex of need, simply nodded, absorbing all three threads. “Okay. David, your error handling is too aggressive, it’s missing the header reset. Change line forty-seven. Maya, the variance is the prepaid committed use discount we negotiated last month; it’s applied but not reflected in that projection tab. Mike, your concern is valid; swap the failover order and the latency drops.”

He solved their problems in under five minutes, a symphony of effortless competence. But each solution spawned a new, follow-up question, a necessary clarification, a “what-if” scenario. They were not malicious. They were real work blocks. And Bell, constitutionally incapable of leaving a thread dangling, patiently addressed each one.

Anya watched from the periphery, a satisfied ghost. She saw Non strut from his office, patting his suit jacket where the single, glorious summary slide was tucked. He glanced toward Bell, saw him deeply embroiled with three colleagues, and a visible wave of relief washed over his features. His path was clear.

“Alright, team,” Non announced, his voice too loud. “Holding down the fort. I’m off to align leadership on our strategic vision.” He sailed out toward the boardroom, the glass door swallowing his misplaced confidence.

In the bullpen, the coordinated pressure on Bell eased the moment Non disappeared. “Thanks, Bell,” David said, clapping him on the back. “You’re a legend.”

“Anytime,” Bell smiled, utterly unaware he’d just been tactically prevented from walking into a leadership slaughter. He turned back to his own monitor, the model of productivity.

The executive boardroom was a tomb of polished oak and suppressed sighs. The air, cooled to a crisp chill, carried the scent of expensive coffee and lemon-scented cleaner. Non stood at the head of the table, the large display behind him glowing with his lone slide—a masterpiece of clarity and concise data that he had not created.

“As you can see,” Non began, pointing a laser dot at a healthy, upward-trending graph, “our Q3 deliverables are tracking with aggressive positivity against the projected milestones. The team has really leaned into the core competencies, synergizing cross-functional bandwidth to maximize throughput.”

Ken, at the table’s opposite end, slowly stirred his coffee. Miriam, Head of Finance, adjusted her glasses. Marcus ‘The Muscle’ Reynolds, the tech lead, leaned back in his chair, his massive frame making the leather creak. His presence was a quiet, looming counterpoint to Non’s fluttering presentation.

“Can you quantify the ‘throughput’ in terms of story points completed versus committed?” Ken asked, his tone neutral.

Non’s laser dot wobbled. “Absolutely. It’s… a significant uplift. A direct result of my hands-on sprint management and daily stand-up refinements.”

“What was the percentage?” Miriam pressed, her pen poised.

“The synergy makes a precise percentage… less meaningful,” Non parried, a bead of sweat tracing a path from his temple. “The key takeaway is the forward momentum.”

Marcus spoke, his voice a low rumble. “The slide mentions redesigning the service layer for the new compliance requirements. Which pattern did the team decide on? Gateway aggregation or a façade?”

Non stared at the slide. The bullet point read: Service Layer Refactor - Compliance. He cleared his throat. “We’re leveraging a best-practice, holistic pattern. It’s dynamic. The technical details are, frankly, beneath the strategic overview this forum requires.”

“I’d like the technical details,” Ken said, sipping his coffee. “They inform the cost.”

The questions fell like gentle, precise hammers. Each one targeted a specific, beautiful bullet point on the slide Bell had crafted. Each one sent Non deeper into a morass of circular buzzwords and evaporating substance. Leverage. Holistic. Paradigm. Ecosystem. His dress shirt developed dark patches under his arms. His answers became longer, emptier, a defensive fog of jargon.

Miriam’s expression shifted from polite attention to thinly veiled impatience. Ken’s face was a mask of calm appraisal. Marcus simply watched, his arms folded, a silent monument to actual knowledge.

It was then that Anya, who had been sitting quietly taking notes next to Ken, made her move. As Non floundered through a question about risk mitigation, she opened a sleek folder and slid a thick, neatly bound document across the table to Miriam. It was the full forty-page progress report. Bell’s report. Every data point, every technical decision, every cost analysis and risk log, meticulously documented and painfully clear.

Miriam opened it. Her eyes scanned a page, then another. She flipped to the architectural diagrams, her finger tracing the clean logic Marcus had helped devise. She checked the financial breakdown, seeing the precise variance Bell had identified minutes earlier. Her stern features softened, then settled into an expression of profound admiration.

Non, seeing her engrossed in the document, mistook her focus for fascination with his presentation materials. He puffed out his chest slightly, attempting to regain footing. “As you can see, the deep-dive documentation supports the high-level narrative—”

“How did you arrive at the projected savings figure on page thirty-two?” Miriam interrupted, not looking up from the report.

Non froze. “Page… thirty-two?”

“The computation for the reduced latency and its impact on cloud spend,” Marcus clarified, his voice like grinding stones.

The silence stretched. Non’s mouth opened and closed. The report, in all its terrifying detail, was a foreign country to him. He had only demanded the passport photo.

Ken finally set down his cup. The soft click was deafening. He looked from Non’s sweating, desperate face to the impeccable slide on the screen, then to the report in Miriam’s hands. He let the silence sit, a judgment in itself.

“This progress report,” Ken said, his words measured and clear, “is very impressive. It is detailed, careful, and exactly what we need to understand the project’s health.” He gestured to the screen. “And this summary is informative. It makes the complex easily understandable. Excellent work on the materials.”

A wave of pure, undiluted relief washed over Non. He heard the praise, felt it soak into his parched ego. He stood a little taller, the sweat now feeling like a badge of effortful triumph. He’d done it. He’d weathered the storm. The CEO was pleased. He was pleased with him.

“Thank you, Ken,” Non said, his voice regaining a shred of its earlier confidence. “The team is firing on all cylinders under my direction. I’m glad the deliverables resonate.”

“They do,” Ken said, his gaze unreadable. “We’ll take it from here. Thank you, Non.”

Dismissed, and believing himself victorious, Non gathered his one crumpled slide with a flourish. He nodded to the room, a magnanimous leader. “Always a pleasure.” He exited, pulling the boardroom door shut with a solid, happy thud.

The moment it closed, the atmosphere shifted. The held breaths were released. Miriam tossed the bound report onto the table with a soft thump. “That was embarrassing.”

“The work is outstanding,” Marcus rumbled. “Every question we had is answered in here. In detail. Clearly.”

“It’s Bell’s work,” Anya said quietly, stating what everyone now knew for certain. “The summary, the report, the architecture. All of it. Non couldn’t explain the font choice, much less the failover protocols.”

Ken leaned back, steepling his fingers. He looked at the closed door, then at the brilliant, orphaned work on the table. “The gap,” he said, “between the quality of the output and the understanding of the person ostensibly leading it is no longer a gap. It’s a chasm. And everyone in this room just watched him try to build a bridge out of corporate platitudes. It was pathetic.”

He wasn’t angry. He was… disappointed. A clean, cold, final sort of disappointment. The kind that makes decisions for you.

“The slide is informative,” Ken repeated, his earlier praise now hollowing out into its true, damning meaning. “The report is impressive. The presenter was a talking brochure, and not a well-written one.”

In the bullpen, Bell finally solved the last of the manufactured problems, unaware that his work had just been simultaneously celebrated and used as the definitive yardstick to measure a man’s profound inadequacy. Non walked back to his office, his step light, already composing a self-congratulatory email in his head, forever mistaking the praise for the product as praise for the person. The chasm widened, silent and deep, and on one side of it, the executives sat in quiet, unanimous disappointment. On the other, a man whistled a happy tune, completely alone.

On the other, a man whistled a happy tune, completely alone. The boardroom’s silence held for a three-count after the door clicked shut. Then Ken exhaled, a long, weary sound that seemed to deflate the room’s formal pressure. He gestured to the thick report. “That document is the project. Not his slide. This.”

Miriam nodded, tapping the cover. “The financial modelling is meticulous. The risk analysis is actually insightful, not just a copied template. This is senior-level work.”

“It’s Bell’s work,” Anya repeated, her voice a definitive period at the end of the sentence. “From the first data pull to the final conclusion. Non’s contribution was the deadline pressure and the demand for a single slide. He is a conduit. A noisy, anxious funnel. Nothing flows out of him that doesn’t first come from Bell or the team.”

Marcus shifted in his chair, the leather groaning in protest. “Seen it for months. The kid does the work. Non does the talking. The team knows it. Now you all know it.”

Ken swiveled his chair slowly, looking out the window at the city grid below. “So the question becomes,” he said, his reflection vague in the glass, “what is his actual function? If you removed Bell from the equation tomorrow, what would happen?”

The quiet was answer enough.

Anya leaned forward, her elbows on the polished table. “He would flail. Publicly. He has no independent grasp of the details. He manages up with buzzwords and manages down by taking credit. The operational machinery is entirely separate from him. He just… stands in front of the controls and looks busy.”

“The rumor is already spreading,” Miriam stated, not looking up from the report she was still leafing through with admiration. “Quietly. On my floor, they’re saying Non’s success is borrowed. That Bell is the actual engine. That every win Non claims smells like Bell’s cologne.”

A faint, dry smile touched Ken’s lips. He turned back to them. “Good.”

Miriam looked up, surprised. “Good?”

“It’s the truth finding its own shape,” Ken said. “A rumor like that isn’t sabotage. It’s collective recognition. It’s the market correcting a valuation. It means people are paying attention to what actually gets done, not just who talks loudest in a meeting.”

He paused, his gaze sweeping over Anya, Miriam, and Marcus. “But. We need to be careful. This rumor is a tool, not a trumpet. If Non hears it, he’ll panic and become unpredictable. He might lash out at Bell, try to sabotage him to prove his own worth. That damages the project. Worse, if Bell hears it…”

Ken let the thought hang. They all pictured it: Bell’s confused, earnest face, his inevitable attempt to defend his manager, to correct the record. It would shatter his focus. It might even make him leave.

“Bell can’t know,” Ken said, his tone firming up. “Not yet. His ignorance is his protection. It lets him operate at full capacity. And Non can’t know the rumor has reached this room. Let him enjoy his hollow victory today. It’ll make the eventual landing… instructive.”

Marcus grunted in agreement. Anya gave a single, sharp nod. Miriam closed the report, her hand resting on it protectively.

“So we let the rumor do its work,” Anya summarized. “We don’t propagate it, but we don’t stop it. We continue to create environments where their respective contributions are… visibly distinct.”

“Exactly,” Ken said. He stood up, signaling the meeting’s true end. “Support the work. Support Bell. Document everything. And give Non all the rope he could ever ask for.”

Back in the bullpen, two realities hummed side by side. In his office with the door closed, Non was typing a jubilant email to his own director. “Presentation was a home run… Ken visibly impressed… solidified my strategic leadership…” Each keystroke was a nail in a coffin he was building for himself.

Twenty feet away, Bell finished syncing the updated project files to the shared drive. He saw David struggling with a deployment log. “Here, try filtering by the transaction ID before you parse the timestamp,” he said, rolling his chair over again. The work, the real work, continued seamlessly, a deep, steady current flowing beneath the day’s fragile surface of perception and rumor.

Read on DreamPress

Write your own erotic story with AI