Why Some Work Actually Feels Like Work Worth Doing
I’ve been keeping what I call a “process notebook” for the past eight months, and it’s become this weird mirror that shows me which projects I actually give a damn about. Not the ones I’m supposed to care about, or the ones that look impressive on paper, but the ones that make me forget to check my phone for three hours straight.
The notebook started as an accident. I was working on a community garden mapping project and got frustrated trying to explain to my partner why I was spending my Saturday morning crouched in someone’s backyard, measuring raised beds with a tape measure that kept snapping back and hitting my thumb. So I started writing it down, not for any grand purpose, just to figure out what the hell I was doing and why it mattered to me.
What I discovered is that the projects I actually care about share this strange quality: they’re all slightly broken in ways that make them more interesting. The garden mapping thing? Half the community gardens don’t have official addresses, some exist in legal gray areas, and three of them are just “behind the blue house on Maple Street.” But that’s exactly what makes the project feel alive instead of bureaucratic.
The Difference Between Clean Problems and Real Problems
My day job involves a lot of what I’ve started calling “clean problems.” Clear scope, defined deliverables, stakeholders who know exactly what they want. These projects run on time, get approved without drama, and leave me feeling like I’ve successfully operated a very efficient machine that could have operated itself.
The projects in my notebook are messier. There’s the local history podcast where I’m trying to track down the story of why our town has seventeen different street names that all reference the same guy who apparently wasn’t even from here. Every interview leads to three more questions and two contradictory newspaper clippings from 1987. The research sprawls everywhere, leads nowhere definitive, and hooks me completely.
Or the project where I’m helping a friend document traditional recipes from his grandmother before she forgets them. Except it turns out she doesn’t really use recipes, just “a little of this” and “until it feels right,” and half her techniques involve reading the mood of her sixty-year-old oven. We’re basically trying to reverse-engineer decades of muscle memory, which is probably impossible and definitely worthwhile.
What My Notebook Actually Looks Like
I should clarify that this isn’t some beautiful, Instagram-worthy bullet journal situation. It’s a basic composition notebook with coffee rings and pages that curl at the edges because I keep leaving it places where it gets damp. The handwriting is terrible. I use whatever pen I can find, which means some entries are in blue ballpoint, others in pencil that’s barely legible, and one memorable week in purple gel pen that I immediately regretted.
But the content tells a story I couldn’t see while I was living it. There are sketches of garden layouts next to frustrated rants about permit applications. Phone numbers for people who might know something about the mysterious street-naming guy. Half-finished thoughts about why the recipe project feels important even though no one asked me to do it. Lists of what worked, what didn’t, and what I want to try next.
The notebook has taught me that I’m drawn to projects that sit right at the edge of things disappearing. Not preserving them in amber, but catching them before they slip away completely. The community gardens shift constantly as people move, budgets get cut, and neighborhoods change. The recipes live in this space between tradition and whatever happens when tradition meets a different kitchen, different ingredients, different hands. Even the street name thing is really about rescuing stories that get a little more garbled with each telling.
The Permission to Be Incomplete
One of the most liberating things about tracking these projects is seeing how much of the work is about not knowing things yet. The notebook is full of questions I haven’t answered, leads I haven’t followed up on, and experiments I want to try when I have time. Instead of feeling overwhelming, this incompleteness has become oddly comforting.
The garden mapping project will never be truly finished because the gardens themselves keep changing. New beds get built, old ones get abandoned, and people have different opinions about whether that patch of tomatoes behind the community center counts as part of the official garden or not. But this ongoing nature is part of what makes it feel alive and worth doing.
I’ve started thinking of these projects as conversations rather than assignments. The notebook captures not just what I’m doing, but how I’m thinking about what I’m doing, and why certain approaches feel right while others make me want to abandon the whole thing and reorganize my sock drawer instead.
What This Reveals About the Work That Matters
Looking back through eight months of scribbled entries, I can see patterns I wasn’t conscious of at the time. The projects I care about most are the ones where I’m not just executing someone else’s vision, but actively figuring out what the vision should be. They involve real people with real stakes in the outcome, not abstract concepts or theoretical improvements.
They’re also projects where the process teaches me something I didn’t expect to learn. Mapping gardens has taught me about urban planning, water rights, and the surprisingly complex politics of shared space. The recipe documentation has become a crash course in cultural preservation and the challenge of turning muscle memory into words. The street name research has revealed layers of local history that somehow never made it into any official records.
Maybe most importantly, these projects give me permission to care about things that seem small or niche to other people. Not everything has to scale or disrupt or change the world. Sometimes the most satisfying work is quietly useful to a handful of people who need exactly what you’re building.
I’m curious about your version of this. What projects make you lose track of time? What work feels worth doing even when it’s frustrating or unclear or slightly ridiculous? I’d love to hear about the things you’re working on that don’t fit neatly into job descriptions but somehow matter anyway.