Guest Post on Design News: Understanding the Differences between Strategic Sourcing Goals, Objectives, and Requirements
Early in the course of a product design and manufacturing organization’s strategic sourcing project it is common to have a kickoff meeting that includes the engineering team. It is the opportunity for the sourcing project team to lay the groundwork for the rest of the effort. One of the most critical discussions that should be a part of the kickoff is around the goals, objectives, and requirements for the project.
This is an effort to be taken seriously by both procurement, which should facilitate the discussion, and engineering, which provides critical inputs. Unlike a mission statement, which is often dismissed as being an overly soft (and largely meaningless) feel-good expression of early-stage enthusiasm, goals, objectives, and requirements are tools that will be used actively in the sourcing project once it reaches the decision-making stage.
When I worked as a consultant at a procurement solutions provider, I held workshops on kickoffs for the procurement teams I coached, as part of their project management skills development. There are two tricky lessons to be learned about goals, objectives, and requirements: how to formulate them and how to tell in which category an idea belongs.