Pattern: Gradual Onboarding

One to three months before the new platform goes live, begin training a couple of teams at a time with a pause between each cohort to incorporate feedback and improve the process/materials

Gradual Onboarding

There is pressure from the top, the executives and board, to start using the cloud native platform as soon as possible and pressure from below, from the development teams, to move to cool technology. The company spent a lot of time and money building the new system, and everyone is eager to reap the rewards. Developers want to learn and use new technology.

In This Context

Onboarding too many teams at once will stress the Core Team and reduce its ability to continue improving the platform. Educating people too early, however, willcreate anxiety in the teams and desire to start as soon as possible (and frustration if there is a long wait before the new system is available).


Start small organizational changes early in the cloud native transformation. Prepare materials to onboard other teams and execute it slowly when teams are ready.Continue onboarding the rest of the organization gradually over a period of 3 to 12 months.


The Core Team can support teams as they onboard and improve the process as they go. The first few teams onboarded to the platform can help educate and support the teams onboarded later.