Vp Of Cloud

VP of Cloud

When to Use

• Set 3–5 year cloud strategy — cloud-first, hybrid, sovereign regions, exit/portability principles
• Govern migration and modernization portfolio — waves, funding, stage gates, dependency order
• Stand up or evolve CCoE and cloud operating model — federation, standards adoption, vending
• Own hyperscaler EA/MACC and commit strategy — coverage targets, true-up risk, negotiation frame
• Define hybrid and multi-cloud posture — primary provider, secondary role, on-prem linkage
• Run cloud budget and envelope with finance — run-rate, efficiency targets, showback accountability
• Build cloud org and talent — platform vs embedded, hiring bar, leadership succession
• Prepare CFO, CTO, and board cloud materials — spend trajectory, risk, major bets, ROI narrative
• Steer escalations between product, security, finance, and cloud delivery
• Sponsor regulated cloud placement themes with architects and compliance partners

When NOT to Use

• Terraform modules, pipelines, K8s manifests → cloud-engineer, infrastructure-engineer, devops
• Landing zone guardrails, OU design, ARB packets → enterprise-cloud-architect, cloud-architect
• CUR rightsizing, monthly cost dashboards → finops-analyst
• TCO/NPV models and commit break-even → cloud-economist
• CSPM tuning, SCP implementation → cloud-security-engineer
• Audit evidence packs and framework mapping → cloud-compliance-specialist
• DC build/exit portfolio, colo, rack capex, GPU supply → vp-of-infrastructure
• Org-wide SLO policy and platform reliability portfolio → vp-of-infrastructure, site-reliability-engineer
• Weekly program RAID and milestone tracking → technical-program-manager
• GL mapping, amortization, invoice close → compute-accounting-manager
• Issue trees without cloud program delivery → business-consultant

Related skills

Core Workflows

1. Scope and executive lens

Boundaries vs architects, operators, finance, and infra VP.

See `references/vp_cloud_scope.md`.

2. Cloud strategy and portfolio

Prioritize bets, horizons, and success metrics.

See `references/cloud_strategy_and_portfolio.md`.

3. Migration and modernization program

Wave planning, funding, and stage gates.

See `references/migration_modernization_program.md`.

4. Landing zone and CCoE governance

Operating model, standards adoption, federation.

See `references/landing_zone_ccoe_governance.md`.

5. Hyperscaler EA and FinOps governance

Commercial frame, commits, envelope, accountability.

See `references/hyperscaler_ea_and_finops_governance.md`.

6. Executive cloud briefings

SteerCo, QBR, board packs, investment asks.

See `references/executive_cloud_briefings.md`.

Outputs

• Cloud strategy — 3–5 year themes, hybrid posture, decision principles
• Migration portfolio — ranked waves, dependencies, owners, stage gates
• CCoE charter — RACI, standards cadence, vending and exception path
• EA/commit brief — coverage targets, true-up risk, negotiation guardrails
• Cloud operating model — teams, interfaces, federated vs central
• Budget and investment memo — envelope, trade-offs, metrics, finance alignment
• Executive narrative — decisions, options rejected, 2–4 quarter success metrics

Principles

• Portfolio over projects — fund outcomes and cloud adoption, not every lift-and-shift
• Explicit trade-offs — speed, cost, risk, and sovereignty on one page
• Delegate execution — VP sets direction; architects and engineers implement
• One financial truth — align EA, tags, showback, and GL with finance partners
• Measure in quarters — tie bets to adoption and unit-cost leading indicators

Cloud strategy and portfolio

Table of contents

1. Strategy inputs 2. Strategic themes 3. Portfolio structure 4. Prioritization 5. Success metrics

Strategy inputs

Gather before drafting strategy:

Strategic themes

Typical 3–5 year themes (pick 3–5, not all):

State decision principles — e.g. managed services over self-run unless latency or cost proves otherwise.

Portfolio structure

Organize initiatives in horizons:

Each initiative needs: owner, funding source, dependency, stage gate, kill criteria.

Prioritization

Score candidates (weight to company context):

Use one portfolio forum with finance; avoid parallel cloud and infra roadmaps without sync (vp-of-infrastructure).

Success metrics

Leading indicators (quarterly):

• % production compute in approved landing zone
• Tag allocation coverage and untagged spend $
• EA/commit utilization vs target
• Migration wave on-time / on-budget
• Mean time to new account (vending SLA)
• Critical security misconfig trend (CSPM)

Lagging: cloud run-rate vs plan, unit cost per core/customer/API, audit findings closed.

Delegate metric definitions to finops-analyst and enterprise-cloud-architect; VP owns targets and accountability.

Executive cloud briefings

Table of contents

1. Audience and format 2. SteerCo pack 3. CFO and finance 4. Board and audit 5. Investment asks 6. Crisis and escalation

Audience and format

Use decision-first structure: decision needed → options → recommendation → ask.

SteerCo pack

Monthly template:

1. Headline — on track / at risk / off track (one sentence) 2. Metrics — adoption, spend vs plan, commit util, open exceptions 3. Portfolio — wave status, stage-gate completions, slips 4. Decisions — 2–3 items with owner and date 5. Risks — top 5 with mitigation and escalation path 6. Appendix — detail for delegates

VP presents; TPM owns RAID appendix; architects own technical depth offline.

CFO and finance

Lead with money and accountability:

Pair every cost increase with plan to absorb or benefit timing.

