Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

Project Communications: What Are the Primary Categories of Comms? Need Advice. 2

Status
Not open for further replies.

bugeyebug

Mechanical
Jan 27, 2007
2
0
0
US
I'm working on a paper on the topic of communication management within an engineering project. I'd like to start the article by discussing the purpose of project communications. I have come up with five basic categories/reasons/purposes of comms, but would like to query this group to see what, if anything, I'm missing. Here's what I've got so far:
[ol 1]
[li]Inform (e.g., status reports)[/li]
[li]Request (e..g, purchase requisitions)[/li]
[li]Discuss (e.g., engineering brainstorming session)[/li]
[li]Decide (e.g., conclude and document findings of a trade study)[/li]
[li]Direct (e.g., assign tasks)[/li]
[/ol]

What else am I missing?
Thanks for any and all feedback!
 
Replies continue below

Recommended for you

All the above are a bit unidirectional. If you look at it for a moment from the other end of the telescope, you might come up with things like:

Authorise
Audit (request and provide non-routine information)
Define requirement
Regulate / impose constraints
Impose change
Clarify
Agree (including contractual arrangements and internal SLA)

A.
 
Specify. Contract technical specifications, scope of work, and drawings are to communicate to the Contractor what the work is and the project requirements.
 
Often times the purpose of an email is CYA.

==========
"Is it the only lesson of history that mankind is unteachable?"
--Winston S. Churchill
 
Note there is a distinction between upward communication (reporting to people above you) and downward communication (sending information, instruction, etc. to people below you). Upward communication is harder but more important.
 
Status
Not open for further replies.
Back
Top