L4M2 Exam Dumps : Defining Business Needs

Detailed Explanation:

Consumer data provides specific, measurable insights into purchasing behavior, preferences, and willingness to pay. This is the most accurate method for setting a pricing strategy, as it uses real-world data rather than subjective opinions or generic trends. Reference: CIPS Level 4, Market Research Techniques.

Explanation

Value Engineering (VE) is concerned with new products. It is applied during product development. The focus is on reducing costs, improving function or both, by way of teamwork-based product evaluation and analysis. This takes place before any capital is invested in tooling, plant or equipment.

This is very significant, because according to many reports, up to 80% of a product’s costs (throughout the rest of its life-cycle), are locked in at the design development stage. This is under-standable when you consider the design of any product determines many factors, such as tooling, plant and equipment, labour and skills, training costs, materials, shipping, installation, maintenance, as well as decommissioning and recycle costs.

The Kano model is a theory for product development and customer satisfaction developed in the 1980s by Professor Noriaki Kano, which classifies customer preferences into five categories. Both Kano model and Value Engineering aims at optimising new product, so they can be combined to-gether. CIPS L4M2 study guide consider Kano model is a tool of Value Engineering

Example of Kano model (source: Wikipedia)

Explanation

An Outcome Based Specification (OBS) focuses on the desired outcome of a service in business terms, rather than a detailed technical specification of how the service is to be provided; this allows providers scope to propose innovative solutions that might not have occurred to the procurement team. Outcome should be distinguished from output, which is the measurable results of a set of inputs. The example of difference between outcome and output is written at the bottom of page 123 in the study guide.

Outcomes should be the starting point in making new specification. However, using outcome-based specification has some setbacks:

- First, it is not easy to measure the outcomes. Usually, outcome of a project is a statement like 'increase customer satisfaction', 'maintain ambient temperature' or 'provide a convenient way to do something'. They are not easy to measure as output.

- Second, sometimes the desired outcomes require time to be materialised

- Third, outcomes can be ambiguous