Technical writer / Toronto

Complex products need simple instructions.

Hi, I'm Kevin. I design documentation that is clear, concise, and consistent from the perspective of readers.

Documentation types

Clear docs for the moments where readers need direction.

01

Product Guidance

User guides, online help, reference guides, and task-based documentation that help readers understand what to do next.

02

Release Communication

Release notes and change explanations that turn product updates into useful context.

03

Learning Support

Training materials, video tutorials, onboarding content, and cleanup work that make documentation easier to maintain.

I care about the moment when a reader goes from stuck to unstuck.

My work sits between product teams, subject matter experts, and the readers 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 rewrote it to cut repetition and clarify the instructions, then redesigned it so readers can find information faster.

Tools
Visual redesign, PDF layout, procedural writing
Strength
Clarity, hierarchy, and scannability
Improved quick start guide redesign
Original cluttered quick start guide

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

At Tecsys, I improved onboarding for technical writer interns learning Oxygen XML Editor. I built a hands-on training guide inside the software itself, so interns learn by working through real examples.

Tools
Oxygen XML, DITA, training design
Strength
Hands-on onboarding
View training package

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
View document

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 explains each of the watch's features in full, using Samsung's brand voice.

Tools
Structured user guide, product research
Strength
Feature explanation and tone matching
View document

Release notes

Zoom Mobile Release Notes

This is an unofficial mock-up for the Zoom mobile app. Release notes should do more than list what changed. I write them to explain what is different, why it changed, and what it means for the person using the product tomorrow.

Tools
Release writing, user impact framing
Strength
Context-rich change communication
View document

FAQ

Ministry of Transportation FAQ

This is an 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
View document

White paper

Vertical Farming

This is a white paper explaining the benefits of vertical farming. It can be distributed at a conference for investors interested in green technology. White papers educate readers while making a persuasive case. This one argues for investing in the technology.

Tools
Research writing, persuasive structure
Strength
Audience-aware argumentation
View document

Method

How I make information usable.

01

Map the task

Start with the user goal, the product state, and the point where confusion usually enters.

02

Shape the path

Separate setup, decisions, steps, reference, warnings, and recovery so the page can be scanned.

03

Test the explanation

Read like a new user, then revise for gaps, hidden assumptions, tone, and maintenance.

Writing

Notes on docs, work, and learning.

Yes, ChatGPT is impressive. No, it won't replace you (probably). A technical writer's reflection on ChatGPT, automation, and why documentation work still depends on human judgment. I read a manual for a power strip...and made a career out of it A personal reflection on discovering technical writing through manuals, information design, and everyday documentation. Learn from my mistakes: advice from one intern to another Advice for interns on confidence, communication, learning, and getting more out of early work experience.
View all writing

Contact

Need docs that are easier to read, maintain, or trust?

I'm open to technical writing roles, documentation projects, and conversations about product education.