My Coworker Stole My Work for Ten Months — So I Built Him a Trap He Walked Into Himself
Part 2
Hartwell didn’t raise his voice.
That was the part I hadn’t fully anticipated — how quiet it would be.
He closed the report, set it flat on the table, and said he’d seen this document before.
Not the content.
The structure.
He’d noticed my formatting months ago and had quietly started tracking which reports were actually moving the company’s metrics.
He knew.
He’d known for longer than I had realized, and he’d been waiting for Derek to walk himself off a ledge.
Derek’s face did something I can only describe as deflating.
All that practiced confidence, all those smooth pivots and borrowed phrases — none of it had anywhere to go.
Hartwell told him to gather his things.
Not angrily.
Almost gently, the way you speak to someone whose situation is already too obvious to require emphasis.
Derek left the building that afternoon.
I sat at my desk and stared at my monitor for a long time.
I wasn’t celebrating.
I was thinking about the document — specifically, about the copies I suspected Derek had made.
He was the kind of man who kept files.
He liked having leverage, liked the feeling of walking into a room with something in his pocket.
I’d built the red folder knowing that.
Three months later, a contact at another firm mentioned a disaster in their logistics chain — a major breakdown in their Q4 planning that had cost them somewhere north of four million dollars.
The source of the bad data traced back to a consultant they’d recently brought in.
The consultant’s name was Derek.
He’d used the red folder.
He’d taken my poisoned document to a new company, repackaged it, and presented it as proprietary analysis.
The watermarks held.
The file metadata held.
The sentence on page four held.
The investigation was not kind to him.
I heard about it secondhand, over coffee, from someone who had no idea I was the one who’d built the trap.
I just nodded and said that sounded like a serious situation.
Here’s what I keep coming back to, though — if you’d been sitting across from Derek in that conference room, watching him smile and flip through those pages, would you have seen it coming?
Part 3
The Red Folder
Part One
Ryan kept his desk the way some people keep a secret — everything in its exact place, nothing there by accident.
The stapler sat at a precise forty-five-degree angle to the monitor stand.
His reference binders ran alphabetical order, left to right, their spines flush with the desk edge.
Printed reports waited in a shallow tray, never stacked higher than three deep, always facing the same direction.
His colleagues had noticed this over the years and stopped noticing it, the way you stop noticing someone’s handwriting after enough time with their emails.
The corner of the second floor belonged to the data team — a quiet quadrant of humming monitors and cold coffee cups, where the real architecture of the company happened without fanfare or foot traffic.
Ryan had worked there for four years.
He had mapped supply chains, modeled failure scenarios, and built dashboards that the executive team relied on every quarter without once asking who had built them.
That was fine with him.
He was thirty-one years old and had long since stopped expecting recognition to arrive on schedule.
What he had not expected was Derek.
Derek Marsh joined the company in the spring, eighteen months after Ryan, transferring in from a regional office where, apparently, he had been highly regarded.
Ryan noticed him the first week — not because Derek was loud, but because Derek was strategic about noise.
He laughed at the right moments in meetings, a beat before everyone else, so that his laughter seemed to set the tone rather than follow it.
He emailed the right people and always found a way to copy someone senior without making it feel like a CYA maneuver.
He had an instinct for political weather the way some people have an instinct for rain, and he moved accordingly — always dry, always composed, always standing in the right part of the room when the sun came out.
Ryan had nothing against charisma.
He understood its value and had no particular ambition to compete with it.
What he had against Derek was specific and accumulating.
It started in the third week of October.
Ryan had spent a Tuesday evening finishing a supply chain vulnerability report — twelve pages of careful analysis, color-coded by risk tier, with a three-page executive summary that he had revised four times until the language was exactly right.
He printed it and left it on his desk before he went home, because he always printed his work before Friday syncs.
It was old-fashioned of him and he knew it.
He liked the ritual of it — the physical weight of the thing, the way a printed document felt different from a file name in a folder.
Monday morning, the report was gone.
Ryan looked for it the way you look for something you are almost certain you have simply misplaced — checking the drawer, the recycling tray, the shelf above the monitor, the surface of the filing cabinet.
Nothing.
Tuesday sync came at nine-thirty.
Derek walked in holding a stack of papers and distributed them around the conference table with the easy efficiency of a man accustomed to being thanked for things.
Ryan looked at the first page of the handout and felt something go very still inside him.
The formatting was his.
The tier-color system was his.
The executive summary — all three pages of it, including the fourth revision — was his.
Derek presented it to Mr. Hartwell without a single hesitation, his voice carrying the mild authority of someone who had done the work and was simply explaining it.
Hartwell nodded through the key points, made a small note in the margin of his copy, and called it solid work.
Ryan sat at the end of the table and said nothing.
He kept his hands flat on the surface and looked at the document and breathed slowly in through his nose.
After the meeting, Derek walked past Ryan’s desk and gave him a small nod — the collegial, half-distracted nod of a man acknowledging a piece of furniture he passes every day.
Ryan nodded back.
He opened a new spreadsheet that afternoon and started a log.
The log was simple and precise, because Ryan was simple and precise about the things that mattered to him.
Date, document title, total pages, what was taken, what was said, who heard it, Hartwell’s response.
He kept it in a folder labeled Q4 Admin — nothing that a casual glance would flag as anything other than routine filing.
He did not tell anyone about the log.
He did not mention what he had seen to anyone at the office, not even to Sandra, who had worked in the same corner of the floor for three years and whose opinions on her colleagues were sharp and accurate.
Over the next ten months, the log grew to eleven separate entries.
The pattern was consistent, almost rhythmic: Ryan would leave printed work on his desk, Derek would absorb it over the following weekend or during an evening when the floor was quiet, and by the next Tuesday sync it would be reborn as Derek’s insight, Derek’s analysis, Derek’s contribution to the company’s direction.
The scale escalated slowly, the way all successful schemes escalate — by increments small enough that no single step feels like a significant departure from the last.
Early on it was summary reports and status updates.
By spring it was full quarterly analyses, sixty-page documents that Ryan had spent weeks building from raw data.
By summer, Derek was being described by Mr. Hartwell in all-hands meetings as one of the sharpest strategic minds on the team.
Ryan heard this at the August all-hands and sat in the third row and kept his expression neutral and clapped at the appropriate moments.
That evening, he spent four hours cataloging his own work from the previous fourteen months.
He cross-referenced submission timestamps against meeting dates, pulled version-control histories from the internal system, and traced the metadata trails embedded in every document he had ever exported.
The evidence was unambiguous and it was extensive.
He printed a twelve-page summary of it and put it in the Q4 Admin folder.
What he did with it was a separate question.
He could have gone to HR.
He considered it the way you consider taking an umbrella when it is only slightly cloudy — technically advisable, the procedurally correct response, but not the one that made the most sense given the specific terrain.
The problem with HR was documentation drag: the formal process would take weeks, Derek would be notified, and the outcome would be murky — a finding, a conversation, possibly a warning, possibly nothing.
The problem with confronting Derek directly was that Derek was the kind of man who could make a conflict look like it originated from the person complaining about it.
Ryan had watched him do exactly that to a junior analyst named Paul, who had raised a legitimate workflow concern in January and spent the next two months quietly being excluded from key project threads, his access to shared drives mysteriously deprioritized in the IT queue.
Paul had eventually transferred to a different team.
He had not looked happy about it.
So Ryan waited.
He kept his face the same in every meeting — attentive, neutral, occasionally noting something in his own pad.
He kept leaving printed work on his desk.
He let Derek keep taking it.
He was studying Derek’s rhythm with the same methodical patience he brought to complex data problems: the cadence of the theft, how quickly Derek acted after spotting something on the desk, what he modified and what he left intact, how thoroughly he claimed to understand the material he was presenting.
That last element was the key.
Derek was not a data person.
He had never been a data person.
He was a presentation person — a man who could make any set of information sound authoritative and strategic, who had a gift for knowing which numbers to emphasize and which to glide past, who understood instinctively how to read a room and adjust his delivery.
But he could not generate the underlying logic himself.
He could not answer a question that went one level deeper than the executive summary.
He understood what the numbers said at the surface, not why the numbers were what they were or what would happen if the assumptions behind them were wrong.
That gap — the distance between what Derek could perform and what Derek actually knew — was the foundation Ryan needed.
He started thinking about it in July, while debugging a recursive join error that had kept him at his desk past eight in the evening.
He thought about it on the drive home and through most of dinner and while he was trying to sleep.
By September he had the architecture of it mapped out in his head.
By October he was ready to build it.
He called it the red folder, though only in his own head, and only because the folder he chose was a red one.
Part Two
On the outside, the red folder was indistinguishable from every other report Ryan had ever produced.
Same header font, the same one he had used for three years.
Same footer format with the document version number in the lower right.
Same corner-staple — always top-left, always at exactly the same angle.
Same paper weight, because Ryan bought his own paper rather than using the common supply, a habit he had maintained since his first job and had never bothered to explain.
Inside it was something else entirely.
The logistics data looked real in the way that a well-made replica looks real — not because it was identical to the genuine article, but because it had all the surface properties a casual eye would expect.
The tables populated correctly.
The graphs moved in the right directions.
The footnotes cited plausible sources.
The executive summary was written in exactly the voice Derek had spent ten months learning to parrot — the precise combination of hedged confidence and strategic implication that Hartwell seemed to respond to.
Ryan had spent three weeks getting all of it exactly right.
But the Q3 throughput projections buried in section four were wrong in a way that was invisible to anyone who did not understand how throughput modeling actually worked.
Wrong by a margin that looked like a bold but defensible forecast and was actually a catastrophic misrepresentation — the kind of error that, if anyone built operational planning around it, would generate a serious downstream failure within two fiscal quarters.
Ryan had also embedded three separate layers of invisible authentication into the document, each one independent of the others, any one of which would be sufficient to establish his authorship.
The first layer was a digital watermark in the file metadata — a timestamp, a workstation path, and a document fingerprint that could be extracted by any standard forensic IT tool, each pointing directly back to Ryan’s machine and user credentials.
The second layer was a steganographic marker embedded in the color values of the three chart backgrounds — a sequence of encoded data, imperceptible to the eye but readable by any software designed to look for it, which had been inserted using an open-source tool Ryan had spent an evening learning to use.
The third layer was a sentence on page four, set two points smaller than the body copy and formatted to look like a standard footnote attribution line, the kind that editors often skim.
It read: Original analysis prepared by R. Marsh — internal use only.
Ryan had used Derek’s own last name.
He had thought about that detail for a long time.
He had considered other approaches — using his own initials, using a timestamp, using nothing — and had kept coming back to Derek’s name.
It was the kind of thing that, if discovered before the trap closed, would look like an extraordinary accident.
And if discovered after, it would look like exactly what it was: a signature.
He placed the folder on his desk on a Thursday afternoon at four-fifty, when the floor was already thinning out toward the weekend.
He adjusted it to the precise angle he always used for printed materials.
He left his monitor on sleep, the way he always did.
He walked to the parking garage, drove home, and made dinner.
He did not sleep badly.
Part Three
Monday morning, the red folder was gone.
Ryan had known it would be.
He had known it before he left the building on Thursday, the same way you know the weather will change when you can feel the pressure in the air.
He sat down, logged into his workstation, and opened his Q4 Admin spreadsheet.
He made one final entry: date, document title, taken.
Then he closed the file, archived it in a compressed folder with a timestamp, and emailed a copy to his personal account.
Then he went to get coffee.
The weekly sync started at its usual time.
Derek arrived with his customary momentum — jacket hanging right, coffee cup from the good place down the street, the particular stride of a man who has never once, in his professional life, questioned whether he belonged in the room he was walking into.
He distributed the agenda with his usual ease.
He connected his laptop to the main screen and navigated to the slide deck with practiced familiarity.
Ryan took his seat at the far end of the table, the seat he always chose, and placed a glass of water in front of him.
Hartwell came in at nine thirty-two with his reading glasses already on.
That meant he had been reviewing something before the meeting, which meant he was already in a reading frame of mind rather than a listening one.
Ryan noted it and said nothing.
Derek opened on Q3 performance — the macro view, the headline numbers, the context-setting that he had learned to do well because it asked nothing of him technically.
He transitioned to the logistics analysis at the seven-minute mark.
He was smooth, as he always was.
The projections went up on the main screen and Ryan looked at them without expression.
Around the two-minute mark into Derek’s section, Hartwell stopped writing.
He had not put his pen down — he had simply stopped moving it, which was different, which was the kind of stillness that happens when something catches a careful person’s full attention.
His eyes went to the projections on the screen and stayed there.
Derek kept talking.
At the four-minute mark, Hartwell removed his reading glasses and set them carefully beside his notepad, the earpiece folded in.
Ryan had seen Hartwell do this twice before in four years.
Both times it had preceded a conversation that significantly changed someone’s position at the company.
Derek finished his summary and looked around the table with the practiced ease of a man who has learned that meetings end with applause if you look confident enough at the close.
Hartwell said: Walk me through the methodology on the Q3 throughput projections.
He said it the way you say it when you already know the answer and are simply giving the other person a chance to arrive there themselves.
Derek said he understood the question.
He found page four.
He started explaining.
He got approximately six words into the explanation before his cadence changed — a micro-hesitation, barely a quarter of a second, the kind of gap that would mean nothing to most of the people in the room.
Ryan noticed it.
He could see from the quality of Hartwell’s stillness that Hartwell noticed it too.
Derek recovered and kept talking, but the recovery was a different rhythm — improvised, constructed on the fly — and somewhere in the improvisation he introduced a small technical error that had nothing to do with the planted flaw in the data.
It was Derek’s own mistake, native to his actual understanding of the material, generated under the specific pressure of being asked to explain something he had never actually understood.
Hartwell let him finish the entire answer.
Then Hartwell said: That is not what the footnote attribution indicates.
Derek’s expression did something Ryan had never seen it do in ten months of watching him.
It paused.
Not a social pause, not the beat of a man gathering his next point.
Something behind the expression paused — the machinery that kept the surface running smoothly.
Hartwell turned to the rest of the room and asked everyone to give Derek and him a few minutes.
He said it quietly and evenly, and no one misunderstood what it meant.
Ryan picked up his water glass and walked out into the hallway.
Sandra from project management was near the door.
She gave him a look — the compressed-lips, wide-eyed look that means we both understand the significance of this and neither of us should say it aloud.
Ryan just walked back to his desk.
He sat down and opened a data pipeline he had been building for three weeks, found the join error he had been working through, and went back to it.
The office was quieter than it usually was for the next forty-five minutes.
At eleven-fifteen, Derek walked past Ryan’s desk.
He had his jacket on.
He was carrying a small cardboard box, the kind that holds a coffee mug and a desk plant and the accumulated personal items of a few years in one place.
He did not look in Ryan’s direction.
The sound of his footsteps on the tile crossed the floor and reached the elevator bay and then there was the sound of elevator doors and then there was nothing.
Ryan saved his work, noted the debug progress in his log, and went to refill his coffee.
Hartwell found him in the break room ten minutes later.
The CEO poured himself a coffee from the same pot and stood at the counter beside Ryan without saying anything for a moment, the way people stand at the counter when they are deciding how to begin.
Then Hartwell said that Ryan had been doing strong work.
Ryan said thank you.
Hartwell said he meant the real work.
Ryan looked at him.
Hartwell said they should sit down later in the week.
He took his coffee and left.
Ryan stood at the counter and felt the specific, quiet satisfaction of a system functioning exactly as designed — not the satisfaction of a fight won, not anything loud or celebratory, but the clean, structurally sound feeling of something built correctly coming to rest at its intended position.
He went back to his desk and finished the pipeline.
Part Four
The months after Derek’s departure were structurally different in ways that took Ryan a while to name precisely.
He got credit.
Not dramatically — there was no ceremony, no correction-of-the-record email sent to all staff, no formal acknowledgment of what had been happening for the previous ten months.
It happened the way real institutional change usually happens: gradually, in small recalibrations, each one individually unremarkable but collectively significant.
Hartwell started including Ryan in strategy conversations that previously would have gone through a project management layer.
Ryan’s name began appearing on the presentations he had built, which had not happened before.
The team started routing questions to him directly.
In November, a formal title change came through — senior data architect, a role that had not existed at the company before and that came with a modest budget for two direct reports.
Ryan interviewed four candidates and hired two of them.
He trained them the way he liked to work: precisely, methodically, with a consistent and documented system for everything that mattered.
He kept his desk exactly as it had always been.
Same font, same corner-staple, same printed reports before Friday syncs.
He did not mention Derek.
He did not tell the story of the red folder to his new reports or to Sandra or to anyone he worked with.
He kept the Q4 Admin spreadsheet archived in a compressed folder on his personal drive, the way you keep documentation for something that is settled but should not be destroyed.
In December, three months after Derek’s firing, Ryan attended an industry event downtown — the kind of mid-year gathering that his company sent two or three people to and that was primarily useful for conversations that happened in the spaces between the formal programming.
He ran into a woman named Beth, a logistics director at a competitor firm whose name he recognized from a conference the previous year.
Beth was not having a good evening.
He could tell from the particular way she was holding her wine glass — both hands, close to the chest, the posture of someone managing something.
Ryan asked how Q4 was shaping up and Beth made a sound that was not quite a laugh and not quite a sigh.
She said they had experienced a serious planning failure.
A consultant they had brought in mid-year had delivered an analysis that had caused a downstream operational collapse in their logistics chain.
The projected costs were still being tallied, she said, but the internal estimate was somewhere north of four million dollars.
Ryan asked what kind of analysis.
Beth described it.
Supply chain vulnerability assessment.
Q3 throughput projections.
Color-coded tier system with an executive summary.
Ryan set his drink down carefully on the tall table beside them and looked at the room.
Beth said the consultant had presented it as his own proprietary methodology, something he had developed at a previous firm.
Their IT team had found watermarks in the document during the investigation — three separate authentication layers, she said, with a kind of exhausted admiration for whoever had put them there.
The watermarks pointed back to a company the consultant had left under circumstances that were still, apparently, being sorted out.
Ryan said that sounded like a complicated situation.
Beth said it was a nightmare.
She said the consultant had already been let go and that the investigation was ongoing.
Someone appeared at her elbow and refilled her glass and she shifted to face them and the conversation moved on.
Ryan stood at the tall table alone for a moment.
He thought about page four.
He thought about the sentence set two points smaller than the body copy, the one that read like an attribution footnote but was actually a signature.
He thought about Derek walking into a conference room at a company he had never worked for, distributing those pages, settling into the chair with that stride and that easy look of authority.
He thought about the moment — probably around the two-minute mark, probably with reading glasses coming off somewhere in the room — when the machinery behind Derek’s expression had paused again.
Then Ryan picked up his drink and went to find someone more interesting to talk to, because the thing about well-designed systems is that they do not require your continued presence once they are running.
They run.
Epilogue
Ryan stayed at the company for another two years after that Tuesday meeting.
His title changed twice.
His team grew from two direct reports to eleven, the data function expanding to cover three business units that had previously managed their own analytics in siloed, incompatible spreadsheets.
He rebuilt the company’s entire data infrastructure over eighteen months — a project that had no public announcement, no ribbon-cutting, no moment when anyone said the thing out loud, but that the company would still be running seven years later, long after Ryan had moved on to a larger role at a different firm.
He never told anyone the full story of the red folder.
Not the planted flaw, not the three authentication layers, not the sentence on page four with Derek’s own last name in it.
Hartwell knew enough.
The IT department forensic log knew the technical details.
Ryan did not need the story to be known.
He had not built the trap to be impressive or to be told as a story.
He had built it because the problem required a solution, and the solution he had designed was the right one, and it had worked exactly as intended.
That was sufficient.
Years later, at a conference in a different city, a younger analyst approached him after a panel discussion on data governance and asked him a question she seemed almost hesitant to ask.
She said: How do you handle it when someone takes credit for your work?
The question had the particular texture of something personal — something she was not asking entirely in the abstract.
Ryan thought for a moment.
He set down his water glass.
He said: Document everything.
She nodded.
She was expecting more.
Ryan picked up his bag.
He said: And understand what they want.
She looked at him.
He didn’t explain further.
He walked toward the exit, and the hallway was long and the light overhead was white and flat and clean, and behind him the room continued, the conversations continuing, the glasses clinking, the accumulation of professional life going on as it always does — and Ryan walked out of it and into the parking structure and drove home, and the documentation was already done, and the system was already running, and he slept fine.
THE END
Tell us what you think about this story, and share it with your friends. It might inspire them and brighten their day.
If you enjoyed this story, read this one: My Father Tried to Steal My $14.5 Million Inheritance — He Left the Courtroom Facing 15 Years
Disclaimer
This story is a work of fiction inspired by real events. Names, characters, and details have been altered. Any resemblance is coincidental. The author and publisher disclaim accuracy, liability, and responsibility for interpretations or reliance. If you would like to share your story, please send it to [email protected].
