1. Tradition and momentum favored learning domains focused on a single AWS service or a group of tightly related technologies, such as databases.
2. Efficiency measuring was biased toward simpler domains, faster to turn around and required fewer SMEs.
3. Lack of knowledge that 60+% of customer IT employees are developers/engineers, e.g. builders.
4. Data was missing about customer interests and desires, favoring existing CSAT and sales data which was readily available.
5. New senior leadership was unfamiliar with technical education, trying to apply retail (reseller) logic to LD (learning development) domain without necessary context.

APPROACH

To address these challenges, I focused on ...:

1. Spoke with Harley, Nabeel, about the builder experience; gaps in training, customer feedback from their customers.
2. Identified overlaps where very similar content was produced from scratch in solos, an opportunity to reduce redundant effort.
3. Outlined the learning journey for a full-cloud builder, from ideation, architecture, development, DevOps, and CloudOps. Mapped these to existing & planned curricula.

Approach closing statmeent.

EXECUTION

I led the team through ...:

1. Mapping Solutions Architecture, Developing, DevOps, and CloudOps curricula into a linear model. Collaborated with PdMs of SA and CO by getting materials from them.
2. Marked overlaps where similar/identical content was presented in modules, sections, chapters, other divisions in online and classroom courses.
3. Identified where level of difficulty varied between roles for same topics. Dive deeper into networking for architects than others.

Exec closing statmeent.

RESULTS

Projected savings included:

1. Time
2. Cost
3. # of SME resources required from outside T&C
4. Ongoing maintenance.
5. Requirements and diagram of proposed content sharing platform to automate after POC.
6. Streamlining
7. Cross-functional cost savings

Improved time to market with new and updated courses, more consistent user experience, lower costs and faster TTM.

LESSONS and TAKEAWAYS

1. Even more cross-functional than typical because of impact on instructors preparation, release teams, marketing teams, ...
2. Dependencies were difficult to find because previous siloed approached did not require knolwedge. However, this also contributed to poor and inconsistent user experiences.
3. In software terms, this proposal introduced some "tight coupling" between previously independent courses, requiring metadata and systems to read such to make it all efficient.