Technik und Fachkommunikation
Chapter Overview and Objectives
The pilot phase that Herr Brandt approved in Chapter 8 now needs documentation: the partner teams who will actually use the new communication routines have never heard of the research behind them, and they need a explanation they can act on rather than a summary aimed at leadership. Tobias is asked to write a short technical explanation of the routine for two audiences — the team members who will use it day to day, and the IT staff who must configure the scheduling tool that supports it — and to build a small glossary so both groups use the same terms consistently. The chapter introduces definition structures for naming and explaining a concept precisely, the compound chains typical of German technical prose, passive and imperative process style for describing steps, and the audience-adaptation skills needed to explain the same system differently to a lay reader and a specialist.
By the end of this chapter, you will be able to:
- Write precise definitions using standard German definition structures.
- Read and form multi-part compound chains and break them into their components.
- Describe a process using passive voice, impersonal constructions, and imperatives as appropriate.
- Adapt the same technical explanation for a lay audience and for a specialist audience.
- Build and use a small bilingual glossary consistently across a document.
- Explain a specialized system clearly without inventing terminology.
- Revise a technical explanation for terminological consistency and audience fit.
Opening Scenario
Frau Vogt asks Tobias to prepare two short documents before the pilot team's kickoff meeting: a plain-language explanation of the new communication routine for the team members who will follow it, and a slightly more technical note for the IT colleague who must configure the shared scheduling tool. Both documents must use exactly the same terms for the same concepts, so Tobias first drafts a small glossary, then writes each explanation, checking that neither version invents a term the other does not use.
- List the key concepts that both audiences need to understand and define each one precisely.
- Draft the plain-language explanation for team members using accessible compounds and clear process steps.
- Draft the technical note for IT using appropriately denser terminology and passive process style.
- Compare both drafts against the glossary and correct any inconsistent terms.
Core Vocabulary
This chapter's vocabulary supports technical explanation: the nouns used to name systems and their parts, the verbs used to define and describe processes, and the compound chains typical of German technical documentation.
Definition und Erklärung — Definition and Explanation
- der Begriff, die Begriffe — term, concept
- die Definition, die Definitionen — definition
- das Merkmal, die Merkmale — characteristic, feature
- die Bezeichnung, die Bezeichnungen — designation, name for something
- der Zusammenhang, die Zusammenhänge — connection, context
System und Prozess — System and Process
- der Ablauf, die Abläufe — procedure, sequence of steps
- die Einstellung, die Einstellungen — setting, configuration
- die Schnittstelle, die Schnittstellen — interface
- die Voreinstellung, die Voreinstellungen — default setting
- der Bestandteil, die Bestandteile — component, part
Nominalkomposita — Technical Compound Chains
- der Terminplanungsassistent, die Terminplanungsassistenten — scheduling assistant (tool)
- die Benutzeroberflächeneinstellung, die Benutzeroberflächeneinstellungen — user-interface setting
- die Kommunikationsroutinenvorlage, die Kommunikationsroutinenvorlagen — communication-routine template
- der Zugriffsberechtigungsstatus, (no common plural) — access-authorization status
- die Fehlermeldung, die Fehlermeldungen — error message
Zielgruppe und Erklären — Audience and Explaining
- die Zielgruppe, die Zielgruppen — target audience
- der Laie, die Laien — layperson
- die Fachkraft, die Fachkräfte — specialist, skilled professional
- das Glossar, die Glossare — glossary
- die Kurzanleitung, die Kurzanleitungen — quick guide, short instructions
All active nouns are given with article and plural where a plural is established. Compound chains are grouped separately to support the word-formation analysis below.
Delivery Focus: Compound Chains and Term Stress
Multi-part technical compounds such as Benutzeroberflächeneinstellung carry primary stress on the first component, with a lighter secondary stress on the head noun at the end. When reading such a compound aloud in a briefing, a brief pause after the first one or two recognizable components — Benutzer-oberflächen-einstellung — helps a listener parse the word into its parts without breaking the compound's status as a single word in writing.
When explaining the same term to a lay audience, it is often more natural to expand it briefly into a short phrase the first time it is used, for example die Einstellung der Benutzeroberfläche, also die Benutzeroberflächeneinstellung, before continuing to use the compound alone. This supports comprehension without changing the correct written form.
Grammar: Definitions, Compound Chains, Process Style, and Audience Adaptation
This chapter activates four interconnected writing and speaking targets: fixed structures for stating a definition precisely, the internal logic of longer compound chains, passive and imperative style for describing a process, and the deliberate adaptation of density and terminology to a specific audience.
Stating a Precise Definition
A technical definition names the term, places it in a category, and states the feature that distinguishes it from other members of that category. Skipping any of the three parts produces a definition that sounds authoritative but does not actually explain anything, which repeats, in technical language, the same failure a vague risk statement produced in Chapter 8's strategic writing.
Reading and Forming Compound Chains
Longer technical compounds are built by chaining components, each of which modifies the head noun that follows it, until the chain ends in the true head noun that carries the gender and plural of the whole word.
- Kommunikationsroutinenvorlage = Kommunikation + s + Routine(n) + Vorlage communication-routine template head noun: die Vorlage → die Kommunikationsroutinenvorlage
- Zugriffsberechtigungsstatus = Zugriff + s + Berechtigung + s + Status access-authorization status head noun: der Status → der Zugriffsberechtigungsstatus
Every component in a chain must be independently verifiable, and the linking elements between components (such as the -s- in Kommunikationsroutine) follow established patterns rather than the writer's preference. When a new compound is genuinely needed for a system that has no established German term, mark it explicitly as an author-created working term rather than presenting it as standard usage.
Passive, Impersonal, and Imperative Process Style
German technical documentation typically describes a process either impersonally, with passive voice foregrounding the action rather than the actor, or directly, with imperatives addressing the person carrying out the steps. The choice depends on genre and audience.
- Die Voreinstellung wird im Menü "Optionen" geändert. (passive, describing what happens, suitable for a specification document)
- Ändern Sie die Voreinstellung im Menü "Optionen". (imperative, addressing the user directly, suitable for a quick guide)
- Mixing both styles within the same short document without reason makes the text feel inconsistent; choose one dominant style per document and use the other only for deliberate emphasis.
Model Text: Technical Explanation and Glossary Excerpt
Two short excerpts from Tobias's documents: the plain-language explanation for team members, followed by the corresponding technical note for the IT colleague.
Guided Practice
- Identify the three parts of the definition given for "der Terminplanungsassistent" in the model text.
- Break "Benutzeroberflächeneinstellung" into its components and identify the head noun and its gender.
- Compare the two versions of the model text and list every place where the same glossary term is used consistently.
- Identify one sentence in the "Für die IT" version that uses passive voice, and rewrite it using an imperative addressed directly to the IT colleague.
- Explain why the team-facing version uses shorter sentences and fewer stacked compounds than the IT-facing version.
Listening Practice
Ask a partner, instructor, or text-to-speech tool to read the following passage aloud. Listen once for overall meaning, then again for the compound terms and process verbs used.
Frau Vogt zur guten technischen Erklärung — Listening Script
Eine gute technische Erklärung verwendet für denselben Begriff immer dieselbe Bezeichnung, egal ob man sie einem Laien oder einer Fachkraft gibt. Für Laien sollte man einen Fachbegriff beim ersten Gebrauch kurz erklären; für Fachkräfte kann man ihn ohne Erklärung verwenden. Wichtig ist, dass niemand rät, was ein Begriff eigentlich bedeutet.
Verständnisfragen
1. According to Frau Vogt, what should stay the same regardless of the audience?
2. What should a writer do the first time a specialist term is used for a lay audience?
3. Warum sollte laut Frau Vogt niemand raten müssen, was ein Begriff bedeutet?
Speaking Practice
Aufgabe: Ein System zwei Zielgruppen erklären
Working with a partner, a small group, or by recording yourself, explain the scheduling assistant orally twice: once to a partner playing a team member with no technical background, and once to a partner playing an IT colleague, using the same glossary terms consistently in both versions.
Rolle: Erklärende Person
- Define each key term before using it with the lay audience.
- Use denser compounds and passive process style with the specialist audience.
- Use exactly the same glossary term for the same concept in both versions.
Rolle: Teammitglied oder IT-Fachkraft
- Ask for clarification if a term is unclear or inconsistent.
- Request a concrete next step or setting to check.
- Point out if the same concept was named two different ways.
Bewertungshinweise — Speaking Criteria
- Defines key terms clearly for the lay audience before using them.
- Adjusts compound density and process style appropriately for each audience.
- Uses glossary terms consistently across both versions.
- Responds to requests for clarification without inventing new terminology.
- Parses long compounds clearly enough for the listener to follow.
Solo alternative: Record both versions of your explanation, then listen back and check that every glossary term appears identically in each recording.
Reading Practice
Kurzanleitung: Terminplanungsassistent einrichten
Öffnen Sie zunächst die Benutzeroberflächeneinstellung und prüfen Sie den Zugriffsberechtigungsstatus jedes Teammitglieds. Wählen Sie anschließend die passende Kommunikationsroutinenvorlage aus der Liste aus und bestätigen Sie die Auswahl. Erscheint dabei eine Fehlermeldung, überprüfen Sie zunächst, ob die Vorlage bereits einem anderen Team zugewiesen wurde.
Verständnisfragen
1. Welche zwei Schritte sollen laut Text vor der Auswahl der Vorlage erfolgen?
2. Identify the sentence style used throughout this quick guide (passive or imperative) and explain why it suits this genre.
3. Based strictly on the text, write one sentence explaining what to check first if an error message appears.
Writing Workshop
Complete the two documents Frau Vogt requested: a plain-language explanation for team members and a technical note for IT, both built from a shared glossary of four to six terms.
Aufgabe — Task
Erstellen Sie zunächst ein kurzes Glossar mit vier bis sechs zentralen Begriffen. Schreiben Sie anschließend zwei kurze Erklärungen desselben Systems: eine für Laien mit klaren Definitionen und Imperativen, und eine für Fachkräfte mit passivem Prozessstil und dichteren Komposita. Verwenden Sie in beiden Versionen dieselben Begriffe aus dem Glossar.
Die drei Teilaufgaben — The Three Sub-Tasks
- Glossar: define four to six key terms precisely, each with term, category, and distinguishing feature.
- Laienversion: write a short explanation using clear definitions and imperative steps.
- Fachversion: write a short explanation using passive process style and denser compounds.
- Choose a system or tool (real or invented for the task) and list its key concepts.
- Draft a precise definition for each concept using the term–category–feature structure.
- Write the lay-audience version, expanding any dense compound briefly at first use.
- Write the specialist-audience version, using passive process style and full compounds.
- Compare both versions against the glossary and correct any inconsistent terms.
- Reread both versions and confirm that no sentence in either version invents an unverified compound.
- Revise for concision, cutting any sentence that repeats information already given.
Revision checklist:
- Does every glossary term appear identically in both the lay and specialist versions?
- Does each definition include a term, a category, and a distinguishing feature?
- Have I chosen one dominant process style per document rather than mixing both without reason?
- Have I verified every compound rather than inventing one to fill a gap?
- Would a true beginner understand the lay version, and would a specialist find the specialist version efficient?
Culture and Communication
Technical writing in German-speaking workplaces, as elsewhere, is expected to reflect the actual configuration of the system being described rather than a plausible-sounding approximation. A confident, well-formed technical compound does not substitute for verifying that the underlying feature, setting, or step actually works as described. Readers in Germany, Austria, and Switzerland generally expect technical documentation to be checked against the real system before distribution.
When a genuinely new concept has no established German term, careful technical writers mark their proposed term explicitly as a working label rather than presenting it as standard usage. Inventing terminology silently, even when the compound is grammatically well formed, risks creating confusion across a team that later encounters the standard term elsewhere.
Common Mistakes to Recheck
Error: A learner writes "Der Terminplanungsassistent ist ein Werkzeug" and stops, without stating what makes it different from any other tool.
Correction: Add the relative clause that names the distinguishing feature, as in "...das Teammitgliedern hilft, gemeinsame Termine automatisch zu koordinieren."
Error: A learner calls the same setting "die Einstellung" in one paragraph and "die Konfiguration" in another, without signaling that these refer to the same thing.
Correction: Fix one glossary term per concept before drafting, and use that exact term consistently throughout both audience versions.
Error: A learner creates a plausible-looking compound by translating an English technical term word for word, without checking whether the German term is actually used.
Correction: Verify technical compounds against a dictionary, established documentation, or a subject specialist, and mark any genuinely new coinage explicitly as a working term.
Chapter Summary
Chapter 9 moved Tobias's writing into specialized technical communication: stating precise definitions with term, category, and distinguishing feature; reading and forming compound chains without inventing unverified terms; choosing between passive and imperative process style depending on genre; and adapting the same technical content for a lay audience and a specialist audience while keeping terminology consistent across both versions.
Chapter Review
Before moving to Chapter 10, confirm that you can:
Analyse
- identify whether a definition includes a term, category, and distinguishing feature;
- break a technical compound chain into its components and identify the head noun;
- recognize whether a text uses passive or imperative process style, and why; and
- check whether two versions of the same explanation use terminology consistently.
Produktion
- write precise definitions using the term–category–feature structure;
- form and verify technical compound chains without inventing terms;
- choose passive or imperative process style appropriately for a genre; and
- adapt a technical explanation for a lay audience and a specialist audience consistently.
Practical Performance Task
Kapitel 9 — Praktische Aufgabe
Technische Erklärung mit Glossar und Zielgruppenanpassung — Technical Explanation with Glossary and Audience Adaptation
Complete the glossary and two audience versions described in the Writing Workshop, then present both versions orally using the Speaking Practice task above.
1. Begriffe festlegen
Define four to six key terms precisely for the glossary.
2. Für Laien erklären
Write a clear, imperative-style explanation for a non-technical audience.
3. Für Fachkräfte erklären
Write a denser, passive-style explanation for a specialist audience.
4. Konsistenz prüfen
Check both versions against the glossary and present them orally.
| Criterion | What to look for |
|---|---|
| Definition quality | Each glossary term has a term, category, and distinguishing feature |
| Compound accuracy | Compound chains are correctly formed and verified, not invented |
| Process style | Passive or imperative style is chosen deliberately and used consistently per document |
| Audience adaptation | Lay and specialist versions differ appropriately in density and explanation |
| Terminological consistency | The same glossary term is used for the same concept across both versions |
| Scope discipline | Explanation stays within language and communication goals; no certification-level instructions given |
Answer Key
Guided Practice
- Term: "der Terminplanungsassistent"; category: "ein Werkzeug"; distinguishing feature: "das Teammitgliedern hilft, gemeinsame Termine automatisch zu koordinieren."
- Benutzer + Oberfläche(n) + Einstellung; head noun: die Einstellung → die Benutzeroberflächeneinstellung.
- "Terminplanungsassistent," "Benutzeroberflächeneinstellung," "Zugriffsberechtigungsstatus," and "Kommunikationsroutinenvorlage" all appear identically in both versions.
- "Die Voreinstellung wird im Menü 'Optionen' geändert" is not present verbatim, but the IT version's passive constructions (e.g., "wird ... verwaltet," "muss ... hinterlegt werden") could be rewritten as "Verwalten Sie ... " or "Hinterlegen Sie die Vorlage einmalig."
- Open production; a good answer notes that the team-facing version avoids stacking multiple compounds in one sentence and defines terms briefly, while the IT version assumes familiarity with the terminology.
Listening Practice — Comprehension Questions
- The designation used for a given concept should stay the same regardless of audience.
- The writer should briefly explain a specialist term the first time it is used for a lay audience.
- So that no one has to guess what a term actually means, which would undermine clear communication.
Reading Practice — Comprehension Questions
- Man soll zuerst die Benutzeroberflächeneinstellung öffnen und den Zugriffsberechtigungsstatus jedes Teammitglieds prüfen.
- The guide uses imperative style ("Öffnen Sie," "wählen Sie," "bestätigen Sie," "überprüfen Sie"), which suits a quick guide addressed directly to the user performing the steps.
- Open production; a good answer states that one should first check whether the template has already been assigned to another team.
Speaking and Writing
Open production. Evaluate using the performance task criteria table above, with particular attention to definition quality, compound accuracy, and terminological consistency across both audience versions.
Independent Study Tools
Für Selbstlerner
- Find a short German-language product manual or software help page and identify its key definitions and compounds.
- Practice breaking three long compounds from a technical text into their components and identifying the head noun.
- Choose a familiar app or tool and write one definition and one process step for it, checking your compounds in a dictionary.
Selbstüberprüfung
- Does every definition I wrote include a term, category, and distinguishing feature?
- Have I verified my compounds rather than translating an English term word for word?
- Would a lay reader and a specialist reader each find their version of my explanation clear and appropriately detailed?
Looking Ahead
Was Sie nach Kapitel 9 können — What you can do after Chapter 9
You can now write precise term–category–feature definitions; read and form technical compound chains without inventing terminology; choose passive or imperative process style deliberately; and adapt the same technical explanation for a lay audience and a specialist audience while keeping terminology consistent. Chapter 10 draws together the academic, organizational, and technical communication developed across Chapters 6 through 9 into a single specialized report assessment.