Want your product knowledge easier to find, understand, and maintain?

“No Comments” came from a pretty common problem in technical teams: important information exists somewhere — just not where or when people actually need it.

So engineers explain the same things repeatedly. Customers wait for clarification. Product knowledge lives in meetings, chat threads, and someone’s memory.

My background as an FPGA engineer and technical communicator means I understand both sides of the problem: the people building the product, and the people using it.

That’s why my work goes beyond writing documentation.

I help teams figure out:

• how to build workflows that support engineering teams instead of slowing them down
• how documentation stays maintainable as products evolve
• how reviews and approvals should work
• how information moves across teams
• what actually needs to be documented

From SME interviews and customer-facing documentation to publishing workflows, tooling, and scalable documentation systems — the goal is to make technical information easier to create, maintain, and use.

Because scaling products also means scaling how knowledge is created, maintained, and shared.