Most organisations now hold more data about multi-cloud architecture adoption than they can actually act on. The constraint on this area of digital and data-driven work is rarely the model or the platform — it is the data and the operating discipline behind it. Cases are chosen to expose the trade-offs in the practice within digital and data-driven work rather than to illustrate ideal conditions. The content is relevant to those who own multi-cloud architecture adoption and to those who are held accountable for its results. It treats this part of digital and data-driven work as an operating discipline and equips participants to run it as one. Buying a tool rarely fixes this strand of digital and data-driven work; the underlying capability has to be built internally first. Participants take away a working set of documents supporting multi-cloud architecture adoption, ready to be adapted internally. Mature organisations treat this area of digital and data-driven work as a standing capability rather than a project that finishes. The closing exercise tests whether the participant's plan for the wider digital and data-driven work agenda survives a hostile question.
Expected Learning Outcomes
✓
Agree the retirement plan for the legacy process multi-cloud architecture adoption replaces.
✓
Review contracts and agreements for the obligations they create around multi-cloud architecture adoption.
✓
Quantify the running cost of multi-cloud architecture adoption — compute, licensing, and the people who keep it alive.
✓
Sequence improvements to multi-cloud architecture adoption so that each step makes the next one easier.
✓
Draw practical lessons from failures in multi-cloud architecture adoption without assigning blame that suppresses reporting.
✓
Map the regulatory obligations that apply to multi-cloud architecture adoption in each market of operation.
✓
Define escalation and fallback for multi-cloud architecture adoption when the automated path fails.
Who Should Attend
✓
Coordinators responsible for keeping records and documentation of multi-cloud architecture adoption current.
✓
Data and analytics leads responsible for the pipelines behind multi-cloud architecture adoption.
✓
Programme managers coordinating delivery of multi-cloud architecture adoption across teams.
✓
Technology and digital transformation managers leading multi-cloud architecture adoption.
✓
Operations managers whose processes are changed by multi-cloud architecture adoption.
✓
Newly appointed managers taking on multi-cloud architecture adoption for the first time.
Course Modules
Open any module to see its sessions and topics.
01
Multi-cloud architecture adoption: monitoring, drift and operational ownership
2 sessions · 8 points
Session 1Where multi-cloud architecture adoption touches systems nobody wants to change
Distinguish symptoms from causes when multi-cloud architecture adoption underperforms.
Specify the fallback path when multi-cloud architecture adoption is unavailable.
Assess the regulatory obligations multi-cloud architecture adoption triggers in each jurisdiction.
Classify the data in multi-cloud architecture adoption and apply access controls that match the classification.
Session 2Choosing a supplier for multi-cloud architecture adoption without being captured
Agree the indicators that will show whether multi-cloud architecture adoption is improving.
Set the metrics that will show whether multi-cloud architecture adoption is drifting from its intended behaviour.
Reduce the variation in how multi-cloud architecture adoption is carried out between teams.
Measure the current quality of the data feeding multi-cloud architecture adoption before assuming it is usable.
02
Multi-cloud architecture adoption: people, skills and the change that follows
2 sessions · 8 points
Session 1Explaining multi-cloud architecture adoption to people whose jobs it changes
Estimate the resource multi-cloud architecture adoption requires to run as designed.
Record what was learned when multi-cloud architecture adoption did not go as planned.
Decide which legacy process multi-cloud architecture adoption retires, and set the date.
Design the pilot for multi-cloud architecture adoption so that a negative result is still useful.
Session 2The hard cases in multi-cloud architecture adoption and how to reason about them
Remove steps in multi-cloud architecture adoption that add effort without adding assurance.
Build the user briefing that explains what multi-cloud architecture adoption does and does not decide.
Test multi-cloud architecture adoption against edge cases drawn from real historical records.
Define the service level multi-cloud architecture adoption must meet and what happens when it is missed.
03
Multi-cloud architecture adoption: measuring benefit and retiring what it replaces
2 sessions · 8 points
Session 1Testing multi-cloud architecture adoption before relying on it
Rank the weaknesses in multi-cloud architecture adoption by consequence rather than by ease of fixing.
Estimate compute and licensing cost for multi-cloud architecture adoption at expected and at peak load.
Compare the cost of multi-cloud architecture adoption with the cost of its absence.
Plan how multi-cloud architecture adoption is versioned and how a bad release is rolled back.
Session 2Building lasting competence in multi-cloud architecture adoption
Identify where judgement in multi-cloud architecture adoption is legitimate and where it is not.
Map the handovers in multi-cloud architecture adoption between functions and secure them.
Confirm the retention and deletion rules applied to data inside multi-cloud architecture adoption.
Build the competence framework that supports multi-cloud architecture adoption.
04
Multi-cloud architecture adoption: business case, scope and the data it depends on
2 sessions · 8 points
Session 1The governance multi-cloud architecture adoption needs and the governance it does not
Verify that multi-cloud architecture adoption still performs when input volume doubles unexpectedly.
Check that records of multi-cloud architecture adoption answer the questions likely to be asked.
Identify the skills the team lacks to operate multi-cloud architecture adoption independently.
Confirm that contractual obligations around multi-cloud architecture adoption are understood.
Session 2The pilot that actually settles the argument about multi-cloud architecture adoption
Define acceptance criteria for multi-cloud architecture adoption in advance.
Agree who is on call for multi-cloud architecture adoption outside working hours.
Check that multi-cloud architecture adoption still works when volumes rise unexpectedly.
Anticipate the objections multi-cloud architecture adoption will raise and prepare the answers.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
Workshop or Program Participation
Airport Transfers
Customized Badge
Expert Mentorship (Private Sessions)
Supervision & Secretarial Services
Accredited Certificate of Participation
Complete Training Kit
Coffee Break
Closing Ceremony
Gold Package
At least 3 people
USD1,850
5-night stay in a 5-star hotel
Workshop or Program Participation
Airport Transfers
Customized Badge
Expert Mentorship (Private Sessions)
Supervision & Secretarial Services
Accredited Certificate of Participation
Complete Training Kit
Coffee Break
Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.
