As someone who has been a technical writer for five years, I’ve always been curious about the deep roots of this profession. While I’ve written API documentation, edited developer guides, and participated in docs-as-code workflows, I know my experiences barely scratch the surface of the discipline’s long and rich history.
To many in tech today, technical writing seems like a modern career that only gained traction in the last five years, often viewed as an easy transition for those wanting to escape the rigors of software engineering or UX. But technical writing is far from new. It has been a pillar of software and product development for decades.
To bring this to light, I created a video series featuring some of the most experienced technical writers in the field, true OGs who have been doing this work since the 1980s and beyond. These are people who documented software when floppy disks were still relevant, who collaborated with engineers before email became mainstream, and who distributed printed manuals through the mail. I had the immense privilege of speaking with five incredible professionals: Tanja Lober, Dennis Dawson, Lynne Thompson, Christopher Scannell, and Carol Kosman.
A Different World: The 1980s and 1990s Technical Writing Era
Before diving into the individual interviews, it's important to set the stage. Being a technical writer in the 80s and 90s was a far cry from what it is today. There was no Google Docs for collaboration, no GitHub for version control, and certainly no Slack for real-time messaging. If you wanted feedback on a document, you printed it, passed it around, and your teammate would use a red pen to mark their comments legibly. Faxes were used, i mean actual physical faxes.
As Dennis Dawson, with over 40 years in the field, shared, articles were often written on typewriters or very early word processors. When the documentation was ready, it would be printed, packaged, and mailed to clients physically. There was no instant feedback loop. If you made a mistake? Well, tough luck, it might not be caught until weeks or months later. There was a kind of finality to publishing back then that made accuracy even more critical. Imagine the pressure.
Hearing their stories gave me chills. We talk about shipping documentation today as just a "merge and deploy" process. Back then, shipping was literal. And any errors? You'd have to wait for the client to find them if they even had a way to report them back. These veterans truly suffered and persevered so that writers like me today can enjoy the comforts of Markdown, version control, and instant publishing.
The Conversations That Changed Me
1. Tanja Lober – 30+ Years in the Game
In this conversation, Wisdom Nwokocha interviews Tanja, a seasoned technical writer with over 30 years of experience. They discuss Tanja's journey into technical writing, the evolution of tools and processes over the years, and the impact of AI on the profession.
Tanja shares valuable advice for aspiring technical writers, emphasizing the importance of finding content that resonates with them and honing their interview skills. The conversation also touches on the significance of documentation and the balance between traditional methods and modern technology in the writing process.
Takeaways
- Tanja started her career in technical writing through a university course.
- The evolution of tools has made technical writing easier yet more complex.
- AI presents both opportunities and challenges for technical writers.
- Aspiring writers should find content that resonates with them.
- Documentation is crucial for retaining knowledge and experiences.
- Traditional methods like paper can still be valuable in a digital age.
- Interview skills are essential for gathering information effectively.
- Networking with experienced writers can provide valuable insights.
- Balancing technology with traditional methods can enhance productivity.
- Personal experiences in writing can lead to future solutions.
2. Dennis Dawson – 40+ Years of Wisdom
In this conversation, Dennis Dawson shares his extensive journey in technical writing, starting from his early days in the 1980s to the present. He discusses the evolution of tools, the shift from typewriters to digital platforms, and the impact of AI on the profession. Dennis emphasizes the importance of continuous learning, collaboration with engineers, and adapting to new technologies.
He also provides valuable insights and advice for aspiring technical writers, highlighting the significance of style guides and the need for consistency in documentation.
Takeaways
- Dennis started his career as a typist and secretary before transitioning to technical writing.
- The introduction of personal computers revolutionized the way technical writing was done.
- Early word processing tools like WordStar and WordPerfect were foundational in his career.
- The 1990s saw the rise of PageMaker and FrameMaker for book writing.
- Creating an index for printed materials was a significant challenge in the past.
- Style guides like Strunk and White and the Chicago Manual of Style have been influential.
- Technical writers must adapt to Agile methodologies and collaborate closely with engineers.
- AI is changing the landscape of technical writing, automating mundane tasks.
- Continuous learning is essential for staying relevant in the field.
- Books like 'Map It' and 'Multimedia Learning' are recommended for technical writers.
3. Lynne Thompson – 25 Years of Tenacity
In this conversation, Wisdom Nwokocha interviews Lynne Thompson, a seasoned technical writer with over 15 years of experience. Lynne shares her journey into technical writing, discussing the evolution of tools and techniques from the early days of Unix to the current landscape influenced by AI.
She emphasizes the importance of continuous learning, collaboration with engineers, and the changing dynamics of the job market. Lynne also reflects on the significance of editing skills and the need for technical writers to adapt to new technologies while preserving their core writing abilities.
Takeaways
- Lynne's journey into technical writing began unexpectedly through a friend's recommendation.
- The evolution of tools from Unix to modern software has significantly changed the technical writing landscape.
- Technical writers must understand the technical aspects to ask relevant questions and improve their work.
- AI is reshaping the job market, creating both opportunities and challenges for technical writers.
- Continuous learning and adapting to new tools and technologies is essential for career growth.
- Collaboration with engineers has evolved, with writers gaining more respect in technical teams.
- Editing skills are crucial, and there is a noticeable decline in good editing practices today.
- Networking and personal recommendations play a vital role in securing job opportunities.
- The job market is more competitive now, requiring writers to be flexible and open to contract positions.
- Maintaining a unique voice while editing is important for preserving the original intent of the writer.
4. Christopher Scannell – 30+ Years of Impact
In this conversation, Chris Scannell shares his extensive journey in technical writing, discussing how he transitioned from an English graduate to a seasoned technical writer. He reflects on the evolution of tools and processes in the field, the changing role of product managers, and the impact of AI on technical writing.
Chris offers valuable advice for aspiring technical writers, emphasizing the importance of understanding the subject matter and the tools of the trade. He also addresses common misconceptions about the ease of entering the field and highlights the ongoing relevance of technical writing in a rapidly changing technological landscape.
Takeaways
- Chris Scannell's journey into technical writing began with a degree in English.
- He started in office services at a software company before transitioning to technical writing.
- The tools used in technical writing have evolved from Microsoft Word to XML and DITA.
- Product managers now play a crucial role in the documentation process.
- Technical writing has always faced challenges regarding its perceived value and relevance.
- AI is becoming a part of technical writing, but human verification is still essential.
- Understanding the subject matter is critical for effective technical writing.
- The pace of work in technical writing has increased significantly over the years.
- Networking and job listings were key to finding opportunities in the past.
- Technical writing is not an easy field; it requires dedication and skill.
5. Carol Kosman – 17+ Years of Excellence
In this conversation, Carol Kosman shares her extensive journey in technical writing, starting from her roots in biotechnology to her current role. She discusses the evolution of tools and technology in the field, the impact of AI on writing, and offers valuable advice for aspiring technical writers. The conversation highlights the importance of curiosity, adaptability, and networking in navigating the modern job market.
Takeaways
- Carol started her career in the biotech field during the Human Genome Project.
- Technical writers must be tenacious and advocate for the importance of their work.
- The advent of content management systems has changed the efficiency of technical writing.
- AI is a tool that can assist in drafting but should not replace human creativity.
- The recruitment process for technical writers has evolved with the use of AI and algorithms.
- Technical writing is often misunderstood as an easy profession, but it requires significant skill and thought.
- Networking and community involvement are crucial for aspiring technical writers.
- Technical writing spans various fields, not just technology.
- Curiosity and a willingness to learn are essential traits for success in technical writing.
- The support among technical writers is strong, fostering a sense of community.
More Than a Series, It’s a Movement
This series wasn’t just for me, it’s for all of us in the technical writing community. I created this as a member of the TWMP (Technical Writers Mentorship Program) community because I wanted every writer, junior, mid-level, or senior, to hear the voices of the people who paved the way for us. These conversations are proof that technical writing isn’t a fallback career or a new “easy tech job.” It’s a discipline, an art, and a profession with a rich history.
To hear how they dealt with pressure, deadlines, and outdated tools, and yet still delivered excellence, is inspiring. They didn't have spellcheck or Grammarly. They didn’t have version control. They had typewriters, fax machines, red pens, and a fierce commitment to clarity.
Why This Matters Today
Too often, I hear people say, “I just became a technical writer,” as if it’s a short-term gig or a stepping stone. But speaking with these veterans made me appreciate the weight of that title. Even with only five years of experience, I now feel part of a legacy. A movement. A profession that has evolved alongside software engineering, design, and IT, not beneath them.
And for those who think technical writing started in the last five years, watch these interviews. Learn from these legends. You’ll walk away with a deeper appreciation for what this career truly entails.
Final Thoughts: Honoring the Past, Building the Future
I started this project to shine a light on the technical writers who came before us. What I didn't expect was how emotional it would be. I laughed, I paused in disbelief, and I walked away feeling honored to be part of this field.
This series is a thank-you letter to every writer who wrote under a fluorescent lamp, wrestled with early documentation tools, and sent physical copies of manuals to clients. Because of you, we have style guides, version control, continuous deployment, and recognition. You endured so we could create with ease.
To Tanja, Dennis, Lynne, Christopher, and Carol, thank you for your time, your stories, and for leaving a lasting legacy.
And to every writer reading this: don’t let anyone belittle this profession. We are not just scribes; we are builders of clarity, guides for users, and quiet heroes behind successful products.
The torch has been passed. Let’s honor it.
