Q: “Graham, can you please give me some more detail on that.”
GC: “Sure. The line that you see there on the diagram, well that really represents three different lines bundled together to create a single integration.”
Q: “Thanks, can you give me details please?”
GC: “Each of the three lines within the one line are a combination of different technologies, some operating synchronously and others working asynchronously depending upon the data being transmitted. Each of the lines is traversing the firewall boundary between public and private using an encrypted connection.”
Q: “But I still don’t understand, can you give me some more detail.”
Do you see what I did there? I launched into an answer to the question based on the words used in the question. I often make this mistake and it frustrates me how often it happens. I put lots of effort into providing correct responses only to discover that correct doesn’t mean helpful.
My understanding of the word detail leads me to answer by taking a component of the thing being described and add further information to the information already provided. For me, detail is the specifics behind the generality of what’s outlined; a request to for further detail means that you want a deeper level of specificity.
The Collins Dictionary describes detail as: “its individual features or elements.” or “a minor point or aspect of something, as opposed to the central ones.”
Detail doesn’t, generally, bring understanding, in many cases it brings further confusion. It’s much more common that understanding is gained by providing a different perspective and less detail.
I also try to be precise in the questions that I ask, but regularly receive answers that show that I didn’t communicate my need in a way that the person answering understood. Again, the answers are correct, but not necessarily helpful.
Next time someone asks me for more detail, I will try to remember that they are probably not asking for what they need, it’s more likely that they are asking me to help them understand.