Project Execution

For your project to succeed, you must have the courage to move forward. 

After you understand what resources you have, you will define a project schedule. The project schedule simply is a list of tasks, with data on how long each task will take, when it will start, and when you expect it to be complete. Once you have a project schedule, all you have to do is perform the work.


The problem is that often, the work isn’t completed as the schedule lays it out. Everyone has a reason (or excuse) for why the work wasn’t done according to the schedule.

The real reason that people don’t adhere to the project schedule is a matter of execution. Execution energy is spent elsewhere. 

If you start with the assumption that people aren’t sleeping at their desks, we can assume that a person who is at work is doing something. People are executing some task, whether it is email or coding for another project. But if people aren’t completing the project tasks for today, they won’t be able to execute the project tasks for tomorrow. 

Your Choice

Everyone has limited time. And workers must decide what they will complete or execute. The reason for the project plan, especially when you compare it to the other pile of work that people might have, is so that someone can choose what they work on. As long as people are making a conscious decision that their email is more important than the project plan, then you can work on helping people understand the project plan. 

But if people don’t understand the trade-off they are making between executing one task above another; then they are just hamsters spinning on a wheel. 

Being able to execute work consistently is a valued skill. Someone who executes the right work is worth gold.