If you're expecting this first journal entry to be a technical guide on configuring Docebo's advanced settings, you're going to be surprised. I didn't touch the platform configuration once during my first week at Mobileye.
Instead, I had to undergo a complete professional paradigm shift.
For years, I had managed learning platforms from within the Learning & Development (L&D) or HR departments. But at Mobileye, my role sat squarely inside Information Systems (IS). That might sound like a minor detail on an org chart, but it changes the entire DNA of how you approach an LMS implementation.
The L&D Trap
When you sit in L&D, you view the LMS as your tool. You are the primary customer. You design the platform around how the training team likes to upload SCORM files, structure catalogs, and pull completion reports. It's a very centralized, top-down approach.
But when you sit in Information Systems at a massive enterprise, the LMS is no longer just "the training team's tool." It is a piece of critical organizational infrastructure.
Suddenly, you aren't the only customer. You are the product manager of an internal platform, and you have multiple, distinct clients demanding solutions:
- Compliance & Legal: They need bulletproof audit trails and automated recertification logic that cannot fail.
- R&D and Engineering: They need a space to share training content quickly and effortlessly. Let me be clear right now (and I will dedicate a whole post to this later): an LMS is not a documentation platform, nor is it a knowledge management system (KMS). But development teams still need frictionless ways to distribute technical onboarding and rapid updates.
- External Teams & Partners: Mobileye has a massive ecosystem of external users. But strategically, we made a hard call during the mapping phase: we are not focusing on them in Phase 1. You cannot boil the ocean, and securing the internal foundation had to come first.
- L&D/HR: They still need their core onboarding tracks and leadership development programs to run smoothly.
Mapping the Terrain
Because of this shift, my first week, and honestly, the second week too, was entirely dedicated to mapping.
I couldn't just build a Docebo branch structure based on a generic HR spreadsheet. I had to deeply understand the existing legacy systems. What was working? What was universally hated? How did data actually flow from the HRIS to the endpoints?
I spent hours in discovery meetings. I wasn't asking how they wanted the menu bar to look; I was asking about their business processes. I needed to understand Mobileye's operational blueprint before I could decide how to architect Docebo to support it.
The Biggest Lesson
If there is one piece of advice I can give to anyone starting an enterprise LMS implementation, it is this: Do not configure the system for the people who manage the training. Configure it for the organization that consumes it.
By sitting in the IS department, I was forced to look at Docebo not just as a learning system, but as an architectural solution that had to serve multiple masters flawlessly.