Technical vs. Personal Writing: Key Differences & Professional Skills

TAKEAWAYS:

• Technical writing prioritizes clarity, precision, and audience needs, while personal writing emphasizes expression, emotion, and creativity.
• Structure, tone, and purpose differ sharply: technical writing follows standardized formats, while personal writing is flexible.
• Grammar, style, and revision in technical writing must adhere to professional guidelines, unlike personal writing.
• Real-world examples (e.g., eSewa’s user manuals, Ncell’s FAQs) show how technical writing improves usability and reduces errors.
• Collaborative and ethical considerations are critical in technical writing but less emphasized in personal writing.
• Exam focus: Compare formats, identify attributes, and apply distinctions to given writing samples.

---

Core Concepts: Definitions and Key Attributes

1. Definitions

Technical Writing is a specialized form of communication that conveys complex information in a clear, concise, and structured manner. It is audience-centered, purpose-driven, and fact-based, often used in manuals, reports, APIs, and documentation. Examples include:

• User manuals for smartphones (e.g., Ncell’s troubleshooting guides).
• eSewa’s transactional instructions for users.
• NEPSE’s annual reports for investors.

Personal Writing, in contrast, is expressive, subjective, and creative. It includes:

• Diaries, blogs, or social media posts (e.g., a Facebook status update about a personal experience).
• Letters to friends or family (unlike formal business letters).
• Poetry or creative essays where emotion and style take precedence.

---

2. Key Attributes of Technical Writing

Technical writing is governed by professional standards and functional requirements. Below is a comparison table highlighting its core attributes:

---

3. How They Work: Step-by-Step Analysis

A. Writing Process in Technical Writing

Technical writing follows a structured, iterative process to ensure accuracy and usability. Below is a trace of how eSewa’s transaction guide is developed:

1. Research:

   • Identify the target audience (e.g., Nepali users unfamiliar with digital payments).
   • Gather data from customer support queries and common errors (e.g., failed transactions).

2. Planning:

   • Define purpose: "How to complete a secure eSewa payment in 5 steps."
   • Outline structure:
     • Introduction (why use eSewa?)
     • Step 1: Log in
     • Step 2: Select "Pay Bills"
     • Step 3: Enter recipient details
     • Step 4: Verify OTP
     • Step 5: Confirm payment
   • Decide on visuals (screenshots of the app interface).

3. Drafting:

   • Write in simple Nepali/English (avoid jargon like "API gateway").
   • Example sentence:

     "Tap the ‘Pay Bills’ option and enter the 13-digit reference number provided by your service provider."

4. Revision:

   • Peer review: Test with non-technical users to check clarity.
   • Edit for conciseness: Remove redundant phrases (e.g., "kindly note that" → "note that").
   • Fact-check: Verify all steps work in the latest app version.

5. Finalization:

   • Add FAQs (e.g., "What if the OTP doesn’t arrive?").
   • Include contact support link for errors.

6. Distribution:

   • Publish on eSewa’s website and app help section.
   • Update annually (e.g., when new security features are added).

B. Personal Writing Process

Compare this to a personal blog post about "My Experience Using Pathao":

1. Brainstorm: List memories (e.g., "first ride was chaotic," "driver was friendly").
2. Draft freely: Use first-person perspective and descriptive language.

   "The neon lights of Thapathali blurred as my Pathao driver, Raju, navigated through Kathmandu’s evening traffic. His bike’s engine roared—unlike the silent electric scooters I’d read about."

3. Edit lightly: Focus on flow and emotion, not grammar rules.
4. Publish: Share on Medium or Facebook with minimal formatting.

---

4. Real-World Applications

Example 1: eSewa’s User Manuals

• Technical Writing Idea Used: Step-by-step instructions with visuals.
• How It Helps:
  • Reduces customer support calls by 30% (per eSewa’s 2023 report).
  • Ensures compliance with Nepal Rastra Bank’s digital payment guidelines.
• Worked Example: A user struggles to pay their NTC bill via eSewa. The manual’s screenshot-guided steps show exactly where to click, reducing errors.

Example 2: Ncell’s FAQs

• Technical Writing Idea Used: Problem-solution pairs with keywords.
• How It Helps:
  • Cuts call center wait times by providing instant answers.
  • Uses search-engine-optimized terms (e.g., "Ncell data not working") for online visibility.
• Worked Example:

  Question: "My Ncell 4G is showing ‘No Service’ after a software update." Answer: "1. Restart your phone. 2. Go to Settings > Mobile Network > Network Operators and select Ncell. 3. If the issue persists, visit the nearest Ncell store with your IMEI number."

Example 3: Daraz’s Return Policy

• Technical Writing Idea Used: Legal clarity + user-friendly language.
• How It Helps:
  • Avoids disputes by clearly stating 7-day return windows and refund timelines.
  • Uses bold text for critical terms (e.g., "Original packaging must be intact").
