Hi everyone,
With the rollout of Docebo Companion, it feels like we're finally making the jump from "destination learning" (expecting users to stop everything and log into the LMS) to true performance support in the flow of work.
Technically turning it on is one thing, but I've been thinking a lot about what this means for our day-to-day L&D operations. Suddenly, the traditional 30-minute SCORM package doesn't make sense for a rep trying to close a ticket in Salesforce.
I’d love to hear how you are all preparing your teams and your architecture for this shift:
-
Instructional Design Shift: How are your IDs adapting? Are you breaking down existing courses into micro-assets? Focusing more on searchable text and checklists rather than heavy modules?
-
Metadata & Curation: Since Companion relies heavily on context and search, are you doing a massive cleanup of tags, categories, and metadata to make sure the AI/search surfaces the right answers?
-
Looking Ahead to MCP: This is the part that really fascinates me. With the rise of the Model Context Protocol (MCP), are any of you planning (or hoping) to expose your Docebo knowledge base so that internal AI agents can securely pull LMS data and procedures directly into other workflows?
Would love to hear your thoughts, strategies, or even the roadblocks you're anticipating. How is your team making the LMS "invisible" but more relevant than ever?