Knowledge-management operating model & KNOCK
Built the knowledge-management operating model and the KNOCK toolset from scratch across eight Operations & Technology groups and 38 subgroups at Versant Media — discovery, structure, governed migration, and an AI agent for the steady state.
- 01
Discover & structure
Made a complex org legible
Resolved an unconventional media-tech structure into a verified map of teams, functions, and champions, and cleaned up the shared sites that had drifted into disorder — roughly two working sessions per team.
- 02
Assess
Designed the Lumi readiness model
A five-stage scale, Dreaming to Exemplary, that made every team’s progress toward a governed knowledge state visible at a glance and gave the program a shared language.
- 03
Migrate
A governed move, not a free-for-all
An AI-assisted inventory of each site (metadata only), reviewed and approved by the team’s own champions, then an automated relocation of every asset to its right home. Piloted end to end on my own team.
- 04
Operate
Built KNOCK for the steady state
An AI agent that lets anyone create or update knowledge in the right shape: it enforces the fields that matter, routes the draft for approval, and files it in an access-controlled, governed library — and it never fills in what it hasn’t been told.
- Dreaming
- Collecting
- Organizing
- Ready
- Exemplary
Built end to end and piloted the full cycle on my own team's knowledge.
I was preparing the other groups for the same steps — and building out the dashboards and metrics — when the project was deprioritized. Versant still runs the system. The problem it kept surfacing is what led me to build All Clear, a commercial product that solves it in a more sophisticated way.
The build A governance register, a champions model, the Lumi framework, an AI scanning and migration workflow, and the KNOCK agent — plus the Slack and intake structure that kept eight groups moving in parallel. Happy to walk through any of it.
Change-management workflow redesign
A Microsoft 365 change-intake workflow built during a global SAP S/4HANA finance transformation — replacing an untracked, email-driven process with one that was fast and traceable end to end.
Before — legacy state
- 01Requests submitted ad hoc by email
- 02Manual routing across multiple owners
- 03Required fields and attachments missing or inconsistent
- 04No status visibility for requestors
- 05No traceable record from request to close-out
After — redesigned flow
- 01Standardized intake form — required fields and attachments enforced
- 02Forms, email, SharePoint, Lists, and Planner connected into one flow
- 03Role-based routing with notifications and clear disposition
- 04Every request tracked from submission to close-out
Designed and configured end to end — from process discovery through rollout.
The workflow replaced fragmented email coordination with a governed, traceable process across 10–15 requests a day.
Start with what's stuck