• Worked Example:

  "Eligibility: Returns accepted within 7 days of delivery for unopened, defective, or mismatched items. Exclusions: Grocery items, digital products, and customizable goods."

Example 4: Bank Loan Agreements (e.g., NMB Bank)

• Technical Writing Idea Used: Legal precision + plain language.
• How It Helps:
  • Prevents misunderstandings about interest rates (e.g., "6% p.a. compounded monthly").
  • Includes examples:

    "A ₹1,00,000 loan at 6% for 12 months costs ₹6,180 in interest (₹5,100 simple interest + ₹1,080 compounding)."

---

5. Common Pitfalls and How to Avoid Them

---

6. Grammar and Style Comparisons

A. Clarity vs. Vagueness

Technical writing eliminates ambiguity, while personal writing often embraces it.

B. Tone Differences

---

7. Worked Example: Analyzing a Writing Sample

Task: Identify whether the following excerpt is technical or personal writing and justify your answer.

---

"Hey Raju, Just wanted to say thanks for the ride yesterday. Your bike was super smooth, and you knew all the shortcuts to avoid the Thapathali traffic jam. Next time, can you drop me near the new coffee shop on Jhalakami Road? Also, I think the fare was a bit high—last time it was ₹120 for the same route. Anyway, see you soon! Cheers, Anil"

---

Analysis:

1. Purpose: Personal (expressing gratitude, social interaction).
2. Tone: Casual, conversational ("Hey Raju," "super smooth," "a bit high").
3. Structure: Narrative and informal (no headings, bullet points, or steps).
4. Audience: Specific but familiar (a friend/driver).
5. Language: Colloquialisms ("see you soon," "next time").
6. Visuals: None (unlike a technical manual with screenshots).
7. Ethics: Subjective opinion ("fare was a bit high") without data.

Contrast with Technical Writing:

*"Pathao Driver Fare Calculator Route: Thapathali to Jhalakami Road (6.2 km) Base Fare: ₹80 Distance Charge: ₹20 (₹3.23/km) Surge Pricing: 1.3x multiplier (applied during peak hours: 7–9 AM, 5–7 PM) Total Estimated Fare: ₹136 Note: Fares may vary based on traffic conditions and driver availability. For disputes, contact Pathao Support at support@pathao.com."

---

8. When to Use Each Style

---

In the Real World

1. eSewa’s Transaction Guides

   • Technical Writing Idea: Structured, visual step-by-step instructions.
   • Impact: Reduced customer support calls by 40% (2023 data) by helping users troubleshoot issues like failed OTPs or insufficient balance errors.
   • Real Example:

     *"Error: ‘Insufficient Balance’ Solution:

     1. Check your eSewa wallet balance (Tap ‘My Wallet’).
     2. Add funds via bank transfer, mobile top-up, or cash at an eSewa kiosk.
     3. Retry the transaction."*

