Technical writing: what is the most surprising thing?

[Sonya]

For me it's how much psychology is involved. Not what I expected at all.

We spend so much time talking about how people read (they don't, they scan), how people learn (by doing, not reading), how people handle mistakes (poorly, emotionally). It's essentially applied psychology with documentation as the output.

Last week we read about cognitive load theory and I finally understood why my previous attempts at instructions failed—I was asking users to remember too much at once. Break it into smaller chunks. Give them one thing to do at a time. Don't make them hold information in their head while they're trying to complete a task. Simple principles but they come from actual research about how brains work. I expected to learn about commas and formatting. Didn't expect to learn about human cognition.

Anyone else surprised by the psychology angle?

 

[Anthony]

Sonya, the psychology angle is genuinely what hooked me on this major. I came in thinking I'd be learning grammar rules (boring). Instead I'm learning about how people process information under stress, how to design for different learning styles, and why users blame themselves when instructions fail even when it's the writer's fault.

The chunking principle you mentioned is huge. Miller's Law (7±2 chunks) and all that. But what really got me was reading about emotional design—how frustrated users literally cannot process information as well because their stress response shuts down parts of the brain. So good technical writing isn't just clear, it's also calming. Wild stuff.