Growing depth. Expanding responsibility.

Chapter 01

Making knowledge work in production

Writers, illustrators, engineers, and customers each held part of what a technical publication needed. I led projects that brought their contributions together, taking responsibility for assignments, schedules, customer communication, reviews, and delivery.

For a major rail program, I led the documentation, illustration, and content-management work. Working with software and subject-matter specialists, I helped establish an authoring environment integrated with a custom content-management system. It was in full production before handoff.

Improving those structures became a recurring part of my contribution. On a major documentation iteration, changes to the operating model reduced required resources by approximately 50% and doubled expected profit. The improved approach carried into subsequent work, lowering customer cost while maintaining profitability.

Chapter 02

Making complex work meaningful to different audiences

Advanced R&D brought together hardware, software, firmware, and semiconductor specialists. I worked closely with those teams to understand their contributions and maintain classified and declassified program accounts in parallel, preserving technical meaning while keeping each account appropriate to its audience and disclosure requirements.

I led documentation and contractual reporting across multiple programs, coordinating technical input, validation, reviews, and submission. I also co-led the first phase of a cloud emulation discovery study with a lead engineer. We developed the research approach, gathered requirements, engaged providers, and evaluated infrastructure options. Our recommendations were adopted for the next phase of development.

I also designed and implemented a property inventory system spanning five sites, hundreds of assets, and thousands of component records. I brought asset tracking and secure sign-offs for sensitive property into a consistent process and reconciled longstanding discrepancies. The typical physical-audit cycle fell from approximately one month to one week.

Chapter 03

Building the capability behind engineering work

At Lam Research, my responsibilities grew from engineering documentation practices to cross-group coordination, systems advice, and an investigation for engineering leadership.

• Engineering investigation. Led more than 40 sessions across 6 product groups; findings and recommendations are helping guide future investments and leadership planning.
• Team capability and delivery. Established all of the team’s engineering templates, writer guidance, and training; coordinated an update involving 191 documents across seven groups and approximately 90 document owners.
• Systems and practical AI use. Advised on document review and approval system development and published an AI support website; I help resolve AI ingestion problems.

My ongoing work includes system guidance, process and tool assistance for writers, and systemic document control across content management systems.