I've worked in IT for about 15 years, and one of the most frustrating parts of the job is communicating with managers and other non-technical stakeholders. I can create diagrams, presentations, and technical plans, but the details often seem meaningless to people who don't work with technology every day. As a result, I sometimes end up defending against unrealistic proposals or doing work that I believe is ineffective simply because I haven't explained the problem well enough. Are there books, courses, or practical communication techniques for explaining technical issues and better alternatives in a way that non-technical decision-makers can understand?
4 Answers
Use plain language and familiar analogies. Explain the relationships between things with examples involving cars, buildings, stores, or other everyday systems, while leaving out unnecessary implementation details. Aim for language a teenager could understand, avoid jargon, and be honest about which technical details you’re simplifying. If something may require more investigation later, say so rather than pretending the short explanation covers everything.
Start by finding out what problem they’re actually trying to solve. People often suggest a specific technical solution before clearly defining the underlying goal. Ask questions like, “What outcome are we trying to achieve?” or “What will this allow us to do?” Once the goal is clear, compare a few possible approaches and explain the costs, benefits, risks, and trade-offs. The tone matters too: sound collaborative and curious rather than like you’re rejecting their idea.
Translate the technology into consequences. Instead of spending twenty minutes explaining why an architecture is flawed, say something like, “This option adds three weeks to the schedule, increases the chance of failure, and would take two days to recover from.” Managers usually care about business impact: cost, delivery time, risk, downtime, and recovery. A simple table comparing those factors can be more effective than a detailed technical presentation.
Communication, persuasion, and assertiveness courses can help, but a practical technique is to prepare two versions of every explanation: a short executive summary and a deeper technical explanation for anyone who wants it. Tools such as AI can also help rewrite a technical proposal into simpler language, but you should check the result carefully. The goal is not to replace your expertise; it’s to make the important implications easier for others to understand.
If a normal simplified explanation still doesn’t work, try changing the format rather than just removing more technical details. A short spoken conversation, a risk-and-options summary, or a concrete example can work better than another document or slide deck.