We have talked about processes and tools, but as technical writers, we hardly ever discuss KPIs for our documentation, measuring the effectiveness of our documentation.

Ziv Bass-Specktor is the Head Of Knowledge at AppsFlyer. He has done documentation well at the company but also has figured out a way to measure our KPIs for technical writing in our companies.

Ziv shares some of the KPIs they use at AppsFlyer including self-service ratio, search KPIs, documentation and support, user trust KPI, and localization - locale self-service ratio and locale coverage.

These are KPIs that you can implement now in your own company and business!

---------------

This episode was produced by: Intent Media.

Music by: Beatsbyalf

Comments, questions, or to submit "a word to retire":

Email: fiedler.alex@gmail.com

Getting ready to hire a Junior writer to join your team? Alex talks about his experience growing from a Junior writer (copy-paster) to a full-blown Senior writer. His insights will help team leaders and aspiring writers learn how to hire and train a Junior writer successfully.

Stay tuned for the Linkedin noteworthy post of the week and word to retire!

---------------

This episode was produced by: Intent Media.

---------------

Music by: Beatsbyalf

Comments, questions, or to submit "a word to retire":

Email: fiedler.alex@gmail.com

What is the difference between "docs as code" and "docs as product?" Alex discusses the approach of "docs as product"; what is it, is it relevant to you, and pitfalls to avoid when starting with "docs as product." He also does a deep dive into how to actually implement this type of product strategy for your documentation.

1. What is traditional technical documentation, and how does it differ from "docs as product"?
2. Where should I start to implement "docs as product"?
3. Is your documentation pre or post-sales?
4. What type of product do you have?
5. How does this change the way I relate to my technical documentation?

Stay tuned for the Linkedin noteworthy post of the week and word to retire!

---------------

This episode was produced by Ahron Wohlgelernter

Intent Media.

---------------

Music by: Beatsbyalf

Comments, questions, or to submit "a word to retire":

Email: fiedler.alex@gmail.com

What is the business purpose for Tech documentation? Alex discusses how technical writing can positively or negatively effect your business's bottom line.

Stay tuned for the Linkedin noteworthy post of the week and word to retire!

• Can documentation help with the process of onboarding your company's new hires and new customers?
• Customer support tickets?

---------------

This episode was produced by Ahron Wohlgelernter Intent Media

---------------

Music by: Beatsbyalf

Comments, questions, or to submit "a word to retire":

Email: fiedler.alex@gmail.com

Naomi Soman: https://www.linkedin.com/in/naomi-soman/

Technical documentation tools are critical for building good documentation, so today Alex gives you a few key points you must clarify when thinking about what documentation tools your team needs.

• What type of product do you have?
• Keep your docs in line with your industry standards
• Make sure you're speaking to your end-user
• What experience do you want to deliver?
• Who owns this tool?
• What kind of docs do you currently have?
• What dos do you want to have in the future?

---------------

This episode was produced by Ahron Wohlgelernter Intent Media

---------------

Music by: Beatsbyalf

Comments, questions, or to submit "a word to retire":

Email: fiedler.alex@gmail.com

Naomi Soman: https://www.linkedin.com/in/naomi-soman/

You're convinced that you need a writer and understand the basics of what to look for. But are you planning for today's needs only and not thinking about building a team? It doesn't only take two to tango, it also takes 2 (at least) to successfully document a product.

• How do you achieve diversity within technical writing teams?
• Your responsibility preparing for the interview process?
• What type of content do you expect your writer to write?
• Why an inside-the-box thinker is important?
• Full-stack writer: Fact or fiction?

---------------

This episode was produced by Ahron Wohlgelernter Intent Media

---------------

Music by: Beatsbyalf

Comments, questions, or to submit "a word to retire":

Email: fiedler.alex@gmail.com

Naomi Soman: https://www.linkedin.com/in/naomi-soman/

Technical writers are stereotypically an odd bunch, how do find the right ones that culturally are "aligned" with our values? Alex talks about how to improve the recruitment process and make the right hires.

• Do we concentrate too much on tools?
• Who should be involved in the recruitment process?
• How to properly onboard a technical writer?

---------------

This episode was produced by Ahron Wohlgelernter Intent Media

---------------

Music by: Beatsbyalf

Comments, questions, or to submit "a word to retire":

Email: fiedler.alex@gmail.com

This week Alex talks about finding the right technical writer for your company. There are many descriptions and expectations when it comes to writing so Alex helps you navigate this issue.

• What are some unrealistic and realistic expectations?
• Are job descriptions too broad?
• What skill sets does one need to be a good technical writer?
• what is a full-stack writer?

---------------

This episode was produced by Ahron Wohlgelernter Intent Media

---------------

Music by: Beatsbyalf

Comments, questions, or to submit "a word to retire":

Email: fiedler.alex@gmail.com