Executing is where deliverables appear and where the plan meets other people's calendars. Directing work is coordination, not heroics. If your status report is a list of meetings you attended, you are executing a diary.
Direct and manage the work — then prove it exists
The core executing process is getting authorised work done and producing the outputs the baseline promised. That includes approved changes, not just the original scope. A team busy on last week's interpretation of the charter is executing something. It may not be the project.
Manage project knowledge while you are at it. Decisions, rationale, and 'we already tried that' walk out of the building unless you capture them. A shared space that nobody updates is not knowledge management. It is a graveyard with search.
Procurements and vendor work sit here too: you conduct the buying you planned, then you manage the relationship so the contract is not the only person in the room who knows what 'done' means. A PO is not a deliverable.
Team, quality, and communications are execution, not extras
Acquire, develop, and manage the team in this group. You are often borrowing people who still report to someone else. That is not a personal failing; it is the job. Clarity, impediment removal, and escalating resource conflicts to the person who can actually move a functional manager beat motivational posters.
Manage quality here means building the work the way you said you would — checklists, reviews, definition of done — not waiting for a test phase to discover the process was theatre. Inspection later is control. Prevention now is execution. Confusing the two is how 'we test at the end' becomes a personality.
Communications and stakeholder engagement are work, not courtesy. The plan said who gets what, when. Executing that plan is how rumours stay unemployed. Silence is also a message. It usually says 'invent your own status.'
Risk responses and change requests are also work
Implementing a risk response is executing, not 'monitoring.' If the fallback vendor was the mitigation, someone has to brief them and pay the retainer. A response that lives only in the register is a wish with a colour.
Work will generate change requests. Your job in execution is to route them through integrated change control, not to absorb 'small' ones because the requester is senior and the team is tired. Execution without a change path is how baselines die of a thousand favours.
Do not wait for the monitoring meeting to notice that the work is the wrong work. Execution produces data — completed packages, defect counts, vendor dates. If you only look at those numbers in a steerco pack, you have outsourced control to a slide.
Summary & next steps
Executing directs authorised work, grows the team, builds quality in, runs communications, implements risk responses, and feeds change control. Activity is not earned value. Knowledge that is not captured will need to be rediscovered, usually in week twelve.
Next: Monitoring and controlling — the parallel group that compares that work to the baseline and decides what to do about the gap.