Persuasive & Informative Writing: Techniques, Ethics & Audience Impact

TAKEAWAYS:

• Persuasive writing uses ethos, pathos, and logos to influence decisions, while informative writing prioritizes clarity and factual accuracy.
• Audience analysis determines tone, complexity, and structure—e.g., a bank’s loan terms for customers vs. internal compliance teams.
• Ethical dilemmas in technical writing include bias, transparency, and data integrity, requiring clear conflict-resolution strategies.
• Collaborative writing enhances credibility but introduces challenges like version control and stakeholder alignment.
• Visuals (tables, graphs, diagrams) simplify complex data—e.g., Daraz’s order status updates or Ncell’s billing breakdowns.
• Real-world examples show how persuasive writing sells products (e.g., eSewa’s security claims) and informative writing reduces errors (e.g., NTC’s traffic rule notices).

Core Concepts: Persuasive vs. Informative Writing

Technical writing often blends persuasion (to influence action) and information (to educate). The key difference lies in purpose and rhetorical appeal:

How They Work Together Even technical manuals (informative) may use persuasive elements to encourage compliance:

• Example: A Khalti security alert explains phishing risks (informative) but urges users to "Act now to avoid fraud!" (persuasive).

1. Persuasive Writing Techniques

Persuasive writing in technical contexts relies on three rhetorical appeals (Aristotle’s Rhetoric):

A. Ethos (Credibility)

Build trust by:

• Citing experts: "As recommended by Nepal’s Central Bank, use OTPs for all transactions."
• Showing authority: "Approved by Ncell’s cybersecurity team."
• Transparency: "Our data encryption meets ISO 27001 standards."

Real-World Example: Daraz’s Return Policy Daraz’s website uses ethos to reassure buyers:

"100% Secure Payments | 7-Day Easy Returns | Trusted by 10M+ Customers" → Why it works: Combines user testimonials (credibility) with clear policies (transparency).

B. Pathos (Emotion)

Trigger feelings to drive action:

• Urgency: "Your account is at risk—verify now!" (Khalti alert)
• Fear: "Unpatched software? Hackers can access your files." (Ncell warning)
• Empathy: "We know delays frustrate you—here’s how we’re fixing it." (Pathao customer update)

Worked Example: NEPSE’s Investor Advisory NEPSE sends emails like:

"Your portfolio is down 15%. Act now to diversify—our analysts recommend these low-risk stocks." → Pathos: Fear of loss + Logos: Data-driven advice.

C. Logos (Logic)

Use facts, data, and structure to convince:

• Statistics: "90% of data breaches start with a phished email." (Ncell training)
• Step-by-step reasoning: "If you don’t update your OS, your device will be vulnerable to Malware X."
• Comparisons: "Our cloud storage costs 40% less than Google Drive for businesses."

Real-World Example: eSewa’s Loan Pitch eSewa’s loan ads target logical and emotional triggers:

"Need ₹50,000 fast? Our 12% APR loan is approved in 2 hours—no collateral needed. Thousands of Nepalis trust us!" → Logos: Clear interest rate + Ethos: Social proof.

2. Informative Writing: Clarity and Precision

Informative writing avoids bias and focuses on:

• Accuracy: "The server downtime lasted 45 minutes (12:30–13:15 PM)."
• Conciseness: "To reset your password, go to Settings > Security > Reset."
• Visuals: Tables, flowcharts, or screenshots to explain processes.

Key Techniques

Real-World Example: NTC’s Traffic Rule Notice NTC uses informative writing to explain new rules clearly:

"From June 1, 2024, all vehicles must use lane discipline in Kathmandu. Violators will be fined ₹5,000. Why? To reduce accidents by 30%." → Structure: Rule → Penalty → Benefit (logos + pathos).

3. Audience Analysis: Tailoring Your Message

The same topic can be written five different ways depending on the audience:

Worked Example: Bank Loan Terms A bank’s loan agreement must be:

• Informative for the customer: "Your EMI will be ₹12,000/month for 36 months at 10% APR."
• Persuasive for the sales team: "This loan helps you buy a home—secure your future today!"

4. Ethical Dilemmas in Technical Writing

