Why Do So Many Project Plans Fail?

For something so essential to project success, planning is often surprisingly weak. Time and time again, we hear from clients and review plans that fall into the same traps—flat task lists, unrealistic timelines, and little to no collaboration. Even experienced PMs can default to building their plans in isolation, relying on instinct rather than process.

The result? Plans that look good in PowerPoint but fall apart in practice. They lack stakeholder engagement, miss dependencies, and fail to reflect the reality of team availability or evolving scope. A plan like this isn’t a roadmap—it’s wishful thinking.

The truth is that most failed projects don’t fail in delivery. They fail in planning. But there’s good news: modern, collaborative planning techniques can dramatically improve your project’s chances of success—and your reputation as a project leader.

What Is the Best Way to Start Planning a Project?

You don’t need fancy software to start planning your project well—you need clarity, collaboration, and a big sheet of paper.

At Wellingtone, we teach a technique in our APM Accredited Project Fundamentals Qualification courses that remains one of the most powerful and effective ways to begin: the sticky note plan. It’s simple, low-tech, and incredibly insightful.

Rather than jumping into Microsoft Project or drafting a Gantt chart, gather your initial team and subject matter experts and start mapping the journey. By visually laying out the scope of work—without worrying about technical precision—you build a shared understanding of what the project actually involves.

This early planning process is not about locking in dates. It’s about surfacing assumptions, identifying unknowns, and laying the groundwork for a realistic schedule that the team believes in.

How Do I Create a Sticky Note Plan for My Project?

Here’s the process we walk through in our courses:

Start by defining the start and end points of your project or phase. These are your “bookends.” Then, working with your team, write out every task, milestone, or activity that needs to happen—each one on its own sticky note.

At this stage, the goal isn’t order—it’s completeness. Get everything out of people’s heads and onto the table. Once you’ve captured the full scope, begin arranging the sticky notes in sequence. Draw lines between them to show dependencies—what needs to happen before something else can start.

Some tasks will happen in parallel. Others will trigger new streams of work. You’ll quickly begin to see the flow of the project emerge in a way that no spreadsheet ever captures this early on.

Why does this work? Because it’s tactile, inclusive, and visual. It encourages conversations like:

“We forgot about testing!”
“We’ll need sign-off before that can happen.”
“That task depends on procurement—we should factor in delays.”

You can even colour-code by owner, task type, or risk level. And the best part? You now have a high-level plan the entire team helped create—and understands.

How Can I Accurately Estimate Time for Tasks?

A common trap in planning is guessing how long tasks will take based on gut feel or pressure from above. But effective estimation is a skill—and like any skill, it improves with the right approach.

In training, we focus on separating work effort (how many hours of actual work a task takes) from elapsed time (how long it will take to complete based on availability). For example, a task may take 8 hours of work, but if your resource is only available for 2 hours a day, the elapsed time is 4 days.

To improve your estimates, try this workflow:

Ask your team members how much work is required—not when it’ll be done.
Discuss how that work fits into their existing commitments.
Adjust the timeline based on real availability, not just ideal conditions.

We also teach techniques like analogous estimating (comparing to previous similar projects), bottom-up estimating (building from the task level), and Delphi technique (drawing on expert consensus). Each one helps reduce bias and improves the accuracy of your initial plan.

Remember: estimates are never perfect. But with the right process, they’re useful—and defendable.

How Do I Assign the Right People to the Right Tasks?

One of the most overlooked steps in planning is resourcing—and it’s often the difference between an achievable plan and one that’s doomed from the start.

Once you’ve built your sticky note plan and estimated durations, the next step is assigning ownership. Who will complete each task? Do they have the right skills? And crucially—are they available?

It’s not enough to assign a name. You need to understand each resource’s capacity, their other project commitments, leave, and even potential burnout. This is where project management becomes about people, not just process.

We recommend using tools like a Responsibility Assignment Matrix (RACI) to clarify roles, and holding dedicated resource planning sessions with line managers or team leads. Get agreement early—don’t just hope your plan fits reality.

By considering resource constraints at the planning stage, you avoid last-minute reshuffling and costly delays down the line.

When Should I Move My Plan to Microsoft Project (or Other Tools)?

Your sticky note plan isn’t the end—it’s the beginning. Once the team has validated it, you can translate it into scheduling software like Microsoft Project for the web, or another tool that suits your organisation.

But here’s where many PMs go wrong: they dive into the software too early or misuse its features. Microsoft Project is powerful, but only when used with a solid foundation.

What you should do:

Input your structured task list.
Define dependencies and critical path.
Assign resources and check for overallocations.
Set baselines to measure progress.

What you shouldn’t do:

Let the tool “build” your plan for you.
Skip human conversations and collaboration.
Ignore the need for regular plan reviews and updates.

If you’ve never been trained in Microsoft Project, now’s the time. Our courses walk you through how to use it properly—so your digital plan reflects the reality of delivery.

Should Project Planning Be Done Alone?

No—full stop.

If there’s one message we emphasise in every project management course, it’s this: planning is a team activity. The best plans are built collaboratively. When people contribute to the plan, they’re more likely to believe in it, support it, and deliver on it.

As the project manager, your role isn’t to have all the answers. It’s to facilitate the conversations that reveal the answers. Host workshops. Ask “what’s missing?” Get input from your sponsor, delivery team, and stakeholders.

Modern planning isn’t a solo exercise—it’s a shared discovery process. The more inclusive your approach, the stronger your plan will be.

What’s the Difference Between a Good Plan and a Great Plan?

A good plan outlines tasks and timelines. A great plan tells a story—of how a team will work together to deliver something meaningful, within constraints, and with clear visibility of risks and opportunities.

Here’s what sets great plans apart:

They’re built collaboratively, not in a silo.
They account for resources and constraints early.
They adapt to change, with clearly defined decision points.
They are used—not filed away after approval.

In short, a great plan becomes a living tool. It drives conversations, decisions, and delivery. It’s not just about what will be done—it’s about how, when, and by whom.

Want to Learn These Skills and Get Certified?

If you’re ready to take your planning skills to the next level, check out our APM-accredited training courses. They’re practical, modern, and built around real-world tools and techniques.

Learn more about the APM Project Fundamentals Qualification

Perfect for new project managers or those looking to formalise their knowledge with a respected certification. You’ll walk away with practical experience and the ability to immediately apply what you’ve learned.

We cover: