Case study

What Senior Technical Writers Know About Cross-Functional Impact

Research based on interviews with nine senior technical writers about their work across product, engineering, support, and internal communication.

Client: Independent community research project

The brief
The project set out to document how senior technical writers contribute across teams and how they describe that contribution to the people who manage them.
The challenge
The value of the role is often spread across product decisions, support, engineering, and internal communication, which makes it difficult to describe with a single metric or job description.
The approach
Interviewed nine senior technical writers, including practitioners from companies such as Google and Mastercard. Coded the interviews for recurring themes and used those themes to build the final narrative.
The work
A long-form resource built around the interview findings, published and distributed to the technical writing community.
The outcome
The resource sparked sustained discussion among senior practitioners on LinkedIn, reached around 700 technical writers, and shifted how several of them framed the value of the role inside their own organizations.
What this demonstrates
Original research design, expert interviews, thematic analysis, and an argument built from primary sources.

Read the resource →

It should be required reading for anyone who still thinks technical writing is just a finishing step. The value is invisible by design and this makes it visible.
Adrian Ashley, Senior Technical Writer
This made the invisible value of technical writers visible.
Kelley Bennett, Senior Technical Writer

Related service: Technical Thought Leadership

Need this kind of content? Hire me →