Writing for Technical Audiences

Most DeepTech founders either dumb down their science (lose credibility) or write academic papers (lose readers). To avoid this trap, here's my 5-step roadmap on how to explain complex tech without compromise: Step 1: The "Technical Sandwich" Method. To master this: → Start with a simple outcome ("We reduce ocean plastic by 40%") → Layer in the technical mechanism ("using bio-enzymatic polymer chains") → Close with the human impact ("saving 2M marine animals annually") Start here, then move onto Step 2. Step 2: Choose your Precision Framework. Now you have two options: 1/ Analogies (quantum computing = library with infinite books in one space) 2/ Metrics (latency from 200ms to 3ms = Netflix vs buffering) There's no wrong answer, but you must decide. Step 3: Master two Core Communication Pillars. 1/ Simple Hooks. → 9 words or less in your opener → Lead with outcomes, not process → Use contrast ("$100K sensors vs our $4,900 buoy") Once you master this, focus on: 2/ Technical Credibility. → Drop one precise term per paragraph → Link to peer-reviewed sources → Show the math when it matters Step 4: Know when to embrace complexity. Most founders oversimplify everything. Your audience is smarter than you think. Here are your options: → Technical founders? Go deeper on mechanism → Investors? Show the physics constraint you solved → General audience? Keep the complexity in comments The key is matching depth to reader expertise. Step 5: The credibility check. This final step is how you: → Validate claims with independent sources → Show real deployment numbers → Name the institutions backing you Do this and you can unlock both reach and respect. It's as easy as that. — What's the hardest technical concept you've had to explain in plain English? PS. I've ghostwritten for 10+ climate tech founders. The ones who balance simplicity with precision get 10x the engagement.

In my 14yrs career in engineering working for Big Tech companies such as Google and Uber, there is no other skill I used more than writing. And no, I don’t mean writing code. I mean English writing. Emails, Design Docs, Presentations, Feedback, Code Reviews, you name it. Here's how I make my written communication clear, effective, and punchy. 👇 Written communication can sometimes be daunting, especially for non-native speakers—like me. That’s why I wanted to share  the 6 questions that I use when writing anything. This helps me communicate more effectively and connect with my audience better. 1. Who is my target audience? Identify the specific group or individuals you are speaking to. Knowing your audience assists you in customizing your writing to meet their requirements and interests. 2. What is my main objective or purpose? Clarify the primary goal of your writing. Whether it's to inform, persuade, entertain, or educate, knowing your objective guides your content. 3. What key points do I want to convey? Identify the main idea or key points you want to communicate. This will help you stay focused and make sure your message is clear and logical. 4. Why should the reader care about this? Consider the value or benefit your writing offers to the reader. Highlight how it addresses their needs or solves a problem. 5. Is my writing clear, concise, and organized? Make sure your content is clear and easy to understand. Keep the flow logical and avoid using complex language or jargon that might confuse the reader. 6. Can I make my writing shorter? The answer is always yes. So make sure to edit edit edit. Brevity saves time for both the writer and the reader. What else would you add to this list? How does your writing process look like? ♻️ Please repost if you found this useful

The difference between a good design doc and a great one is usually clarity. Technical writing should be crisp and to the point. So, it is always better to treat every sentence like it has a cost. After writing, cut aggressively. Remove extra words. Then check if a line can go. Sometimes even a full paragraph is unnecessary. One thing I always do is to start the doc with the conclusion; this way, the reader/reviewer knows where we are heading. This is contrary to how most engineers write docs - listing every approach first and only concluding at the end. That slows readers down. I avoid this because long explanations make people lose track; most readers want the conclusion quickly. So, always start with the answer and why it matters. Then add details and alternatives below for those who want depth. A habit that helps is a quick editing pass like this: - Remove filler words and repeated ideas. - Break long sentences into smaller ones. - Prefer bullets when listing options or steps. - Check if the first section clearly states the outcome. - Add a link or short explanation where a reader may pause. Empathy matters more than most people realize. Try to read your document as someone new to the topic. Ask yourself what might confuse them. Add the missing context. Add the helpful link. Let the ideas evolve naturally from problem to solution. This skill develops over time. Use simple language and fewer buzzwords. The goal is to communicate, not impress. Simple documents get read more. More readers means better alignment and better visibility for the work. Finally, always provide enough context. A short setup about the problem, constraints, and prior decisions goes a long way. It helps readers understand why the decision exists, and, of course, it prevents unnecessary back and forth later. Hope this helps.

