EXECUTIVE OFFICER

A leadership framework for the work leaders are already expected to govern.

Role-Agnostic Project Leadership™ is a leadership capability framework designed to help organizations examine & address the gap between what strategic work requires & what leadership systems deliberately build. The model follows the full value path from business need & strategic choice through governance, delivery risk, adoption & sustained operational value the same Leadership Capability Gap introduced on the RAPL™ home page.

Executive office with city view
WHAT ROLE-AGNOSTIC MEANS

The capability follows the work, not the job title.

Role-agnostic means the capability follows the work, not the job title. Any leader who sponsors, governs, prioritizes, shapes, enables or depends on strategic initiatives may require RAPL™ capability.

It does not mean every role requires the same depth. A CEO, CIO, CHRO, CFO, COO, chief transformation officer, PMO leader and business-unit leader should each be assessed against the demands of the seat and the consequences of weak performance — a comparison made explicit through the Leadership Capability Alignment Diagnostic.

CEO CIO CHRO CFO COO Chief Transformation Officer PMO Leader Business-Unit Leader
A CLEAR DISTINCTION

Executive project leadership, not practitioner substitution.

RAPL™ does not ask senior leaders to build schedules, maintain backlogs, manage RAID logs or perform the specialist work of delivery teams. It asks them to know what questions the evidence should answer, when information is insufficient, when risk is being normalized, when a dependency needs executive action, when a business case has weakened and when work should stop.

This distinction — between leading the work and performing it — is what the twelve capabilities below are built to develop.

THE FULL MODEL

Four phases. Twelve capabilities. One value cycle.

Each phase groups three leadership acts. The same capability can be exercised in different phases and at different depths depending on the seat and the work.

PHASE 1

Define the Work

Diagnose what is really required before anything is committed.

01

Diagnose

Frame the business need, the operating context and the work required before committing investment.

02

Choose

Make strategic, evidence-informed choices between competing options, with explicit reasoning.

03

Translate

Convert strategic intent into briefs, mandates and language that delivery and the business can act on.

PHASE 2

Govern the Work

Hold the work, the people & the system together through delivery.

01

Select

Determine the right delivery shape — portfolio, program, project, product or hybrid — for the work at hand.

02

Integrate

Coordinate across functions, vendors, governance bodies and operating models so the whole system works.

03

Deliver

Sponsor major milestones, unblock dependencies and protect the conditions delivery needs.

PHASE 3

Protect the Work

Keep value, risk and accountability visible from intent to operation.

01

Protect

Hold risk, security, ethics and AI exposure as visible executive concerns, not delivery-team tasks.

02

Align

Keep stakeholders, governance and operating model aligned as the work evolves.

03

Govern

Maintain clear decision rights, investment discipline and accountability through change.

PHASE 4

Land the Value

Make the result stick in adoption, in operations, in sustained value.

01

Optimize

Adjust the work in flight, with the business case and value thesis always visible.

02

Adopt

Drive adoption through change, capability, communication and sponsorship — not just deployment.

03

Sustain

Transition outcomes into the operating model and protect benefits realization over time

HOW TO READ THE MODEL

Four views of one model.

RAPL™ can be read as four different things at once — depending on what the work needs from you.

01

Value cycle

Define the Work, Govern the Work, Protect the Work and Land the Value.

02

Capability set

Twelve leadership acts & the established practice domains they draw upon.

03

Role-demand model

The depth required varies by seat, context and consequence.

04

Capability-management system

Capability is assessed, developed, applied, evidenced and refreshed.

AT ORGANIZATIONAL SCALE

Embedding RAPL™ into roles, governance and talent systems.

The framework is most effective when it moves beyond individual development and shapes role design, governance forums, performance standards & succession criteria across the leadership system.

The capability gap

A capability gap exists when the capability a strategic role requires is not what the leadership system deliberately develops, assesses or rewards.

RAPL™ is built to make that gap visible, then close it — through seat profiles, capability baselines, gap heatmaps and governance integration.

Seat Profiles Baselines Heatmaps Targeted development Governance integration
BEGIN THE FRAMEWORK

Explore the model. Build the capability. Govern the work.

Whether you're an individual senior leader, an organization, or a researcher — there is a structured on-ramp.