You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/articles/2021-01-09-survey-results-docs-like-code.md
+28-19Lines changed: 28 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
layout: post
3
3
title: Survey Results for learning and teaching docs-like-code techniques
4
4
excerpt: "Review the results of a mid-2020 survey about learning and teaching team mates and yourself how to work with docs like code, Git, and GitHub for technical documentation."
I asked three questions in a survey emailed to my mailing list and got nearly 40 responses.
16
+
I asked three questions in a survey emailed to my mailing list and got more than 30 responses. Thanks to everyone who took the time to share their stories and respond. Here are the three questions:
17
17
18
-
Here are the three questions:
18
+
* Question 1: When you talk to your leaders about docs-as-code, can they describe the benefits as well as the difficulties?
19
19
20
-
Question 1: When you talk to your leaders about docs-as-code, can they describe the benefits as well as the difficulties?
20
+
*Question 2: How do you onboard people who are new to your docs tools and processes?
21
21
22
-
Question 2: How do you onboard people who are new to your docs tools and processes?
23
-
24
-
Question 3: What tips or discussions (from any source) was most helpful to you when learning docs-as-code techniques?
22
+
* Question 3: What tips or discussions (from any source) was most helpful to you when learning docs-as-code techniques?
25
23
26
24
Docs-as-code processes are still new in the field and it seems many of the responses are split, with no overwhelming patterns in any single area. Let's look into the data and charts for the first two questions.
27
25
@@ -30,13 +28,18 @@ Docs-as-code processes are still new in the field and it seems many of the respo
26.8% Yes, my leader started our processes and makes it possible for us to use our current tools and processes.
34
-
19.5% Yes, my leader can provide their leadership complete justification for our choices.
35
-
19.5% No, I work in an environment where my tool selection does not need justification from a management chain.
36
-
19.5% No, my leadership chain doesn't really know what I do or why I use certain tools.
37
-
14.6% It depends on which leader I'm talking to.
38
31
39
-
In a way, nearly all the responses could be viewed as "leadership either supports the selection does not get in the way of tool selection." For about 65% of the responses, either leadership can justify, started the processes, or isn't a deciding factor.
32
+
**26.8**% Yes, my leader started our processes and makes it possible for us to use our current tools and processes.
33
+
34
+
**19.5**% Yes, my leader can provide their leadership complete justification for our choices.
35
+
36
+
**19.5**% No, I work in an environment where my tool selection does not need justification from a management chain.
37
+
38
+
**19.5**% No, my leadership chain doesn't really know what I do or why I use certain tools.
39
+
40
+
**14.6**% It depends on which leader I'm talking to.
41
+
42
+
In a way, nearly all the responses could be viewed as "leadership either supports the selection does not get in the way of tool selection." For about two-thirds of the responses, either leadership can justify, started the processes, or isn't a deciding factor.
40
43
41
44
Looking at the number of lone writer responses in the next question, this indicator makes sense as five of thirty-five respondents noted that they were the only writer in the organization, which would make up 14% of all responses. Let's take a look.
42
45
@@ -45,12 +48,18 @@ Looking at the number of lone writer responses in the next question, this indica
45
48

46
49
47
50
**Legend**
48
-
14.6% Internal write-up only
49
-
20.2% Meeting only
50
-
1.1% Pre-built environment only
51
-
5.6% Lone writer
52
-
23.6% Internal write up and meeting
53
-
34.8% Internal write-up, meeting, and pre-built environment
51
+
52
+
**14.6**% Internal write-up only
53
+
54
+
**20.2**% Meeting only
55
+
56
+
**1.1**% Pre-built environment only
57
+
58
+
**5.6**% Lone writer
59
+
60
+
**23.6**% Internal write up and meeting
61
+
62
+
**34.8**% Internal write-up, meeting, and pre-built environment
54
63
55
64
My favorite answer to this question was one I hadn't considered, where the person is a lone writer, but works with the devs to get the docs working in the source code repo. It's along the lines of "It's complicated."
0 commit comments