SaaS companies, stop overcomplicating your content. Yes, you’re creating an advanced solution. But if you can’t explain it simply – your customers won’t understand it. And what happens when they don’t get it? 👉 Confusion 👉 Frustration 👉 No conversions Here’s the fix: 1/ Break it down Use everyday language. And when things get technical, try: • Give an example – Walk them through a real-life scenario • Provide an analogy – Compare it to something they already understand 2/ Focus on clarity Make every sentence count. You should: • Cut the fluff – Keep things direct and easy to digest • Avoid jargon – Don’t alienate your audience with technical terms 3/ Guide them step-by-step Lead them through the process by: • Creating a roadmap – Show them the clear path to the solution • Using simple steps – Break down your solution into bite-sized actions Simple, clear, and relatable content drives conversions. PS. Share it with a technical founder who struggles to communicate their product’s value.

I reviewed a Technical Specification today. It made me reflect on a few important points. Effectively drafting technical specifications is not about writing more — it’s about writing better. Too often I see specifications become a dumping ground for generic clauses, copied standards, disclaimers and risk transfer masquerading as “technical requirements”. The result? Ambiguity, ultimately disputes, and delivery teams forced to interpret intent long after decisions should have been clear. The UK Construction Playbook (and similar guidance we see echoed across Australia) keeps coming back to a few fundamentals that are worth repeating: 👉 Clarity of outcome before prescription Specifications should not be drafted in isolation to the intended contract. They should be explicit about what is required — performance, durability, safety, whole-life outcomes — before defaulting to overly prescriptive solutions or resorting to death by referencing too many industry standards. 👉 Align the Spec with the commercial model If you’re pursuing early contractor involvement, two-stage procurement, or modular delivery, your technical specifications must support collaboration — not lock in assumptions too early. 👉 Standardise where possible, tailor where it matters Standard forms and reference specs reduce friction, but only if they are actively curated. Blind cut & paste copying introduces risk, not certainty. 👉 Design for buildability and operation The Playbook (see image below) is clear: for good specifications consider what to avoid when drafting. 👉 Write for the people who will actually read and them A specification is a communication tool. If the contractor, subcontractor, or facilities team can’t easily understand it, the project will pay for that later. Ultimately, effective technical specifications are a management tool. They set tone, allocate risk intelligently, and enable better decision-making across the lifecycle of an asset. Less boilerplate. More intent. Better outcomes. #Construction #TechnicalSpecifications #ConstructionPlaybook #Procurement #Infrastructure #BetterProjects

Technical Writers Do Not “Write Too Technical.” That Is the Job Misunderstood. There is a persistent misconception about technical writing that keeps resurfacing. The idea that technical writers write at their own level and forget the end user. That is not a failure of technical writing. It is a fundamental misunderstanding of what technical writing actually is. Technical writers do not write for themselves. We write for the person who needs to complete a task successfully. That audience changes constantly. If a user struggles because of jargon, unclear steps, or poorly broken-down processes, the problem is not that the content was technical. The problem is that the content was not written for that user. Technical writers almost never write for a single audience. Within the same product, we may write: • Developer documentation that requires precise technical language • Administrator guides for power users • Task-based instructions for non-technical end users • Internal documentation for support, sales, and leadership Same system. Different readers. Different context. Different language. Knowing how to shift between those registers without losing accuracy is not accidental. It is a core professional skill. Writing clearly for people with less technical context is hard. That is why it is a role, not an afterthought. When documentation works, users do not feel confused or condescended to. They simply succeed. That is not dumbing things down. That is good technical writing.

