It is understood that communication is the most basic and commonly used tool for human interaction. I realize that there are a lot of management groups that take the concept of communication for granted and create a reactive communication environment. It is understood that in the current market, all workers communicate with one another. The technique that is absent in several establishments is the importance of what needs to be communicated and how is communicated and to ensure that whoever we are communicating to, understands the objective.
What I came to understand is that useful and feasible information and wise decision are the most important aspects of communication. In the engineering design world, when a customer is looking for a custom product then it has to be feasible. It is obvious that a company will not be able to deliver a product that cannot be made with the current technology. So understanding current limitations is vital for development and success. Customer requirement(s) is a form of useful information. We, as a design company, must deliver a product that will meet or exceed the customer’s expectations. In order for a company to do so, customer’s requirement must be documented and relayed to the design and manufacturing group so that the product can be built to customer’s specifications. Finally, making wise decisions during the implementation, manufacturing and delivery of the product must be present. For example delivering a known non-conforming product to the customer, just to meet deliver date, can and will damage customer’s relations and eventually this reputation will drive the business to failure.
This comment has been removed by the author.
ReplyDeleteAnexi, you highlight three great principles: utility (Is the info useful?), feasibility (Can we actually do this?) and wisdom (Will it best meet customer needs?)
ReplyDeleteI also grasp your organizational context as an engineer. Continue to work on your grammar and usage of English. It is rough and will prove a distraction to audiences who could benefit from your excellent insights.
Anexi,
ReplyDeleteLiked your post. I can draw some parallels between engineering work and IT work. As you mentioned, engineering work needs ongoing feedback from customer to define the specifications. I am not IT filed but have had an interaction who is in IT filed. It seems for IT projects too, supplier and customer has to go through round of discussions to define the scope or specifications for the project. I am sure that you can also see how important the need for the spec is. Almost all the work is done comparing the specifications defined upfront. Thank you for sharing.