Organizational Systems Architect

I build the systems that make knowledge work.

Thirty years building the knowledge infrastructure, process frameworks, and translation systems that make complex change actually work, across technical teams, executives, and frontline workers simultaneously. In domains encountered for the first time.

Joshua Bechtel presenting on enterprise knowledge architecture

In practice

What it looks like in practice

At Capital One, I designed and executed the enterprise Microsoft Copilot rollout for 8,568 employees in the Business Technology organization. Eighty percent of them were still actively using it six months later.

That number exists because the knowledge architecture was right before the adoption program launched, not because the tool was good. I built the workflow readiness assessment, the use case prioritization framework, the governance model, the Champions network, the AI literacy curriculum, the adoption scorecards, and the measurement infrastructure that captured the retention data. All of it, end to end, as an individual contributor.

This is what knowledge infrastructure looks like when it works.

Original Methodology

Stateless Content Architecture (SCA)

A proprietary modular information design methodology for structuring organizational knowledge as typed, role-addressable fragments that can be delivered to any audience (operations, development, executive, or AI retrieval system) without duplication or rebuilding.

SCA predates and directly enables the knowledge structures enterprise AI requires to function. Most RAG systems underperform not because of the model, but because the knowledge layer feeding them was never architected for machine retrieval. SCA is the architectural solution to that problem.

Original framework developed 2016 to present. Copyright and patent in progress.

The throughline

The thirty-year thread

Every role I've held has been a version of the same problem: making complex organizations more coherent, more legible, and more effective through better information systems. The scale changes: from a 13-person startup with no documentation to an 11,000-person post-merger enterprise. The domains change: life insurance, SaaS, IoT, financial services, AI consulting. The underlying work is always the same: enter the knowledge vacuum, learn the domain, identify what information exists and what's missing, build the architecture that fills the gaps, translate across audiences simultaneously, and leave behind something that works without me.

The Foundations onboarding program I designed in 2015 still runs at Transamerica in both divisions as of 2026. The knowledge repository I built the same year still functions as their operational baseline. The Copilot program I ran in 2023 still produces measurable retention data. I don't leave outputs. I leave systems.