Creating a Job That Didn't Exist Before
Key point
Toss's Technical Writing Chapter is evolving beyond simple documentation into a role that designs the organization's knowledge infrastructure.
Details
Toss's Technical Writer(TW) role is expanding beyond simply writing documents to becoming someone who designs the organization's knowledge system. Unlike existing code, which leaves only the result behind, the key is preserving the Context of why the code was written that way.
To this end, Toss is shifting its work in the following directions:
- From documents to systems: Instead of waiting for users to come find documents, Toss builds knowledge systems like the chatbot 'Parksy', which provides answers within messengers or IDEs.
- Building knowledge infrastructure: Toss directly builds and operates 'Todoc', its internal knowledge management platform, serving as infrastructure that boosts organizational productivity.
- Adopting AI workflows: Toss reduces the amount of documentation people write by hand, and creates an environment where anyone can write and receive reviews on high-quality documents through AI and automation.
Ultimately, the TW's goal is to build a system where knowledge accumulates without people having to write documents themselves, thereby reducing the organization's communication costs and completing the SSoT(Single Source of Truth) for knowledge.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.