GeistHaus
log in · sign up

The Seven-Action Documentation model

passo.uno

I think all technical writers, at some point or another, feel the urge to base their work on something more systematic than “it’s just the way folks documented stuff since forever”. Toolkits and frameworks provide content types, which is immensely valuable when you know what you want to write, but starting from there is like buying a hammer without knowing that half of the work you’ll do is turning screws. As I find the lack of deeper conversation around this topic rather unsettling, I decided to contribute some verses.

1 page links to this URL
The Not-Boring Tech Writer | Growing as a technical writer in the AI era with Fabrizio Ferri-Benedetti

In this episode, I talk with Fabrizio Ferri-Benedetti about moving beyond strictly following documentation frameworks to embrace strategic thinking, his Seven-Action Documentation model that priori...

1 inbound link website en Technical writingTech writersDocumentationTechnical communicationContent strategyUser experience (UX) writingAPI documentationSoftware documentationTechnical documentationInformation architectureKnowledge managementTechnical editingCareer in tech writingTech writing skillsProfessional development for writersWriting for technologyTechnical storytellingUser manualsHelp documentationTechnical writing toolsTechnical writing careerWriting for softwareTechnical writing podcastTech writer interviewsTech writing communityTechnical writing tipsDocumentation best practicesWriting for developersTechnical communication skillsTech writing industry insights