When Work Stops Feeling Like Work
I’ve been keeping a running list in my phone of projects that make me forget to check the clock. Not the ones my boss assigns or the client deliverables with red flags in my email. The weird side quests that somehow matter more than anything on my official job description.
Last month it was reorganizing our team’s documentation system. Sounds thrilling, right? But here’s the thing: I kept finding these buried gems. Email threads from 2019 where someone had already solved the exact problem we’ve been wrestling with for weeks. Design mockups that never made it to production but contained brilliant solutions to current headaches. It felt like archaeological work, except instead of pottery shards, I was uncovering institutional knowledge that was slowly evaporating.
The documentation project wasn’t assigned. It wasn’t even on anyone’s roadmap. But every time I opened that chaotic shared drive, something in my chest tightened. Maybe it’s the same feeling librarians get when they see books shelved randomly. Or the satisfaction a chef feels organizing their knife drawer. Some inefficiencies are just too painful to ignore.
The Accidental Mentorship Pipeline
Another project that’s been consuming my brain space: building what I’m calling “the coffee chat system.” It started when I noticed our new hires looking lost during their third week. You know that specific type of lost where they’ve finished onboarding but haven’t quite figured out how things really work around here.
So I started scheduling informal 30-minute conversations with them. No agenda, no performance review vibes. Just “how’s it going, what’s confusing, what questions do you have that you’re afraid to ask?” The conversations showed patterns. Everyone struggled with the same unwritten rules. Everyone had the same knowledge gaps that weren’t covered in training.
Now I’m three months into what’s become an unofficial mentorship program. I’ve got a waiting list of people who want coffee chats, and I’m documenting the most common questions in a shared doc. It’s turning into something bigger than I expected. HR noticed and wants to formalize it. Part of me is excited about the recognition. Part of me worries that making it official will kill whatever magic made it work in the first place.
The honest truth? I have no idea what I’m doing. I’m making it up as I go, borrowing ideas from mentors I’ve had and hoping the combination doesn’t completely backfire. But the feedback has been good enough that I keep saying yes when people ask for time.
Building Things That Don’t Exist Yet
The project that’s really keeping me up lately is harder to explain. I’ve been prototyping a tool that doesn’t have a name yet. It’s part project tracker, part decision journal, part team mood ring. The idea came from frustration with how hard it is to remember why we made certain choices six months ago.
You know how you’ll be in a meeting and someone asks “why did we decide to go with option B instead of option A?” and everyone just stares at each other? Or how projects get derailed because the person who understood the original vision left the company? I’m trying to build something that captures not just what decisions were made, but the context around why they felt right at the time.
I’m calling it a “context preservation system” in my head, which sounds pretentious even to me. But the core idea feels important. Most project management tools track tasks and deadlines. This would track the reasoning, the trade-offs, the “we tried this approach but it didn’t work because…” stories that usually get lost.
Right now it’s just a rough prototype built in Notion with way too many database relations. I’ve been testing it with my team for the past month. Early feedback is mixed, which probably means I’m onto something but haven’t figured out the execution yet. The complexity is the enemy here. If it takes longer to document a decision than to make it, no one will use it.
The Pattern I’m Starting to See
Looking at these three projects, I’m noticing something. They’re all about information that gets lost. Documentation that disappears. Knowledge that walks out the door when people leave. The unspoken stuff that makes teams actually function.
Maybe this says something about the type of problems I’m drawn to. Or maybe it says something about the state of most workplaces. We’re really good at tracking the what and when, but terrible at preserving the why and how. The human context gets treated as nice-to-have instead of necessary.
I’m not sure where any of these projects will end up. The documentation system is live and slowly getting adopted. The mentorship thing might become an official program or might stay grassroots. The context preservation tool might turn into something useful or might remain an interesting experiment that taught me about database design.
But here’s what I know for sure: working on problems I actually care about changes everything. The energy is different. The attention to detail is different. The willingness to iterate and improve is different. It’s the difference between checking boxes and building something that matters.
I’m curious about your version of this. What are the side projects at work that you can’t stop thinking about? The problems that nag at you until you finally decide to do something about them? I’m collecting stories about the work that doesn’t feel like work, so if you’ve got one, I’d love to hear it.
