ENGAGEMENT DETAIL

Cloud Migration & Zscaler Execution — Program Leadership from Strategy to Cutover

Program direction across seven engagement types — organizational readiness, programplanning, governance, vendor orchestration, and delivery oversight for cloudmigration and Zscaler rollouts. This is execution leadership, not hands-onengineering.

FOR
Executives andPMOs who need someone accountable for cloud and Zscaler program outcomes —scope, schedule, governance, vendors, and cutover.

NOT FOR
Teams lookingfor a hands-on engineer to configure tenants, write policies, or build thetechnical solution.

← Back to Cloud & Zscaler Practice

Migration Readiness Diagnostic

A structured pre-program diagnostic of yourorganization’s readiness to execute a cloud migration. Using the CloudMigration PM Bible™ framework, I evaluate the people, processes, governance,and vendor landscape before any program commitment is made — surfacing therisks and gaps that would otherwise appear mid-execution, when they cost themost to fix.

The engagementproduces a written readiness report with findings, risk ratings, andprioritized recommendations. It is not a vendor selection exercise, atechnology evaluation, or a technical assessment of your environment. It is adelivery readiness diagnostic — built to tell you whether your program is setup to succeed before you commit budget and resources.

What is delivered
Typical EngagementScoped after intake,
typically 2–6 weeksdepending on organizational
scale and stakeholder access
FormatRemote with optional on-site
OutputWritten report + recommendations

Best for: Executives and PMOs planning a cloud migrationwho need an honest pre-program diagnostic — and a clear go/no-go view — beforecommitting budget, vendors, and internal resources.

For organizational-level diagnosis, see Engagement 07 →

PMO Design & Stand-Up

Design andstand-up of a program management office calibrated to the complexity, vendorstructure, and governance requirements of your specific program. The CloudMigration PM Bible™ framework does not deploy a generic PMO template — everystructure is built around what the program actually needs to execute.

PMO Design& Stand-Up engagements cover operating model design, reporting cadence,escalation framework, tooling selection, and initial governance documentation.Delivery continues until the PMO is operational and running independently underyour leadership.

What is delivered
  • ✅ PMO operating model design (governance, reporting cadence, decision rights)
  • ✅ Escalation framework and decision authority matrix
  • ✅ Program tooling selection and rollout guidance
  • ✅ Template library: status reports, risk logs, RAID,decision registers
  • ✅ Stakeholder communication structure
  • ✅ Handover documentation and transition support
Typical EngagementScoped after intake — driven by programcomplexity, vendor structure, and governance maturity
FormatRemote with optional on-site kickoff
OutputOperational PMO + documentation suite

Best for: Programs launching without PMO infrastructure,or organizations rebuilding a failing governance structure mid-program who needa senior leader to design and stand it up.


Embedded Program Leadership

A senior CloudMigration PM Bible™ practitioner embedded inside your organization as programlead, deputy program manager, or delivery executive. The practitioner holdsfull accountability for delivery milestones, vendor coordination, andstakeholder reporting — functioning as a member of your leadership team, not anexternal consultant on the sidelines.

Embeddedengagements are ongoing. The practitioner joins at whatever stage the programis in, establishes delivery rhythm, and remains accountable until theengagement is complete or transitioned to internal leadership.

What is delivered
  • ✅ Senior practitioner embedded in client organization as program leadership
  • ✅ Ownership of delivery milestones and program rhythm
  • ✅ Vendor and SI management and accountability
  • ✅ Weekly stakeholder reporting and executive updates
  • ✅ Escalation management and issue resolution
  • ✅ Ongoing delivery discipline and governance oversight
Typical EngagementMinimum 3-month engagement; full duration scopedto program lifecycle and transition plan
FormatRemote with optional on-site
CommitmentPart-time or full-time based on scope

Best for: Programs that need senior delivery leadershipwithout adding permanent headcount, or organizations recovering a program thathas lost momentum and need an experienced leader accountable for restoring it.


Zscaler Program Oversight (Client-Side)

Client-sideprogram leadership for Zscaler ZTNA rollouts. I operate independently of theZscaler implementation partner — representing your interests, overseeing thetechnical delivery being performed by the SI, and ensuring the deploymentprogresses in a way that serves your organization’s actual security andoperational requirements.

I am not aZscaler reseller, implementation partner, or hands-on technical engineer. Thisengagement provides independent client-side oversight — covering architecturereview coordination, identity integration oversight, policy design sign-off,phased rollout management, and user adoption planning. The SI performs thebuild; I make sure the build serves you.

What is delivered
  • ✅ Independent client-side oversight of Zscaler implementation partner
  • ✅ Architecture review coordination and technical deliveryaccountability
  • ✅ Identity integration oversight (Okta, Azure AD, LDAP)
  • ✅ Policy design review and sign-off process
  • ✅ Phased rollout planning and milestone tracking
  • ✅ User adoption and change management coordination
