My Coworker Stole My Work for Ten Months — So I Built Him a Trap He Walked Into Himself
Part 1
For ten months, I watched another man take credit for my work — and I let him.
Not because I was afraid.
Not because I didn’t know what was happening.
I let him because I was building something, and I needed him to keep going until it was ready.
My name is Ryan, and I’m a data architect at a mid-sized logistics firm.
I’m not the guy people notice at company parties.
I’m the one in the corner with a coffee cup, watching the room like it’s a spreadsheet.
Derek was the opposite of me in every way that mattered at that company.
He had the handshake, the haircut, the laugh that arrived exactly when a room needed it.
Leadership loved him.
Everyone assumed he was the engine behind whatever project had gone well that quarter.
The truth was simpler and uglier than that.
Derek couldn’t architect a database schema if his career depended on it — and eventually, it did.
It started small enough that I almost missed it.
I’d leave a printed report on my desk before a Friday status meeting.
Monday morning, the report would be gone.
Tuesday, Derek would walk into the weekly sync and present those exact findings to Mr. Hartwell like he’d spent the weekend buried in data.
The first time it happened, I thought I’d made a mistake.
Maybe I’d left it somewhere he’d picked it up by accident.
The second time, I told myself I needed more evidence.
By the fifth time, I had a spreadsheet of my own — dates, documents, meeting timestamps, Derek’s exact phrasing lifted straight from my printed pages.
He wasn’t even paraphrasing.
He was reading my conclusions aloud and watching Mr. Hartwell nod.
I sat in those meetings and said nothing.
I kept my face neutral the way you keep a window closed during a storm.
Inside, something was calcifying.
This wasn’t frustration anymore.
This was architecture.
I started thinking about it the way I think about data systems — what’s the failure point, what’s the input that breaks everything, where does the whole structure collapse if you pull one piece out.
Derek’s weakness wasn’t arrogance, exactly.
His weakness was appetite.
He couldn’t stop himself from taking things.
Once you understand a person’s appetite, you can design a meal they can’t resist.
I spent three weeks building what I privately called the red folder.
On the outside, it looked exactly like every other report I’d ever left on my desk — the same font, the same header, the same corner-staple I always used.
Inside was a different story.
The data was fabricated, precisely and deliberately.
Every figure was designed to look authoritative while hiding a fatal flaw that any real expert would catch in under sixty seconds.
The logistics projections were off by exactly the kind of margin that would cause a serious operational problem if anyone acted on them.
I embedded invisible watermarks throughout the document.
Not the kind you see — the kind that survive photocopying, reformatting, even retyping.
Buried in the metadata of the digital version was a timestamp and a file path that led straight back to my workstation.
And on page four, in a font two points smaller than the body text, was a sentence that read like a footnote.
It said: Ryan drafted this document.
That was the quiet part.
The loud part was what I wrote into the data itself.
I left my desk on a Thursday afternoon with the red folder sitting exactly where all the others had been.
I went home and I slept better than I had in months.
Friday came and went.
The folder was gone by Monday.
I sat at my desk and I waited.
Derek came into the Tuesday sync with that walk he had — the easy, owning stride of a man who has never once doubted his own welcome.
He opened the report in front of Mr. Hartwell and three other senior staff.
He started talking.
I watched Mr. Hartwell’s expression shift around the two-minute mark.
Not dramatically.
Just a small tightening around the eyes, the kind of adjustment a man makes when something doesn’t add up.
Hartwell let Derek keep going for another full minute.
Then he asked one question.
Just one.
He asked Derek to explain the methodology behind the Q3 throughput projections on page four.
The room went still the way rooms go still when everyone except one person understands what’s happening.
Derek smiled and started to answer.
He got about eight words in before the smile slipped.
I had a glass of water in front of me and I took a slow sip.
That was the last time Derek smiled in a company meeting.
What happened next is something I still think about when I’m having a bad day at work.
