Technical Writer

Heather Cloward Portfolio

Technical writer and instructional designer with a focus on user guides and knowledge-base content for SaaS products. Her portfolio highlights measurable support-ticket reduction from documentation improvements.

User GuidesKnowledge BaseInstructional DesignSaaS

What makes it work

A breakdown of the choices that make this portfolio stand out.

1

Business-impact metrics tied to documentation

Citing a measurable drop in support tickets after a documentation overhaul connects writing work directly to a business outcome.

2

Instructional design framing

Positioning knowledge-base work through an instructional-design lens shows structured thinking about how people actually learn from docs.

3

SaaS-specific context

Naming the SaaS product category signals familiarity with the fast-shipping, frequently-changing documentation environment common in that industry.

What Technical Writers can take from this

Specific, actionable tips to apply to your own portfolio — no generic advice.

  • Whenever possible, tie documentation work to a measurable business outcome like reduced support tickets.

  • Apply an instructional-design lens to knowledge-base work — structure content around how people actually learn, not just what's true.

  • Name the specific industry or product category you've written for so prospective clients can gauge relevant experience quickly.

Ready to build your portfolio?

Follow the Technical Writer roadmap — skills, projects, and timeline to get hired.

Technical Writer Roadmap