Project Toolkit

Executive

Executive

The Executive role - chairs the Project Board, owns the business case, and is ultimately accountable for project success.

Executive

The Executive is the single individual ultimately accountable for the success of the project. They chair the Project Board, own the business case, and make sure the project delivers value for money. If something goes wrong, the Executive answers for it.

Purpose

The Executive exists to:

  • Chair the Project Board and run effective governance
  • Own the business case and protect its viability
  • Ensure value for money across the life of the project
  • Balance user, supplier, and business interests
  • Decide on stage gates, exceptions, and major changes

Key Responsibilities

Area Responsibility
Business case Owns it, keeps it current, defends it
Direction Sets project tolerances and decision boundaries
Board chair Convenes, leads and concludes Project Board meetings
Approvals Authorises each stage, plans and exceptions
Escalations Receives issues exceeding Project Manager tolerance
Closure Confirms project objectives met; closes the project

The Three-Sided Balance

The Executive’s core job is to balance three perspectives represented on the Project Board:

flowchart LR E[Executive] --> B[Business
Value] E --> U[User
Needs] E --> S[Supplier
Capability] B --> D[Balanced
Decisions] U --> D S --> D classDef blue fill:#108BB9,stroke:none,color:#fff class E,B,U,S,D blue
Perspective Represented By Tension to Resolve
Business Executive themselves Value for money vs scope ambition
User Senior User Wants more features and quality
Supplier Senior Supplier Wants realistic timelines and resources

The Executive’s job is not to side with any one perspective but to make the trade-offs explicit and decide.

Decision Authority

The Executive holds decisions that the Project Manager cannot make alone:

Decision Type Examples
Stage approvals Authorise the next stage, end of stage reports
Change requests Approve scope, cost, or time changes beyond tolerance
Exceptions Decide what to do when tolerances are breached
Resource conflicts Reallocate resources across the project
Risk acceptance Accept significant residual risks
Closure Confirm project is complete and benefits owned

Executive vs Project Sponsor

In many organisations these roles overlap or are held by the same person. When they are separate:

Aspect Executive Project Sponsor
Position On the Project Board Above the Board
Engagement Active, ongoing Periodic, milestone-based
Focus Project success, business case Benefits realisation, strategic fit
Accountability Delivery within tolerance Value to the organisation

What Good Executives Do

  • Make decisions promptly — silence is a decision, just a bad one
  • Read the Project Manager’s reports before the meeting
  • Ask “so what?” questions that drive clarity
  • Protect the project from organisational politics
  • Hold the Senior User and Senior Supplier to account too
  • Close the project cleanly when it’s done — and stop it if it shouldn’t continue

Common Executive Pitfalls

Pitfall Symptom Mitigation
Delegated chair Sends a deputy who can’t decide Insist on attendance or written delegation
Rubber-stamping Approves everything without scrutiny Surface trade-offs explicitly in reports
Conflict avoidance Won’t take sides between user and supplier Force the trade-off; document the decision
Drifting business case Original justification no longer holds Re-baseline or trigger an exception
Last updated: 18 May 2026
Themes

Governance

Stakeholder Engagement