![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Sticking to the point
Jul. 25th, 2005 04:22 pmI would just like to talk briefly about how useful it is when a meeting, especially one intended for training purposes, has a definite structure which can be followed. That way the sequence stays nice and clear, and no-one gets confused. So, for example, I have here a plan which I intend to follow today…
Of course it's useful if a such meeting can be related to specific transactions which have been undertaken recently, as that gives a focus for discussion. For example, one that I'm currently involved in is Project X...
Is that the deal where we had [this situation]? I thought that [this particular technical issue] was fascinating...
Yes, and I was going to come to that in a...
Is everyone clear about what that issue is? To run though it quickly, where [something happens]...
Though of course you should bear in mind that in [certain bizarre circumstances] you have to look at entirely different rules. Watch out for [something completely unrelated], too - which reminds me of a deal I was doing recently [blah blah blah]
Yes, very interesting. To return to the initial point, we…
One thing I always find fascinating is…
ETC ETC ET BLOODY CETERA!
*Sigh*. Who was it was emphasising the importance of a structure for these things only half an hour ago? Was it the person going off at *completely* irrelevant tangents ALL THE TIME? Was it, ironically, the person who has been going on at me to make sure that everything we do for a client must be covered by the agreed scope for the project, and we cannot possibly go outside a set scope for love nor money? No, shurely not…
Now I enjoy rambling discussions on interesting technical points, and I'm more than happy to have them, but not when we're talking over the heads of half a dozen people who haven't the foggiest what we're talking about because whenever I try to explain things to me you cut me off before I can finish a sentence.
And not when you make me use an exclamation mark. I don't do those, they have no place in civilised speech or writing.
Rotten swines, the lot of you.
Of course it's useful if a such meeting can be related to specific transactions which have been undertaken recently, as that gives a focus for discussion. For example, one that I'm currently involved in is Project X...
Is that the deal where we had [this situation]? I thought that [this particular technical issue] was fascinating...
Yes, and I was going to come to that in a...
Is everyone clear about what that issue is? To run though it quickly, where [something happens]...
Though of course you should bear in mind that in [certain bizarre circumstances] you have to look at entirely different rules. Watch out for [something completely unrelated], too - which reminds me of a deal I was doing recently [blah blah blah]
Yes, very interesting. To return to the initial point, we…
One thing I always find fascinating is…
ETC ETC ET BLOODY CETERA!
*Sigh*. Who was it was emphasising the importance of a structure for these things only half an hour ago? Was it the person going off at *completely* irrelevant tangents ALL THE TIME? Was it, ironically, the person who has been going on at me to make sure that everything we do for a client must be covered by the agreed scope for the project, and we cannot possibly go outside a set scope for love nor money? No, shurely not…
Now I enjoy rambling discussions on interesting technical points, and I'm more than happy to have them, but not when we're talking over the heads of half a dozen people who haven't the foggiest what we're talking about because whenever I try to explain things to me you cut me off before I can finish a sentence.
And not when you make me use an exclamation mark. I don't do those, they have no place in civilised speech or writing.
Rotten swines, the lot of you.
