23.11.2013 Aufrufe

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

MEHR ANZEIGEN
WENIGER ANZEIGEN

Erfolgreiche ePaper selbst erstellen

Machen Sie aus Ihren PDF Publikationen ein blätterbares Flipbook mit unserer einzigartigen Google optimierten e-Paper Software.

User Assistance<br />

UA 4<br />

Presentation<br />

Addicted to Meaning: How Good Technical<br />

Communication is Like Bad Magic Tricks<br />

Kai Weber, SimCorp GmbH, Frankfurt<br />

Being meaningful is an essential, but elusive feature of good technical<br />

communication. This paper draws on the theories of semiotics and mental<br />

models to examine how meaning works in technical communication,<br />

why it sometimes fails and how you can improve its chance for success.<br />

Being meaningful in technical communication is just as essential as being<br />

correct and clear, concise or consistent: Understanding how and why<br />

communication is meaningful can help you to make your documentation<br />

more effective and to make your product more useful.<br />

What is meaning?<br />

Information theory posits a hierarchy of information which proceeds<br />

from data at the bottom via information and knowledge to wisdom at the<br />

top (Weinberger 1–5). For example, data is the sheer fact that the Microsoft<br />

Office 2007 software has an “Office button” icon in the upper left<br />

corner. The information that this icon gives you access to functions such<br />

as opening, saving, and printing a file helps you with generic functions.<br />

The knowledge that this functionality has replaced the habitually used<br />

File menu adds meaning and supports your active experience.<br />

So meaning occurs at the knowledge stage in this hierarchy when you<br />

make sense of data and information, when you “connect the dots” into<br />

something that you can apply purposefully. Meaning gives answers to<br />

questions such as “So what?”, “What does this mean for me, in my situation?”<br />

and “Why should I care?” (Cortada 4).<br />

Why should technical communicators care?<br />

Technical communicators should care about meaning, because we are<br />

in the business of creating meaning and transmitting it to users. We can<br />

provide all the data and information we want, if it is not meaningful<br />

to customers, it is wasted and dead. Any time documentation fails, it is<br />

either because meaning has not been created or not been transmitted<br />

successfully. Documentation that merely informs the user “To print a<br />

file, click the Print button” does not support the user in any active experience.<br />

It does not create any meaning if it omits the context, such as<br />

the task the user may be engaged in, the prerequisites and the expected<br />

results of the user’s action.<br />

How does meaning get transmitted in communication?<br />

The Mathematical Theory of Communications by Shannon and Weaver<br />

of 1949 explains communication as the transmission of messages that<br />

are broken up into small signals (see Fiske, ch. 1). A sender (a technical<br />

communicator) uses media (HTML files) via channels (the internet) to<br />

transmit messages to receivers (users). This model aims to show what<br />

keeps communication efficient and accurate.<br />

This technical model is clear, linear, and easy to understand. However,<br />

communication doesn’t really work this way beyond the very technical<br />

levels of a telephone cable, a radio wave, or a TCP/IP network. It’s only<br />

<strong>tekom</strong>-<strong>Jahrestagung</strong> <strong>2012</strong><br />

497

Hurra! Ihre Datei wurde hochgeladen und ist bereit für die Veröffentlichung.

Erfolgreich gespeichert!

Leider ist etwas schief gelaufen!