Be the first to like this
Technical Communicators are often the face or the voice of a technical organization. When users are in trouble, they go to the online help. When we admit we had a bug and have to fix it, users find out about it in the release notes. Whether we need to say "I'm sorry it's confusing" or "I'm sorry it's broken", we need a Technical Communicator to carry the message. This presentation will discuss some of my personal experiences when technical things go wrong and several meaningful yet fun ways I found for saying "I'm sorry" and "thank you for your understanding". This presentation involves toys!