Geeks: how to write for a non-technical audience

Technical writing and glasses “Two peoples divided by a common language.” George Bernard Shaw said this about the British and the Americans, but the same can be said of anoraks and suits.

I have been on both sides of the fence: first, as a computer games programmer and then as CEO of a development company; finally as a journalist writing about technology for magazines like Director and Wired.

Now I sit right on the fence as writer-in-chief at Articulate Marketing, a company dedicated to helping technology companies get their message across to business people. This mission is also the subject of this blog.

IT people need to speak to the rest of the world. Emails, reports, budget requests, proposals, pitches, websites, manuals, FAQs, etc. etc. Get it right and your clients will love you. Get it wrong and you will mystify customers and end-users alike.

Let me try to approach the problem from an engineering perspective. What are the failure modes when technical people start writing?

  • Too much ‘how’ and not enough ‘why’. I regularly see reports written by IT people that spend pages on the technical details of a particular solution but cover the benefits to the buyer in a short paragraph. It’s like a laptop review that tells you what the case is made of but doesn’t tell you if the machine is good value for money.
  • Too much detail. Completeness and accuracy are virtues that good software engineering instils. But sometimes 100 well-chosen words will make the point better than 2,000 words covering every detail. It’s a question of prioritisation – you have no right to your readers’ time.
  • Jargon and acronyms. It’s easy to scatter industry standard buzzwords and shorthand, assuming that every reader will know what they mean. Making assumptions about what readers know is dangerous.
  • Wanting to sound big and clever. Research shows that using short words make writers seem more intelligent, but many people think they have to use long words and complicated sentences to appear smart. Too much IT copy looks like the winner of an obfuscated code competition translated into English.

I want to take an engineering approach to solving the problems too.

  • Top down design. The Pyramid Principle (Barbara Minto) brilliantly describes how to persuade people through writing. Writing to Deadline (Don Murray) talks about how to construct an article and tell a story. Both books are short and sweet.
  • Get the syntax right. Check out the Economist Style Guide and The Elements of Style (Strunk and White) to learn how to write good, clean prose. These are like the Mythical Man Month – required reading.
  • Requirements analysis. What is your document trying to achieve? Who is it for? What are the constraints? A good specification is the foundation of all good writing.
  • Pick the right language for the job. Don’t think you have to write like a PhD thesis in order to seem authoritative. If you write what you know as if you were explaining it to an intelligent friend over coffee, you won’t go far wrong. Use everyday English words and short sentences.
  • User testing. I recommend three kinds of testing: read the article aloud to yourself. Does it sound like you? Is it natural? Does it make sense? Ask a non-technical friend or colleague to read it and check that they picked up on the main points you wanted to convey. Finally, try to find someone who can proofread it properly- it’s very hard to proofread your own work.
  • Optimisation. Most prose can benefit from liposuction. Generally cutting the word count by 10 percent will improve any text. If you’re writing for the web, aim for a 50 percent cut because people read slower online. Tools like Bullfighter and Microsoft word’s grammar checker provide readability metrics to guide you.
  • Best practice: Look at how newspapers and magazines convey information. They use short paragraphs, strong headlines, sidebars and boxed out quotations. They also write pithy opening sentences and strong final paragraphs. Do the same. And remember: paragraphs don’t crash and a syntax error in a sentence is embarrassing but not a bug.

30 Days to Better Business Writing
Get free email updates whenever we publish new posts on Bad Language.

No spam. Just essential marketing insights.

Sign up today and we'll send you a free copy of '30 Days to Better Business Writing' too.

