Skip to content
GanttPal
Log in Get started

Project Planning in 7 Steps: Build a Plan You Can Actually Follow

Project planning turns an idea into an agreed sequence of work. It settles what will be delivered, how the work will be done, who is responsible, and when each part should happen. The written plan is the shared record of those choices, but planning itself continues whenever scope, dates or people change.

What project planning does

A useful plan answers five questions. What are the main deliverables? How will the team reach them by the deadline? Who is on the team and what will each person do? Which stakeholders must review work, and when? When will the team reach its milestones? If those answers are clear, the plan is ready to share.

Planning is different from the plan itself. The document captures decisions at a point in time; planning is the ongoing work of revisiting those decisions as conditions change. A project is a temporary effort created to produce a unique result, so even a familiar type of work needs its own tailored plan rather than an unedited template.

Charter, management plan and project plan: how they differ

Three early documents are often confused. A charter asks whether the project should proceed and who owns it; it records goals, broad scope, sponsor, budget range and success criteria for sponsors and leadership. A project management plan explains how the project will be run, covering scope, schedule, budget, risk, communication and change for the manager, sponsors and core team. A project plan schedules the work itself, listing tasks, timing, milestones, dependencies and assignments for the whole team and key stakeholders.

On a small team, the charter may be a one-page brief and the management approach may fit into a few paragraphs in a kickoff deck. The project plan is the document you will open each week. All three should describe the same scope; when they drift, unexamined requests can enter and scope creep follows. For a small, low-risk project, a short brief plus a detailed project plan is usually enough.

Where planning fits in the project life cycle

Planning is the second phase in a common five-phase view of a project, and it continues in smaller doses until close. Initiation establishes why the project exists, who sponsors it and whether it is worth doing. Planning converts goals into tasks, timing, assignments and budget. Execution is where the team does the work and hands off deliverables. Monitoring and controlling runs alongside execution, comparing progress with the plan and correcting course. Closing completes final deliverables, approvals and lessons learned.

This five-phase model is a simplified map, not a formal standard; process groups and life-cycle phases are not the same thing, and other labels such as feasibility, design, build, test, deploy and close are also used. In practice the phases overlap: a mid-project requirement change sends that slice of work back into planning while execution continues elsewhere. Because later phases depend on it, planning deserves the most thought upfront, and gaps tend to surface later as missed handoffs, surprise deadlines and repeated replanning.

What every project plan needs

Every project plan needs five building blocks. A task list organised by phase, process step or work group. A schedule showing start dates, durations and deadlines on a visual timeline with progress indicators. Milestones marking major events, decisions, approvals and deliverables. Dependencies linking tasks that must happen in a particular order. Resource assignments naming the person or team responsible for each task.

A milestone marks a key approval, handoff or deadline. A dependency shows which tasks cannot start until others finish, preserving handoffs when dates move. Larger or riskier projects may also need a scope statement defining what is in and out, a RACI chart clarifying who is responsible, accountable, consulted and informed, a risk plan describing what could go wrong and how to respond, and a communication plan setting who receives updates, how often and in what format.

Example: a 10-week website redesign

Consider a 10-week website redesign run by five people. Discovery in weeks 1-2 covers stakeholder interviews, analytics review and a content audit, ending when the project brief is approved; it depends on the kickoff meeting. Information architecture in weeks 3-4 produces a sitemap and wireframes, ending with wireframe approval, which depends on brief approval. Design in weeks 4-7 creates visual concepts and page designs, ending with final design approval, which depends on wireframe approval. Development in weeks 6-9 builds templates and migrates content, ending with a staging site ready, which depends on approved designs for each template. Launch in week 10 covers quality checks, fixes and go-live, ending with the site launched, which depends on staging sign-off.

Notice the overlaps: design begins before every wireframe is finished, and development begins before every page is designed. Dependencies show which approvals genuinely gate the next phase. Use the same structure for your own plan: phases, a milestone at the end of each, and only the dependencies that affect timing.

Why planning pays off

A shared picture of the work, agreed before it starts, makes later decisions faster. First, everyone aligns on process, scope, staffing and communications while agreement is still easy, and each task has an owner and due date so nobody has to guess. Second, overload and slippage become visible early: a plan shows who is doing what and when, so three deadlines landing on one person in a week can be rebalanced before they become late nights, and falling behind can be spotted while there is still time to shift work. Third, change and risk are easier to handle because assumptions, constraints and dependencies are named upfront and can be watched; when something unexpected happens, its effect on scope, timing and workload can be weighed and the plan adjusted instead of restarted. Tying each plan to the business goal it supports also gives trade-offs on scope, time and budget a clear tiebreaker.

