2.3 Execution Phase

The execution phase is where the project blueprint becomes real. Teams take action, build deliverables, and work together toward the project's goals.

This phase consumes the most resources — people, time, cost — and is where real progress, quality, and adaptability are tested. The key isn't just "follow the plan," it's how well the team adjusts and keeps moving forward when reality shifts.

Purpose of the Execution Phase

The goal here is clear: Carry out the plan within the agreed scope, quality, timeline, and budget — and deliver actual results.

To get there, you need to manage the team and the project from several angles:

Progress Tracking: Monitor and adjust execution in real time
Quality Control: Ensure outputs meet required standards
Team Management: Keep people aligned, motivated, supported
Change Management: Handle scope changes and surprises
Stakeholder Communication: Respond clearly and quickly to outside input

Key Activities During Execution

1. Assign and Launch Work

Tasks are assigned based on the WBS and schedule. Success here depends on whether the plan has been broken down into executable, clearly owned actions.

2. Track and Report Progress

Monitor task completion daily, share weekly/monthly updates. If delays or issues emerge, act immediately to prevent them from cascading.

3. Manage the Team and Communication

When communication breaks down, progress and quality suffer. Use regular standups, 1-on-1s, chats, and informal check-ins to keep information flowing. Support psychological safety and flexibility — the human side matters.

4. Perform Quality Control

Ensure deliverables meet expected standards. Use documented review processes, test plans, and checkpoints to compare outputs against predefined quality criteria.

5. Manage Issues and Changes

Unexpected problems and change requests will happen. The key is having a clear process for logging, prioritising, and getting alignment on actions — not relying on gut instinct or one person's judgment.

6. Handle Stakeholder Interactions

Requests from external clients or other departments need handling efficiently. How well you respond directly shapes trust and ongoing support.

Tools and Techniques That Help

Use tools to increase transparency and efficiency:

Gantt Charts / Kanban Boards: Visualise task progress
Daily Logs / Progress Reports: Keep everyone aligned
Issue Tracking Sheets: Log and manage unresolved problems
Chat & Document Sharing Tools: Enable smooth remote collaboration

Common Pitfalls in Execution

Over-reliance on the plan: Expect things to go off-script — that's normal.
Delayed reporting: The worse a situation gets, the more tempted people are to stay silent — which makes things worse.
Knowledge silos: If only one person understands something, it's a risk. Document and share.

Summary: Balance Action with Oversight

The execution phase moves fast and unpredictably. Rather than sticking rigidly to the plan, teams must adapt without losing sight of the goal.

For project managers, this phase is about more than oversight — it's about bridging the team on the ground and the decision-makers above. That balance is what defines successful execution.

How this looks in AB

Execution is the phase where AB Project Management earns its keep:

Progress tracking → the progress % field on each task plus the status field roll up into the project dashboard. The Calendar shows what's due this week without anyone writing a report.
Issue tracking → tasks with type "Bug" or "Issue" sit alongside delivery work, so problems aren't kept on a separate list nobody updates.
Communication → Adaptive Cards in your Teams or Slack channel announce status changes; mentions ping the right person on the right task; the change-history tab keeps an audit trail without manual logging.
AI assistance → AI assistants connected via the MCP server can read open tasks, post comments, change status, and create subtasks — closing the loop on routine updates without dragging you back to the dashboard.

The goal isn't more reporting. It's making the actual state of the project visible to everyone, all the time, so the conversation can be about what to do next instead of what's currently true.

→ Next: 2.4 Closing Phase