May 10, 2021
Before I begin any project, I take the time to fill out the project plan outlined below. This not only helps me flush out what the desired outcome looks like, but more importantly it sheds light on the impact and importance of the project.
Sometimes, after filling out the project plan, you realize that there is no real problem, or that there isn’t a big enough WHY... So you scrap the project.
After having defined a clear Success Criteria and clarifying Why the project is important, you can more easily delegate it because they’ll have the necessary context they'll need to autonomously and successfully complete the project.
What problem are you going to solve?
Why is this important?
🍾 Success Criteria
What specific results must be true for this project to be a success?
👥 Your Whos
Who can help you achieve this?
👤 Project Manager
Who is going to manage this project? Maybe there's a Who for that too...
🏃♂️ Next Action
What is the single next action to push this project forward?
What if the project is really large and requires smaller projects within?
The process is quite similar:
- Create a project plan for the vision
- Turn your success criteria into individual projects
- Create a project plan for each of the projects
Now you have a clearly defined vision, along with clearly defined projects that you can delegate to your Whos.
If you'd like to define the project further, you can add the following constrains to both the vision and nested projects:
- Project Timeline
There you have it. Now get cracking! 🚀
PS. Whenever you're ready... Here are two ways I can help you gain back control of your time and feel less overwhelmed:
- How to get started with Virtual Assistants → Download The Free Guide
- Schedule a FREE 1:1 call to learn how you can optimize your business → Free Systems Audit
More recent posts ⤵️
Delivering high-impact tips every Thursday
Every Thursday, you’ll get 1 actionable tip on systems and productivity: