Your peers, team mates, and management want to understand your writing. They want to quickly get your point, find supporting information, and take action.
As a reliability engineer, you write proposals, plans, and reports. You write problem statements, failure analysis findings, recommended process improvements, and much more.
You write to document a process or plan. More often you write to encourage others to take action. Continue reading
Did you hear what they said? Or, were you busy loading for your next verbal barrage?
As my mother would remind me, one should listen twice of often as speaking. Something about the ratio of ears to mouths in the population. I have to agree with her, that one can learn a lot by listening.
Listening may not seem to be a skill that one needs to master. Yet, how often have you walked away from a meeting where one or more participants obviously were not listening? How often are points repeated in an effort to be heard? Continue reading
Not every request we make is fulfilled. Not every assignment is accomplished. Not every task we assign is completed.
Why is that? Possibly, the lack of a complete request.
It may be the person we made the request to was incapable or decided to ignore us. Or, more likely, it may be our request was not clear. Continue reading
We facilitate. As reliability professionals, we often lead teams to identify risk. We help cross-functional teams find and implement solutions. We bring people together and ease their ability to communicate clearly with each other.
Whether a leader or participant we have a role to achieve the desired goals. Our ability to facilitate enables us to work with others to get things done. Understanding how to facilitate well permits us to add value when leading or participating on a team.
The process to design and deliver a reliable product involves identifying risks. Taking action to understand or mitigate those risks involves much of the day to day work of reliability engineering.
Taking action to set expectations and improve decisions involves change. Change of understanding, change of specifications, change of expectations, change of designs, processes, and results. Continue reading