Sreejith GS’ Post

View profile for Sreejith GS, graphic

Experienced Technical Writer| Blogger| Storyteller|

Started the day reading the interview from David Nunez who was leading the documentation team at Stripe. I had heard good things about Stripe docs from developers. This was a chance to hear something straight from the horse's mouth. Here are some of things I liked from the interview and my take on them. 1. Documentation should provide a smooth onboarding experience for the product. In my experience, it is a very critical aspect the technical writing teams should look into. Most people try out things before they make a purchase decision in the SAAS world. Once, one of the software architects mentioned that they have to evaluate 4-5 products in a limited time frame to recommend the best option. Hence, a good getting started plays a key role in product adoption if we can help the users to speed up their onboarding time. David is recommending different people in your company to go through the getting started experience, get the feedback, and fix any loopholes. 2. While extensive documentation is good to have it is very hard to maintain. We may have to trim it down because so many things change in a very short span. However, it is very hard to convince different stakeholders to agree upon remove the existing content. I have seen some of the features everyone thought critical in the initial stages of the product may not have the same priority or hardly any takers a few years later. Those content needs to be updated whenever there is change. For example, the underlying platform like Kubernetes may change key functionalities in their new release that requires a change in every feature. Link to the interview is provided as the first comment.

To view or add a comment, sign in

Explore topics