Like 5 hours ago, actually. It was an over the midnight vine-chatter with neighbor girl. I did realise something fascinating and helpful tho. You can notice it in the eyes. The "I lost plot a lil bit here" kind of look. Eyes stop shining for a sec and move somewhere else from you. That moment you know you went rambling, and gotta find short and satisfying ending. Great video, thank you.
Thanks for sharing. Good Video. You touched on some valid points. When you stop speaking as if you need to sell yourself or prove yourself, you realize how simple you can convey a message. Not using jargon goes a long way too. It is the coolest achievement to say something super technical and not sound technical.
Great video with really great tips. All of this works well when you have time to gather and sift information to fit your audience/interlocutor, and many "detail-oriented" people I know (including me) eventually learn how to do it to some degree. The really hard part is doing this impromptu, and sadly, I haven't found much helpful information for this. Do you have any tips on this?
In an impromptu situation, I'll usually listen closely to figure out what they want to know and start by repeating a simple version of what they just said with one or more added limits. For example, if someone asked me about recording themselves playing guitar, I might answer, "So you want to know more about recording yourself playing acoustic guitar at home without vocals?" In that example answer, I intentionally added the details of the type of guitar (acoustic), location (at home), and number of sound sources (with/without vocals) to help me understand the use case surrounding the initial question. At that point, they might say, "Yeah, I want to help my daughter record herself playing some songs that she plays really well." From there, I'd ask about the use cases surrounding the outcome they just gave me: "Does she want to submit demos to labels, self-publish to services like Spotify, or is this more of something to share with friends?" Once I get a solid feel for the outcome they're looking for from "recording themselves (or someone else) playing guitar," I can start to ask about budget (time & money) and chart a simple path to the desired outcome. At this point, I make it clear (multiple times) that I'm not giving them the perfect or the only path, just the best one I can come up with at the moment, and (if I'm genuinely interested) offer to help them more at a future date.
But what if you are the complete opposite. What if you say little, what's important, yet need to learn on how to give an over abundance of information for those whose brains are wired that way? My brain is more wire for the 'meat and potatoes'.
That's a great question. And to be candid, I'm more wired for meat and potatoes than extra fluff. The key is to figure out where they want that overabundance of info and why. For example, when speaking to a software developer, they may want extra info to determine how far the solution can be pushed in the future without needing a complete rewrite. Conversely, a network engineer may want to dig into traffic routing failure states to help make the solution more robust so that folks can sleep in if there is a 4 a.m. failure.
When’s the last time you shared too much?
I clearly remember the moment their eyes glazed over and they grasped for some reason to escape 😅.
Like 5 hours ago, actually.
It was an over the midnight vine-chatter with neighbor girl.
I did realise something fascinating and helpful tho.
You can notice it in the eyes. The "I lost plot a lil bit here" kind of look. Eyes stop shining for a sec and move somewhere else from you. That moment you know you went rambling, and gotta find short and satisfying ending.
Great video, thank you.
Very insightful thank you for the lesson
Thanks for sharing. Good Video. You touched on some valid points. When you stop speaking as if you need to sell yourself or prove yourself, you realize how simple you can convey a message. Not using jargon goes a long way too. It is the coolest achievement to say something super technical and not sound technical.
nice one. also wasnt expecting the cowboy bebob ending
Great video with really great tips. All of this works well when you have time to gather and sift information to fit your audience/interlocutor, and many "detail-oriented" people I know (including me) eventually learn how to do it to some degree. The really hard part is doing this impromptu, and sadly, I haven't found much helpful information for this. Do you have any tips on this?
In an impromptu situation, I'll usually listen closely to figure out what they want to know and start by repeating a simple version of what they just said with one or more added limits. For example, if someone asked me about recording themselves playing guitar, I might answer, "So you want to know more about recording yourself playing acoustic guitar at home without vocals?"
In that example answer, I intentionally added the details of the type of guitar (acoustic), location (at home), and number of sound sources (with/without vocals) to help me understand the use case surrounding the initial question.
At that point, they might say, "Yeah, I want to help my daughter record herself playing some songs that she plays really well." From there, I'd ask about the use cases surrounding the outcome they just gave me: "Does she want to submit demos to labels, self-publish to services like Spotify, or is this more of something to share with friends?"
Once I get a solid feel for the outcome they're looking for from "recording themselves (or someone else) playing guitar," I can start to ask about budget (time & money) and chart a simple path to the desired outcome.
At this point, I make it clear (multiple times) that I'm not giving them the perfect or the only path, just the best one I can come up with at the moment, and (if I'm genuinely interested) offer to help them more at a future date.
But what if you are the complete opposite. What if you say little, what's important, yet need to learn on how to give an over abundance of information for those whose brains are wired that way? My brain is more wire for the 'meat and potatoes'.
That's a great question. And to be candid, I'm more wired for meat and potatoes than extra fluff.
The key is to figure out where they want that overabundance of info and why.
For example, when speaking to a software developer, they may want extra info to determine how far the solution can be pushed in the future without needing a complete rewrite. Conversely, a network engineer may want to dig into traffic routing failure states to help make the solution more robust so that folks can sleep in if there is a 4 a.m. failure.