Hello,
I am not sure this is the proper forum nor the proper place to ask this non-technical question but i will just go ahead...
I am sure you have already been asked to speak about the project you are working on and the your current tasks you are involved in, in front of the other process engineers, during a process team meeting (for example) ?
Suppose the process department manager ask informally to each engineer to tell about it during 5 min.
Usually people talk about any aspect they find interesting on their project: some point out the very specific problems they met, others stay very general...
I would like to have the advice/guidelines of experienced industrial professional engineers on the proper articulation/outline of such a short presentation. What would be the points to highlight and in which order for example? If you were the manager or an engineer, what would you like to hear? I know each project is specific, but from a general point of view what would you propose?
Hope my query is clear enough
Thank you in advance
|

Relevant Aspects To Highlight During A "short" Presentation
Started by sheiko, Jan 05 2009 02:31 PM
6 replies to this topic
Share this topic:
#1
Posted 05 January 2009 - 02:31 PM
#2
Posted 06 January 2009 - 03:09 AM
Its difficult to give you specific advice for this presentation you must give, but as a general rule I believe the most important thing is to put yourself in the shoes of the audience and think about what they want/need to hear.
If you are giving a presentation to senior management don't talk about kinetic rate constants, heat transfer coefficients and computer algorithms. They want to know why you did the work, what alternatives you considered and what your conclusions are - and of course how much money it will make for them.
If you are in a technical meeting with your peers don't talk about the 20 year strategic plan for the company. Here you can talk about why you used the technical tools you did, and why they were suitable. Sharing lessons (even mistakes) at this level is a powerful way to learn.
If you are giving a presentation to senior management don't talk about kinetic rate constants, heat transfer coefficients and computer algorithms. They want to know why you did the work, what alternatives you considered and what your conclusions are - and of course how much money it will make for them.
If you are in a technical meeting with your peers don't talk about the 20 year strategic plan for the company. Here you can talk about why you used the technical tools you did, and why they were suitable. Sharing lessons (even mistakes) at this level is a powerful way to learn.
#3
Posted 06 January 2009 - 04:52 PM
sheiko,
There is very much to say on the subject.
First of all, I hate the type of meetings you are describing, when the word goes around the table and everybody is saying something useful or not for the group. I am considering them at least a waste of time. There are much more efficient ways to communicate with the team members.
At least for myself this is the most annoying way to communicate. When I am forced to attend this kind of meetings I am mumbling something like all the others, if that's what the supervisor wants, that's going to get, or simply I say "I have nothing to add".
When I have a problem I do not wait for the next meeting to raise it, I am doing it on spot, and try to solve it. And that is what I am expecting when the others have a problem with me, to raise it to me on spot.
When I have an achievement, I am expecting the recognition from my supervisor, instead of painting myself in heroic colors in public. And also, when I make a mistake I expect my supervisor to bare a part of the responsibility.
As I said, there is much to say, this is a very short version.
There is very much to say on the subject.
First of all, I hate the type of meetings you are describing, when the word goes around the table and everybody is saying something useful or not for the group. I am considering them at least a waste of time. There are much more efficient ways to communicate with the team members.
At least for myself this is the most annoying way to communicate. When I am forced to attend this kind of meetings I am mumbling something like all the others, if that's what the supervisor wants, that's going to get, or simply I say "I have nothing to add".
When I have a problem I do not wait for the next meeting to raise it, I am doing it on spot, and try to solve it. And that is what I am expecting when the others have a problem with me, to raise it to me on spot.
When I have an achievement, I am expecting the recognition from my supervisor, instead of painting myself in heroic colors in public. And also, when I make a mistake I expect my supervisor to bare a part of the responsibility.
As I said, there is much to say, this is a very short version.
#4
Posted 07 January 2009 - 10:47 AM
QUOTE (Andrei @ Jan 7 2009, 02:52 AM) <{POST_SNAPBACK}>
sheiko,
There is very much to say on the subject.
First of all, I hate the type of meetings you are describing, when the word goes around the table and everybody is saying something useful or not for the group. I am considering them at least a waste of time. There are much more efficient ways to communicate with the team members.
At least for myself this is the most annoying way to communicate. When I am forced to attend this kind of meetings I am mumbling something like all the others, if that's what the supervisor wants, that's going to get, or simply I say "I have nothing to add".
When I have a problem I do not wait for the next meeting to raise it, I am doing it on spot, and try to solve it. And that is what I am expecting when the others have a problem with me, to raise it to me on spot.
When I have an achievement, I am expecting the recognition from my supervisor, instead of painting myself in heroic colors in public. And also, when I make a mistake I expect my supervisor to bare a part of the responsibility.
As I said, there is much to say, this is a very short version.
There is very much to say on the subject.
First of all, I hate the type of meetings you are describing, when the word goes around the table and everybody is saying something useful or not for the group. I am considering them at least a waste of time. There are much more efficient ways to communicate with the team members.
At least for myself this is the most annoying way to communicate. When I am forced to attend this kind of meetings I am mumbling something like all the others, if that's what the supervisor wants, that's going to get, or simply I say "I have nothing to add".
When I have a problem I do not wait for the next meeting to raise it, I am doing it on spot, and try to solve it. And that is what I am expecting when the others have a problem with me, to raise it to me on spot.
When I have an achievement, I am expecting the recognition from my supervisor, instead of painting myself in heroic colors in public. And also, when I make a mistake I expect my supervisor to bare a part of the responsibility.
As I said, there is much to say, this is a very short version.
Dear katmar/Andrei Hello/ Good Afternoon,
It is really pleasure to see your replies conveying my feelings and I do second these in general.
However sometimes someone gets stucked-up with fulfillment of such demands of higher ups and finds no way-out.
For such instances (I was also once required to do this)
I suggest 'sheiko' to Google with the theme Jist and he should find lot of help indeed; that should be altered for your specific needs.
Hope this helps
Best regards
Qalander
#5
Posted 12 January 2009 - 01:23 PM
Qualander, nothing on google on this specific subject...unless you have found something relevant. In this case, could you please share some of them?
Thank you in advance.
Thank you in advance.
#6
Posted 13 January 2009 - 01:28 PM
QUOTE (sheiko @ Jan 12 2009, 11:23 PM) <{POST_SNAPBACK}>
Qualander, nothing on google on this specific subject...unless you have found something relevant. In this case, could you please share some of them?
Thank you in advance.
Thank you in advance.
Dear sheiko
Just Googled 'process engineers proper articulation/outline for a short presentation' obtained 151,000 results
Contact on my email to get few of the downlads or see the PM sent by me to your PM box for further help if any!
Regards
Qalander
#7
Posted 13 January 2009 - 01:51 PM
Thank you Qualander,
I have indeed found some material via Google, but they tend to be generic and academic.
The purpose of posting in this forum is to exchange real-world anecdots/advice with industrial professionals...
I have indeed found some material via Google, but they tend to be generic and academic.
The purpose of posting in this forum is to exchange real-world anecdots/advice with industrial professionals...
Similar Topics
Short Path Distillation Rotor SpeedStarted by Guest_MEC_* , 11 May 2023 |
|
![]() |
||
Practical Nonisothermal Reactors Design. Looking For Relevant ReferencStarted by Guest_lnbsak_* , 17 Apr 2021 |
|
![]() |
||
![]() Compressible Flow Through A Short PipeStarted by Guest_akstapp_* , 13 Jul 2018 |
|
![]() |
||
![]() Short Cut Method For Distillation Column ( Proii)Started by Guest_rahul vikram_* , 14 Jul 2015 |
|
![]()
|
||
Tanks Internal To Avoid Short Circuiting Of Oily WaterStarted by Guest_Arham_* , 18 Apr 2015 |
|
![]()
|