I'm a data analyst at a mid-size logistics company. Nothing glamorous. But about two years ago, my manager Derek asked if I could put together a better way to handle client reporting because the existing process was just someone manually copying numbers into a spreadsheet every Friday and emailing it out. Real sophisticated stuff.

So I said sure. I didn't know it would take over my life for the next eighteen months.

I built the whole thing. Every dashboard, every automated pull, every exception alert. I learned SQL properly because of this project. I interviewed fourteen different clients to understand what they actually wanted to see. I failed a bunch of times and rebuilt pieces from scratch twice. I named the internal build folder "Project Albatross" as a joke about how it hung around my neck, and somehow that name just stuck.

By month sixteen it was genuinely good. Clients who saw early demos were excited. Derek was presenting it at leadership meetings like it was his idea, which fine, whatever, that's just how it works sometimes. I was proud of it regardless.

Then about two weeks before the full company rollout, Derek called me into a one-on-one and said something I still think about.

"We're bringing Marcus in to lead the launch. He's got fresh eyes and strong client-facing skills. You'll stay on in a support role."

Marcus was a sales ops guy. Nice enough. Had never touched the system once.

I asked what "support role" meant specifically and Derek said I'd be "available for questions." That was it. Available for questions.

I want to be honest here because people always make themselves sound too noble in these posts. I did not handle it gracefully. I told Derek I thought it was a bad idea two or three times over the next week. He kept saying things like "I hear you" and "this is about optics with the clients" and eventually I just stopped bringing it up because it was clear the decision was made and I was coming across as difficult.

I wrote Marcus a very thorough handoff document. Like embarrassingly thorough. Forty pages. Color coded. I thought maybe if I made it impossible to fail, nothing would go wrong and I could still feel okay about the whole thing.

He read maybe a third of it. I could tell from the questions he was asking me in Slack, which were questions I answered on pages two through eight.

The rollout was the last week of March. I watched from my desk. I had no formal role. I was just a person who worked there.

The first thing that broke was the exception alert system. I had documented exactly why it needed a 24-hour buffer built in or it would fire duplicate notifications. Marcus had asked IT to remove the buffer because a client said the delay felt "too slow." Within 48 hours, one client received the same alert 91 times in a single morning. I know it was 91 times because they forwarded the email chain to Derek with a subject line that said "What is happening."

The second thing was the permission structure. I had set up role-based access carefully because some clients shared parent accounts but needed segmented views. Marcus simplified it to save time during onboarding. Two clients ended up able to see each other's shipment data. One of them noticed.

I found out about most of this through the Slack channel I was still in but no longer active on. I would just see messages pop up and feel this specific kind of sick that I don't really have a word for. Not happy. Not vindicated. Just tired and a little hollow.

Derek came to me on day five. He didn't apologize. He said they needed to "stabilize" things and asked if I could jump back in.

I said yes. Of course I said yes. I still worked there.

It took me three weeks to fix what took three days to break. Marcus got reassigned to something else. Derek and I never talked about any of it directly, which is its own kind of answer I guess.

Here's the thing I keep sitting with. I don't think Derek was malicious. I think he genuinely believed that the person who builds something is not automatically the right person to launch it. And maybe sometimes that's even true. But he never asked me. He never said "here's my concern about you leading this, what do you think?" He just decided, and then managed me around the decision.

Project Albatross is running fine now. Clients like it. Someone mentioned it in a company all-hands last month as an example of good internal innovation, and my name was not said, and I sat there and felt nothing, which honestly felt like its own kind of progress.

I'm updating my resume. Not dramatically, not storming out. Just quietly. Because I realized sometime during those three weeks of fixing things that I'm really good at building something from nothing, and I'd like to do it somewhere that notices.