Contents
Most technical writers consider terminology an important part of their work. However, the main objective of what terminology is supposed to achieve – if existent at all – is often too vague. As a result, terminology is pushed further and further back on the roadmap and eventually fails before any process can even begin. So, it’s not surprising to find out that most technical documentation teams are frustrated with their terminology process, according to our surveys. But what if the “classic” terminology process according to the waterfall model could be kept to a minimum? What if terminology could be up and running within a few days? This presentation is about an agile and pragmatic approach to terminology management without getting tangled up in complex details. Just like the agile approach in software development, we’ll start from the ground up and challenge the terminology principles we’ve all taken for granted so far.
Takeaways
- How to set up a lean terminology process without obstructing future additions.
- How to get terminology up and running quickly.
Prior knowledge
Basic knowledge in terminology management
Basic knowledge in technical writing