Value Analysis is a structured method. However, the success of a project does not depend solely on whether individual tools are applied in a formally correct way.
What matters is the interplay of project selection, management support, team, data, methodological approach, facilitation and implementation.
1. Select the Right Project
A project with little economic leverage, technology that can hardly be changed or missing data can only have a limited effect, even with good facilitation.
It should therefore be checked before the start whether the product, assembly or process is actually suitable. A Project Potential Assessment can help with this.
2. Create a Clear Project Brief
The team needs clarity on:
- objectives,
- scope of the study,
- cost target,
- time frame,
- decision-making authority,
- technical constraints.
Unclear objectives quickly lead to fundamental debates instead of project work.
3. Secure Management Support
Value Analysis projects often affect existing solutions, standards and responsibilities. Without visible support from management, decisions and implementation can stall.
Management attention does not mean dominating every workshop. What matters are clear priorities, resources and the ability to make decisions.
4. Put Together the Right Cross-Functional Team
Value is created across departmental boundaries. The perspectives relevant to the product, costs and customer should therefore be represented.
Typical roles come from development, procurement, production, product management, cost estimating, sales, quality and, where appropriate, service.
5. Prepare Reliable Data
Creativity is no substitute for a sound data basis.
Costs, unit volumes, technical documentation, competition, customer requirements and relevant constraints should be structured before the project, as far as they are available.
6. Don't Jump into Idea Generation Too Early
A common mistake is to start straight away with brainstorming.
First, the team should understand:
- what customers need,
- which functions the product performs,
- where costs arise,
- which opportunity areas are relevant.
Only then does the creativity phase become focused.
7. Facilitate Professionally
Cross-functional teams need structure. Discussions may go into technical depth, but they must repeatedly be brought back to the actual question.
Good facilitation ensures that all relevant perspectives are taken into account, decisions are made transparently and tasks are followed through consistently.
8. Evaluate Ideas Methodically
A long list of ideas is not a project result.
Ideas must be evaluated in terms of technical feasibility, cost impact, investment, risk, time, impact on customers and other project-specific criteria.
9. Develop Concepts Rather Than Individual Actions
Several individual ideas can influence one another. Relevant actions should therefore be bundled into consistent concepts and assessed in terms of their overall effect.
10. Plan for Implementation from the Start
The project must not end with the final presentation.
Responsibilities, verification tasks, decisions, deadlines and tracking are part of the project. The actual technical implementation typically remains embedded in the company's line or project organisation.
Conclusion
Even the greatest methodological effort achieves little if the wrong project is chosen, the team is not given time for the work or implementation is not organised.
Successful Value Analysis therefore combines method and project organisation.
Further Reading
- The Value Analysis Work Plan in 10 Steps
- Cross-Functional Teamwork in Value Analysis Projects
- Evaluation in Value Analysis
- Implementation: Turning Ideas into Effective Actions
- Project Potential Assessment: Selecting the Right Projects
- Cost Reduction Project and Cost Reduction Workshop
- Function Analysis: Looking at Tasks Instead of Components
- Function Cost Analysis: Allocating Costs to Functions
- Our Consulting Process for Value Analysis Projects
- Value Analysis Project Examples and References
