1.3 Types, Styles & History of Technical Communication

Types of Technical Communication

Technical communication takes many forms — different purposes call for different types. The most-used classification:

Some sources classify differently

Other valid classifications you may see in textbooks:

• By direction — internal (within org) vs external (to clients/public)
• By mode — oral vs written vs visual
• By formality — formal vs informal
• By time-sensitivity — synchronous (live) vs asynchronous (delayed)

All are valid; pick the framework that fits the question.

---

Styles of Technical Communication

Within technical communication, the style (tone, register, formality) depends on the audience and purpose.

Choosing the right style

   ┌─────────────────────────────────────────────────┐
   │ Audience: who reads / hears this?              │
   │ Purpose: what should they do after?             │
   │ Relationship: how formal is your equation?      │
   │ Permanence: is this on record?                  │
   │ Cultural setting: which norms apply?            │
   └─────────────────────────────────────────────────┘
                          ↓
                    Pick the style

A common mistake by fresh graduates: writing client emails in the same casual style they use on WhatsApp. Match the style to the situation.

---

Technical Communication Skills

A complete technical communicator has skills in all four modes (listening, speaking, reading, writing) plus visual / digital skills.

The LSRW model

Additional modern skills

A balanced communicator is roughly equally strong in LSRW + visual + digital. Most learners lean strong in one or two — recognising your weak areas and practicing them is half the work.

---

Language as a Tool of Communication

Language is the primary tool of communication, but not the only one. Treating language as a tool means:

1. The right tool for the job — pick the right language, level of formality, and vocabulary
2. Mastery improves outcomes — vocabulary, grammar, structure matter
3. Tools have limits — when language fails, switch channels (visual, demo, in-person)
4. Tools evolve — language changes; technical English in 2025 differs from 1995

English as a global business language

English is the dominant language of global business and technology. For Indian students, fluency in English is the biggest single career multiplier — not because English is intrinsically superior, but because it is the agreed-upon medium of international commerce, technical documentation, and academic research.

Some realities:

• ~85% of scientific papers are in English
• ~60% of internet content is in English
• Most software documentation is English-first
• Most outsourcing contracts assume English fluency

Building strong English communication is therefore one of the highest-ROI skills for any Indian technical professional. It does not require abandoning your mother tongue — bilingual / multilingual professionals are the strongest.

Indian English

Indian English is a recognised, legitimate variant of English with its own dictionary entries. Words like prepone, cousin-brother, out-of-station are Indian English usage — fine in informal context, but international audiences may need clarification. Develop awareness of:

• Vocabulary that's purely Indian (timepass, jugaad, kindly do the needful*)
• Grammar habits that differ (use of will be doing for present continuous)
• Pronunciation patterns (the r in parking, th sound, v vs w)

This is not about "fixing" your English — it's about calibrating it to the audience.

---

History and Evolution of Technical Communication

Technical communication is as old as technology itself.

Key shifts

• From printed manuals to searchable online docs
• From broadcast (one-to-many) to conversational (one-to-one at scale, via chatbots)
• From document-centric to task-centric (help me do X, not read all docs)
• From English-only to multilingual (auto-translation, localised docs)
• From specialist writers to every engineer contributes (docs-as-code)

---

Computer-Aided Technical Communication (CATC)

Modern technical communicators rely heavily on software tools. The major categories:

1. Writing and editing

2. Documentation platforms

3. Visual / diagram

4. Collaboration

5. Translation / Localisation

Impact of computer-aided tools

The trade-off: tools make production faster but can mask weak fundamentals. A document with perfect grammar can still be useless if the content is unclear. Tools amplify; they don't replace skill.

---

Study deep

1. Style is audience times purpose. Two questions answer 80% of style decisions: who is reading this? and what should they do after? Get those clear; the style follows.

1. The LSRW skills are non-redundant. Strong writing does not guarantee strong speaking — different muscle. Strong reading does not guarantee strong listening. Practice each separately.

1. Indian English is not a deficiency. It's a recognised dialect (Oxford English Dictionary acknowledges Indian English). But cross-cultural calibration is a skill: when audience changes, vocabulary should adjust.