Technical writers often face ethical conflicts, especially in IT. Common dilemmas:

Steps to Handle Ethical Issues

1. Identify the conflict: Is the request legal, honest, and transparent?
2. Consult guidelines: Check company policies (e.g., Ncell’s Code of Ethics).
3. Seek alternatives: "Can we say ‘temporarily unavailable’ instead of ‘hacked’?"
4. Document decisions: Keep records if you push back.
5. Escalate if needed: Report to HR or legal (e.g., if forced to lie about safety).

Real-World Case: WhatsApp’s End-to-End Encryption WhatsApp’s persuasive marketing ("Messages no one else can read") aligns with ethical transparency—they prove their claims with open-source code reviews.

5. Collaborative Writing: Pros and Cons

Technical writing is rarely solo. Collaborative writing involves:

• Subject-matter experts (SMEs)
• Designers (for visuals)
• Editors (for clarity)
• Stakeholders (e.g., NTC traffic planners)

Real-World Example: Kathmandu Traffic Management Plan

• Collaborators: NTC engineers, city planners, UI designers.
• Process:
  1. Engineers draft technical specs (informative).
  2. Planners add persuasive elements ("This will cut congestion by 40%!").
  3. Designers create clear signage (visuals).
  4. Final review by legal/compliance teams.

6. Visuals in Persuasive & Informative Writing

Tables, graphs, and diagrams make complex ideas digestible. Examples:

A. Tables for Comparisons

Where Used: Bank loan comparison pages, Ncell’s plan selector.

B. Graphs for Trends

Example: NEPSE’s stock performance chart (persuasive + informative).

Stock Price (2023–2024)
   ₹5000 │●
         │  \
         │   \
   ₹4000 │    ● (Q3 Dip)
         │     \
         │      ● (Recovery)
   ₹3000 │________________→ Time

→ Persuasive: "See the recovery? Now’s the time to invest!" → Informative: "Q3 dip caused by global oil prices."

C. Flowcharts for Processes

Example: How to file a complaint on eSewa (informative).

flowchart TD
    A["Start"] --> B["Log in to eSewa"]
    B --> C["Go to 'Help Center'"]
    C --> D["Select 'File Complaint'"]
    D --> E["Choose issue type\n(e.g., Fraud, Delay)"]
    E --> F["Upload proof\n(screenshot, receipt)"]
    F --> G["Submit"]
    G --> H["Receive ticket #\n(e.g., #TW2024-001)"]
    H --> I["End"]

Exam Tip: How to Score Full Marks

This unit tests application, not memorization. Follow this 3-step formula for any question:

1. Define Clearly

   • Start with a one-sentence definition (e.g., "Persuasive writing uses rhetorical appeals to influence decisions while maintaining ethical standards.").
   • Example: For "Discuss the importance of ethics," begin:

     "Ethics in technical writing ensures trust, accuracy, and legal compliance, which are critical in IT where misinformation can cause financial or safety risks."

2. Use Real-World Examples

   • Nepal-specific: eSewa’s loan terms, NTC traffic rules, Ncell security alerts.
   • Global: Google’s AI ethics guidelines, WhatsApp’s encryption transparency.
   • Worked Example: If asked about audience analysis, compare:
     • Pathao driver update (urgent, simple) vs.
     • Daraz investor report (data-heavy, formal).

3. Structure Like a Pro

   • For "Advantages/Disadvantages": Use a table (as shown above).
   • For "Processes": List numbered steps with real examples.
   • For "Ethical Dilemmas": Use the 5-step resolution (identify → consult → seek alternatives → document → escalate).

Common Pitfalls to Avoid

• ❌ Generic answers: "Technical writing is important." → Why? Give an example (e.g., "Ncell’s manuals reduce customer calls by 30%.").
• ❌ Ignoring ethics: If asked about dilemmas, always suggest a solution (e.g., "A writer should disclose limitations to maintain transparency.").
• ❌ Overusing jargon: Explain terms like "ethos" in plain language ("Credibility—like when Ncell cites cybersecurity experts").

Sample Exam Questions & Model Answers

Question 1:

