Free Certified Value Specialist Practice Questions

The correct answers are A and D . When a VM study team struggles to complete a FAST diagram, the facilitator should guide the team through questioning, not take control of the technical work. Asking whether a function is missing is an appropriate facilitation technique because a break in the How/Why logic often means the team has skipped a needed function, used an unclear verb-noun statement, or failed to connect a supporting function to a higher-order function. This keeps ownership with the team while helping them complete the logic chain.

Reviewing the level of abstraction is also correct. FAST diagramming requires functions to be placed at the right level: not too broad, not too detailed, and consistent with the project scope. If one function is stated at a strategic level and another at a component-detail level, the FAST diagram becomes difficult to organize.

Option B is incorrect because the facilitator should not reorganize the functions for the team; that weakens team participation and ownership. Option C is incorrect because not every identified function must appear in the final FAST diagram. Only functions that support the logical function model should be used.

References/topics: Function Analysis Phase; FAST Diagramming; Facilitation; Function Logic; Level of Abstraction.

The correct matches are FAST Diagram = Describes the purpose of the study subject and Flowchart = Describes the activities of the study subject . In Value Methodology, a FAST diagram is not an activity map. It is a function model. SAVE’s Study Guide defines a function as the original intent or purpose that a product, service, or process is expected to perform, expressed in active verb/measurable noun form. It also defines FAST as a graphical representation of dependent relationships between functions within a project. Therefore, FAST is used to understand the functional purpose and how functions logically relate through “how/why” thinking.

A flowchart is different. It represents process flow: the sequence of activities, steps, or operations used by the study subject. SAVE’s glossary defines a process as a sequence of activities that delivers a product or project. That aligns directly with the option “Describes the activities of the study subject.”

“Identifies flaws” is too narrow; defects may be discovered during analysis, but that is not the defining purpose of either tool. “Prioritizes activities” is also incorrect because prioritization normally belongs to evaluation or decision methods, not basic FAST or flowchart definition.

References/topics: Function Analysis Phase; FAST Diagramming; Function Modeling; Process Flowchart; How-Why Logic.

The correct answers are A, C, and D because the Presentation Phase is focused on communicating developed VM results in a form that enables decision makers to understand, judge, and act on the team’s recommendations. SAVE’s Value Methodology Standard describes the Presentation Phase as the point where the team leader develops a report or presentation that “documents and conveys the adequacy” of the developed alternatives and their value improvement opportunity. ( )

Therefore, tailoring the material to the participants is essential. Executives, technical reviewers, owners, cost specialists, and implementation personnel require different levels of detail and emphasis. Timing of the presentation is also critical because VM results should be presented while the study findings are current, decision attention is active, and implementation momentum has not been lost. Level of development of proposal write-ups is equally important because weak or incomplete write-ups reduce credibility and make approval difficult.

Option B is incorrect because the team should not present every idea generated in Creativity; only evaluated and developed alternatives should advance. The Evaluation Phase selects ideas with value potential, and the Development Phase turns selected ideas into documented proposals for decision making. ( )

References/topics: Presentation Phase; Development Phase; VM Proposal Write-Ups; Decision-Maker Communication; VM Results Presentation.

The correct “How” direction follows the classical FAST logic path from the broader purpose toward the dependent means of accomplishment. SAVE defines FAST as a graphical representation of dependent relationships between functions and states that a Classical FAST model displays function interrelationships using how-why logic . In this eyeglasses example, Improve vision is the higher-order purpose: it explains why the basic function exists. The basic function is Correct vision , because prescription eyeglasses exist primarily to correct the user’s vision. Moving in the “How” direction, the system corrects vision by Position lenses and Secure lenses ; the frame, bridge, arms, and nose pads exist to keep corrective lenses in the proper relationship to the eyes. The farthest “How”/lower-order decision is Select eyeglasses and Select contact lenses , representing the selected means or alternative correction approach.

The distractors are not on the critical function logic path. Secure position and Resist damage are supporting or secondary dependability functions. Complement appearance is a sell/aesthetic function, because it improves user acceptance but does not define the primary functional logic. SAVE’s glossary distinguishes higher-order, lower-order, and secondary functions and explains that secondary functions support the basic function through a specific design approach.

References/topics: Function Analysis Phase; FAST Diagramming; How-Why Logic; Critical Function Logic Path; Basic, Higher-Order, Lower-Order, and Secondary Functions.