A Guide to Simple Project Management
Leo BabautaBy Leo Babauta. This article has been translated into Spanish by Juan Manuel Lemus from DotPress.

Freelancers are excellent at producing great work if an assignment takes less than a day to complete. But many freelancers (not all) are also notoriously bad at completing projects that take several days or more to complete.
We’re not always great at project management — and part of the problem might be that we don’t have a boss breathing down our necks, pressuring us at every turn and holding us accountable.
Another problem, of course, is that big projects are overwhelming and intimidating, and it’s easier to do a quick one-off job than to plod along at a project that could take a couple of weeks. Yet a third problem: we don’t always have a clear picture of how the project should look when it’s finished — a clearly defined desired outcome.
We’re going to address those problems in this guide to simple project management by modifying some project concepts from David Allen’s Getting Things Done — modified for freelancers. Actually, this method would work for regular employees too, but it’s especially designed for freelancers.
A Simple Project Management Process
1) Clearly defined outcome. Before you even start on the project, you should work with the client to get a clear picture of the desired outcome of the project. Often, the client doesn’t even have a clear picture. But neglecting this step will lead to delays and frustrations down the line. You can communicate through phone, email, or in person, but however you do it, be sure to ask questions to clarify what the client wants, make suggestions, and get a clear picture in your head that shows you how the project will look when it’s done (of course, “look” is a term used loosely here — if the project isn’t visual, you should still have a clear picture in your mind). Once you’ve gone through this process, and have a good idea of the outcome, restate it back to the client to get his or her agreement. Now you have a clear target to shoot at.
2) Set up the process. Once the outcome is clearly defined, talk to the client about the process — how you’ll work with him to manage the project. If it’s a simple project that can be done in a day, this step isn’t necessary — you can just do the project and turn it in, and revise it if the client wants revisions. But a longer-term project will require some kind of timeline and communication process, and you’ll want to be clear about this with the client. The following process is recommended, and it’s at this step that it should be communicated. A detailed timeline, however, isn’t recommended — it can be done if the client insists upon it, but detailed timelines have a tendency to fall apart after a week or two, so it should be clear that it’s a flexible timeline.
3) Focus on the next action. Instead of having a step-by-step process outlined, with deadlines given to each step of the project, tell your client you want to focus on one step at a time. Now, tell the client the next step required to move the project forward (or in this case, the first step), and set a deadline for submitting that to the client. Don’t worry too much about all the other steps needed to finish the project — you’re just going to focus on the next one. That will reduce the intimidating/overwhelming aspect of a large project — just focus on one step at a time. Make sure that’s a step that can be completed in a day or less. One to three hours is ideal. If it can’t be done in less than a day, break it down into smaller steps.
4) Send it to your client. Once you’ve completed that first step, send it to the client within the deadline you set up. This will show the client you’re moving along, and keep you accountable. If you don’t have to turn in a project until it’s completed, there’s no one to know that you’re procrastinating until the very end, when you cram to get it finished on time (and possibly bust deadline). But if you send each step to the client, even if it’s not finished yet, you are holding yourself accountable.
5) Communicate. The other great thing about sending each step of a project to the client is that you can get feedback from the client, and modify the project accordingly. This can actually make the project take longer, but in the end you’ll have a better product and the client will be happier. This continual feedback loop is actually integral to a successful project, and building it into the process makes sense.
6) Focus on the next action. Now that you’ve sent the client the first step, and gotten feedback, focus on the next step. Again, focusing on one step at a time keeps it from being overwhelming. Be sure that you set a deadline, and be sure that the task can be done in 1-3 hours (or a day at the maximum). When it’s done, send it to the client for review and feedback.
7) Repeat until completion. You get the idea. Just keep focusing on one step at a time, setting a deadline for each step as you go along, and sending the completed step to the client. This will keep you on top of things and running smoothly, without the need for a boss.





















Rajesh Shakya
July 13th, 2007
Very good post on project management.
Please read my article on this:
Everbody in project team is the project manager
and check other links under Project Management category.
Rajesh Shakya
http://www.rajeshshakya.com
Helping technopreneurs to excel and lead their life!
Ryan Bickett
July 13th, 2007
I’ve been reading David Allen’s book and highly recommend it. Great post by the way.
Aria Rajasa
July 13th, 2007
In cases like this, using a CRM could really help. Maybe not a full-blown CRM. But simple ones like Basecamp, goplan or the like. Or use an Open Source and Free activecollab
I myself use activecollab to communicate my progress to the client.
Mike Robinson
July 13th, 2007
I am one of those who are notoriously bad at project management. These tips are great, and will definately help this weekend when I have set aside some time to look at my current/future projects and reorganize them.
Andrei Potorac
July 13th, 2007
Try that when you have 15 projects at the same time.
Sue Elvins
July 14th, 2007
Great tips to follow for building an organization list. As a web developer, this is something I rely on for all of my projects. I have tried MS Project and I have tried SmartWorks for applications. Both have done well but what has always mattered to me is the use of a Gantt chart and seeing the critical path and the milestones as they are passed. Thanks so much for posting the article as it will help me improve in areas I may have overlooked.
William Profet
July 15th, 2007
Very good tips. For my projects I use MS Project with multiple milestones, multiple tasks, etc. I think it is too complicated. The approach of Leo is laser sharp and easy to use. I will try it on my next project.
bsmity
July 15th, 2007
Basecamp is a life saver…
Shawn
July 15th, 2007
Great tips - I’ve actually been trying to do these very things and they seem to help a great deal.
Jermayn Parker
July 16th, 2007
Very good tips
Rob
July 16th, 2007
As a web developer (and I’m sure this happens in other professions), I’ve always had trouble defining what the “next action” actually is, when several different things can happen concurrently without any change in the project outcome. That is, if I have 5 distinct features to add to an application, none of which rely on each other, which unique action step becomes the next one? Does each “feature” become its own sub-project within the overall application? This is one spot where my project management breaks down and falls apart for me. If I’m just focusing on the next action, where do I stash (and how do I deal with) the other 99 next actions that could also move this project forward?
How does anyone else do it?
Thanks!
-Rob
Kumar
March 7th, 2008
Great post! keep them coming!
Bern
March 7th, 2008
For Mac users there is an awesome app being developed called Things. It’s still in Alpha or Beta orrr…something. Anyway, I definitely have huge problems with staying on track and focused, and not panicing when the project becomes overwhelming.
This is a great, simple, lightweight app and it has definitely helped me a lot.
Thanks for the article.
Maicon
March 10th, 2008
really useful!
Janak Rajani
March 10th, 2008
Does anyone have any document templates they could share for Web or Print projects?
Charles Forster
March 18th, 2008
Project Management is one of those areas that took me a long time to get on top of. One of the most important pieces of the whole bit is the Clearly Defined Outcome. Once I started creating a marketing brief, THEN a proposal, I was all of a sudden getting more respect as a business AND i was getting more accurate quotes. It greatly reduced the amount of “Hey what about this, we can add this in, right? riiiiiiiiiiiight?” (for free usually).
Now I use basecamp and my own system for keeping on top of my work, and I can’t tell you what a difference its made in my business.
Blair R
November 6th, 2008
@Rob,
Agile project management has one feature called a backlog. These are all the features in your case. You can capture them all but only start working on them and adding a due date when you’re ready or when other parent tasks have been completed. Hope that helps. Google agile project management for more info. VersionOne is a good tool and has a good Web site for learning more.