How I think about these problems.
Writing forces me to get clear about what I actually believe.
These articles look at problems I have seen repeatedly inside organizations, why common fixes often fail, and what I think works better. They are written for people responsible for getting work done, making decisions, and living with the consequences.
Each article is published on LinkedIn.
-
Knowledge Management That Puts People First
The shared drive nobody can navigate and the AI pilot that produced a confidently wrong answer are the same problem showing up in different ways.
The article starts with a new employee opening a shared folder and realizing almost immediately that finding the right answer is going to be harder than it should be.
That is the real test of a knowledge system. Not whether documentation exists, but whether someone with no institutional memory can find the current, authoritative answer quickly enough to keep working.
If a person cannot do that, AI cannot reliably do it either. The difference is that AI will still give you an answer.
The article looks at what people-first Knowledge Management means in practice, what organizations should measure, and why the employee experience is part of the system rather than something to worry about after it is built.
-
Why Deliberate Pilot Sprints Help Leaders Say Yes
What looks like resistance to change is often a rational response to unmanaged risk.
Leaders are accountable for what happens after they approve an idea.
A broad transformation asks them to accept a long list of assumptions before they have much evidence. The issue is not a lack of ambition. It is the size of the first commitment.
Deliberate Pilot Sprints change that decision.
Deliberate reduces ambiguity. Pilot reduces exposure. Sprint creates momentum.
The article breaks down what each part means and why a contained approach can make meaningful change easier to approve, test, and expand.
-
KM Governance Without Bureaucracy
Most organizations do not have a knowledge problem. They have an ownership problem.
The article opens on a dataset in Los Angeles County that was corrected, sent, received, and filed exactly the way the process required. Nobody did anything wrong. The people downstream kept working from numbers that had already been superseded.
Compliance with a process does not mean the process works. The process never made ownership visible at the point where the data was being used.
Governance should make four things obvious: what is authoritative, who has the authority to decide, where the authoritative version lives, and how the people who rely on it know when it has changed.
The article lays out the 4x3 KM Governance Model, four roles and three review cycles, small enough that a new hire can understand it on day one. It also covers how to keep the model from becoming bureaucracy: govern according to consequence, and start with one asset that has to be right.
Recognize any of this?
If something here sounds familiar, tell me what is getting in the way and what would be different if it were fixed.
I review every inquiry personally and respond within one business day.
Clarity is what scales.