When I communicate verbally or in an email, I try to explain things in depth. Generally, if there are a lot of caveats my pattern is:<p>* Explain the problem<p>* Explain the solution<p>* Cover caveats, exceptions<p>* Re-explain the solution in case they forgot<p>* Answer any questions<p>* Re-explain the solution to solidify what I explained including their questions to make sure they got it<p>This leads to me being very wordy, and I can easily reply to a simple question by talking for 10 minutes. I find my behavior problematic, especially since I'm an SME for a bunch of different things, this leads to having to explain a lot of things daily.<p>I don't just do this for technical questions, I do it pretty much for everything. My significant other, which is a lot more socially adept than me, thinks that I have an inherent assumption that other people won't get it, so I repeat myself. At times this comes across as condescending, I think.<p>However, when I try to explain things less, it becomes obvious that a lot of times they will make wrong assumptions, which leads to me having to explain the same thing in 2-3 occasions.<p>Part of me thinks I miss-calibrate people's competencies so I go too deep or not deep enough. Regardless, the primary problem is explaining too much or repetitively.<p>Does anyone have a good heuristic, book, thoughts I can use?<p>PS. I on purpose wrote this in the way I would normally explain something verbally to stress the point of what I'm struggling with. Consider the meta of my post :)
It sounds like your approach is ok, but here's a few things I have picked up from experience:<p>* Always give an overview - a complete, but low-resolution version of the whole picture. Identify key parts of the picture by name and use those same names when you get into more detail<p>* Number and name things. If there are 3 points, tell people there are 3 points. Then cover them...1, 2, 3. Don't get into sub-points like 2.1, 2.2 so that people lose track of the fact that there are <i>3</i> points.<p>* There's an old mantra that goes "Say what you're going to say; say it; then say that you have said it". That's 100% the way to go imo. Tell people "I'm going to give you a quick overview of the 3 main points first; then I'll go into detail on each of those 3 points. That'll take longer. Then I'll recap in case anything is still unclear, then we'll have Q & A".<p>* When you transition from one thing to another, refer back to the outline you established so that people know where they are on the map, i.e. "So much for point #2. Now, point #3...". Or "So that's the 500-foot view. Now I"ll go through each of these points in more detail...".<p>* Don't try to anticipate the questions too much. You'll be wrong about what what's going to give people difficulty no matter what, so listen to how people react and adjust accordingly!
The question you need to ask yourself is why do you feel you need to be so verbose in your answers? When I was more junior, I felt over-explaining concepts/answers/etc in great depth would impart confidence in my audience that I knew what I was talking about, when in reality, it often did just the opposite because people tend to only want the answer to their question, not the entire philosophy and means of how it's solved. More to the point, you tell an upper management all the caveats, problems, and exceptions in the same convo as your recommended solution, and that will often plant a seed of doubt in their mind regarding your proposed solution.<p>TLDR: The man that truly knows his shit through and through is confident and doesn't feel the need to over-explain every detail unless specifically asked to provide such detail. Over-explaining by default makes me wonder "did you just learn this or something and are excited about it and want to overshare all this detail? Hmm, gonna get a senior person to review your proposal... complicated != cheap/fast/reliable"<p>TLDR TLDR: would you continue to use a search engine that takes 30 minutes per query to get you an answer or switch to the search engine that gives concise 1-2 min tailored answers limited to answering exactly what was asked? by far most people would use the latter. that's your audience.
There's a huge difference between spoken and written communications. Don't use the same methods for both.<p>Over-explaining comes from lack of confidence: either in yourself or in your estimate of the other person to understand. Talk slower, take pauses, and be more interactive. Don't rush.<p>Provide the right amount of context. Gauge if they need more or you can shorten it. Go back and fill in if necessary. Different people listen differently. Some want the facts. Some want the story of how the facts were determined, etc. Effective communication isn't easy.<p>Btw, the way you wrote your post is in good form for someone like me to take in. I tend to overestimate others ability to understand and speak tersely. At the same time, I'll usually always start with some context. I know some people who just start blurting thoughts out of nowhere expecting you to have read their mind for context.
Here's a way to "cheat" your way out of this problem. Write it down.<p>Whenever you find yourself explaining the same thing several times, either to a single person or to several people, just put down the argument in a short memo, word doc, email, powerpoint, whatever. Send it to the last person who needed it, or just save it somewhere. Next time you're asked you can just send them the writeup.<p>I have the same problem as you. The underlying condition is that often times I'm just too lazy to write down what I have in mind. But being lazy results in more effort in the end.<p>Don't be lazy like me.
Tough spot - these days people look for tailored information for the answer to only their question. But often they really need all the context in order to understand the answer to just their question. (And we all hope they grow into stewards of the whole answer.)<p>At work, you could maintain documents for things you need to explain in detail, and when verbally discussing specific parts, reference relevant parts of the written doc.
Deliberate practice. You're a developer so you know how important it is to keep code short, tidy, and obvious. Keeping natural language explanations short, tidy, and obvious is equally important.
Honestly, i don't think there's a single answer because there isn't a single audience.<p>One issue I encounter is in group discussions e.g. management meetings. Lack of detail up-front leads to derailment from edge-cases or whataboutery as the conversation moves on. Whereas excessive detail up-front leads to derailment from nit-picking, or abject boredom, or failing to catch all the detail.<p>During this sort of conversation I scribble notes about the points I want to raise. Then let everyone else talk to see if my points are raised or if I learn something new. Finally, I try to raise points by saying something like "there are three things I'd say about X", followed by a super-brief headline for each point. Single sentences. That should be enough, but if not, I'd expand each as required.<p>But even this has issues. Management meetings can be fraught, and time is scarce. Waiting until after others have spoken means that they may have sucked the life from the conversation and people may be impatient to move on. I'm aware of coming across as someone who simply wants to stick their beak into every conversation.<p>So, I've tried to be more Zen and simply let things go, or take certain conversations off-line i.e. discuss in depth outside the room. Results vary.<p>Good luck! :)