14 Responses to Geeks: how to write for a non-technical audience

  1. nic mitham says:

    So true!

    I see this A LOT from companies based in Cambridge, UK. Cambridge is known as Silicon Fen due to the high number of high-tech companies based here (particularly from Cambridge University)…it’s also known as Biotech Basin..but that’s not important right now.

    Many high-tech companies are founded by the people that invented the technology….highly intelligent people. And sure, they understand what their product/service does, but that doesn’t mean anyone else will. I see this a lot when reviewing advertising/marketing messages pushed out by these companies….more often than not its the ‘what’ as opposed to the ‘how’…let alone the ‘why’ as opposed to the ‘how’.

    It’s the classic features vs benefit argument of technology marketing.

  2. It’s very rare to find a brilliant technician that is also a good communicator (written or other forms).

    It gets even worse when the tech-person needs to talk to a “hard-nosed” business type! I have spent most of my career translating between technicians and executives (fortunately for me I admire and respect both groups a great deal) – and it’s been challenging at times!

    Thanks for a great – “how to” on writing. We (even us non-techies) can all use it!

  3. ming says:

    I think sometimes engineers and artist or designers mystify their comunications on purpose… if you think about it there are benifits for doing this…

    would you buy a painting with no mystery?

  4. Craig says:

    I see this a lot when working on technical documentation with developers. They tend to be so close to the enhancements they’ve built into a program that they assume the benefits of using those enhancements are obvious. Then, when they draft instructional content on how to use those features, they forget to tie the details together and explain how the features work together so that the end-user of the product can complete a task.

    It takes a bit of empathy and marketing know-how; you have to determine what the other person really wants or needs to hear, not just what you are excited to talk about.

    Great tips, thanks!


  1. Storie di me - 23 September 2006

    Sì, sì, per favore, è da leggere…

    Come i geek dovrebbero scrivere (e parlare) per farsi capire…ODIO chi, per fare il figo, parla in tecninglese e si vanta delle facce stranite degli inermi ascoltatori…….

  2. iScatterlings » Blog Archive » Weekend Blogroll Round-Up - 24 September 2006

    […] 19. Bad Language – good article for geeks about how to write for non-tekkie people like me. Good one! Technobilge will be outed for the sham it is!! […]

  3. Work smarter not harder - 25 September 2006

    Scrivere come un ingegnere…

    Queste pillole sono uno dei frutti della mia passione per la scrittura che, da sempre, cerco di applicare nel mio lavoro quotidiano. La realizzazione di un progetto è un lavoro di squadra, nel quale gli specialisti coinvolti devono scambiarsi …

  4. Manage Your Writing - 26 September 2006

    No right to your readers’ time…

    Matt, at Bad Language, has great advice for geeks on how to write for a non-technical audience. My favorite sentence: You have no right to your readers’ time….

  5. וורדפרס עברית » ארכיון » המלצות קריאה לבלוגרים : מנועי חיפוש ובלוגים, ואיך לכתוב ללא-גיקים - 20 November 2006

    […] Geeks: how to write for a non-technical audience (מתוך Bad Language) – מדריך קצר-ארוך ומעניין לטכנולוגיים ביננו, שנדרשים לכתוב עבור אנשים חסרי ידע טכנולוגי וכיצד להסביר להם כיצד להפעיל את הדבר הארור הזה.זה תרגול מעניין בכתיבה במיוחד לרבים מאיתנו, שמגיעים עם רקע טכנולוגי כלשהו ומנסים להרחיב את קהל הקוראים שלנו לקצת פחות חנונים. […]

  6. Steve Clayton: Geek In Disguise - 27 November 2006

    Test your document’s readability…

    Emma just reminded me of this great hidden feature in Word. I attended one of Matthew’s excellent sessions…

  7. Marketing For Nerds - 11 December 2006

    How to write for a non-technical audience……

  8. Bad Language / Tools for writing: Economist Style Guide online - 2 January 2007

    […] For more on this subject. Check out my previous articles: Geeks: How to write for a non-technical audience and Surprise and delight: ten tips for writers. […]

  9. Bad Language / How NOT to lead geeks - 14 February 2008

    […] in my experience is "two peoples divided by a common language".  I wrote about Geeks: how to write for a non-technical audience and (in the opposite sense) How to write like a […]

  10. Useful links about writing plain English — Bad Language - 11 June 2009

    […] Geeks: how to write for a non-technical audience […]

Leave a Reply