This week, I want to discuss the gathering of PLM requirements.
Over the years, I have learned how important it is to gather requirements. The better job you do of gathering requirements, the better the PLM implementation. Thorough, complete requirements will make your job of implementing PLM software easier.
Any changes you make during the implementation will increase the complexity and the price of that implementation.
Active Listening Helps
Active listening is about hearing what people are really saying. You need to let the other person know that you are listening to what he or she is saying.
Pay attention to what they are saying. Look directly at them and acknowledge what they have said. An acknowledgement can be as simple as a nod of the head or a simple ‘uh huh.’
To be sure, restate what you thought you heard in your words. If you got it wrong, they will be able to explain themselves. You can ask things like ‘what do you mean by that’ to get an explanation.
Why is this important?
Again, better requirements will help you arrive at a better PLM implementation.
You see a person go into a hardware store to purchase a ¼ inch drill bit. Do they really want the drill bit? Or do they actually want what the drill bit will do for them – create a ¼ inch hole.
The same thing can happen when gathering requirements. You need to know why that requirement is important to them. What do they want it to do for them?
This may increase the time needed to gather requirements, but it will shorten the actual implementation time and increase the odds for a successful implementation.
Good luck – Need some help?