A focused solution
From SharePoint sprawl to institutional memory
You know this feeling
- The answer exists somewhere: a drive, a channel, an inbox, or one veteran employee's memory, and finding it takes longer than redoing the work
- Three versions of the same document live in four places, and nobody is sure which one is current
- Every departure takes institutional knowledge with it, and every onboarding takes months longer than it should
- SharePoint keeps growing, but findability keeps shrinking
How I approach it
The fix is upstream of the software
A pile of documents is not memory; it is a haystack. I start with a knowledge audit, not a tool: what does the organization know, where does it live, and what is high-consequence and single-person. Then I build the architecture: a taxonomy that matches how your people actually think, documentation systems with owners and rhythms, digital workspaces designed for the moment of need, and playbooks as the unit of memory. The result is knowledge that survives turnover and compounds instead of evaporating.
- Knowledge management strategy, information architecture and taxonomy, and SharePoint and digital workspace design are core capabilities of the practice
- Reusable playbooks and toolkits so capability stays with your team instead of leaving with people
- Discovery and synthesis methods that turn scattered stakeholder knowledge into themes, risks, and prioritized recommendations traceable to evidence
- AI knowledge systems where they genuinely help, built on an architecture that makes them trustworthy
Questions
What people ask first
Is this a SharePoint migration project?
Sometimes it includes one, but the migration is the last step, not the first. Moving a mess to a new address produces a newer mess. The architecture, taxonomy, and ownership design come first; then whatever platform you use starts working.
Our knowledge lives in people, not documents. Can this still work?
That is the most common starting point, and the most urgent one. The practice's methods are built for exactly this: structured capture from the people who hold the knowledge, turned into durable, findable, owned documentation before it walks out the door.
How do engagements usually start?
With the Systems and Automation Audit: two weeks, a map of how knowledge actually flows and where it stalls, your three highest-value fixes, and a prioritized plan you keep either way. If we continue into a retainer, the audit fee credits toward your first month.
Does this work for regulated industries?
Yes. Finance, energy, healthcare, and government-funded organizations have the most expensive version of this problem, because findability failures become compliance findings. Audit readiness is a core practice area.
How this starts
Start with the audit
Two weeks. Your three highest-value fixes. A plan you keep either way. Investment is shaped to your context and shared in conversation. The audit is a fixed fee that credits toward your first retainer month.