5.1 Project Execution, Adoption & Phase Gates

Execute the Authorized Plan

Execution converts approved plans into deliverables. The team performs tasks in the project management plan, implements only approved changes, captures actual cost and schedule data, and raises risks or issues rather than quietly changing scope. The project manager coordinates work; technical specialists remain responsible for the technical decisions assigned to them.

A practical execution rhythm links five activities:

1. Confirm the current approved task, owner, dependency, acceptance criteria, and required environment.
2. Perform the work and record actual effort, cost, progress, defects, risks, and issues.
3. Validate intermediate deliverables and resolve exceptions through the defined quality, issue, risk, or change process.
4. Report status to the correct audience and update the budget forecast and timeline forecast without rewriting approved baselines.
5. Present required evidence at a milestone or phase gate before moving into the next controlled stage.

Organizational Change Management

A technically correct deliverable can still fail if users do not adopt it. Organizational change management addresses the people and operational effects of a new system or process. Assess who is affected, what behavior changes, why resistance is likely, and how readiness will be measured.

Responses include role-based training, repeated communication, job aids and documentation, new knowledge-base articles, revised operating processes, and support during go-live. Adoption is not a one-time announcement: reinforce it over time with coaching, metrics, feedback, and corrective action. Product deployment and user adoption are separate outcomes, so report both.

Manage Vendors During Execution

Enforce the contract’s rules of engagement: authorized contacts, reporting cadence, access boundaries, escalation path, change procedure, and invoice or time-entry rules. Monitor performance against milestones, quality measures, service levels, and the statement of work. A vendor saying work is complete is not approval; the authorized reviewer compares the deliverable with documented acceptance criteria and records acceptance, rejection, or corrective work.

Meetings, Reports, Budget, and Timeline

Use team touchpoints for coordination and blockers; risk reports for exposure and response status; external status reports for customer or regulator needs; overall progress reports for integrated health; gap analysis for differences between required and actual capability; and ad hoc reports for an authorized one-time decision. Update budget and timeline forecasts with current actuals. If an approved change alters a baseline, update it only after the decision is documented.

Conflict choices in the objectives are smoothing, forcing, compromise, collaboration, and avoiding. Collaboration addresses underlying interests and is often durable, but the best response depends on urgency, authority, safety, and whether a temporary cooling-off period is useful.

Coordinate a Phase Gate

A phase gate is a governance decision point, not a celebratory meeting. Assemble the required deliverables, test results, open risks and issues, budget and schedule status, approvals, and next-phase plan. Reviewers compare that evidence with defined exit criteria and may continue, continue with conditions, require rework, pause, or terminate. Record the decision, conditions, owners, and communications before the next phase begins.

Worked Scenario: Identity-Service Rollout

An IT team is replacing a legacy identity service. The approved plan requires a pilot, employee training, a weekend maintenance window, vendor support, and a phase gate before enterprise rollout.

During execution, the vendor reports the pilot package complete. The project manager does not approve it from the status email. The technical owner checks the build and rollback documentation against the statement of work, testers verify the acceptance criteria, and the training lead confirms that support materials are ready. One requirement fails, so the defect is logged and the vendor corrects it under the contract.

At the same time, adoption data shows that pilot users keep signing in through the legacy workflow. This is not a reason to hide the metric or call deployment complete. The team revises job aids, holds manager briefings, adds a searchable support article, and measures successful use of the new path. The timeline forecast is updated for the correction; the approved baseline remains unchanged because no baseline change has been authorized.

For the gate, reviewers receive the test result, defect closure, adoption measure, open-risk report, vendor acceptance record, budget and timeline forecasts, rollback evidence, and next-phase plan. They authorize rollout with a condition that the adoption measure be checked again after the first department. The scribe records that condition, its owner, due date, and escalation rule.

This scenario separates five commonly confused outcomes: task completion, vendor acceptance, technical validation, user adoption, and governance authorization. None automatically proves the others.