A post about doing something right, getting shouted at for it anyway, and why I’m publishing this even though I know it’s going to ruffle feathers.

I’m not going to name the club. Not because I’m scared, but because this post isn’t about dragging anyone. It’s about a system, and systems are worth talking about even when the people running them would rather you didn’t.

Here’s the setup. Six months ago I got what I’d call the biggest opportunity handed to me in that whole stretch: permission to initiate a new club at my college. I pitched it to the higher-ups, explained the value to my reporting officer, laid out exactly why students needed it and what it would actually do for them. Green light given. I built it.

Ten to fifteen days later, it was live. Fully running. And the feedback I got back was, more or less, “this isn’t something just anyone could pull off.” I took that as confirmation I’d done the job right. Turns out I’d also just opened a support ticket I didn’t know existed.

The Feature Nobody Told Me Was a Bug

Somewhere in the club charter, or maybe just in a conversation I had with the person who greenlit the whole thing, I was told I could pick my own teammates. Not vetted through some approval chain, not run past a committee. Just: pick people you trust, people who’ll actually show up, people who fit. That’s what I did. I built a small, capable team and got to work making the club something worth being part of, a space where students could learn together instead of one person hoarding all the good opportunities for themselves, which, frankly, is the failure mode I see in half the clubs on campus.

I documented everything else. Every task, every milestone, every update went straight to my reporting officer. The one thing that didn’t get forwarded up the chain was the team selection, because as far as I understood it, that decision was mine to make. Not a workaround. Not something I hid. Just a permission I was explicitly given.

Except somewhere between my reporting officer and the higher officials above them, that context never made it through. Classic broken telephone. The kind of miscommunication that, in any well-run system, gets caught in a review before it becomes a problem. Instead, it became a problem for me, personally, in a room, out loud.

The Incident Report Nobody Filed

I got called in. Higher officials, raised voices, the works. “Why are you doing stuff like this? Why are you doing it like this?” Demands that I report every single move to them going forward, as if the club itself was some rogue process running without a permissions check.

Here’s the part that actually stings, and I’m not going to dress it up: getting yelled at like that in front of people who trusted me to lead something didn’t just knock my own motivation down a few notches. It knocked the whole team’s. The same students who were excited to finally have a place to learn something real watched their lead get torn into for doing exactly what he was told he could do. You don’t recover team morale from that in a week. Maybe not in a semester.

And since that day, silence. Nobody upstream brings it up. Not my reporting officer, not the officials who did the shouting. In my experience, that kind of silence usually means one thing: everyone involved knows something went wrong on their end, and it’s easier to pretend the incident never happened than to own it.

I’m not going to pretend that’s not a mistake, technically, on paper, in whatever binder governs how my college wants things reported. But it wasn’t a mistake against any actual rule I was given. It was a mistake because the chain of command between my reporting officer and the people above them has a bug in it, and I got treated like the exploit instead of the person who found it.

Why I’m Still Posting This

I know putting this out there might cause friction. Someone’s going to read this and know exactly which club and which people I mean, even without names attached. That’s fine. I’d rather be honest about what actually happens when you try to build something good inside a system that isn’t built to handle initiative gracefully, than stay quiet and let the silence do the talking for everyone else.

The club is still running. The team is still there, even if some of that early spark got knocked out of them for a while. I still believe the whole point of starting it, giving students a place to actually learn together instead of one person gatekeeping every opportunity, was worth doing, and worth doing again.

If you’re building something at your own college or company and you hit a wall like this, here’s the only advice I’ve got: document everything, even the parts you think don’t need documenting, and don’t let one bad meeting convince you the whole project was a mistake. Sometimes the system’s the one with the misconfiguration. Not you.