Whenever I am ready to start a new project, I usually sit down and start thinking about the tasks that need to be completed. And I start wondering which tasks I should complete first, second, third, etc. What often ends up happening is that I end up with such a long list of things that have to be done that I struggle to decide which one to do – and I end up in sort of an analysis paralysis.
I can’t tell you how many times I’ve tried to start a personal project and ultimately failed to even get going, due to this. I call it Project Inertia.
Inertia is the state of wanting to stay the same or do nothing at all. All objects in the universe have some form of inertia – either to sit still, or to keep moving. In terms of a project, project inertia is the tendency to be stuck, to not be able to do anything at all. It could come from analysis paralysis, a state where you have so many options it’s hard to choose. Or it could come from simply not knowing what needs to happen next.
Either way, it’s real, and it kills projects.
Not starting a project is often not an option, though. Work projects are requirements, not suggestions, and procrastination on a work project can lead to problems with your boss or the business itself. So how do you get started on a project?
I like to take a page out of Dave Allen’s Getting Things Done playbook, and come up with the “next action” for the things on my to-do list. A next-action is something that is specifically actionable. “Install the framework” isn’t specifically actionable if the steps to install the framework include downloading Composer, running
composer create project and going through some configuration options. In that case the next actionable step is “download Composer.”
I also borrow a rule out of Dave Allen’s book, called the 2 Minute Rule. In this rule, any next action that takes me less than 2 minutes to complete gets done now. Installing composer is as simple as running the phar installer – it’ll take 30 seconds, so let’s do it. Running through the configuration? That might take a little bit longer to achieve, so let’s put that on the back burner for now, until we’re ready to do it. Unless we decide to do it now.
Knowing what the specific next-action is helps me to get a project started. And that’s where project inertia takes over – because inertia works both ways. Once the ball is rolling on a project, it’s much easier to continue working on the project, even if you don’t specifically look for next-actions. I find that in the thick of a project, the barriers to getting things done come down and I can do my best work.
Getting started on a new project can be a true challenge, but it’s not insurmountable. By figuring out the specific next-action and doing it, you can get the project started – and put inertia to work for you.
Frustrated with your company’s development practices?
You don't have to be!
No matter what the issues are, they can be fixed. You can begin to shed light on these issues with my handy checklist.
Plus, I'll help you with strategies to approach the issues at the organization level and "punch above your weight."