![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Short ramble...
May. 6th, 2007 08:33 amI've been up since about 5:45 am, and have done one hazard report since 6:30.
I took a short break a few minutes ago to read the first few pages of How to Get Your Point Across in 30 Seconds or Less, by Milo Frank. Its theme goes well with some of the Gitomer advice I've been reading (as in: develop a 30-second marketing message and know it cold).
The first example Frank gives (a contrasting pair of scenarios where a manager is interacting with a corporate beancounter) demonstrates the difference between knowing what you want and not knowing, and it tweaked something in my mind, in an allied area: that of asking for information.
Somewhere along the way, whenever I need to ask folks to help me understand something (e.g., a terminology issue or some technical question), I've developed the habit of posing the question in such a way as to show that I've thought about a possible answer, typically including it along with my question.
For example, instead of asking "Could you show me how to derive expression X from Y?" I'll ask, "Could you take a look at my attempt below to derive expression X from Y and show me where I went wrong?" I do this with terminology queries all the time, too.
I suppose I do that because simply asking a "naked" question seems, to me, to imply that I'm too lazy to take a crack at it myself.
At any rate, there seems to me to be a correlation between the two: Knowing what you want correlates with having taken a crack at some issue on your own.
Beyond this initial impression, I am not prepared to further ramble, as I want to do two more hazard reports and 1000 words of translation before turning to the home stretch (relatively speaking) on the paper chase.
Cheers...
I took a short break a few minutes ago to read the first few pages of How to Get Your Point Across in 30 Seconds or Less, by Milo Frank. Its theme goes well with some of the Gitomer advice I've been reading (as in: develop a 30-second marketing message and know it cold).
The first example Frank gives (a contrasting pair of scenarios where a manager is interacting with a corporate beancounter) demonstrates the difference between knowing what you want and not knowing, and it tweaked something in my mind, in an allied area: that of asking for information.
Somewhere along the way, whenever I need to ask folks to help me understand something (e.g., a terminology issue or some technical question), I've developed the habit of posing the question in such a way as to show that I've thought about a possible answer, typically including it along with my question.
For example, instead of asking "Could you show me how to derive expression X from Y?" I'll ask, "Could you take a look at my attempt below to derive expression X from Y and show me where I went wrong?" I do this with terminology queries all the time, too.
I suppose I do that because simply asking a "naked" question seems, to me, to imply that I'm too lazy to take a crack at it myself.
At any rate, there seems to me to be a correlation between the two: Knowing what you want correlates with having taken a crack at some issue on your own.
Beyond this initial impression, I am not prepared to further ramble, as I want to do two more hazard reports and 1000 words of translation before turning to the home stretch (relatively speaking) on the paper chase.
Cheers...
