I examine the process before building the solution. Shortcuts that skip the foundation create debt, not savings.
What I do
I work at the intersection of knowledge management, content operations, and AI adoption, disciplines that share a single problem: getting people to use what I’ve built.
Tools alone don’t change how work gets done. Workflows do. Documentation does.
The judgment to know when AI helps and when it gets in the way does. Organizations can tend to underestimate this when they start, and it often proves expensive.
.
How I think About This Work
Fifteen years in knowledge management, content operations, and technical writing taught me that systems fail at the gaps between people and tools, not at the tools themselves.
AI hasn’t changed that. It’s just raised the stakes.
I start with mapping the actual workflow — what people do, where the friction lives, what already works — to simplify tool selection downstream. Implementation follows that.
The order matters because the order is what makes the work stick.
That’s the methodology I write about here.
Credentials
– AI Operator Certified
– 15+ years in knowledge management, content operations, and technical writing
– Methodology developed across nonprofit, corporate, and small-business engagements
Let’s connect
If you’re hiring for an AI adoption or enablement role, considering a selective engagement, or want to compare notes on this work, I’d like to hear from you.
Why I put Process Before Tools
- Tools that fit your actual workflow (not generic solutions forced in)
- Training that uses your real scenarios (not abstract examples)
- Documentation your team can understand and follow
- Foundations that last