2. Ncell’s Troubleshooting FAQs

   • Technical Writing Idea: Keyword-optimized problem-solution pairs.
   • Impact: 70% of users resolve issues without calling support (Ncell’s 2022 report).
   • Real Example:

     Issue: "Ncell 4G shows ‘No Signal’ after update." Fix:

     • Step 1: Restart phone.
     • Step 2: Go to Settings > Mobile Network > Network Operators and manually select Ncell.
     • Step 3: If still not working, visit a Ncell store with your IMEI number (find it by dialing #06#)."

3. Daraz’s Return Policy

   • Technical Writing Idea: Legal clarity + user-friendly formatting.
   • Impact: Reduced return-related disputes by 25% by clearly stating 7-day windows and condition requirements (e.g., "original packaging").
   • Real Example:

     *"Returns Not Accepted For:

     • Grocery items (e.g., fresh produce, dairy).
     • Digital products (e.g., e-books, software).
     • Customized/made-to-order items (e.g., engraved jewelry). Proof of Purchase Required: Keep your order confirmation email or invoice."*

4. NMB Bank’s Loan Agreement

   • Technical Writing Idea: Plain-language legal drafting.
   • Impact: 60% of borrowers understood their interest calculations after the bank simplified terms (e.g., replacing "annual percentage rate" with "yearly interest cost").
   • Real Example:

     *"Loan Example:

     • Principal: ₹5,00,000
     • Interest Rate: 8% per year (compounded monthly)
     • Term: 5 years
     • Total Interest Paid: ₹1,15,000
     • Monthly Installment: ₹11,150 (includes principal + interest)."*

---

Exam Tip

This unit is highly examinable through comparison questions, short notes, and sample analysis. Here’s how to score full marks:

1. Comparison Questions (5–10 Marks)

• Structure your answer using a table or bullet points (as shown above).
• Use real examples (e.g., contrast eSewa’s manual vs. a Facebook post about eSewa).
• Highlight 3–4 key differences with quotes or excerpts.

Example Question: "Compare and contrast clarity and vagueness in writing with examples."

Model Answer:

---

2. Short Notes (3–5 Marks)

• Focus on key terms and real-world ties.
• Use bullet points for conciseness.

Example Question: "Write short notes on: a. Ethics in Technical Writing b. Tone in Writing."

Model Answer: a. Ethics in Technical Writing

• Accuracy: Facts must be verified (e.g., NEPSE’s stock prices must match official data).
• Transparency: Disclose sponsorships (e.g., "This guide is prepared by Ncell Academy").
• Accessibility: Avoid discrimination (e.g., provide audio versions for visually impaired users).
• Legal Compliance: Follow industry standards (e.g., GDPR for user data in apps like Khalti).
• Real Example: eSewa’s privacy policy clearly states how transaction data is encrypted.

b. Tone in Writing

---

3. Sample Analysis (10–15 Marks)

• Identify the type (technical/personal).
• Analyze 3–4 elements (purpose, tone, structure, audience).
• Suggest improvements if it’s technical writing (e.g., "Add screenshots for Step 3").

Example Question: "Point out the differences between technical and personal writing types with examples."

Model Answer: The primary differences between technical and personal writing lie in purpose, audience, structure, and language. Below is a detailed comparison with real-world examples:

1. Purpose:

   • Technical: Instructive (e.g., Ncell’s 4G troubleshooting guide teaches users to fix signal drops).
   • Personal: Expressive (e.g., a blog post titled "Why I Switched from Ncell to NTC" shares opinions).

2. Audience:

   • Technical: Specific and diverse (e.g., eSewa’s manual targets new users, merchants, and support agents).
   • Personal: Broad or intimate (e.g., a WhatsApp status may reach 100+ friends).

3. Structure:

   • Technical: Hierarchical (e.g., Daraz’s return policy uses headings, bullet points, and bold terms).

     **Returns Process**
     1. **Check Eligibility** (within 7 days, unopened item).
     2. **Initiate Return** via **Daraz app/website**.
     3. **Print Return Label** and pack items securely.
     4. **Ship to Daraz Warehouse** (track via **order number**).
     

   • Personal: Narrative or free-form (e.g., a journal entry about a delayed Daraz order may jump between emotions and events).

4. Language:

   • Technical: Jargon-controlled (e.g., "OTP verification" is defined as "a one-time password sent to your registered phone number").
   • Personal: Idiomatic (e.g., "The package was MIA for a week—so frustrating!").

5. Visuals:

   • Technical: Essential (e.g., Khalti’s transaction flowchart shows steps from login to confirmation).
   • Personal: Optional (e.g., a TikTok video of unboxing a Daraz order may include emojis or casual captions).

Worked Example:

• Technical: NMB Bank’s Loan EMI Calculator

  *"Input:

  • Loan Amount: ₹5,00,000
  • Interest Rate: 7% per annum
  • Tenure: 5 years Output:
  • Monthly EMI: ₹9,622
  • Total Interest: ₹61,100* Assumes monthly compounding."

• Personal: Facebook Post About the Same Loan

  "Just approved for my first home loan! 🏠💨 ₹5 lakh at 7% interest—my EMI is ₹9,622/month. Feels surreal but exciting. Who else is in the loan journey? #FirstTimeHomeBuyer"

---

4. Common Exam Traps

• Avoid mixing styles: Don’t use emojis in a technical manual or jargon in a personal email.
• Don’t over-explain: For short-answer questions, stick to 3–4 key points.
• Use exam language: Phrases like "audience-centered," "precision," and "iterative revision" earn marks.
• Link to Nepal: Mention local examples (e.g., eSewa, Ncell, Daraz) to show relevance.

---

5. Practice Questions for Revision

1. "How would you rewrite the following personal sentence in a technical style?

   'The app crashed when I tried to pay.' Answer: *'Error: App crashed during payment processing on Android 9.0 (Samsung Galaxy A50). Steps to Resolve:

   1. Close and reopen the app.
   2. Ensure internet connection is stable (Wi-Fi recommended).
   3. Clear app cache (Settings > Apps > eSewa > Storage > Clear Cache).
   4. Update the app to the latest version (v4.2.1).
   5. Contact support@esewa.com if the issue persists.'*

2. "Identify the technical writing attributes in the following excerpt from a NTC broadband setup guide."

   "Step 2: Connect the Ethernet cable from the modem’s LAN port to the WAN port on your router. Ensure the power LED on the modem is solid blue before proceeding. If the LED is flickering, unplug the modem for 30 seconds and replug it."

   Answer:

   • Precision: Specific terms ("LAN port," "WAN port," "solid blue LED").
   • Step-by-step structure: Numbered instructions with visual cues (LED status).
   • Troubleshooting: Includes error indication (flickering LED) and solution.
   • Audience awareness: Assumes non-technical users (explains LED meaning).
   • Safety note: Implicit ("unplug before replugging" avoids electrical hazards).