My coworker asked me last week what I’d been working on that actually excited me lately. I paused mid-bite of my sandwich because honestly, most days feel like pushing pixels around for someone else’s quarterly goals. But then I realized I had three solid answers. Projects that make me forget to check Slack notifications. The kind of work that feels less like work and more like building something that needs to exist.
The Documentation Nobody Reads (But Should)
I’ve been obsessed with our company’s onboarding process for months now. Not the HR stuff with the benefits slides and the awkward icebreakers. The actual technical onboarding that determines whether a new developer spends their first month confused and frustrated or actually shipping code.
Our existing documentation was a graveyard of outdated screenshots and broken links. New hires would spend three days just trying to get their local environment running. I started rewriting it from scratch, testing every single command on a fresh machine. Added troubleshooting sections for the weird edge cases that always happen. Put in actual timestamps for how long each step should take.
The best part? I included a section called “Things That Will Probably Break” with solutions for the most common gotchas. Last month, a new hire messaged me to say they got everything set up in two hours instead of two days. That’s the kind of small victory that makes the tedious parts worth it.
Teaching My Manager to Actually Manage
This sounds more dramatic than it is. My manager is smart and well-intentioned, but they got promoted from senior developer to team lead without any real training on the human side of things. They’d schedule one-on-ones and then spend the entire time talking about tickets instead of asking how I was actually doing.
Instead of complaining or job hunting, I started treating it like a project. I found articles about effective one-on-ones and forwarded the best ones. Suggested we try different formats. Started bringing my own agenda to our meetings with actual career development topics instead of just project status updates.
It took about six months, but now our one-on-ones are actually useful. We talk about growth opportunities, skills I want to develop, and problems before they become crises. My manager started using the same approach with the rest of the team. Sometimes the best way to improve your work environment is to actively participate in improving it instead of waiting for someone else to fix things.
The Side Project That Became Real
I built a tool to track my coffee expenses because I was spending an embarrassing amount at the fancy place near the office. Started as a simple spreadsheet, then became a web app when I realized I wanted to see patterns over time. How much was I really spending? Did expensive coffee correlate with better days or worse ones?
The data was fascinating in completely unexpected ways. I discovered I bought coffee most often on Mondays and Thursdays. Expensive drinks correlated with deadline stress, not productivity. I was spending less on coffee than I thought but more on the pastries I bought with it.
Three friends asked if they could use it. Then five more. Now it’s a proper app with user accounts and a small but enthusiastic user base. People send me screenshots of their data discoveries. Someone used it to realize they were stress-eating expensive lunches during their job search. Another person figured out their optimal coffee schedule for maximum alertness without afternoon crashes.
Why These Projects Actually Matter
None of these are going to win awards or get written up in tech blogs. They’re small, specific solutions to real problems I encountered. But they share something important: they all made someone’s life measurably better in a concrete way.
The documentation saves new hires from frustration and gets them contributing faster. The manager coaching improved not just my work experience but created a ripple effect across the whole team. The coffee app helps people understand their own patterns and make better decisions.
I think that’s what distinguishes projects I actually care about from the ones I just complete. The meaningful ones solve real problems for real people, even if those people are just me and a handful of others. They have clear success metrics that matter: time saved, stress reduced, insights gained.
Finding Work Worth Caring About
The common thread isn’t the technology or the scope. It’s that I spotted something broken or missing and took ownership of fixing it. I didn’t wait for permission or a formal project brief. I just started building solutions and iterating based on real feedback from real users.
This approach works for any role. Customer service reps who create better scripts. Accountants who automate repetitive processes. Designers who fix confusing user flows without being asked. The key is spotting the gap between how things are and how they could be better.
What work problems have you been mentally solving during your commute? What small thing could you fix that would make your colleagues’ days slightly better? Sometimes the projects we care most about start with the problems that annoy us just enough to do something about them.
Recent Comments