Role lenses

0:00Welcome to this explainer. I am absolutely thrilled to have you here today. We're going to unpack a really fascinating challenge in enterprise software, which is housing multiple distinct enterprise roles inside a single Production Console without it turning into total chaos. If you've ever tried to force different cross-functional teams to use the exact same system, you know exactly what I'm talking about. So, let's look at how Knowledge Foundry handles this elegantly using something they call role lenses.

0:27Okay, let's dive into this. When an organization buys a learning platform, they are bringing together very different groups, right? You've got your producers, reviewers, HR, L&D, and leadership. And usually, you face a massive dilemma. If you buy a completely separate tool for each group, your handoffs just break down completely. It's a mess. But actually, if you try the opposite approach and give everyone the exact same undifferentiated wall of features, well, adoption completely stalls out because the interface is just way too cluttered for anyone to actually use efficiently. Which brings us to the core question of our explainer today. How do mixed teams share a platform without fighting over the UI?

1:07The outcome-oriented solution to this problem is what Knowledge Foundry calls role lenses. Instead of building five totally different products, you create different emphases. Think of it like giving everyone a different front door, perfectly tailored just for them, but it leads right into the exact same building. Because underneath those personalized views, the entire organization relies on one unified, constant operating cycle. You produce programs, you assure their release, you keep evidence of that design and governance, and finally, you measure the transfer.

1:38This backbone literally never changes, no matter who happens to be logging in. This exact shared lifecycle completely drives the user experience. The home screen actually organizes the work into shared shelves, building, awaiting publish, editing live, and live. Since everyone is looking at the same underlying cycle, this portfolio vocabulary remains identical across the board. It acts as a permanent common ground, proving for sure that you can have different perspectives without losing that shared truth. So let's break down the individual spokes of this shared hub.

2:10First up, the operator and producer lens. Build and refine. When an enterprise operator or producer logs into the Console, they aren't hit with a mess of irrelevant analytics or heavy administrative tools. Instead, they land directly at their key destinations, the Studio and the creator. This drops them right into the work they actually care about, which is turning documents into concrete learning programs. This lens is strictly focused on the outcome of building and refining. Producers can effortlessly turn those documents into programs, jump into the creator to execute really precise fixes, and then seamlessly return that work right back to review. Basically, they get in, they do their specific job, and they move the work along the cycle without having to navigate past a dozen features they just don't need. Moving on to our next role perspective, the assurance lens. Review and sign off. Now what's really interesting about this slide is how the emphasis changes for assurance-minded roles.

3:05For someone responsible for signing off on a program, they land immediately toward the review destination. They completely bypass all those builder tools the producers were just using because, well, they simply do not need them to do their job. And when it's time for oversight, assurance roles can just seamlessly move from review right into audit to find the required evidence of design and governance. It's a super quick shift, providing exactly what compliance-minded stakeholders require without ever forcing them into a deep dive of complex administrative or technical setups.

3:38Let's transition to our third and final role perspective, the HR and L&D lens, focusing on uptake and operations. The folks accountable for platform adoption and learning outcomes have a very different set of priorities. So when HR and L&D leaders log in, they land specifically on learning and oversight. Once again, no getting bogged down by production tools or those detailed assurance workflows. This specific lens allows them to focus purely on their distinct goals, tracking cohort progress, measuring engagement, and monitoring operational activity after a program actually goes live.

4:11And here's the kicker. While they are looking at these metrics, they are viewing the exact same underlying portfolio as the producers and the reviewers. Now that we've seen the individual lenses in action, let's pull back from those spokes and look at the shared hub. One console, shared success... Role lenses are absolutely not separate products. Deploying separate products inherently creates shadow processes and data silos, which we definitely want to avoid.

4:37Role lenses instead are simply different emphases on one shared picture. It is one console, ensuring nobody needs to build a parallel shadow process just to get their own specific view. Let's return to this shared backbone one last time to really cement this idea. Produce. Assure. Evidence. Measure. Cross-functional teams only actually adopt a platform when this underlying truth connects everyone effortlessly. When the operator building the program and the L&D leader measuring its success are working from the exact same shared lifecycle, internal socialization across functions goes from being a total nightmare to being incredibly easy.

5:15And that brings us to the ultimate measure of success for Knowledge Foundry's unified approach. Our mixed stakeholders could share one console without fighting over the UI. It is just a brilliant way to ensure cross-functional adoption. But it leaves us with one final provocative question for your own organization. If you stopped building parallel systems and just built a better front door, how much faster could your teams finally move?

5:35Thanks so much for joining me for this explainer.