Choosing a planning approach

Four main approaches differ in how far ahead they plan in detail. Predictive planning, often called waterfall, maps full scope, sequence and schedule before work starts; it suits stable requirements, a fixed deadline and clear handoffs, such as an event or a regulatory filing. Iterative and agile planning works in short cycles called sprints, planning each sprint in detail while keeping a prioritised backlog and release roadmap for the longer view. Hybrid planning fixes dates and dependencies on a shared schedule while teams work in sprints inside each phase, for example locking a launch date and marketing milestones while a build team runs two-week sprints. Rolling-wave planning details the next phase and keeps later phases high level, adding tasks, estimates and owners as each phase approaches and unknowns shrink.

A simple rule follows: if requirements are stable, plan predictively; if they will change as you learn, plan in cycles or waves, and keep immovable dates and dependencies on one shared timeline.

The 7 steps, from discovery to execution

Step 1, discovery and definition. Learn as much as possible before promising a plan. Review the scope of work and any relevant documents or communications, such as a request for proposal or notes from sales calls or client meetings. Ask thoughtful questions before committing, and record four things: the goal and business outcome, the deliverables and what done looks like for each, dependencies on other teams, vendors or projects, and risks, open questions and assumptions. If you cannot yet explain the project goal in one sentence, keep asking questions before moving on.

Step 2, stakeholder and team interviews. Stakeholder interviews reveal how decisions are made; team conversations reveal how much time people actually have. Ask stakeholders about product ownership and decision-making, their interest and involvement levels, key outages, meetings, deadlines and driving factors, related projects and their goals, and the best way to communicate with partners and stakeholders. Then ask the team how they like to work, what else is on their plate and when they will be out. Discuss concurrent work and key dates to avoid so nobody is double-booked. Write down every date mentioned, because each becomes a constraint when you build the schedule.

Step 3, a rough outline. Sketch the work to test your thinking before committing to dates, starting with who, what, when and how. Include deliverables and the tasks needed to create them, the approval process, timeframes, resource ideas, assumptions, and absolutes around budget or deadlines. Think deliverables first and phases second: for a design concept, what must happen before it can begin, and what can happen once it is approved or concurrently? A work breakdown structure helps by splitting each deliverable into smaller pieces until every piece is small enough to estimate and assign. Sketch in a document, on a whiteboard or on sticky notes; the tool will not do the thinking for you. Detail the next 2-6 weeks down to individual tasks and keep the rest at phase or deliverable level, adding detail as each phase nears.

Step 4, team input on process, effort and timing. The people doing the work give the most accurate estimates, so build the plan with them; a designer knows how long a homepage concept really takes. Ask how each task should be approached and what could run in parallel, such as visual concepts starting while wireframes are still being developed, or two people sharing one task. Ask for effort in hours as well as duration in days, because an eight-hour task can stretch across a week when its owner is split across projects. Check workload across projects to spot double-booking before the schedule is final, and when an estimate feels low, ask what could make the task take longer and plan for that.

Step 5, formalise the schedule. Turn the outline and estimates into dated tasks, dependencies and milestones on one timeline, giving every task a clear start and end date. Organise work into phases, then subgroups for deliverables or teams, using labels or colour-coding to make the plan scannable. Link only the tasks whose relationship changes timing, then find the critical path, the longest chain of dependent tasks; any delay on it pushes the finish date by the same amount. Add milestones for approvals, handoffs and launch dates, and block out holidays, closings, vacations and recurring meetings on both your team's and stakeholders' sides. Note top risks and who is watching each one, expanding them into a full risk plan if the project is complex. A Gantt chart brings this together, with dependencies linked, the critical path highlighted, and list, calendar or board views available for teammates who prefer them.

Lead times deserve the same visibility. In a kitchen remodel, cabinets may take six weeks to arrive after ordering; installation cannot start until they are on site, the countertop template cannot happen until cabinets are installed, fabrication follows the template, and the backsplash waits for the countertops. If the cabinet order goes in a week late, every task behind it shifts a week. Put the lead time on the same timeline as the install task, linked by a dependency, so the wait is visible to everyone. The same move works for vendor deliveries, legal reviews or client approvals: put the wait on the plan as its own task or milestone so it cannot hide.

