Enterprise Learning Architecture: Creating an Organization-Wide eLearning System

Research and Discovery

Before storyboarding any content, I partnered with stakeholders and business leaders to conduct a workflow audit: reviewing existing course assets, interviewing cross-functional team members, and mapping the current instructional development process end-to-end.

Key findings:

• No Unified Standards: The organization lacked a shared "source of truth" or unified asset library for how an eLearning module should look, feel, or be structured. Each instructional designer and facilitator had developed personal conventions that weren't documented or easily transferable.

• Accessibility Bottlenecks: WCAG compliance was a stated value, but it wasn't systematically built into the development process. Accessibility decisions were being made case-by-case.

• Wasted Capacity: The time spent on formatting and resolving visual inconsistencies across modules was consuming a disproportionate share of capacity—time that should have been spent partnering with SMEs to define performance needs and write strong behavioral outcomes.

Strategy: Two Tracks, One Deliverable

Rather than building the framework first and the course second, I ran both tracks in parallel. Every instructional design decision made for the flagship course also became a decision about the organization's new enterprise standard.

Track 1: The Flagship Professional Learning Program

The course needed to teach Universal Design for Learning to an audience of adult learners who ranged widely in their prior knowledge and tech comfort. A course about UDL needed to embody UDL. That meant developing multi-modal learning solutions: multiple means of representation, flexible pathways through the content, and assessments that measured genuine behavioral understanding rather than simple recall.

Visually, the course used a brand-aligned, clean, high-contrast design system. Every interactive element was keyboard-navigable, and accessible color combinations strictly met WCAG 2.1 AA contrast ratios. Alt text was applied systematically. The visual design wasn't just aesthetically considered; it was structurally accessible.

Track 2: The eLearning Design System

The system I built alongside the course served to raise the bar across the entire L&D team. It had three components:

• Component Library: A set of reusable, WCAG-aligned instructional building blocks (text + image layouts, scenario structures, knowledge checks, and interactive patterns). Each component was documented with usage guidelines outlining how it connects to learning objectives. I created a Canvas Course Template to be copied and edited for future courses, including a "designer/instructor-view only" module containing all approved design assets.

• Development Workflow: A standardized process map from SME content intake to final QA, with defined handoff points. This served as a single source of truth for brief templates, QA checklists, and version control.

• Governance & Mentorship Documentation: A living style guide covering accessibility standards, voice and tone, and component update protocols. I actively used this documentation to share best practices and mentor junior designers, ensuring the L&D team could sustain and scale the system independently.

Key Design Decisions

• WCAG at the Component Level: Accessibility was embedded into every reusable component, shifting compliance from a cumbersome QA step to a baseline system constraint.

• Maintainability over Feature Richness: I prioritized long-term maintainability, enabling non-technical staff and facilitators to sustain and update courses independently.

• Miro for SME Collaboration: Chosen to reduce cross-functional friction and ensure active, seamless partnership with SMEs and business leaders during the storyboarding phase.

What the Deliverables Looked Like

• The PL eLearning Course: A multi-module Canvas course with a clean layout and clear visual hierarchy that guided learners through conceptual content, scenario-based practice, and reflection prompts. Interactive elements included accordion structures for optional depth and embedded knowledge checks with explanatory feedback.

• The Component Library: Organized by content type. Each component had a "do / don't" annotation layer. Color and contrast documentation was embedded directly in the file.

• The Development Workflow: A visual process flowchart from SME brief to launch, ensuring that all future learning solutions stay aligned with business needs.

Results

1. Successfully launched the organization's flagship learning program, unblocking an initiative that had been stalled due to infrastructure gaps.

2. Established a reference architecture now used for all subsequent multi-modal course development across the enterprise.

3. ~70% reduction in development time for future courses using the new design system.

4. 80% improvement in instructional consistency across their learning portfolio.

Key Takeaways

1. The system is the deliverable: The highest impact was not just the single course, but the scalable infrastructure that enabled all future multi-modal learning solutions.

2. Accessibility only scales when it is embedded: Moving WCAG compliance into the component layer eliminated downstream rework and ensured all learning products were clean and accessible by design.

3. Design for continuity, not just delivery: Every decision prioritized maintainability and clarity for the L&D teams and facilitators who would inherit the system later.