When Work Stops Being Work
You know that feeling when you’re supposed to be doing something else, but you keep sneaking back to that one project like it’s a good book you can’t put down? I’ve been thinking about this lately because I’m neck-deep in something that doesn’t make sense on paper. It’s a documentation system for our customer support team that I started three months ago, and somehow it’s become the thing I think about in the shower.
The funny part is that nobody asked for it. Not really. There was some vague mention in a meeting about “knowledge management” and “reducing ticket resolution time,” but mostly it was me noticing that Sarah from support was answering the same question about password resets for the fifteenth time that week. She had this look. You know the one. Like she was slowly being drained of her will to live, one repetitive email at a time.
That’s when I realized I cared about this more than I probably should. Which got me wondering about the difference between projects that feel like pushing a boulder uphill and the ones that somehow pull you forward. What makes something worth the extra brain space it inevitably takes up?
The Messy Middle of Actually Caring
Here’s what nobody tells you about passion projects at work: they’re ridiculously inefficient at first. I’ve rewritten the same help article about API authentication four times because I keep thinking of better ways to explain it. Each version gets closer to something that might actually help a confused developer at 2 AM, but the time investment is pretty nuts by any normal productivity metric.
Yesterday I spent an hour debating whether to call something a “workflow” or a “process.” An hour. On one word. My rational brain knows this is overkill, but there’s this other part that insists the distinction matters. Because when Jake from sales needs to figure out how to handle a billing dispute, the difference between clear and almost-clear could mean the difference between a solved problem and a frustrated customer.
I’m starting to think this inefficiency might be a feature, not a bug. The projects I actually care about seem to demand this kind of obsessive attention to detail. It’s like they know when you’re just phoning it in versus when you’re really trying to solve something important. And they respond accordingly.
Small Victories That Feel Enormous
Last week, Tom from the dev team mentioned that he’d used the new troubleshooting guide I’d written and it actually worked. Just a casual comment in Slack, nothing dramatic. But I screenshotted it anyway because sometimes you need proof that the thing you’ve been building in the corners of your schedule is actually useful to real humans.
The weird thing about work projects that matter is how the wins sneak up on you. You’re not expecting fanfare or recognition, so when someone mentions that your thing made their day a little easier, it hits different. Sarah told me she cut her response time for password reset questions in half, which means she has more time for the complex issues that actually require human judgment. That’s not going to make it into any quarterly review, but it feels more meaningful than most things that will.
I’ve been keeping a running list of these tiny wins in my notes app. Not for any official reason, just because I want to remember that this stuff matters to someone. The documentation helped Lisa onboard two new support agents without having to shadow her for a week. The workflow diagram prevented three different billing errors that would have required manual cleanup. Small stuff that adds up to something bigger.
The Questions That Keep Coming Back
I keep wondering if I’m doing this right. There’s no roadmap for “make work better for people in small, incremental ways.” Some days I feel like I’m building something genuinely useful. Other days I wonder if I’m just procrastinating on my actual responsibilities by creating elaborate solutions to problems that maybe don’t need solving.
The scope keeps shifting too. What started as a simple FAQ document has morphed into a mini-knowledge base with decision trees and troubleshooting flows. I added a section for common edge cases after watching Brad struggle with a customer who had somehow created three accounts with the same email address. Then I realized we needed templates for different types of responses. Now there’s a whole section on tone and voice guidelines because “professional but friendly” apparently means different things to different people.
Is this scope creep or natural evolution? I honestly don’t know. But every addition feels necessary once I see the gap it fills. It’s like renovating a house and discovering that fixing one thing reveals ten other things that need attention. Except in this case, the house is made of information and the tools are Google Docs and a stubborn belief that work doesn’t have to be unnecessarily frustrating.
Learning to Work in the Gaps
The most surprising thing about this whole process is how much I’m learning about project management by accident. Not the formal kind with Gantt charts and stakeholder meetings, but the organic kind that happens when you’re trying to make something useful without disrupting everything else around it.
I’ve gotten better at building in 20-minute chunks. Writing one help article during the gap between meetings. Testing a new workflow diagram while I’m waiting for code to deploy. It turns out that caring about something makes you surprisingly good at finding pockets of time that you didn’t know existed.
The collaboration part has been unexpected too. People keep suggesting improvements or pointing out gaps I hadn’t noticed. Marcus from engineering mentioned that the troubleshooting steps I’d written could be automated, which led to a whole conversation about building tools that actually serve the people using them. Now we’re planning a small integration that might save everyone involved about an hour a week.
I’m curious about your version of this. What’s the project that’s been quietly pulling at your attention? The thing that doesn’t quite fit in your job description but feels too important to ignore? I’d love to know how you’re navigating the space between what you’re supposed to be doing and what you think needs doing. Sometimes the best solutions come from comparing notes on the stuff we’re figuring out as we go.
