From onboarding completion to developer readiness.
A global financial-services organization needed to transform an extensive webinar-based developer onboarding program into a more focused digital learning experience.
New developers had a lot to learn — and a short time to learn it.
New developers were entering a complex financial-services environment with organization-specific development standards, tools, processes, terminology, architecture, security requirements, and technical practices to learn.
Much of that onboarding had been delivered through hours of live webinars. The organization wanted to move most of the content into digital learning while creating a more focused and scalable onboarding experience for a global developer audience.
The resulting curriculum included approximately 30 learning experiences plus checkpoints, with developers expected to move through the onboarding path in about two weeks.
How do we move new developers from completing onboarding content to becoming ready for real work?
Turn dense technical content into learning developers could navigate and apply.
I transformed recorded webinars and SME source content into more focused digital learning experiences. Depending on the content and learning need, that meant bite-sized video, interactive eLearning, practice, questions, or other supporting learning content.
The design challenge wasn't to make technical content feel less technical. It was to organize it, explain it clearly, and create opportunities for developers to engage with important concepts without losing the accuracy the work required.
Hours of webinar content and a large onboarding curriculum to complete.
Focused digital learning that helped developers understand how development gets done within the organization.
Build capability progressively, not all at once.
Developer onboarding naturally moves from foundational knowledge toward increasingly authentic work. That progression creates a useful way to think about the learning journey—not simply as a collection of courses, but as increasing capability.
Make complex technical learning easier to navigate without oversimplifying the work.
My work focused on the learning content inside the larger onboarding experience: organizing dense source material, explaining technical concepts clearly, designing practice, and connecting learning with the broader journey.
Turn webinar content into focused digital learning.
I worked from recorded webinars, presentations, and SME source material to identify the information developers needed, reorganize it for digital delivery, and create a clearer path through complex topics.
Design decision: Don't recreate the webinar online. Restructure the content around what developers need to understand and do.
Make technical concepts easier to follow without removing the complexity that matters.
Developers needed to understand organization-specific development practices, systems, standards, security requirements, and terminology. I translated SME explanations into clearer learning content while preserving the technical meaning.
Design decision: Simplify the learning experience—not the technical accuracy of the work.
Give developers opportunities to do more than consume information.
I designed interactions, questions, and learning activities that gave developers opportunities to work with important concepts and decisions throughout the onboarding experience.
Design decision: Use interaction when it helps developers think, decide, or practice—not simply to make the course feel interactive.
Interaction should support the decision or skill—not decorate the content.
Technical onboarding already carries a high cognitive load. Practice works best when the interaction helps the developer notice something important, make a decision, or apply what they have learned.
Fit the learning into a larger gamified onboarding environment.
A separate engineering team created a Unity-based journey around the onboarding experience. I designed learning content that worked within that larger structure and provided content for checkpoints and pauses in the journey.
Design decision: Maintain continuity between the learning content and the surrounding experience so the courses did not feel disconnected from the journey.
The course was one part of a larger onboarding journey.
What if completing a course didn't automatically mean a developer was ready for the next level?
The original experience already had several powerful ingredients: a Unity journey, LMS-connected learning, checkpoints, and development sandboxes. Today, I would use that foundation to connect progression more directly with demonstrated capability.
Developer Readiness Journey
Select a stage to see how developers could move from foundational learning toward increasingly authentic work.
Foundation
- Learn the development environment and terminology.
- Understand core standards and expectations.
- Become familiar with tools, systems, and security requirements.
- Complete foundational learning and checkpoints.
Can the developer demonstrate foundational understanding before moving into guided application?
The opportunity isn't to add more gamification. It's to use the journey to move developers from learning about the work to demonstrating that they're ready to do it.