Technical writing · Knowledge management · AI workflows

I make complex information easier to use and the systems behind it easier to manage.

I have 13 years of experience in technical writing, with a focus on documentation strategy, knowledge management, information architecture, and improving the processes behind technical documentation. I also design and build AI-assisted documentation workflows, with an emphasis on efficiency, accuracy, and human oversight.

Eliza Lenz
What I do

Documentation is often an information problem before it's a writing problem.

My work includes customer-facing documentation, knowledge-base architecture, content migration, release planning, source-quality review, and workflow design. I’ve created multiple style guides to support consistent language, formatting, and editorial review. I use AI where it removes mechanical work, while keeping human judgment at the points where incomplete or ambiguous information can create downstream errors.

↑ Back to the Top
Case studies

Documentation systems built around editorial judgment.

These case studies show how I approach documentation operations: establishing an editorial quality gate, improving source information, and developing more integrated workflows that support human judgment.

01 · Workflow design

Documentation Triage at Scale

A release documentation quality gate: individually screening bulk-labelled Jira tickets for customer relevance, internal-only information, existing coverage, and required guide updates before drafting.

View recreated artifact ↓
02 · Source quality

QA Liaison Workflow

A source-quality gate designed after documentation capacity was reduced: QA reviews Jira completeness, SMEs resolve gaps, Glean drafts from approved source material, and the writer verifies the result.

View workflow ↓
03 · Documentation operations

Release Documentation Manager

Building on a Confluence Database I designed for Jira ticket review, this fictional prototype connects assessment, editorial decisions, SME follow-ups, and release tracking.

Explore case study ↓
01 · Documentation Triage at Scale

The manual system behind the automation.

Release tickets were often bulk-labelled for documentation without first being assessed for customer impact or suitability for external publication. I reviewed them individually to determine what customers actually needed to know—and what should never appear in customer-facing content. Many tickets described backend changes, internal bugs, or implementation details; others were already covered in existing documentation or required clarification before a decision could be made.

My triage process involved:

  • Assessing customer relevance: Determining which bulk-labelled tickets described changes customers actually needed to know about.
  • Protecting internal information: Excluding backend processes, internal bugs, implementation details, and other information unsuitable for customer-facing publication.
  • Checking existing coverage: Identifying changes already addressed in other articles, guides, or releases to avoid unnecessary duplication.
  • Resolving uncertainty: Flagging incomplete or conflicting tickets and asking SMEs for clarification rather than guessing.
  • Determining documentation scope: Identifying updates needed across release notes, user guides, configuration references, and installation or upgrade instructions.
  • Recording decisions: Tracking inclusion and exclusion decisions, rationales, assigned SMEs, unanswered questions, affected guides, and completion status.

I maintained these decisions in a working triage database. Unknowns remained visible until they were resolved, helping keep unnecessary, duplicate, or internal-only information out of customer documentation.

Why this matters:
This was not the AI triage agent. It was the manual content-quality and information-disclosure gate: deciding which tickets warranted customer documentation, which were internal-only, and which needed human clarification. It helped define what useful automation needed to do — and which decisions still required a person.

Portfolio sample: a fictionalized Northstar recreation of the working structure.
Northstar Cloud 1.1 TicketsFictionalized Confluence-style recreation
Jira work itemGoes in docs?SMEQuestionAnswerNotes
NC-1: Refactor permission evaluation serviceUnknownDaniel RossCan you confirm whether this changes any customer-facing permission or role behaviour, or is this strictly an internal refactor?—New ticket. Added to DB Oct. 7/26. Ticket says no functional changes are expected, but confirming before excluding from docs.
NC-2: Upgrade SAML authentication libraryUnknownPriya ShahDoes the SAML library upgrade change any customer configuration, supported identity providers, certificate requirements, or upgrade steps?—New ticket. Added to DB Oct. 7/26. Security/dependency update. Need confirmation of customer impact.
NC-3: Improve notification service performanceNoMarcus Reed——Backend performance change only. Ticket states there are no user-facing changes and existing templates/preferences are unchanged.
NC-4: Upgrade reporting databaseNoSofia Alvarez——Infrastructure-only database upgrade. No customer action, schema change, or UI change indicated.
NC-5: Add configurable session timeoutYesMaya Chen——New feature. Add setting location, available values, permission requirement, and default behaviour.
NC-6: Add inactivity warning before session expirationYesMaya ChenHow long before the session expires does the warning appear? If the session expires, is unsaved work lost?—New ticket. Added to DB Oct. 7/26. Need warning timing and unsaved-work behaviour before guide update.
NC-7: Update password complexity requirementsYesMaya Chen——Straightforward user-facing change. SSO users are not affected.
NC-8: Add password history enforcementYesMaya ChenHow many previous passwords are retained? Is the history value configurable by an administrator?The previous 10 passwords are retained. The value is not configurable in 4.8.Answer received. Add restriction with the other local password requirements.
All Northstar product details, tickets, names, and answers are fictional. The workflow is based on a documentation-triage process I designed and used professionally.
↑ Back to the Top
02 · QA Liaison Workflow

