From Clashing to Collaboration [On-Line Event]

14% of knowledge workers felt like striking a coworker in the past year but didn’t. If you are a technical writer, chances are that you were a potential target. Collaborative authoring comes at a price. It is also at odds with 87% of employees worldwide that are not engaged at work and 35.5 million European workers that report mental ill-being due to beating tight deadlines.

How, then, can we effectively author in collaboration with diverse professions and personalities? Technical writers tend to be precise; they naturally seek detail, correct errors, define terms with exactness, and question thoroughly. How can you manage stress when working with someone who generalizes, jumps to conclusions, makes changes without reasons, and races the clock?

In this presentation, you will learn how to:

  • Engage your document stakeholders effectively
  • Respond to different ways people collaborate
  • Have the freedom to be yourself at work

You will receive an introduction to a scientifically-verified framework that enables you to collaborate better on documentation projects.

Continue reading “From Clashing to Collaboration [On-Line Event]”

Who Are You? (I Really Wanna Know)

“Who is the audience for this project?” runs the risk of a smarty-pants response (“the user”). For a smart answer, take time to define and understand who is reading and using the information you develop.

In this TC Dojo session, we’ll talk about audience analysis: what it is, ways to do it, and how it adds value to projects.

Continue reading “Who Are You? (I Really Wanna Know)”

Writing (Non-Agile) Business Requirements

Writing requirements requires the ability to write clearly, concisely, and succinctly so others can design, develop, and test the product. This session covers 8 characteristics of writing a good requirement, reviews 4 steps to requirements gathering, and concludes with 17 tips for writing good requirements.

Come and learn how to craft a good requirement regardless of waterfall or agile approach. Yes, agile is a bit different, yet requires the same clarity, conciseness, and succinctness.

Continue reading “Writing (Non-Agile) Business Requirements”