Step 6, present and confirm. Review the plan in two rounds, starting with the team. Internally, check review and work times for each task, dependencies and handoffs, time off, meetings and milestones, assumptions, and changes since your last conversation. Then present to stakeholders, opening with a short executive summary covering the goal, key milestones, finish date and biggest risks, since busy sponsors may read only that part. Walk through major deliverables and phase timing, how much time stakeholders will have to review deliverables, and how much room remains before the final deadline. Once everyone agrees, decide who gets schedule updates and how often, capture that in a simple communication plan, share the current schedule through a live link, and ask stakeholders to confirm the plan in writing, even by email, so you have a clear starting point for future change requests.

Step 7, execute and adjust. Plans are living documents, and someone must stay on top of change and record it. Before work starts, save a baseline, a snapshot of the original plan, so you can measure what changed and learn from it. Set aside time once a week to review the plan, timelines and dependencies, note the past week's accomplishments and define next week's goals. Add a short daily check of 30 minutes or less: review what is due today and tomorrow, check for blocked tasks and handoffs waiting on someone, and update the plan with what changed, why, and what it affects. Compare today's schedule against the baseline and use a project health report for a quick read on whether the project is on track. Give the routine a few weeks to sink in; a steady habit keeps the plan trustworthy.

Common mistakes and how to fix them

Five mistakes recur. Planning alone: a solo plan produces optimistic estimates and hidden dependencies, so draft the outline yourself, then review effort and sequence with the people doing the work. Skipping blocked dates: a schedule that ignores vacations, holidays and recurring meetings looks fine until someone is out, so collect blocked dates during interviews and add them before setting task dates. Adding too much detail too early: planning every task of a six-month project on day one means rewriting most of it later, so detail the next 2-6 weeks and keep later phases at deliverable level. Letting the plan go stale: an unupdated plan stops being trusted and work moves into side lists and chat threads, so use a weekly review and a short daily check, noting what changed each time. Leaving tasks without an owner: tasks assigned to the team tend to sit until someone notices, so give every task one owner even when several people contribute, and use a RACI chart for shared deliverables. When a plan starts slipping, check these five first, because one of them is usually the cause.

Using a project plan template

Instead of building phases, tasks and milestones from scratch, a template supplies that skeleton ready to edit, which cuts initial setup effort. It works best when successive projects share a similar phase pattern; even then, dates, owners and dependencies must be reworked for each project.

Charter, management plan and project plan compared
DocumentQuestion it answersTypical contentsWho relies on it
Project charterShould we do this project, and who owns it?Goals, high-level scope, sponsor, budget range, and success criteriaSponsors and leadership
Project management planHow will we manage this project?Approach to scope, schedule, budget, risk, communication, and changeThe project manager, sponsors, and core team
Project planWhat work happens, who does it, and when?Tasks, schedule, milestones, dependencies, and assignmentsThe whole team and key stakeholders

All three documents should describe the same scope; drift between them is a common source of scope creep.

Example plan: 10-week website redesign
PhaseKey tasksMilestoneDepends on
Discovery (weeks 1-2)Stakeholder interviews, analytics review, and content auditProject brief approvedKickoff meeting
Information architecture (weeks 3-4)Sitemap and wireframesWireframes approvedBrief approval
Design (weeks 4-7)Visual concepts and page designsFinal designs approvedWireframe approval
Development (weeks 6-9)Template build and content migrationStaging site readyApproved designs for each template
Launch (week 10)Quality checks, fixes, and go-liveSite launchedStaging sign-off

Overlaps are intentional: design starts before wireframes are complete, and development starts before every page is designed.

Frequently asked questions

What are the 7 steps of project planning?

Discovery and definition; stakeholder and team interviews; a rough outline; team input on process, effort and timing; a formal schedule; presentation and confirmation; then execution with adjustments as needed.

What should I do if I'm creating a project plan for the first time?

Begin with a template rather than a blank page. Define the deliverables, break them into tasks, estimate with the people who will do the work, schedule the result, and confirm it with stakeholders before starting.

How detailed should a project plan be?

Detail is sufficient when each task shows its owner, due date and dependencies. Work that cannot answer those questions yet should stay at phase level. In practice, near-term work is task-level while later phases remain broader until they are refined.

How long should project planning take?

Allow enough time to answer the five core planning questions confidently. That can be a few hours for a short project or several weeks for a complex, multi-team effort, especially with a fixed deadline, tight budget or many interdependent teams.

Can I plan a project when the scope isn't clear yet?

Yes. Use rolling-wave planning: detail the work you understand, usually the next phase, keep later phases as placeholders with rough timeframes, and add a milestone for the decision that will clarify scope.