National University

Building Confidence, Judgment, and Responsible AI Use

The decision to prioritize responsible AI capability came from an early realization—access to an AI tool does not automatically translate into effective use. Employees may have access, but that does not mean they know when to use it, how to evaluate it, or how to apply it effectively.

That insight shifted my focus. The real opportunity was not just introducing a tool but creating an effective user experience that gives employees real-time access to relevant resources while also building the confidence and judgment needed to use AI responsibly.

From a learning and development perspective, it shifted the focus from training on features to applying the tool in the flow of work. Responsible AI capability means employees understand where AI adds value, where human judgment is required, and how to use the tool to improve decision-making and efficiency.

Building that kind of effective user experience also requires a clear understanding of what actually creates confidence. Employees need direct experience with AI in realworld situations. Confidence comes from applying, testing, and understanding how it performs.

In my experience, confidence and utilization are closely connected. When trust increases, adoption follows. Focus is also critical; employees build confidence faster when AI is tied to a high-impact use case supported by reliable data.

Finally, expectations must remain clear. AI should support decision-making, not replace it. Employees still need to interpret information, verify accuracy, and determine the best course of action. That is where sound judgment becomes essential.

Why Implementation is Only the Beginning

One of the biggest lessons we learned was the value of pilot testing. Pilots create the opportunity to evaluate how the tool performs, how employees experience it, and whether it supports the intended operational goals.

What we learned was important. While employees recognized the potential, our confidence scores were lower than expected, directly impacting utilization.

“ Responsible AI capability is not built by scaling quickly; it is built through piloting, learning, refining, and improving the experience until confidence and utilization move together. “

Those results led us to conduct a performance analysis. Instead of adding more data sources, we stepped back to evaluate where the tool could have the greatest impact. We decided to focus first on the most valuable and reliable data source rather than attempting to implement everything at once.

That shift improved the user experience, strengthened trust, and created a more stable foundation for future expansion. Responsible AI capability is not built by scaling quickly; it is built through piloting, learning, refining, and improving the experience until confidence and utilization move together. That is what ultimately drives operational effectiveness.

One of the biggest challenges in moving from implementation to sustainable capacity building is assuming that implementation equals success. Deploying a tool is only the beginning. The harder work is ensuring employees find the experience useful, trust the information, and apply it effectively in their work.

Another challenge is scaling before trust has been established. When organizations introduce too many use cases or data sources too early, the experience often becomes inconsistent.

Organizations also tend to focus too heavily on access rather than performance outcomes. The more important questions are whether employees find value, whether they trust the responses, and whether the tool improves efficiency and effectiveness. Those are the indicators of sustainable capability.

In my view, sustainable capability-building requires more discipline than speed. It takes pilot testing, performance analysis, and a willingness to refine the experience based on employee feedback and operational results.

Start With Experience, Not Technology

My advice to the learning and development leaders would be to start with the experience you want employees to have, not simply the technology you want to deploy. If the goal is to help employees access information in real time, then the experience must feel useful, relevant, and trustworthy from the beginning.

I would also strongly encourage leaders to pilot before scaling. Pilots provide insight into how employees are using the tool, where confidence is strong or weak, and what is driving utilization. That feedback helps inform decisions before expanding.

It is equally important to start with the highest-impact use case first. Beginning with a strong data source and a clearly defined problem creates a better experience and helps establish trust faster.

Most importantly, leaders should keep trust, confidence, and utilization at the center of their strategy. When utilization increases and employees see meaningful value in their work, organizations begin to realize measurable gains in efficiency, effectiveness, and long-term capability.