Clear technical content isn’t less expert. It’s more effective. The single best way to make technical B2B topics more accessible? Talk like someone who actually understands them. Not like a marketer trying to 𝘴𝘰𝘶𝘯𝘥 technical. Not like an engineer quoting the documentation. Like someone who knows the product and knows the person on the other end of the screen. The goal isn’t to oversimplify. It’s to remove friction. Make the right people understand the right things, faster. So how do you do that? Here are a few ways we break down complexity without watering it down: → Lead with the business case → Swap out jargon for clarity, selectively → Use analogies that land → Show, don’t just tell → Segment by audience → Test your content with someone outside your industry Clarity is a skill, not a compromise. Technical content can be detailed without being dense. It can be smart without being confusing. It can sound like your brand and still make sense to people outside your team. Because making it easy to understand isn’t oversimplifying. It’s respecting your audience’s time. --- Follow Jeff Gapinski for more content like this. ♻️ Share this with a marketer tackling technical topics.

Technical writing and UX design are inseparable partners in creating exceptional end-user experiences. As technical writers, we must embrace UX principles like user-centered design, information architecture, and cognitive load management to create documentation that truly serves our audience's needs. We aren't just simply explaining features, we're guiding users through their knowledge-gathering journey. Every #documentation decision we make impacts user experience. From choosing the right headings and creating scannable content to implementing progressive disclosure and clear navigation paths, we're constantly applying UX principles to make complex information digestible. When we ignore these principles, even the most accurate technical content can fail to serve its purpose. The most effective technical documentation emerges when we combine solid writing skills with UX best practices. By understanding user behaviors, mental models, and pain points, we create content that not only informs but empowers. If users can't find or understand the information they need, it might as well not exist at all. #TechnicalWriting #UX #UserExperience #Documentation #TechComm #ContentStrategy

Your LinkedIn Post: Is Your Content Too Complex? Too Academic-Like? Your content is pushing away your best prospects (esp if you write like an long essay post). I've watched consultants spend hours crafting technical content that gets ignored by the clients they want to attract. Here's the painful truth you need to hear... Being "expert-level" in your content often means you're only speaking to other experts... Not to your ideal clients. I recently reviewed a consultant's LinkedIn where every post was packed with jargon (that only made sense to them). Who engaged? Other consultants. Who didn't? Decision-makers with money to spend. The fix? Balance complexity with clear communication and clarity. ✅ Use analogies for complex ideas ✅ Drop the jargon—speak their language ✅ Frame complexity as "hidden problems" ✅ Break frameworks into digestible steps ✅ Test what actually gets engagement Easy english works best... Funny enough if you can make a 12 year old get it, everyone will get it. Big takeaway: You can attract sophisticated clients without overwhelming them. What's one way you simplify complex topics for your audience?

𝗛𝗼𝘄 𝗪𝗶𝗹𝗹 𝗬𝗼𝘂 𝗕𝗲 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗼𝗼𝗱 𝗪𝗵𝗶𝗹𝗲 𝗦𝗵𝗮𝗿𝗶𝗻𝗴 𝗬𝗼𝘂𝗿 𝗘𝘅𝗽𝗲𝗿𝘁𝗶𝘀𝗲? You are standing in front of an audience of experts and interested non-specialists: how do you convey your knowledge to reach everyone? The specialists expect your expertise by using technical terms. But the others do not understand that. My tip: 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗲 𝘁𝗵𝗲 𝘁𝗼𝗽𝗶𝗰 𝗶𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗶𝗯𝗹𝘆. Then dive deep into the details and pick up the experts, before translating it so that everyone can follow you. I once had this experience at a science conference: I explained my content too simply in front of specialists. There was an immediate discussion that I needed to explain things more precisely – but that would have lost the interested non-experts. Regardless of the precision of your data, it is crucial that your audience immediately understands it. Emma Horn, PhD student at the University of Cape Town in South Africa, gives a good example at the Falling Walls Lab 2022 in Berlin: “Ceramic tiles: 16 billion square meters were produced globally last year. That’s enough to tile the entire area of Berlin almost twenty times over.” In this way, 𝗮𝗻 𝗮𝗯𝘀𝘁𝗿𝗮𝗰𝘁 𝗽𝗮𝗿𝗮𝗺𝗲𝘁𝗲𝗿 𝗯𝗲𝗰𝗼𝗺𝗲𝘀 𝗮 𝗰𝗼𝗻𝗰𝗿𝗲𝘁𝗲 𝗶𝗱𝗲𝗮, here even regarding the location of the talk. Nowadays, scientists need to ensure that their often very complex work is accessible to a diverse audience by being understood immediately. How do you ensure everybody will understand your content?