"Explain the role of audience analysis in technical writing. Provide an example of how understanding the audience affects the content and style of a document."

Model Answer: Audience analysis ensures the tone, complexity, and structure of a document match the reader’s knowledge level and needs. It directly impacts:

1. Language: Simple terms for Pathao drivers vs. technical jargon for Ncell engineers.
2. Persuasive vs. Informative Mix: A loan advertisement (persuasive) vs. a loan agreement (informative).
3. Visuals: Flowcharts for beginners (e.g., "How to set up Wi-Fi") vs. API specs for developers.

Example: NTC’s Traffic Notice

• Audience 1: General public (informative + urgent)

  "From June 1, 2024, all vehicles must use lane discipline in Kathmandu. Fine: ₹5,000. Why? To reduce accidents by 30%. How? Follow the new signs marked with blue arrows." → Style: Bold headers, emojis (if digital), simple steps.

• Audience 2: Traffic police (technical + directive)

  "New Rule 4.2(a): Enforce lane violations using GPS-tracked fines. Attach photo evidence to citations. Training on new signage (see Annex B) is mandatory by May 15, 2024." → Style: Legal terms, references to annexes, deadlines.

Impact:

• Public notice uses pathos (fear of fines) + logos (statistics).
• Police memo uses ethos (authority) + direct commands.

Question 2:

"Discuss the advantages and challenges of collaborative writing in technical documentation. How would you resolve conflicts in a team writing a user manual for a banking app like eSewa?"

Model Answer: Advantages of Collaborative Writing:

1. Accuracy: Subject-matter experts (e.g., eSewa’s security team) ensure technical correctness.
2. Speed: Multiple writers draft different sections (e.g., one for transactions, one for security).
3. Credibility: Approvals from legal, design, and compliance teams add trust.
4. Diverse Perspectives: A UI designer might suggest clearer buttons, while a customer support rep flags confusing steps.

Challenges:

1. Version Control: "Team A edited Section 3, but Team B’s changes got overwritten."
2. Divergent Opinions: "Should we say ‘tap here’ or ‘click next’?"
3. Miscommunication: "The SME assumed we’d include advanced features—now the manual is too complex for new users."
4. Bureaucracy: "We need 5 approvals before publishing!"

Conflict Resolution for eSewa’s Manual:

1. Use a Style Guide:

   • Agree on terms: "Always use ‘tap’ for mobile, ‘click’ for web."
   • Template for consistent structure (e.g., "Every step must have a screenshot").

2. Assign Roles:

   • Lead Writer: Finalizes content (e.g., "You").
   • SME Reviewer: Checks accuracy (e.g., eSewa’s security lead).
   • Designer: Ensures screenshots match the latest app version.

3. Tools for Collaboration:

   • Google Docs (real-time edits + comments).
   • GitHub for code-related sections.
   • Weekly syncs to align on progress.

4. Example Conflict: "Should we warn users about phishing in the manual?"

   • Solution:
     • Step 1: Security team provides data ("90% of fraud starts with phishing").
     • Step 2: Lead writer drafts a clear warning (informative) + persuasive call-to-action ("Enable 2FA now!").
     • Step 3: Legal reviews for compliance; designers add a visual alert icon.

Outcome: A user-friendly, accurate, and persuasive manual that reduces eSewa’s support tickets by 25%.

Key Formulas to Remember

1. Persuasive Writing Checklist:

   • Ethos (Who says it?) + Pathos (Why should I care?) + Logos (What’s the proof?).

2. Audience Analysis Framework:

   • Who reads it? → What do they know? → What do they need? → How should it be written?

3. Ethical Decision-Making:

   • Is it legal? → Is it honest? → Is it transparent? If no, escalate.

Real-World Applications Recap

Final Checklist Before Submitting

• Defined terms clearly (e.g., "Persuasive writing uses ethos, pathos, and logos").
• Used 2–3 real-world examples (eSewa, Ncell, Daraz, etc.).
• Compared formats (e.g., loan ad vs. loan agreement).
• Addressed ethical dilemmas with solutions.
• Structured answers logically (intro → examples → conclusion).
• Avoided jargon (explained terms like "rhetorical appeals" in simple language).