more insights from testing with developers.

- devs attribute poor outcomes with tooling to a perceived lack of skill (they think it's a “skill issue”)

- documentation need to answer 3 questions:

1. What prereq’s do I need in order to be successful?
2. What do I do specifically?
3. What is the expected output?

experience researcher & treasure hunter /openux || /manansh

more on documentation:

1. there are wildly different approaches to consuming docs
2. completeness > “let devs fill in the gaps”
3. docs are products too, don't neglect their upkeep if things change or break

more on the “skill issue” thing, people can be quick to blame themselves for a tool/product/interface not working

when, in reality, its not their fault at all.

takeaway: try to not make your developers feel stupid!