Enterprise Knowledge Architecture · AI Readiness · Content Systems
Your knowledge problem is not a writing problem. It is a systems problem.
Fragmented documentation, failed AI retrieval, and tribal knowledge that leaves with every departing employee are symptoms of missing architecture — not missing writers. I design the systems that fix that.
Senior-level enterprise experience — financial services, large-scale technology, 11,000+ employees served
The business case
Your teams are paying for broken knowledge systems every day.
Every hour spent searching for the right answer, every AI tool that returns outdated content, every new hire who cannot find what they need — these are measurable costs. They trace back to the same root cause: no governing architecture. Here is what changes when that is fixed.
Reduced Time-to-Information
When content is structured and findable, employees stop depending on colleagues to locate basic answers. Faster access means fewer delays, fewer escalations, and less duplicated effort.
Content That Stays Reliable
Without governance, content drifts. Policies conflict. Outdated procedures circulate alongside current ones. A structured, metadata-driven architecture eliminates that drift and keeps content trustworthy at scale.
AI Retrieval That Actually Works
Most enterprise AI implementations underperform because the content feeding them was never designed for machine retrieval. I build systems structured for LLMs and RAG from the ground up — not adapted after deployment.
Knowledge Infrastructure That Scales
Growth, mergers, and team changes do not have to reset your knowledge base. A well-designed architecture absorbs organizational change without requiring a rebuild. You scale the content, not the chaos.
Legacy Knowledge Made Usable
Decades of policy, process, and institutional knowledge buried in outdated formats can be restructured into a single, searchable, AI-ready content library. What was a liability becomes an asset.
Governance Without the Bottleneck
Content governance fails when it creates more process than it prevents risk. I design oversight models that enforce quality and accuracy standards without slowing down the teams who need to create and update content.
How I engage
Structured engagements. Defined outcomes. No ambiguity about what you get.
I work with a limited number of organizations at a time. Each engagement is scoped around a specific business problem — not a general retainer. If your challenge maps to one of these, we should talk.
Knowledge System Audit
You have a knowledge problem but are not sure where it starts. This engagement maps your current content ecosystem, identifies structural gaps, duplication, and AI readiness blockers, and gives you a prioritized path forward.
Deliverable: Gap analysis & prioritized roadmapContent Architecture Design
Your content exists but has no unifying structure. This engagement produces a complete knowledge architecture: taxonomy, metadata schema, content types, governance model, and lifecycle framework.
Deliverable: Architecture blueprint & governance modelAI Readiness Transformation
Your AI tools are deployed but underperforming. In most cases the problem is the content feeding them, not the model. This engagement restructures your knowledge assets for reliable LLM and RAG consumption.
Deliverable: Structured content system + AI readiness reportLegacy Documentation Modernization
Years of policy, process, and institutional knowledge in formats no modern system can use effectively. This engagement migrates that content into a structured, stateless model suitable for search and AI retrieval.
Deliverable: Migrated, structured content libraryEmbedded Strategic Advisory
Your team is navigating a knowledge transformation and needs senior-level guidance without a full-time hire. I embed as a strategic partner for a defined period, providing architectural direction and implementation oversight.
Deliverable: Strategic guidance + implementation supportContent Production Modernization
Your content creation process is too slow, too inconsistent, or too dependent on individuals. This engagement redesigns the workflow with AI-assisted pipelines, editorial standards, and quality checkpoints.
Deliverable: Workflow redesign + tooling recommendationsNot sure which engagement fits?
A 30-minute scoping call is usually enough to identify the right starting point. There is no obligation to proceed, and you will leave with a clearer picture of the problem regardless.
Speaking & events
Bringing knowledge architecture to your audience
I speak to enterprise leadership teams, industry conferences, and professional groups on the practical side of knowledge systems, AI readiness, and organizational information strategy. These are not abstract talks — they are grounded in real implementation experience.
The Future of Enterprise Knowledge Systems
Why most organizations are unprepared for AI adoption and what redesigning information architecture actually requires
From Documentation Chaos to Scalable Knowledge
A practical framework for moving legacy content into structured, AI-ready systems without losing institutional history
AI Readiness Starts With Content Architecture
The reason most enterprise AI tools underperform — and why fixing the knowledge layer is the only reliable solution
Stateless Content Design for the Modern Enterprise
How modular, context-independent content architecture eliminates duplication, reduces maintenance burden, and improves retrieval accuracy
What I actually do
Most knowledge problems are not writing problems.
They are architecture problems.
When documentation is inconsistent, it is usually not because the writing was poor. It is because there was no content model, no taxonomy, no governance layer — nothing that tells the organization how knowledge should be structured, owned, updated, or retired.
When AI tools fail to retrieve accurate answers, it is rarely a model problem. It is a content architecture problem. The information exists somewhere, but it was never structured to be found reliably.
I design the systems that make knowledge usable — at scale, over time, across teams, and by machines. I work at the level where those architectural decisions are made, partnering with Directors, VPs, and operational leaders before a single piece of content is written or migrated.
The examples on this site demonstrate what that looks like in practice. They are outputs of a system designed to produce them. The system is what I build. If you need someone to produce documents, I am not the right fit. If you need someone to design the infrastructure that makes your knowledge work — let’s talk.
Not this
A contractor who writes content, delivers files, and moves on
This
A senior operator who designs the architecture, governs the system, and is accountable for whether organizational knowledge actually works
Operating level
Director / Senior Manager / Principal — setting direction alongside executive leadership, not executing tasks handed down from it
Typical scope
Enterprise knowledge transformation, AI content readiness, legacy modernization, post-merger knowledge integration, cross-functional content strategy
Two ways to engage
Know what you need? Here is how to move forward.
Whether you are building a team or solving a specific problem, the starting point is the same: a direct conversation.
Full-time roles
Building a knowledge or AI content team?
I am open to Director, Senior Manager, and Principal-level roles where the work centers on knowledge architecture, AI content strategy, or enterprise content systems. I bring both the strategic vision and the operational experience to build and lead at that level.
Remote preferred / Relevant titles: Director of Knowledge Management, Head of Content Architecture, Principal Knowledge Strategist, AI Enablement Lead
Project-based work
Facing a specific knowledge or AI challenge?
I take a limited number of consulting engagements at a time to ensure the work gets the attention it requires. If your organization is dealing with a broken knowledge system, an AI readiness gap, or a documentation crisis following growth or a merger — a scoping conversation is the right first step.
Typical engagements: 4 – 16 weeks / Most begin with a bounded audit or assessment
If the problem is real, the conversation is worth having.
Most organizations already know something is wrong with how their knowledge works. The question is whether the cost of fixing it is higher than the cost of leaving it broken. That is usually the right place to start.