1. AI writing tools are a force multiplier, not a substitute. ChatGPT can draft a passable email in seconds, but the judgement of what to say and whether it's right belongs to you. Use AI to draft; you do the editing and confirming.

1. Documentation is increasingly "first-class" engineering. Modern dev orgs treat docs as code — version-controlled, peer-reviewed, deployed via CI/CD. The line between "writer" and "engineer" is blurring.

Key Terms — Lesson 1.3

The terms below cover communication types, styles, language as a tool, history, and the modern tools landscape — every Unit-I PYQ on these expects fluent use.

Types of Technical Communication — The high-level categories grouped by purpose: informative (sharing facts — reports, summaries, briefings), instructional (teaching procedures — user manuals, SOPs, tutorials), persuasive (changing opinion or behaviour — proposals, pitches), documentation (recording for future reference — specs, design docs, postmortems), promotional (marketing technical products — datasheets, case studies).

Informative Communication — Communication that shares facts and updates — status reports, briefings, news, summaries. The reader's job is to understand, not necessarily to act.

Instructional Communication — Communication that teaches how to do something — user manual, SOP, recipe, tutorial. Structured as a sequence of imperative steps, often with diagrams. Tested with the simple criterion: can the reader actually do the task after reading?

Persuasive Communication — Communication aimed at changing a reader's opinion, decision, or behaviour — sales proposals, investor pitches, internal proposals for budget. Uses evidence, social proof, and emotional appeal balanced with logic.

Descriptive Communication — Communication that paints a vivid, detailed picture of an entity, process, or scene — product description, scene-setting in a report, location overview. Heavy on sensory and specific language.

Persuasive vs Informative — A common exam contrast. Informative = present the facts neutrally; persuasive = lead the reader to a desired conclusion. Persuasive content is still grounded in facts but emphasises selectively and frames intentionally.

Communication Style — The manner of communication, independent of content. Common styles: formal (polished, structured, official), semi-formal (professional but conversational), informal (casual, friendly), persuasive (advocacy-leaning), descriptive (vivid, detailed).

Formal Style — Polished, structured, follows conventions; used for on-record official communications — reports, contracts, official letters, board presentations. Avoids contractions and slang; uses complete sentences and proper salutations.

Semi-Formal Style — The default register for most professional communication today — email to a colleague, project status update, meeting summary. Polite and structured but conversational, allowing some contractions and lighter sentence forms.

Informal Style — Conversational, casual; used in friendly contexts — Slack messages between teammates, casual emails, internal chat. Allows slang, emoji, ellipsis. Inappropriate for clients, regulators, or external stakeholders.

LSRW Skills — The four core language skills: Listening, Speaking, Reading, Writing. Each is a separate competence — strong reading does not guarantee strong listening; strong writing does not guarantee strong speaking. Each requires deliberate practice.

Listening Skill — Active, attentive reception of spoken communication. Distinguished from hearing (passive reception). Includes following the argument, noticing tone, asking clarifying questions, and remembering. The most-underrated communication skill.

Speaking Skill — Clear, organised, audience-appropriate oral expression. Includes pronunciation, pace, tone, body language, and structure. Critical for interviews, presentations, meetings, sales, and leadership.

Reading Skill — Comprehending written text with appropriate speed and depth. Includes skimming (fast overview), scanning (specific information), intensive reading (deep understanding), and critical reading (evaluating arguments).

Writing Skill — Producing clear, structured, audience-appropriate written communication. The most permanent of the four — what you write follows you. The single most-tested skill in technical-communication exams.

Indian English — A recognised variety of English with its own vocabulary ("prepone", "good name", "do the needful"), spellings (British-derived), and idioms. Acknowledged by the Oxford English Dictionary. Effective communicators calibrate between Indian, British, and American English depending on audience.

Standard English — The variety taught in formal education and used in international business — typically based on either British English (most of the Commonwealth) or American English (US-led companies). Indian academic and business communication generally follows British conventions with growing American influence.

Style Guide — A document defining an organisation's conventions for written communication — terminology, formatting, capitalisation, punctuation, citation style. Examples: Chicago Manual of Style, AP Stylebook, Microsoft Style Guide, Google developer documentation style guide, Indian Express Style Manual. Internal style guides ensure consistency across teams and time.

