3 ms·
This is basically what I did & do with my team. It requires you have someone who is already excellent at technical writing. Document the principles of what mak
by droopyEyelids 4y ago
This is basically what I did & do with my team. It requires you have someone who is already excellent at technical writing.
Document the principles of what makes good technical writing for your team.
Then you assign people on the team to document/write something, and have the person who is good at it edit their writing and discuss the changes in the framework of the principles you documented.
Lotta room for this to go wrong, maybe the person you thought was good at technical writing isn't that good, or can't communicate well. Maybe a lot of people on your team lack the language skills to do a good job. Maybe they don't understand things well enough themselves to communicate to others.
But in my case I was able to get 2 out of the 7 people who never really wrote to be good enough I'm proud to have them represent my team, which was a tremendous improvement.
- ghaff 4y ago>It requires you have someone who is already excellent at technical writing. 100%. You can probably help everyone on the team (to some degree) who is willing to do some work to improve. But you probably want one (or ideally two) people who can work with people and are the gate to actually publishing anything. They don't need to be a dedicated resource and don't even need to be "professional" editors. But they do need to be able to work with people and have strong writing (and copyedit) skills.