emily piech.
technical writer · ux content designer

The bridge between what engineers build and what people read.

For ten years I've taken complicated products in automotive, payments, and SaaS and written the parts people actually read: release notes, in-app text, user guides, and the documentation teams count on to ship.

More than once I've walked in to find no documentation, or no process behind it, and built the whole thing from scratch.

01

A few things I've done

At PayiQ I was hired to build the documentation from nothing. No manual, no guides, no standards. I set up the processes and got it all organized.
fintech · 2023–24
At GM I built the process for over-the-air release notes. It replaced a duplicated, inconsistent mess, and it now handles more release notes than anyone expected.
automotive · 2024–now
I wrote quick reference guides to cut down on support calls and the same onboarding questions coming up over and over. People said they made the software easier to understand, for customers and internal teams both.
fintech · payiq
Often the person QA and product managers came to when the writing had to be right, fixing copy on the fly to get it there.
the go-to writer
03

The toolkit

Content
User guides · release notes · microcopy · tooltips · error messages · notifications · knowledge base · training material
UX writing
In-app content · workflow guidance · interface content standards · Figma & FigJam review
Strategy
Style guides · documentation processes · SOPs · content reviews · editorial feedback · gap analysis
Delivery
Agile / Scrum · cross-functional partnership · SME interviews · release support · content validation
Tools
Figma · Jira · Azure DevOps · Confluence · SharePoint · Microsoft Copilot · structured XML authoring