Typical EngagementScoped after discovery — typically 3–9 monthsdepending on tenant scale, identity complexity, and rollout phasing
FormatRemote with optional on-site
IndependenceNot a Zscaler partner or reseller

Best for: Organizationsimplementing Zero Trust who need independent client-side oversight of the SIrelationship and technical delivery outcome — not another vendor selling themmore product.


PRE-MORTEM Risk Workshop

A structuredrisk discovery session conducted before program execution begins. ThePRE-MORTEM Framework™ surfaces delivery risks, governance gaps, vendordependency issues, and organizational constraints before they becomeprogram-threatening problems. It is structured anticipation, not a traditionalrisk register exercise.

I facilitatethe workshop personally as a senior Cloud Migration PM Bible™ practitioner.Participants include key program stakeholders, delivery leads, and vendorrepresentatives where appropriate. The output is a prioritized risk registerwith recommended mitigations — owned by your program, not parked in a deck.

What is delivered
  • ✅ Facilitated half-day or full-day workshop session
  • ✅ Structured risk identification across delivery, governance, and vendor dimensions
  • ✅ Prioritized risk register with severity ratings
  • ✅ Recommended mitigation actions per risk
  • ✅ Written workshop summary and findings report
Typical Engagement1–2 days (workshop); preparation and findingsreport add approximately one week
FormatRemote or on-site
OutputRisk register + findings report

Best for: Programs in planning or early execution that need structured risk identification before momentum builds and course correction becomes costly.


War Room Activation

Rapiddeployment of an Execution Command Center for programs in crisis, at criticaldelivery milestones, or facing escalating stakeholder pressure. The War RoomModel™ provides structured daily operating rhythm, decision accountability, andreal-time stakeholder visibility — applied immediately, led personally.

War RoomActivation engagements are time-bounded and intensive. I deploy within days,establish the command center structure, and stabilize delivery beforetransitioning the program to a standard rhythm or to an embedded engagementunder continuing leadership.

What is delivered
  • ✅ Rapid deployment within 48–72 hours of engagement confirmation
  • ✅ Daily standup and decision cadence structure
  • ✅ Stakeholder reporting and escalation management
  • ✅ Issue log, blocker resolution process, and accountability tracking
  • ✅ Transition plan to stable delivery state
Typical EngagementDeployment within 48–72 hours; engagement lengthscoped to stabilization milestones, typically 2–8 weeks
FormatRemote with optional on-site
DeploymentWithin 48–72 hours of confirmation

Best for: Programs that have lost momentum, missedcritical milestones, or face board-level scrutiny and need immediate deliverystabilization under a senior leader.


Organizational Readiness Diagnostic — Applying the Burke–Litwin Model

Based on theBurke–Litwin Organizational Performance & Change Model (Burke & Litwin,1992), this is a pre-transformation diagnostic that examines whether yourorganization — not just your program — is set up to absorb major change. Iassess the twelve organizational factors that determine transformation success:external environment, leadership, mission and strategy, culture, structure,systems, management practices, work climate, task requirements, individualneeds and values, motivation, and individual and organizational performance.

This is adiagnostic about organizational design and conditions, not about people orblame. Challenging work cultures, stalled initiatives, and repeatedtransformation failures rarely come from individuals underperforming — theycome from misalignment between leadership, strategy, structure, and the systemspeople work inside. The diagnostic surfaces where that misalignment sits andwhat needs to change before the next transformation starts.

The engagementproduces a written diagnostic report mapping each Burke–Litwin factor to itscurrent state, identifying the transformational factors (leadership, mission,culture) and transactional factors (structure, systems, practices) most likelyto obstruct change, and recommending targeted interventions. It is not aculture survey, an employee engagement study, or an HR exercise. It is anorganizational design diagnostic for executives commissioning major change.

What is delivered
  • ✅ Structured executive interviews across leadership,strategy, structure, and operations
  • ✅ Burke–Litwin twelve-factor assessment of organizationalperformance and change readiness
  • ✅ Distinction between transformational drivers(leadership, mission, culture) and transactional enablers (structure, systems,practices)
  • ✅ Misalignment map showing where organizational design will obstruct planned change
  • ✅ Written diagnostic report with prioritized interventions
  • ✅ Optional: executive readout, leadership team workshop,and integration plan with Engagement 01
Typical EngagementScoped after intake — typically 4–8 weeksdepending on organizational scale and executive availability
FormatRemote with optional on-site
OutputDiagnostic report + intervention roadmap

Best for: CIOs and transformation leads commissioningmajor cloud, security, or operating-model change who suspect — or have alreadyexperienced — that the obstacle is organizational design, not programexecution. Recommended before Engagement 01 when the organization has stalledon previous transformations or when leadership alignment, culture, or structureare likely to constrain delivery.

Ready to discuss your program?

Start with a discovery call. We’ll identify the right service for your delivery situation.