Product Guidance
User guides, online help, FAQs, and task-based documentation that help people understand what to do next.
Technical writer / Toronto
Complex products need calm instructions.
I'm Kevin Siu. I design documentation that helps people orient quickly, recover confidently, and finish the task without fighting the page.
Documentation types
Clear docs for the moments where users need direction.
Release Communication
Release notes and change explanations that turn product updates into useful context for end users.
Learning Support
Training materials, video tutorials, onboarding content, and cleanup work that make documentation easier to maintain.
Why documentation
I care about the moment when a user goes from stuck to unstuck.
My work sits between product teams, subject matter experts, and the people trying to get something done. I turn scattered product knowledge into clear steps, useful context, and documentation systems that can keep growing after the first draft ships.
Selected work
Documentation samples with different jobs to do.
Rewrite / before and after
Quick Start Guide Refinement
This is a quickstart guide I found to be unorganized, cluttered, and confusing. I decided to rewrite it to remove repetitive information, unclear instruction, and formatted the entire guide to be easier to read.
- Tools
- Visual redesign, PDF layout, procedural writing
- Strength
- Clarity, hierarchy, and scannability
Online help
Omni OMS and Omni WMS
During my experience working at Tecsys, I maintained and developed web help content for their Omni WMS and Omni OMS products. I authored with Oxygen XML Editor following DITA standards of practice for content reuse. Git repositories were used for version control. Additionally, I created how-to videos for new product features using Camtasia.
- Tools
- Oxygen XML, DITA, Git, Camtasia
- Strength
- Content reuse and product accuracy
Additional samples
Smaller pieces showing format, tone, and document structure across different contexts.
E-learning
Oxygen XML Editor Training
During my experience working at Tecsys, I was tasked with improving the onboarding experience for technical writer interns. I developed a hands-on training guide for Oxygen XML Editor, shown here as a sample of instructional structure and onboarding flow.
- Tools
- Oxygen XML, DITA, training design
- Strength
- Hands-on onboarding
Instruction rewrite
IKEA Graphics to Text Instructions
I converted IKEA-style visual assembly instructions into text instructions, focusing on clear sequencing, visible decision points, and language that can stand on its own without relying on diagrams.
- Tools
- Visual analysis, procedural writing
- Strength
- Translating visuals into accessible steps
User guide
Samsung Galaxy Watch 4
This is a mock-up user guide for the Samsung Galaxy Watch 4. I created this user guide during my time at Algonquin College. This guide offers a full explanation about the watch's features, and abides by company tone to build ethos.
- Tools
- Structured user guide, product research
- Strength
- Feature explanation and tone matching
Release notes
Zoom Mobile Release Notes
I write release notes that prioritize the end-user by not only stating changes; but how they affect the interaction with the product. Users need to know why changes are needed, and why they matter. After all, they are the user.
- Tools
- Release writing, user impact framing
- Strength
- Context-rich change communication
FAQ
Ministry of Transportation FAQ
This is a FAQ document mock up created during my time at Algonquin College. Information is derived from the Ministry of Transportation of Ontario, and I created the structure and visual design.
- Tools
- FAQ structure, source synthesis
- Strength
- Question-led organization
White paper
Vertical Farming
This is a white paper explaining the benefits of vertical farming. This document is for investors in green technology to be distributed in conferences. White papers offer the benefit of educating the reader, while being a persuasive document.
- Tools
- Research writing, persuasive structure
- Strength
- Audience-aware argumentation
Method
How I make information usable.
Map the task
Start with the user goal, the product state, and the point where confusion usually enters.
Shape the path
Separate setup, decisions, steps, reference, warnings, and recovery so the page can be scanned.
Test the explanation
Read like a new user, then revise for gaps, hidden assumptions, tone, and maintenance.
Writing
Posts from the archive.
Contact