Executing

In project management, executing is the process group where the plan becomes real work. Bodies of knowledge such as the Project Management Institute's Guide to the Project Management Body of Knowledge — commonly the PMBOK Guide — group project activity into process groups: initiating, planning, executing, monitoring and controlling, and closing. Executing is the doing phase. It is where the team performs the tasks laid out in the plan, coordinates people and resources, manages the vendors and stakeholders, assures quality, and produces the actual deliverables the project exists to create. If planning decides what will be done and how, executing is the part where it actually gets done. Because the real work happens here, executing typically consumes the largest share of a project's budget and effort, and it is where the plan meets reality.

Executing is not a single step but an ongoing set of activities that run while the project is live. The project manager directs and manages the work, keeps the team focused, acquires and develops the people doing it, communicates with stakeholders, and handles the coordination that turns a schedule into finished output. It does not run alone. Executing happens hand in hand with monitoring and controlling, which measures progress and feeds corrections back in. That pairing is what keeps execution on track when reality diverges from the plan, as it always does to some degree. So executing is both a phase in the project's arc and a continuous engine of delivery, active from the moment the plan is approved until the deliverables are complete.

Executing is defined partly by what surrounds it. Planning comes first and produces the roadmap: the scope, schedule, budget, resource plan, and risk approach that say what will be built and how. Executing then carries that roadmap out. The two are distinct on purpose — deciding what to do is a different discipline from doing it — and a common failure is to blur them, either executing without a real plan or planning endlessly without ever shipping. Where planning is about decisions and documents, executing is about action and output, the deliverables that only exist once the work is performed. The handoff between them is not always clean, since plans get refined as work reveals new information, but the distinction in purpose is clear.

Executing also pairs with, but differs from, monitoring and controlling. Monitoring and controlling is the measurement-and-correction process group. It tracks progress against the plan, checks quality and scope, and initiates changes when the work drifts. Executing is the work itself, while monitoring and controlling is the oversight that watches the work and steers it. They run at the same time throughout delivery — you execute the tasks while you monitor their progress and control any deviations — which is why the two are often discussed together. The neat way to hold the whole arc in mind is a sequence with a feedback loop: initiate, plan, then execute while you monitor and control, and finally close. Executing is the engine, controlling is the steering, planning drew the map, and closing parks the car.

Executing well means turning a sound plan into finished deliverables without losing sight of it. That takes clear direction of the work, good coordination of people and resources, active communication with stakeholders so no one is surprised, and steady attention to quality as output is produced rather than only at the end. Because executing runs alongside monitoring and controlling, doing it well also means feeding progress and problems back into that loop and accepting the changes it returns, so the work adapts instead of blindly following an outdated plan. The best execution keeps the team focused on the deliverables, removes the obstacles in their way, and treats the plan as a living guide — followed faithfully where it holds, revised through proper change control where reality has moved on.

The traps are familiar. Executing without a real plan is just busy motion, producing activity that may not add up to the intended result. Executing while ignoring monitoring and controlling lets small deviations grow into large ones before anyone notices. Confusing effort with progress — measuring how hard people are working rather than what deliverables are complete — hides trouble, which is exactly why teams pair execution with a burn-up chart or similar tracking to show real output against scope. And letting scope quietly expand during execution, without running changes through control, blows budgets and schedules. Done well, executing is disciplined delivery. The plan is carried out, the work coordinated, quality assured, progress tracked, and changes managed, so the project's deliverables actually appear.

Executing comes from the Latin exsequi, meaning to follow to the end or carry out; in project management it names the PMBOK process group where the plan is carried out.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where executing is a core concern: