01 / Technical writing education
Teaching modern technical writing as a connected practice
Connected docs-as-code, API documentation, coding, content strategy, and visual communication in an applied college curriculum.
Read the case studyTechnical documentation leader
I build documentation teams and content systems that help complex software products scale.
From developer platforms to global help centres, I bring together people, operations, and product thinking to make documentation faster to publish, easier to trust, and simpler to use.
Experience across Okta, Shopify, Algonquin College, and global software organizations.
Selected results
12+people led across writing, editing, engineering, and team leadership
7 yearsbuilding and leading technical writing teams for Shopify’s developer platform
10languages launched for merchant documentation in under six months
15 yearsworking across documentation, developer platforms, and education
Selected work
Proof, not just a list of responsibilities
Three examples of how I approach transformation: understand the system, align the people around it, and make the outcome measurable.
02 / Global content
Scaling merchant documentation from one language to ten
Built the strategy and cross-functional operating model for a ten-language rollout delivered in under six months.
Read the case study03 / Developer experience
Building documentation leadership around a global developer platform
Built and led technical writing teams responsible for API guides and platform documentation on shopify.dev.
Read the case studyHow I lead
Documentation is a product experience, a team system, and a trust signal.
01
Make ownership visible
Teams move faster when decision rights, standards, and feedback loops are clear.
02
Design for the whole system
Quality depends on the workflow around the words—not only the words themselves.
03
Measure what changed
Strong documentation programs connect user trust and team health to observable outcomes.
Let’s talk
Building a documentation organization or modernizing one?
I’m always happy to compare notes on documentation leadership, developer experience, and content operations.
Start a Conversation