Key Concept Archive

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…

How to use root-cause analysis to promote information supply chain methodologies

If your documentation process is implicated in a customer quality incident (CQI), Congratulations! You have the platform needed to shine a light on the problems you’ve been escalating for years. In this presentation, Seth Park will argue that errors in documentation are actually symptoms of underlying data flow issues. If…

How to find the best content management system (or any other tool)

b Post Summary In this article, I hope I can convince you to gather requirements before you buy. It’s the only way to guarantee that you find the best content management system for you. Not for someone else. FOR YOU. Whenever you’re looking to buy more than a simple retail…

How do I Pick the Right Tool for Me?

So many tools to choose from! So many messages from so many vendors. Everyone saying they are the right one! One size does not fit all and one solution is not right for everyone! How could it?! How do you find the right one for you? You need to be…

What happens when you skimp on documentation?

In the TC Dojo last week we found out: Your company is at risk of debilitating lawsuits that, in the worst case, can put you out of business. Joe Devney, forensic linguist, editor, non-fiction writer, and previous STC chapter chair shared stories of companies who delivered insufficient, poorly-written documentation or who failed…

Unhappy Customers are Just the Beginning: Potential Costs of Skimping on Documentation

A perennial question in the technical communication community is how to justify our work in financial terms that management will understand. One partial answer is to consider potential consequences of putting insufficient resources into technical documentation. What happens if the material is poorly written, or not written at all? Consequences…

The Power of Single-Sourcing

Every day, technical communications professionals are faced with maintaining their current productivity in the face of increasing product complexity, increasing number of languages, increasing volume of documentation, increasing product overlap and shorter product life cycles. No matter how large or small, how new or how old your company is, or…

Influencing Change: Getting Stakeholder Buy-In When They Have The Power

Understand the answer to this one little question, “What’s in it for me?”, and I guarantee you will have the keys to the kingdom! – Enthusiastic support from others for an initiative you are interested in. – Motivated help in executing a plan. – Attentive listeners when you are presenting an…

Discovering the Hidden Treasure of Dynamic Product Information

Summary: After this presentation, you will be able to show those in the C-Suite how a transformative adoption in product information can differentiate your company in the market place and provide breakthrough results in driving shareholder value. Regardless of size or the number of years that a company has been…

Where Are They Now?

Summary: Stories of long-term Arbortext customers who are realizing the full potential of their solutions. There’s a software side to dynamic information delivery. We know this. Customers who have seen IBM talk have come to us and said “Sure, they can get there, but can I?” What if you’re not…