<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by David Willenberg on Medium]]></title>
        <description><![CDATA[Stories by David Willenberg on Medium]]></description>
        <link>https://medium.com/@DetroitEnglish?source=rss-42928103790e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Pazm0nn57lnfSVRjUeG5UQ.jpeg</url>
            <title>Stories by David Willenberg on Medium</title>
            <link>https://medium.com/@DetroitEnglish?source=rss-42928103790e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:49:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DetroitEnglish/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Technical English Vocabulary: 5 reasons why you should never study words.]]></title>
            <link>https://medium.com/@DetroitEnglish/technical-english-vocabulary-5-reasons-why-you-should-never-study-words-cd2a4759039f?source=rss-42928103790e------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd2a4759039f</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[language-learning]]></category>
            <category><![CDATA[language]]></category>
            <dc:creator><![CDATA[David Willenberg]]></dc:creator>
            <pubDate>Thu, 21 Apr 2016 17:35:57 GMT</pubDate>
            <atom:updated>2016-04-23T17:12:54.159Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FEno0pUxYCPojVqCjVhC5w.png" /></figure><h4>If you’re learning English for engineering, then learn like an engineer — put down the flashcards, and focus on efficiency.</h4><p>Compare it to all the other flavors, and it doesn’t take an engineer to spot the differences that make technical English a whole other animal.</p><p>The consequences of mistakes are one of the most glaring; they can be <em>really</em> expensive. But so are mistakes in English if you’re, say, an accountant…</p><p>So maybe <em>costly </em>is a better fit here.</p><p>Because when engineers fail to communicate, <strong>people can die</strong>. Besides mafia bookies, I doubt many accountants have to worry about that.</p><p>Another aspect that makes technical English unique is how difficult it is to practice on your own. For example:</p><p>If you want to practice your business English, that’s easy — head to any Irish pub in or near your city’s business district, because that’s where all the English-speaking business travelers hang out. Just look for a guy in a suit, buy him a round and start <em>schnacken</em>.</p><p>Want to improve your English for wastewater engineering? No problem — just attend your local “English-Speaking Wastewater Engineers” meetup and spend a cozy evening talking shi-</p><p>Oh, wait — those don’t exist. Anywhere.</p><h3>A different engineer, a different language</h3><p>But more than anything, what makes technical English so challenging (both to learn <em>and</em> to teach) is the vocabulary.</p><p>Practical vocabulary is entirely different for every engineer, and depends 100% on one’s field, role and project requirements. Even engineers on the same project team might need totally different terms in their <em>Wortschatz</em>.</p><p>So understandably, this is what most new subscribers to <a href="https://www.detroit-english.de/vds-newsletter/anmelden"><em>Vorsprung durch Sprache</em></a> tell me they struggle with above all else.</p><p>Well, after almost seven years of teaching engineers in everything from <em>Abwasser </em>to <em>Zyklonfiltertechnik</em>, the best advice I can give you for learning technical English vocabulary is:</p><p><strong>Stop worrying about it so much.</strong></p><p>Sound crazy? Let me give you five reasons why: </p><h4>1. Words are always available</h4><p>I had a math teacher in high school who never allowed us to use calculators on our exams. His reason was that we “wouldn’t go through life always carrying a calculator in our pockets.”</p><p>Well, he was right — I don’t. I carry a small Linux computer instead.</p><p>And chances are that you carry a smartphone in your pocket, too.</p><p>Gone are the days of sitting on the bus and wondering to yourself, ‘which dinosaur had the biggest head?’, and needing a special trip to the library to find out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ih5pch0EEZ6rwGtEMjF0KA.jpeg" /><figcaption>Torosaurus: King of the Dino-Noggins</figcaption></figure><p>The same applies to technical vocabulary — these days, any word you need is just a few taps or keystrokes away.</p><p>It takes only a few seconds to look up a word you need: so find it, use it, and move on — you’re more likely to remember the word by using it in a practical context anyways.</p><h4>2. A little planning goes a long way</h4><p>Of course there are situations when you can’t stop to look up the words you need, in a meeting or taking a client on a plant tour, for example.</p><p>But these things shouldn’t happen spontaneously — at least not often.</p><p>Therefore, you can avoid vocabulary troubles in these situations the same way we engineers try to avoid every problem: planning.</p><p>Your meeting should have an agenda, your tour should have a plan, and your presentation should have an outline. So, use them!</p><p>With a quick mental rehearsal, you can easily identify the words that you’re missing <em>before</em> your ‘live performance’, and create a quick list of the translations you’ll need beforehand.</p><p>And don’t worry about memorizing it, either. Take it with you to your meeting or on your tour, and use it when you need it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/343/1*TE7DeBW80ryRt703puh_Tg.gif" /></figure><p>Or even better:</p><p>Add that list to <em>everyone’s</em> meeting agenda so that everyone’s on the same page. Some colleagues will probably thank you.</p><p>But of course, you can’t plan for everything, and Murphy’s law is all too real…</p><p>…so just keep this next point in mind the next time you’re forced to improvise:</p><h4>3. You can always cheat</h4><p>I’ll never forget the first time it happened to me in German: I didn’t know the name of the <em>weg</em> used to go <em>über</em> the street, so I just said ‘Überweg’.</p><p>Turned out that my creation was actually correct, and that’s been my strategy ever since — if I don’t know a word in German, I just make one up (and hope).</p><p>I know I won’t always be right, but being right isn’t really all that important in such cases.</p><p>Here’s why:</p><p>Even if my made-up word is wrong, everyone still understands what I’m talking about. Not only that, but I never have to break the flow of my speech simply because I don’t know a certain word.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*bLJ0rgEllnqnxQw3ab6okw.jpeg" /><figcaption>Surprisingly effective strategy (the word formation, I mean)</figcaption></figure><p>And you can do this in English, too, just with one VERY important difference:</p><p>You’ll crash and burn if you try to make up a word in English (trust me).</p><p>But whenever you can’t think of a word in English, technical or not, you can always cheat, and say its <em>definition</em> instead.</p><p>For example:</p><p>If you can’t think of the word ‘chair’, just say ‘thing that you sit on’. Or if you can’t recall the English word for ‘<em>Absperrklappe</em>’, just say ‘shutoff valve with a turning disc’.</p><p>Everyone will know what you mean, and you’ll never have to stop your sentence and stand there scratching your head.</p><p>And the best part? Almost always, someone will end up saying something like ‘You mean a <em>butterfly valve</em>?’.</p><p>It’s almost too easy.</p><h4>4. Learn formulas, not variables</h4><p>When you were in university and learning the basics of engineering, what was more important in the end:</p><p>Remembering how to apply the right formulas in the right situation, or remembering the exact values that you plugged into those formulas in order to solve one particular problem?</p><p>Of course understanding the formulas is more important than the memorizing the variables. Why else do you think we’re taught to read all those crazy charts, graphs and tables?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sUGLymmxaPeCsIgDjxq9Aw.jpeg" /></figure><p>Knowing <em>how to find</em> the right values <em>when you actually need them</em> makes A LOT more sense than trying to remember all of them.</p><p>See where I’m going with this?</p><p>If the focus of your technical English studies is to memorize technical vocabulary, then it’s like you’re trying to memorize material property tables.</p><p>But if you switch your focus to understanding <em>how to use those words</em> by studying concepts like the construction and proper use of English tenses…</p><p>…you’ll immediately find yourself learning the vocabulary for technical English you need <em>without even trying.</em></p><p>You still need to plug the right values into the formula, after all. But this approach brings in new words on an as-needed basis, rather than flooding you with tens or hundreds of context-less words at once.</p><h4>5. Lack of practical learning material</h4><p>23. That’s how many workbooks for ‘technical English’ I have on my shelf so far. And even as my collection continues to grow, so far, all except 2 of them will remain there, untouched, indefinitely.</p><p>Why? Because they’re junk (to put it nicely).</p><p>They’re either written by someone who has no clue about what engineers actually do, or they’re designed to help English teachers who themselves have no idea what engineers actually do.</p><p>Almost all of them focus on teaching technical vocabulary that any engineer above A2 would never need, never use, or would already know.</p><p>So unless you’re willing to write your own workbook with practice questions and silly memory games, good luck finding a technical English workbook that’s actually worth your time.</p><p>(But if you do find one, be sure to let me know.)</p><h3>Closeout</h3><p>Now don’t get me wrong: vocabulary <em>is</em> a very important element when you’re learning technical English. It’s just not important enough to be the central focus of your studies.</p><p>In other words: Cool it with the flashcards, unless you know for sure that that’s a strategy that works for you.</p><p>From what I’ve seen over the years, it always comes down to this: instead of studying lists, <strong>you’re better off learning <em>how</em> to apply the words you need (e.g. grammar) and filling in the words you find are missing as you go.</strong></p><p>Also, regarding point 5: Out of fairness to the authors, I don’t want to endorse or dismiss any particular technical English book, nor do I have any intention of writing my own.</p><p>I am writing <em>something</em> though… but this project isn’t designed to teach engineers specific technical vocabulary. Not directly, at least.</p><p>Instead, I’m working on a method through which <em>any</em> engineer in <em>any</em> field can teach themselves <em>exactly</em> the technical English vocabulary they need to describe and explain <em>any</em> component, process or system.</p><p>In my opinion, it’s much more than any vocabulary workbook could ever do. It’s technical vocabulary: re-engineered.</p><p>Imagine that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd2a4759039f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explain It Like I’m Management]]></title>
            <link>https://medium.com/@DetroitEnglish/explain-it-like-i-m-management-inverse-explanations-4eab859fef82?source=rss-42928103790e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4eab859fef82</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[David Willenberg]]></dc:creator>
            <pubDate>Sat, 27 Feb 2016 04:07:47 GMT</pubDate>
            <atom:updated>2016-03-04T12:32:59.578Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f7kgc46uwDXOdHRH1ch_JQ.png" /></figure><h4>Jargon is for suckers — easily walk a layman through your technical process with an inverse explanation.</h4><p>One of the first exercises I do with a new group of engineers is also my favorite way of introducing the concept of concision.</p><p>Not only is it extremely effective: it’s usually hilarious, and serves as an amazing icebreaker when getting to know a group of new “students”.</p><p>Here’s how it works:</p><p>Every engineer writes me a 4–6 sentence description of their job…</p><p><strong>BUT…</strong></p><p>…they have to explain it to me like I’m 5 years old.</p><p>It’s actually a lot of fun (but not as easy as you might think!), and the idea was inspired by the <a href="http://www.reddit.com/r/eli5">r/eli5</a> subreddit.</p><p>Suddenly, <strong>photoacoustic spectroscopy</strong> becomes “shoot things with lasers and listen to the sound it makes with a microphone”.</p><p>While <strong>project management</strong> becomes “make sure the right people do the all the right stuff at the right time but make sure those things don’t cost too much money and that everyone plays together nicely”.</p><p>But by far, my <em>absolute </em>favorite is when an engineer explains using metaphors, because P&amp;IDs, for example, magically turn into fairy-tale pirate treasure maps…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*YD1rjQAvGHV8WxXyFzzwmA.png" /><figcaption>(some engineers do, in fact, have imaginations)</figcaption></figure><p>This exercise it so effective at clarifying the concept of concision because it demonstrates the <em>exact opposite </em>of what concision in technical English really is.</p><p>Five-year-olds don’t understand big, scary technical words; so, you’re forced to use drawn-out descriptions instead of single words, with exaggerated examples to clarify them.</p><p>In other words, you have to be very <em>unconcise</em>.</p><p>Nevertheless, after only 15 minutes of practicing exactly what this foundation of technical communication <strong>isn’t, </strong>the idea of concision takes root, and my new group of engineers hits the ground running.</p><h4>Getting Past the Jargon</h4><p>Very often, our roles as engineers require us to explain technical processes to people lacking any technical background; they’re usually the ones who can who sign checks with the most zeros, after all.</p><p>For example:</p><p>You might need a commercial manager to approve funding for a project you’ve proposed.</p><p>Or, you might need to explain to a controller why, on a technical level, the more expensive model of a new machine is worth the extra cost for your factory.</p><p>It took us <em>years</em> of engineering study in order to understand these technical processes… so how can we explain them clearly enough to get that layman’s million-dollar signature?</p><p>First, let me be very clear:</p><p><strong>Explaining like they’re five years old is a very bad idea.</strong></p><p>(probably)</p><p>But by using the same <em>principle </em>as my ELI5 exercise above, you can explain a technical process in a way that’ll leave decision makers smiling and nodding out of actual, genuine agreement instead of the usual utter confusion.</p><p>In other words, if you need that grown-up to sign your permission slip before you can go outside and play with big expensive toys, then pay attention -</p><p>Because you’re about to learn how to explain a technical process to non-technical people by <em>doing the opposite </em>of what they’re expecting.</p><h3><em>Everything </em>has an End (only a sausage has 2)</h3><p>Take a look at the first 90 seconds or so of this Learn Engineering video which explains the basics of the Rankine Cycle (i.e. how we generate electricity by burning dinosaur corpses).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIdPTuwKEfmA&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIdPTuwKEfmA&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FIdPTuwKEfmA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/60db08966184a5673ae9207d61983041/href">https://medium.com/media/60db08966184a5673ae9207d61983041/href</a></iframe><p>Notice anything peculiar about HOW the process is explained?</p><p>Let me break it down for you (and then watch it again to see what I mean):</p><p>If you need to explain the process of making a pizza, for example, your instinct will tell you to start with the dough, and then sequentially work your way through the sauce, cheese etc., until finally, that gooey, cheesy goodness comes out of the oven.</p><p>In this case, explaining the process in a step-by-step, beginning-to-end manner makes perfect sense for two reasons:</p><p>First, it’s standard practice to explain a cooking process i.e. a recipe in sequential order. More important than precedent, though, is that <em>we</em> <em>can safely assume that everyone </em><strong><em>already </em></strong><em>understands the process </em>of making a pizza.</p><p>What we <strong>cannot </strong>safely assume, is that everyone already understands the process of incinerating dinosaurs.</p><p>So, because the video above isn’t intended for people who already understand the Rankine Cycle, the creators cleverly defy their instincts and turn the entire explanation on its head.</p><p>How so?</p><p>Their explanation <strong><em>begins </em>with the final result</strong> of the process, and <strong>then works <em>backwards</em></strong> through the steps required to get there.</p><p>This technique is incredibly effective for explaining technical processes to the otherwise unfamiliar. And although it may seem counter-intuitive, it actually makes a lot of sense. Here’s why:</p><h4>The End of the Tunnel</h4><p>Think back to your days in university. Ever have a professor start solving an equation on the blackboard without first telling you what it actually was?</p><p>As you scribbled furiously in your notebook and tried to make sense of it all, two thoughts were likely in the back of your mind:</p><ul><li>What the hell is he getting at?</li><li>When will this finally end?</li></ul><p>By explaining an unfamiliar process from beginning to end, there’s a good chance your explanation will elicit the same frustrations in your audience that you experienced (and still remember) from dear old Professor .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*2OnL6mSftU4cVXbE8N160Q.gif" /></figure><p>Simply put yourself in their shoes for a minute, but instead of some cool engineering project, you’re forced to follow an explanation of German tax legislation. Sound exciting?</p><p>(to be clear, German tax legislation is very not-exciting)</p><p>So imagine how much worse it’ll be when they have no idea <em>what </em>your actual point is, OR <em>how long</em> it’ll take you to finally get there.</p><p>Make this mistake, and the highlight of your explanation is no longer the benefit created by your process; instead, the highlight for them is simply the point at which your mouth stops moving.</p><h4>Mt. Information</h4><p>In 5-year-old spirit, let’s put on our imagination hats for a moment…</p><p>Imagine your explanation as a mountain of information, with the summit being the final result of your process.</p><p>If you force someone to start at the bottom of your mountain and climb <em>up</em>, the stress of the climb will ultimately subtract from their enjoyment of the panoramic peak (assuming they make it there in the first place).</p><p>No matter how great the view is, your end result just won’t be as enjoyable, as their brain will be tired from processing the ‘climb’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*4dysrdV4JEKDnNzgz97Peg.jpeg" /></figure><p>So try it this way instead:</p><p>Start by taking them up to the peak in a helicopter, and <em>beginning your adventure at the top of the mountain</em>…</p><p>Let them take in the spectacular view, breathe that crisp mountain air and snap a few selfies FIRST — while they still have all of their energy.</p><p>Then (keep that imagination hat on…), as your explanation proceeds <em>downwards</em>, you’re able to provide a more effective explanation for these reasons:</p><ol><li>Because the end result <strong>is</strong> something they’re familiar with, it becomes the anchor point they’ll use to repel down the unfamiliar mountain. In other words, they’ll remain safely connected to what they <strong>do</strong> understand as you guide them down through all that they don’t.</li><li>Now that they’ve already seen how amazing things look from the top, they’ll have more appreciation for the mountain itself — and hopefully for their humble Sherpa as well (that’s you).</li></ol><p>If the mountain were made of tax legislation, which tour would <em>you </em>choose?</p><h4>Shock and Awe and Budget Surplus</h4><p>Regardless of <em>what</em> your technical process is, the reason <em>why</em> you’re even explaining it in the first place is that you (hopefully) intend to do something beneficial — make a new product, increase productivity or expand production capacity, for example.</p><p>But to e.g. a manager or a client, at the end of the day, <em>anything</em> beneficial is almost guaranteed to mean only one thing: <strong>having more money</strong> — either by earning more of it, or spending less of it.</p><p>Either way, <em>‘having more money’</em> is a concept that <strong>every</strong> decision maker understands well, and it’s been confirmed by science to make them happy.</p><p>Use this to your advantage (and get a nod of approval from the salespeople):</p><p><em>Grab their full attention at the very beginning </em>by <strong>starting </strong>your explanation with the moneymaker. Once they have that warm, fuzzy have-more-money feeling, anything you tell them afterwards will now be LOT more interesting…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*XxZU9fQg-z8txgHelHut4w.gif" /></figure><h3>Closeout</h3><p>Unfortunately for us engineers, effective communication (technical or otherwise) can never be defined with a formula. There’s not a single one-size-fits-all communication method for <em>any</em> situation, because the context will <em>always</em> be different.</p><p><strong>So pay attention:</strong></p><p>An inverse process explanation is <em>extremely </em>effective in the situations and contexts I’ve described, but <strong>it’s <em>guaranteed </em>to work in <em>none </em>of them</strong>.</p><p>In the end, it’s up to you and your best judgement to decide if this method is appropriate for your process, your audience, and your ultimate objective.</p><p>There are more than a few traps in this method which you should <em>definitely</em> watch out for… as in, if you get caught in one, and you can easily derail your entire explanation leave nothing but chaos and confusion in your wake…</p><p>I’ve got you covered, though — stay tuned.</p><h4>[Meta] Wait…what?</h4><p>What you just read is the English version of an article that I wrote for my German-language blog, <a href="https://www.detroit-english.de/vds-blog"><strong>Vorsprung durch Sprache</strong></a><strong>.</strong></p><p>My job to help German-speaking engineers and technical personnel learn technical English as a foreign language as well as technical and group communication in the context of international projects.</p><p>All of my articles are originally written in English and then translated into German before posting. So, I’ve got a big digital stack of English language articles that’s collecting binary dust on my hard drive.</p><p>Long story short: I’ll be posting occassional articles on Medium in English with the intent of helping engineers of any language improve their technical communication skills, as well as allow my German readers and subscribers the opportunity to learn, practice and improve by reading my articles in English.</p><p>If you speak German, you can learn more about me and my company, Detroit Technical English, at <a href="https://www.detroit-english.de/">https://www.detroit-english.de</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4eab859fef82" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>