There’s a product idea I’ve had for a couple months now. It’s fun to daydream about and even seems (in theory) like it’ll be very useful.
I’ve been “too busy” to work on this new idea, and I’ve been repeatedly setting aside time “a few weeks from now” to break ground on it. And so it remains a sandcastle in the sky.
But all-or-nothing thinking doesn’t serve anyone well. It’s true that I’m not ready to spend full days on this product ideas, much less full weeks. But if it’s interesting enough to me to think about it every day, it ought to be interesting enough to put in a bit of work every day.
With that in mind, I’ve decided to spend 30 minutes a day on the project, until the time comes in “a few weeks” when I’m able to dedicate more to it. If I’m able to do that, then it’ll reduce the friction of a cold start when I do finally clear the time. If I’m not, then maybe it’ll convince me that I’m not as serious about the idea as I thought I was.
It’s good to put ideas to the test. 30 minutes of action beats 30 minutes of daydreaming any day. Even when the action itself is so small as to be nearly invisible, it adds up in aggregate.
So how did I spend my first 30 minutes after making this commitment? The same way most web projects begin for me: Registering a domain name. Fighting with SSL configuration. Waiting on DNS to update for what seems like forever.
But hey, if this is one of a couple dozen things I won’t need to do on my real “Day One” of work… well, then it will have all paid off, right?
One shovel full of sand dug out. A billion to go.