Do You Really Need All Those Projects?

This week we’re exploring the need for projects and why the way a project has been defined is causing most of your task management problems.    You can subscribe to this podcast on: Podbean | Apple Podcasts | Stitcher | Spotify | TUNEIN Links: Email Me | Twitter | Facebook | Website | Linkedin The Planning Course The Time Blocking Course The Working With… Weekly Newsletter The Time And Life Mastery Course The FREE Beginners Guide To Building Your Own COD System Carl Pullein Learning Centre Carl’s YouTube Channel Carl Pullein Coaching Programmes The Working With… Podcast Previous episodes page Episode 272 | Script Hello and welcome to episode 272 of the Working With Podcast. A podcast to answer all your questions about productivity, time management, self-development and goal planning. My name is Carl Pullein and I am your host for this show. How many projects do you have? 50? 75? More than a hundred? Well, if you are defining a project as “anything you want to do that requires more than one action step”, as many people do, you are going to have a lot of projects. And all those projects need looking at to decide what needs to happen next.  When I was researching the reasons why so many people resist doing a weekly planning session, one thing I kept coming up against was the large number of “projects” people told me they had to review, which made doing a weekly review or planning session too long.  I began to realise that if our resistance was down to the sheer number of projects we had to review each week, that was something fixable because we have control over the number of projects we have. More interestingly, we also have control over how we define what a project is.  If we change the way we define a project to something that fits better with the work we do, we can reduce the number of projects we have and that in turn will reduce the time it takes to complete a planning session.  So, before we dive a little deeper into this, let me hand you over to the Mystery Podcast Voice for this week’s question. This week’s question comes from Christian. Christian asks: Hi Carl, I’ve always struggled with managing my projects. When I look at my task Manager, I have over 80 projects. These take a very long time to go through each week and I hate doing it. (Which is why I don’t do a weekly planning session) My question is; is it normal to have so many projects? Hi Christian, thank you for your question. I’ve found those who have read and tried to implement David Allen’s Getting Things Done, do tend to have a lot of projects. This is a consequence of how David Allen defines a project. That being anything that requires two or more steps.  This means, in theory, making an appointment to see your dentist, take your car in for a service or arranging your annual medical check up will all be projects. Yet, if you stop and think about this, if you dedicated thirty minutes on a given day, you could easily make all these arrangements. They certainly don’t need to be projects.  Over my working life, I’ve worked in a number of different industries. From hotel management, to car sales, law and teaching. When I look back over these jobs, I cannot remember treating everything as a project. I came into work, and got on with the work.  For instance, when I was working in a law office, we had around 150 cases ongoing at any one time. We never treated these cases as projects. They were our work. And our work had a process. When a new case came in, we needed to collect information and there was a checklist on the inside of the case file that we checked off as the information came in. The first step, once the new case was entered into the firms computer system was to request the information we needed.  Each day, we were receiving information for many of these cases and we simply printed off the file or, if it came in my regular mail, check the information, put the documents in the case file and checked off the information that had come on the check