Few things help a project — any project — more than objectivity. It's a great ability to view a task, whether editing a paragraph or designing a product completely free of emotion, but few people have that skill when it comes to their own work. That's why most companies use a project manager to guide the new product development process along.
Project managers act as a liaison between all the interested parties working together to get a product made — the customer, product designer, engineering team, manufacturer, sourcing team, suppliers and shipper.
A good project manager will:
The project initiation meeting takes place when early stage items like final drawing approvals, tool planning and prototyping are complete. The purpose of this meeting is to draft the Project Charter which outlines the project details at macro and micro levels. Questions to be addressed include:
These questions are directed to the customer and suppliers. Their answers are built into the Project Charter which is shared with the engineering team and business units for approval. The project scope is "set" and the Charter becomes the basis for all communication about the project.
It is the project manager's job to talk to their team, gathering the facts to create a project schedule that is based in reality. Sometimes negotiations have to happen in order to reconcile customer expectations and supplier capabilities. The project manager also explains any potential risks inherent in the project and applies any lessons learned from previous projects. The schedule is developed by asking the following questions:
If a project manager is really good, you rarely know they are there. They move in the background managing operations, often with the use of cloud-based software tools like Easy Projects, which enable them to monitor the progress of a project from remote locations.
If there is someone tasked with "follow up," it is probably the project manager looking for information from a business unit for a supplier, customer or engineer.
After samples are sent, approved and the project is moving forward, the project manager schedules a "lessons learned" meeting - an after-action debrief to discuss what steps worked and what didn't.
The lessons learned meeting is one of the most important steps in the product development process as information gained through experience helps the process get better each time.
A good project manager is like a pair of binoculars, able to move easily between the micro and macro view of a project. They know all data - good or bad - has value because it can be used to make the team better.
Product development is challenging enough on its own. Do you really want to go through the process without project manager to help guide you through it? Make sure your contract manufacturer uses project managers in their product development process. You will be so glad you did.