📎 Webclip
Personas in Writing
The article adapts the idea of user personas to writing. It says personas help a writer choose topics, shape drafts, and keep different readers in mind, with different levels of attention for different audience groups.
Reading notes#
- Personas are short, clear descriptions of subsets of a broader audience.
- In software teams, personas help keep users present in product and interface decisions.
- The same idea can guide writing by helping select articles and tailor approach to readers’ needs.
- A writer can limit the number of personas based on how focused the audience is, and one persona can be primary while others stay peripheral.
- The author says he writes because software development has a high barrier to entry and that barrier causes problems.
- He criticizes litmus tests that define who counts as a real developer.
- He links this to impostor syndrome, low diversity in software development, and the growth of boot camps and other entry paths.
- Betsy, the bootcamp graduate, needs fundamentals, simple explanations, and introductory tutorials.
- Sara, the not-quite senior developer, needs tradeoff comparisons, maintainability discussions, and approachable architecture topics.
- Priya, the prodigy, needs guidance toward options, experiments, and newer or more radical ideas.
- Matt, the manager, needs writing about teams, projects, trends, and software work at a broad level.
- Tina, the tester, needs simple descriptions and examples of how things fail, especially in software quality contexts.
- Personas can be used to choose topics, review drafts, and decide when an article should not try to serve every audience at once.
- The author closes by saying this article was written for himself and states his goal as helping software professionals discover and understand new tools, processes, and ideas for making quality software.
