Cross-Portfolio Dependency Critical-Path Director

The mandate

Eleven programme reports show acceptable local progress, but the district cannot demonstrate one credible path to opening because shared dependencies are represented as assumptions or milestones owned elsewhere. Venue commissioning depends on permanent power, security accreditation, transport rehearsals, digital wayfinding, collections movement and trained operators arriving in a precise sequence. The defined problem is to expose and govern that cross-portfolio path without replacing individual project controls.

The named deliverable is an integrated opening-dependency architecture containing a product-based breakdown of opening states, a logically linked cross-programme network, 40 critical interface agreements, quantified schedule confidence, decision deadlines and an executive intervention book. It must distinguish physical completion, regulatory permission, operational readiness and guest-experience integration. A verified data model and portfolio-room operating guide are included; new scheduling software, claims opinion and contractor re-planning are excluded.

Milestone one, at month one, delivers the agreed definition of opening, source-control assessment and first dependency inventory. Milestone two, at month three, supplies the integrated network, interface agreements and probabilistic path analysis. Milestone three, at month five, runs two launch-readiness scenarios and resolves ownership gaps. Milestone four, at month six, submits the accepted baseline, intervention book, assurance protocol and ninety-day transition plan.

Acceptance requires every critical dependency to have a providing programme, receiving programme, evidence condition, need date, confidence range and named escalation owner. The Chief Executive and venue operating leaders must trace three representative guest journeys through physical, permission, people and digital readiness. Independent programme assurance must reproduce the critical path from source schedules, while the steering committee signs the top fifteen interventions and no unresolved interface remains labelled simply “by others.”

The client will provide native schedules, contract milestones, permit registers, commissioning plans, operating-concept documents, event calendars, contractor interface logs and access to all eleven programme directors. It will appoint a portfolio sponsor, data controller and empowered working group, secure attendance at two scenarios, and decide disputed priorities within five business days. Client teams retain delivery, contract, schedule-change, claims, regulatory and launch authority throughout.

Why this is external work

Each programme office is incentivised to defend its own baseline and has neither the mandate nor neutrality to challenge another director’s promise. The central portfolio team aggregates milestones but lacks deep opening-integration experience. An external director can establish one evidence standard and surface collective infeasibility without becoming a twelfth delivery programme.

What you will own

• Define measurable opening states spanning completed assets, legal permissions, commissioned systems, trained operators and coherent guest journeys.
• Reconcile eleven source schedules into a dependency network while preserving lineage to each programme’s controlled planning system.
• Draft 40 interface agreements specifying provider, receiver, evidence, need date, tolerance, escalation route and change responsibility.
• Quantify path confidence and expose correlated assumptions, hidden calendar constraints, resource collisions and milestones owned only “by others.”
• Facilitate two launch scenarios that test partial venue readiness, late utilities, security conditions and digital-experience degradation.
• Frame the top fifteen executive interventions with decision deadlines, alternatives, consequence, reversibility and responsible decision forum.
• Hand over the accepted architecture, assurance method, portfolio-room guide, transition backlog and unresolved evidence limitations.

Candidate qualifications

• Integrated portfolios of venues, airports, campuses, major events or mixed-use assets through construction, commissioning and operational opening.
• Can build logic from incompatible native schedules without masking uncertainty through a manually curated executive milestone list.
• Has governed interfaces across utilities, transport, security, permits, digital systems, operators and customer-experience owners.
• Applies probabilistic schedule analysis intelligently and can explain correlation, confidence and decision usefulness to non-planners.
• Has run opening rehearsals that revealed dependencies absent from construction completion and statutory approval reporting.
• Delivered an independent cross-portfolio baseline accepted by project directors, operators, executive sponsors and programme assurance.

Non-negotiables

• Can maintain an onsite Doha portfolio room through the six-month engagement and lead both launch scenarios.
• Will remain independent of programme-management, scheduling-software, engineering, claims and delivery-partner follow-on commissions.
• Accepts that contract, claims, programme baseline, regulatory and launch decisions remain with client-authorised owners.
• Brings actual complex-asset opening integration; single-project planning or dashboard configuration alone is insufficient.

1. 49 words maximum. Describe a dependency that made individually healthy projects collectively unable to open.
2. 49 words maximum. How would you preserve source-schedule lineage while constructing one cross-portfolio critical path?
3. 49 words maximum. What evidence must an interface agreement contain before you treat its milestone as credible?