The Architect, The Banker, and The User

In most organizations, KM doesn’t fail because the platform is wrong. KM fails because leadership treats “knowledge-sharing” as a value statement instead of a management practice. Enterprise KM becomes real only when the C-suite moves from approval to participation…when they start actively designing the narrative, funding the work, protecting the practice, and showing up inside the system.

A senior leader’s first job in KM is sense-making. KM has to stop sounding like an “initiative” and start acting like a strategy. Leaders create the context that orients the organization’s attention, and that translates into what it preserves, what it reuses, and what it chooses to forget.

That’s why the commitment isn’t “encourage sharing.” It’s to learn to speak KM as part of the business story, personally, credibly, and repeatedly. Leaders who can give the KM presentation themselves without delegating the narrative to a program office forcefully demonstrate that knowledge is not a side job, extra work, or an unrewarded project. Regular communication about KM in the channels people actually notice (town halls, leadership updates, operating reviews) turns KM from background noise into a management expectation.

This also has an operational expression: KM belongs on the leadership agenda. When KM becomes a standing topic: knowledge gaps, reuse wins, community signals, emerging lessons, ties to revenue and cost savings, then the organization learns that knowing is part of executing well.

Strategy without resources is cosplay. KM needs a budget that matches the ambition: infrastructure, tooling, community enablement, facilitation, and the unglamorous work of curation and stewardship. Approving a reasonable budget is not generosity; it is the price of admission.

Time matters even more than money. KM leaders can’t lead KM “after the real work.” If leaders aren’t empowered to share and learn, the program suffocates under meetings, delivery pressure, and a thousand urgent priorities. The same is true for everyone else: if the organization doesn’t protect time for sharing, innovating, reusing, collaborating, and learning, KM becomes performative. Leaders build KM capacity by protecting slack, real calendar space, so reflection and reuse can occur without penalty.

KM requires policy and practice, space and technology, the levers of culture, to accept it, permit it and facilitate it. People won’t share what they suspect will be weaponized, and they won’t admit lessons learned if lessons are treated as confessionals. Senior leaders set the tone: psychological safety can’t just be a slogan, or even a policy; it must be a living practice that gets rewarded.

Protection has two concrete faces: accountability and recognition. KM behaviors can’t be optional virtues. Leaders embed KM goals into performance expectations for all employees, then inspect them the way other goals are inspected. When leaders track revenue goals rigorously but treat knowledge goals as aspirational, the organization learns what matters.

Reward closes the loop. Leaders advocate for the people who share, reuse, mentor, and improve the commons. Public and private recognition teach faster than policy. Incentives don’t need to be extravagant, but they do need to be consistent and visible.

KM platforms become meaningful when executives behave like users, not landlords. If the top team never logs in, comments, asks questions, or posts, the platform becomes “for us,” not “for them” (leadership), which punctures the balloon of motivation.

When leaders use the KM system to run work, like asking questions in a forum, pointing to reusable assets, commenting on drafts, and acknowledging contributions, the participation of others follows.

This is not “being social,” it’s being observable. Leaders who show up inside the knowledge environment normalize the behavior they want: curiosity, transparency, and reuse over reinvention. They recognize learning as an asset and not a cost.

Leadership only earns the title of architect, banker, and user of knowledge when it stops admiring KM from the balcony and starts working in the commons: showing up in the system, spending real time and budget, asking questions in public, and giving direct reports time, respect and acknolwedgement for their knowledge-realated activities, which ultimately results in the organization treating stories, lessons, and reusable assets as core infrastructure.

I didn’t integrate KM into this analysis. All of the points made in the main post apply regardless of whether AI is used or not. The role of leadership doesn’t change, regardless of the tool. Should leaders encourage the safe and ethical use of AI? Of course they should. But good leaders also espouse safe working conditions in general. If they incorporate these ideas into their management practices, they can anticipate the change AI is bringing about. A good knowledge management program is not just about lessons learned and the sharing of good practice, but also about the management of learning, which is the key to accepting, naviagating and integrating change.

AI will likely transform many aspects of how an organization implements knowledge management. What won’t change is why organizations should implement KM, or the non-technological components of program success. If AI evolves in the way people think it will, toward a capability that answers questions directly, and reconfigures systems based on data, it will give people time to improve on the people, process and social capital aspects of knowledge management: areas where productivity gains can be measured in days and weeks, not just minutes.