Book a Demo Sign up

User-Friendly Documentation with Sara Tilly of Infobip

User-Friendly Documentation with Sara Tilly of Infobip

Category: Podcast

Last updated on Sep 22, 2022

Sara Tilly, Lead Technical Writer at InfoBip, joins us in this episode of Knowledgebase Ninja to share her experience creating efficient documentation processes and its significance in a product’s journey. Check out all the other episodes of Knowledgebase Ninja here.

Connect with Sara Tilly and Infobip here:

KEY TAKEAWAYS

  • Sara stepped into technical writing to address the product and features specifications for a software house
  • Sara has experience in the user documentation for server monitoring, point administration tools, technical content, and many more
  • Before starting the technical documentation journey with Infobip, Sara worked as a freelance technical writer
  • Sara believes that the development process is the most integral part, be it technical documents or the software. 
  • During the development process at Infobip, technical writers communicate and stay in touch with several other departments depending on the company’s requirements
  • Communication and keeping all the relevant stakeholders engaged results in the production of high-quality documents 
  • Technical writers are the “first line testers”, working on the product development and quality assurance  
  • At Infobip, Sara works on pre-sales planning and client solutions while also communicating with the product marketing managers. This collaboration aids her in aligning with the road map and the document release management
  • Sara defines workflow management as the most crucial element of documentation success. At Infobip workflow management is done through;
    • Drawing an outline two to three weeks before the product release
    • Generating a draft which is used as a guideline 
    • Introducing technical writers to the product for cross-checking purposes
    • Reporting any errors to product developers
    • Handing the documentation over to product managers
    • Proofreading the approved document
    • Posting the document online 
    • Analysing feedback from the product manager or development team
  • Technical writers must know their audience. Only then can their document can be valuable for the end-user
  • Thorough research and data assembly roles should be considered as mandatory prerequisites for quality documentation
  • Synchronisation between the internal teams plays a key role in creating the proper road map and effective document release management

Sara’s advice to her 20-year-old self

Sara wants her 20-year-old self to be more relaxed about not knowing everything. She wants to tell her younger self that there will be things she cannot know, and it’s okay because she is not meant to be a developer. Her key is to see the product and the people who work on it. She wants her younger self to always be willing to learn.

Sara’s favourite technical documentation resource

Subscribe to Knowledgebase Ninjas

Quote:

 

Gowri Ramkumar

Feb 16, 2021

Webinar - How to design and improve your documentation workflow continuously?
https://document360.com/blog/infobips-sara-tilly-on-workflow-management-for-documentation-success/
document360.com
CC-MAIN-2023-06
133831
application/http; msgtype=response
sha1:6U76JEFOG7O7ZWSNRNTMCCHC2KZW7HYH
<urn:uuid:af4586d7-aea7-475f-8348-62d2b03c4694>
2023-01-30T08:40:06Z
141.193.213.11
text/html
sha1:SHBIPAMNAQRP7TZB6EMLIATSBCHO3DAL
<urn:uuid:16befe5d-2321-4553-a8dc-5c88f1ff1c14>
https://document360.com/blog/infobips-sara-tilly-on-workflow-management-for-documentation-success/
response
<urn:uuid:5f9ecfa9-f4f4-4594-a7e8-f860e5e5467b>
isPartOf: CC-MAIN-2023-06
publisher: Common Crawl
description: Wide crawl of the web for January/February 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-56
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/