It’s Dangerous to Go Alone! Lessons Learnt from Onboarding New Cloud...
summary
A one-week Onboarding Week ritual gives new cloud platform engineers a hands-on backlog of deploy tasks, daily standups, whiteboard architecture sessions and retrospectives so novices ramp visibly faster than before 2016. Pair programming, dedicated facilitators, monthly cadence and seating onboardees together create psychological safety and cross-discipline feedback. Materials live in GitHub and sync to Pivotal Tracker; the process uses a CI/CD for onboarding loop so changes are shipped via PRs. Outcome: measurable faster productivity, better cross-team orientation, and broader facilitator participation.
AI-written summary · about
chapters (9)
- 0:00Welcome and introduction
- 1:03Framing the talk
- 2:05Brief history of onboarding
- 3:50North star goals
- 7:22Onboarding week structure
- 11:15Tools and processes
- 13:03Culture and empathy
- 15:35Lessons learned
- 17:44Closing and Q&A
related talks
06mEffective Onboarding: From Zero to Full Speed
28mTechnical Onboarding, Training, and Mentoring
22mHumanising Onboarding: Helping New Team Members Find their Feet in the World...
24mElevating Young Developers: Best practices for seasoned developers on onboardings
21mHow to quickly get engineers up to speed
32mHow to Be Well Onboarded as a Junior Developer Who Retrained
28mTechnical Onboarding, Training, and Mentoring
36mHow To Onboard New Hires Into Happy and Productive Employees