Localisation — Adapting communication for a specific locale — language, dialect, cultural references, units, dates, currency. Different from translation: localisation considers context. Crowdin, Lokalise, and Transifex are dominant localisation platforms.

Translation vs Localisation — Two related but distinct activities. Translation converts words from one language to another. Localisation adapts the entire experience — translation plus cultural calibration, format adjustment, regulatory compliance.

Computer-Aided Communication Tools — Software that supports the production, editing, and distribution of communication. Five broad categories: writing assistants (Grammarly, Hemingway, ChatGPT), documentation platforms (Confluence, Notion, Docusaurus, MkDocs), visual / diagram (Canva, Figma, Mermaid, Lucidchart), collaboration (Slack, Teams, Zoom), translation / localisation (DeepL, Crowdin).

Grammarly — A widely-used writing assistant that checks grammar, spelling, style, tone, and clarity in real time. Browser extension and standalone editor; free and Premium tiers. The de-facto standard for individual writers needing surface-level proofing.

ChatGPT / Claude / Gemini — Large Language Model (LLM) AI assistants that can draft, edit, summarise, translate, and adapt technical text. Powerful as draft generators and editing accelerators; require human review for accuracy and judgement. Increasingly integrated into writing platforms (Notion AI, Docs Gemini, etc.).

Documentation as Code (Docs-as-Code) — A modern practice where technical documentation is written in plain text (Markdown, AsciiDoc), version-controlled in Git, reviewed via pull requests, and deployed via CI/CD like software. Tools: MkDocs, Docusaurus, Sphinx, GitBook, Read the Docs. Treats documentation as a first-class engineering deliverable.

Markdown — A lightweight plain-text markup language invented by John Gruber (2004) that uses simple syntax for headings (#), emphasis (bold, italic), lists, links, and code. The de-facto format for technical writing today (GitHub, Stack Overflow, Slack, Reddit). Can be rendered to HTML, PDF, or other formats.

Mermaid / PlantUML — Text-based diagramming languages that generate diagrams (flowcharts, sequence diagrams, ER, Gantt) from a simple syntax. Lets diagrams live in the same plain-text source as documentation, version-controlled with the code.

Knowledge Base — An organised, searchable central repository of an organisation's documentation — internal processes, customer-facing help, technical references. Tools: Confluence, Notion, Coda, Zendesk Guide, Helpscout Docs.

Single-Source Publishing — Writing content once and publishing it to multiple formats (web, PDF, app help, print) from the same source. Achieved by tools like MadCap Flare, Sphinx, MkDocs. Eliminates the maintenance cost of keeping multiple format variants in sync.

History of Technical Communication — Tracable through milestones: ancient Egyptian / Babylonian instructional texts (irrigation manuals), Vitruvius's De Architectura (~25 BCE — Roman engineering text), medieval craft manuals (apothecary, masonry), the printing-press explosion (Gutenberg 1450), industrial revolution (machine manuals), 20th-century technical writing as a profession (Society for Technical Communication founded 1953), digital era (online help, web docs, AI assistance).

---

Common exam question: "Discuss types and styles of technical communication." — Define types (informative, instructional, persuasive, documentation, etc.) with examples; define styles (formal, semi-formal, informal, persuasive, descriptive) with examples; close with how style depends on audience + purpose.

Common exam question: "What is language as a tool of communication? Discuss its role." — Treat language as the primary tool; pick the right level for the audience; English as global business language; mention Indian English calibration.

Common exam question: "Discuss the impact of computer-aided tools on technical communication." — List 5 tool categories (writing, docs, visual, collaboration, translation); contrast "before vs after"; mention AI's growing role; close with "tools amplify skill, not replace it."

Self-check

Test your grip on types, styles, and the digital-era timeline.

1. Name four types of technical communication by purpose. (informative, instructional, persuasive, documentation)
2. List the three broad styles by formality. (formal, semi-formal, informal)
3. What does "Docs-as-Code" mean in one line? (documentation written in plain text, version-controlled in Git, reviewed and deployed like software)
4. Who invented Markdown, and in what year? (John Gruber, 2004)
5. Which 1953-founded body professionalised technical writing? (Society for Technical Communication)
6. Complete the principle: tools amplify skill, they do not ___ it. (replace)