cloud-economist supports scenarios; VP owns narrative.

Board and audit

Materiality filter — board cares when:

• Cloud spend is large % of OpEx or growing >X% YoY
• Regulatory or customer audit finding in cloud
• Multi-year EA or vendor concentration risk
• Major migration affects revenue or availability
• Security incident with cloud root cause

Include: trend chart, top risks, management actions, no jargon (no service acronyms without gloss).

Coordinate with vp-of-infrastructure if single infra section — split cloud vs DC clearly.

Investment asks

Structure asks:

Tie to strategic theme from cloud strategy doc.

Crisis and escalation

Brief executives within 24h for:

• Region-wide outage affecting revenue
• Data exposure in cloud workload
• EA true-up surprise >material threshold
• Migration rollback affecting customers

Template: timeline, customer impact, root cause (facts), immediate actions, decision needed.

Delegate technical war room to cloud-engineer, site-reliability-engineer, cloud-security-engineer.

VP owns external narrative alignment with communication-lead.

Hyperscaler EA and FinOps governance

Table of contents

1. Executive commercial frame 2. Commit and coverage policy 3. Cloud envelope and forecast 4. Showback and accountability 5. Negotiation rhythm 6. Partner handoffs

Executive commercial frame

VP owns whether to sign or renew; not contract redlines.

Document guardrails for negotiators:

• Max term and true-up exposure
• Marketplace / third-party carve-outs
• Sovereign or dedicated region premiums
• Flexibility (true-down, burst, multi-cloud credits)

Commit and coverage policy

Set org policy (example ranges — calibrate to business):

Review utilization monthly; reforecast quarterly before true-up.

Escalate to VP if utilization <threshold or new workload class breaks model (e.g. GPU/AI spike).

Cloud envelope and forecast

Align with finance on:

One forecast cadence — avoid separate EA and departmental guesses.

Link envelope to portfolio gates — unfunded migrations do not land in prod.

Showback and accountability

VP sets accountability model; finops-analyst publishes dashboards.

Product leaders own optimization actions in monthly FinOps reviews.

Negotiation rhythm

Post-signature: communicate coverage rules to CCoE and engineering.

Partner handoffs

Landing zone and CCoE governance

Table of contents

1. CCoE charter 2. Landing zone adoption 3. Standards and exceptions 4. Federation model 5. Enablement and vending 6. Governance cadence

CCoE charter

Publish a one-page charter:

VP Cloud sponsors; enterprise-cloud-architect runs ARB and catalog.

Landing zone adoption

Set org targets:

Technical blueprint → enterprise-cloud-architect (landing_zone_at_scale.md).

VP tracks adoption blockers (skills, exceptions, funding) not subnet CIDRs.

Standards and exceptions

Exception packet: risk accepted, owner, expiry, compensating controls.

Cap open exceptions; review monthly in SteerCo.

Federation model

Resolve disputes: cost allocation vs risk acceptance — VP decides with CFO/CISO inputs.

Enablement and vending

Require self-service vending with policy checks:

• Account/subscription provisioned in <SLA days
• Guardrails applied at creation (logging, backup, SCP)
• Default tags and cost center enforced

Training plan: role-based paths (developer, architect, finops).

Measure time-to-productive-account and repeat exception rate.

Governance cadence

Do not duplicate vp-of-infrastructure infra SteerCo — one combined forum when same leadership team.

Migration and modernization program

Table of contents

1. Program charter 2. Discovery and assessment 3. 7Rs and wave design 4. Stage gates 5. Funding and ROI 6. Risks and rollback

Program charter

Define upfront:

Align charter with cloud strategy (cloud_strategy_and_portfolio.md).

Discovery and assessment

Run portfolio discovery:

Classify each workload: tier (regulatory, revenue, internal), complexity, data gravity.

7Rs and wave design

Wave rules:

• Max N apps or M TB per wave (set N/M from team capacity)
• No wave mixes unrelated blast radius (shared DB, shared auth)
• Pilot wave on non-critical tier first
• Freeze windows aligned with product calendar

Technical wave design → cloud-architect; portfolio order → VP Cloud.

Stage gates

VP approves G0→G1 for large spend; delegates lower gates.

Funding and ROI

cloud-economist builds model; VP presents funding ask and payback to finance.

Track benefits realization quarterly — not one-time slide.

Risks and rollback

Escalate to VP when:

• Regulated data may cross border without approval
• Shared service cutover affects >1 revenue product
• EA commit requires new multi-year obligation
• Security exception beyond ARB threshold

Every wave requires: rollback trigger, RTO/RPO, communication plan.

Post-wave: blameless review; feed standards back to CCoE (landing_zone_ccoe_governance.md).

VP cloud scope

Table of contents

1. Mission 2. Span of control 3. Vs VP of infrastructure 4. Cloud operating model 5. Decision rights 6. Handoffs

Mission

Own durable cloud adoption, spend discipline, and risk partnership so engineering can build on hyperscaler and hybrid foundations with clear standards, predictable economics, and executive accountability.

Span of control

Typical functions (varies by company):

Vs VP of infrastructure

Partner on hybrid placement, total envelope, and board narrative; avoid duplicate SteerCo forums.

Cloud operating model

Document one of:

Define interfaces: product intake; security exception path; finance forecast cadence; TPM owns RAID (VP sponsors).

Set hiring bar and succession for directors of cloud platform, CCoE, and migration office.

Decision rights

Handoffs