1 of 28

Poll the Docs

WTD Prague - 2016

Kata Nagygyörgy

UX Researcher

kata@pronovix.com

@NagygyorgyKata

2 of 28

Purpose of

Poll the Docs

Particular thanks to David Ryan for the idea and feedback, to Eric Holscher and Kristof Van Tomme for making it happen.

In the beginning of 2016 we put together a survey to investigate how people are doing their jobs, what the current status is of documentation, and what the future will bring.

3 of 28

What you need to keep in mind

Participants

N=100

Method

  • Snowball sampling
  • Online questionnaire
  • It’s not representative

Data distortion effect

It more reflects the thinking of those who’d like to share information, and contribute to the common knowledge.

4 of 28

1.

Demographics

Some basic data about the community

5 of 28

Age and diversity

6 of 28

Country of residence

(99 responses)

12,1%

65,7%

4%

5,1%

7 of 28

Previous and Current Industry

8 of 28

API Content Developer

API Technical Writer

CEO

CoE Process Manager

Content & Documentation Manager

Content Specialist

Data Specialist

Developer Educator

Developer relations

Developer/Writer

Director of support

Documentation Consultant

Documentation Coordinator

Documentation Engineer

Documentation Program Manager

Documentation specialist

Editorial Manager

Educational Services Specialist

Engineering Content Developer

Engineering Manager

Engineering Operations

Freelance Software Engineer

Freelance tech journalist

Growth Hacker

Knowledge Base Administrator

Manager, Technical Communication

Principal Technical Writer

Priority Technical Support

Product developer (i.e. dev + tech writer)

Product Engineer

Product Owner

Professional Content Developer

QA

Research Software Engineer

Rhetorically sensitive socio-technical mediator (with apologies to Brad Mehlenbacher)

Senior Consultant

Senior Engineering Manager/Director of Engineering

Senior Software Engineer

Senior User Assistance Manager

Staff Technical Writer

Support Customer Experience Manager

Technical Communications Manager

Technical Communicator

Technical Content Editor

Technical Editor

Technical Writing Manager

‘’

9 of 28

Work language

10 of 28

Work experience

11 of 28

How did you start working in the field of documentation?

12 of 28

Coincidence

From Tech Support

Like writing

19%

11%

11%

13 of 28

How did you start working in the field of documentation?

14 of 28

2.

Documentation

How do you work?

15 of 28

What kind of tools do you use in your everyday work?

16 of 28

Documentation standards and style guides

Percentage of use / 100 people

17 of 28

Typical technical writing output

Percentage of use / 100 people

18 of 28

What workflow do you use to ensure quality?

19 of 28

Most important personality skills

20 of 28

Most important technical skills

21 of 28

3.

Comparison

Based on work style

22 of 28

How do you work?

23 of 28

Comparing user groups based on work experience

Work experience

Alone

(N=12)

In a team with other professionals

(N=53)

In a team with other technical writers

(N=35)

Around 5 years

58%

67%

57%

Around 3 years

25%

33%

0%

Around 1 year

27%

0%

43%

24 of 28

Technical writing output

Alone

(N=12)

In a team with other professionals

(N=53)

In a team with other technical writers

(N=35)

Typical technical writing output

Software documentation

Online and embedded help

User manuals

Software documentation Release notes

Software documentation Release notes

API documentation

Never or rarely used writing output

Training documents

Website copy

Articles/press releases

API documentation

Release notes

Articles/press releases

White papers

Books

Legal documents

Training documents Website copy

Articles/press release

White papers

Books

Legal documents

How-to videos

QA/testing documents Project documents (proposals, briefs, etc.)

Presentations

25 of 28

Style guide and review process

Alone

(N=12)

In a team with other professionals

(N=53)

In a team with other technical writers

(N=35)

Style guide

In-house style guide

None

In house style guide

In-house style guide

Chicago Manual of Style

Review process

Peer review

Self review

Review process with team

Review process with team

Peer review

SME review

26 of 28

Career progression and writing trends

Alone

(N=12)

In a team with other professionals

(N=53)

In a team with other technical writers

(N=35)

Career progression

Already there

Dev Evangelist

Already there

Content strategies Product/project management

Already there

Content strategies

Product/project management

Technical writing trends encountered past year

API Documentation

Plain Text Markup Languages (Markdown, reStructuredText, Asciidoc)

API Documentation

Plain Text Markup Languages (Markdown, reStructuredText, Asciidoc)

Static site generators

API Documentation

Plain Text Markup Languages (Markdown, reStructuredText, Asciidoc)

Video content

Minimalism

27 of 28

Thanks.

28 of 28

Questionnaire:

https://goo.gl/6SQc63