The Silent Sabotage

My fingers were shaking as I clicked ‘present’ and waited for the slides to load.

The screen stayed black. Just a cursor blinking, silent and mocking. My mouth went dry, and a cold wave washed over my skin. I could hear the restless shifting in the boardroom.

Sweat beaded on my forehead. I frantically clicked again, then the next slide, nothing. The air felt thick with tension. Mr. Harrison leaned forward, “Is there a problem, Sarah?” His voice was smooth, too smooth.

I looked at my laptop, the one I had literally *just* connected, everything tested perfectly an hour ago. My stomach clenched. There was no way this was a glitch. Someone had done this. They had *changed* something.

The conference room door creaked open, letting in a shaft of bright hallway light. It was Mark from IT. He looked straight at Mr. Harrison, not at me.

Mark cleared his throat and said, “Mr. Harrison, I have that file you asked for earlier.”

👇 Full story continued in the comments…Mark cleared his throat and said, “Mr. Harrison, I have that file you asked for earlier.”

Mr. Harrison took the file Mark held out, a thin manila folder, and placed it casually on the table beside him. He didn’t open it, just rested his hand on it, his fingers drumming lightly. His gaze was back on me, and that smile, still in place, seemed to widen infinitesimally. “Thank you, Mark,” he said, his voice carrying across the room. “That will be all for now.”

Mark nodded, gave me a quick, unreadable glance, and slipped back out the door. My heart hammered against my ribs. A file? What file? And why now, at this exact moment? It couldn’t be a coincidence. The pieces slammed together with sickening force. Harrison, Mark, the timing, the black screen, the *smile*. He had orchestrated this.

“As you can see,” Harrison continued, his tone shifting from smooth concern to something colder, “the presentation is… unavailable. A technical failure, it seems. Highly unfortunate, Sarah, given the critical nature of this update.” He paused, letting the implication hang in the air – that I was incompetent.

My mind raced. I had poured everything into this project, into this presentation. It was supposed to be the culmination of months of work, detailing significant progress that flew in the face of Harrison’s pessimistic projections. He didn’t *want* this project to succeed, or at least, not under my leadership.

“There was no technical failure, Mr. Harrison,” I said, my voice trembling slightly, but the anger overriding my fear. The others in the room exchanged surprised looks. Harrison’s smile faltered for a split second before snapping back into place, sharper this time.

“A bold claim, Sarah,” he said softly, leaning back. “Are you suggesting sabotage?”

I looked at the file under his hand. What was in it? Was it a report on the ‘technical failure’? Instructions to Mark? Or something else entirely? I remembered a strange network activity alert I’d dismissed last night, a brief spike of access to the project server from an unusual IP address.

“I suggest,” I said, pushing back the fear, “that my presentation files were intentionally corrupted or blocked. Everything tested perfectly just before I connected.” I looked pointedly at the folder on the table. “Perhaps that file contains information relevant to the issue? An IT report on network anomalies, perhaps?”

Harrison’s eyes narrowed. He picked up the file, holding it loosely. The air crackled with tension. The executives around the table were watching us, sensing the real drama unfolding.

“This file,” Harrison said, his voice regaining its smooth command, “is simply a status update on a separate matter.” He made a move to open it, but I spoke quickly.

“Or is it a report confirming unauthorized access to the project directory last night?” I pressed, a sudden intuitive leap guiding my words. “Access that altered key data feeds necessary for my presentation’s integrity?”

A muscle twitched in Harrison’s jaw. He didn’t open the file. He couldn’t. I had guessed right. The black screen wasn’t just a presentation failure; it was the result of data corruption he’d orchestrated, and Mark had just delivered the IT report confirming it, a report Harrison likely intended to use to frame the failure as my fault or a systemic issue, not sabotage. His smile at the start was the look of a man whose plan was succeeding.

“This meeting is adjourned,” Harrison announced abruptly, standing up. “We will investigate this ‘technical failure’ and reschedule.” He scooped up the file, clutching it tightly.

But the spell was broken. My accusation, the specific mention of unauthorized access and data alteration, and Harrison’s sudden dismissal of the meeting, had landed. The executives weren’t looking at the black screen anymore; they were looking at Harrison and the file in his hand. Whispers started immediately as he practically strode out of the room, the file a damning piece of evidence he couldn’t let go of.

I didn’t get to give my presentation that day. But as the room cleared, several colleagues approached me quietly, asking questions, offering support, and confirming their own suspicions about Harrison’s methods. The project might have failed to appear on screen, but by calling out the sabotage, I had exposed the man behind it, ensuring that while the project faced a setback, my reputation, and the truth, would ultimately prevail. The smile was wiped from Mr. Harrison’s face, replaced by the cold dread of exposure.