Need → Function → Specific Requirement → Product
The correct order is Need → Function → Specific Requirement → Product . This is the exact logic of the Function Performance Specification process. The VM Guide figure for Function Performance Specification shows the sequence as “Need Function Specific Requirement Product” , where a user need is translated into a function, then into measurable requirements, and finally into a product solution.
The sequence is important because Value Methodology begins with the user’s need or desire , not with a predetermined product. After the need is understood, the VM team defines the function that satisfies that need, normally in active verb/measurable noun format. SAVE’s study-guide material explains that work functions are quantitative and stated using an active verb and measurable noun. The next step is the specific requirement , where the function is converted into measurable performance or quality criteria, such as assessment criteria, level, and flexibility. Only after the need, function, and requirement are clear should the team identify the product , which is the solution provided to satisfy the defined need. Starting with “Product” would be a classic VM error because it locks the team into a solution before understanding function.
References/topics: Function Analysis Phase; Function Performance Specification; Need; Function; Specific Requirement; Product; Performance Criteria.