Improving the source before asking AI to draft from it.

When documentation capacity was reduced, I proposed a QA Liaison role and changes to the Jira workflow to address a recurring problem: tickets arriving for documentation without enough information to explain the customer-facing change accurately. This was particularly important when AI-assisted drafting was being considered, because a draft can sound complete even when its source is not.

The proposed QA Liaison would check source tickets before they entered the drafting process, identifying missing steps, unclear behaviour, conflicting requirements, and gaps in the expected customer impact. Rather than leaving writers to reconstruct requirements, the liaison would route specific questions to the appropriate subject matter experts and track outstanding clarifications.

Only after the necessary information was confirmed would a ticket move forward as an approved source for a Glean-assisted draft. A technical writer would still review the resulting content for accuracy, clarity, customer relevance, and suitability for publication. The intent was to improve the quality of the input—not to treat AI-generated text as a substitute for editorial review.

Jira ticket→QA Liaison review→SME clarification→Approved source→Glean draft→Technical writer review→Publish
↑ Back to the Top
03 · Release Documentation Manager

Extending a Confluence review database into a connected release workflow.

I originally built a database using Confluence Databases to review Jira tickets during software releases. It helped me record customer impact, existing documentation coverage, outstanding SME questions, affected guides, and completion status. I then designed a fictional prototype to explore how that manual process could be supported by automation and brought together in one tool.

The Release Documentation Manager brings together:

  • Assessing tickets: Suggesting whether a change requires customer-facing documentation, with supporting reasoning and specific questions when information is missing.
  • Preserving editorial control: Keeping automated recommendations separate from individual reviewer decisions and allowing reviewers to determine the appropriate action.
  • Mapping documentation work: Connecting decisions to the guides and sections that need new or updated content.
  • Coordinating SME follow-ups: Recording questions, responses, and reminders so unresolved information remains visible.
  • Tracking release progress: Maintaining assessment history, documentation actions, and Excel reports as the review progresses.

I defined the editorial requirements, workflows, and review logic, then directed and evaluated the AI-assisted implementation. The prototype uses fictional Northstar Cloud tickets and local rules-based assessments, rather than a live Jira integration or language model.

Release source, assessment controls, and release-triage overview
Release source, assessment controls, and release-triage overview
Release tracker with ticket review and documentation-action status
Release tracker with ticket review and documentation-action status

Explore the Full Prototype

The interactive prototype is available upon request.

Request Access ↗
↑ Back to the Top
Working style

Calm, practical, and systems-oriented.

I work well across teams, particularly when the work involves competing priorities, incomplete information, or complicated processes. I'm good at identifying where things are going wrong, understanding the underlying causes, and finding practical ways to improve them.

I value accuracy, sound editorial judgment, and good working relationships. I enjoy collaborating with SMEs, helping other writers succeed, and developing standards and workflows that make documentation easier to produce and maintain.

Core Strengths
Systems ThinkingCollaborationProblem SolvingCommunicationProcess ImprovementConflict Resolution
↑ Back to the Top
Contact

Contact Me

If you'd like to talk about documentation, knowledge management, content operations, or AI-enabled documentation workflows, I'd love to hear from you.


↑ Back to the Top