A cost reduction project often starts under time pressure. Manufacturing costs are too high, margins are falling or a cost target in a development project is missed.
It is then tempting to schedule a workshop at short notice and collect as many cost-saving ideas as possible.
However, a workshop on its own is not yet a cost reduction project.
To turn ideas into commercially relevant and technically feasible actions, you need a clear project charter, reliable data, the right departments and a structured methodology.
When does a cost reduction workshop make sense?
A facilitated workshop makes particular sense when:
- a product is well above its cost target,
- several departments need to be involved in the solution,
- existing optimisations are not sufficient,
- new technical solution approaches are needed,
- product and manufacturing costs are to be reduced not only through procurement,
- a team needs to agree on shared priorities quickly.
The workshop is part of an overall process, not a substitute for it.
Before the workshop: clarify the project charter and data basis
Before the team works together, the following should be clarified:
- Which product or assembly is being examined?
- Which cost target is being pursued?
- Which unit volumes and boundary conditions apply?
- What data is available on costs, competitors and customer requirements?
- Which decisions may be made within the project?
- Which departments need to be involved?
- What technical or regulatory constraints exist?
The better these foundations are prepared, the more effectively the joint working time can be used.
Putting together the right team
Cost reduction is rarely a task for R&D or procurement alone.
Typical project teams therefore combine different perspectives, for example:
- Design engineering and R&D
- Procurement
- Production and manufacturing
- Cost estimating / controlling
- Product management
- Sales
- Quality
- Service
The composition depends on the product and the specific question.
Start with understanding, not with ideas
In a structured Value Analysis project, the creativity phase is not started immediately.
First, the essential foundations are established:
Customer requirements
Which criteria actually matter to the relevant customer groups? Which features must be retained? Where might there be technical overengineering?
Competition
How do competitor products differ in price, performance, structure and technical principles?
Functions
Which tasks must the product perform? Which functions do individual components and assemblies perform?
Function costs
Which functions cause high costs? Where might effort and importance be out of proportion?
Only on this basis are prioritised opportunity areas for solution development derived.
Ideation workshop: working on the right questions
The central question is then not simply:
“Where can we save?”
but, for example:
- How could this function be performed more simply?
- Can components be integrated?
- Are variants really necessary?
- Are there other working principles?
- Can standard or bought-in parts be used?
- Are tolerances or specifications higher than necessary?
- Are there alternative manufacturing or assembly processes?
This makes idea generation more focused and methodologically robust.
Evaluating ideas and developing them into concepts
Not every good idea makes economic sense or can be implemented in the short term.
Solutions are therefore subsequently evaluated in terms of technical feasibility, cost impact, investment, risks, implementation time and impact on customers, among other things.
Individual ideas are then combined into viable concepts.
Implementation is part of the project
A cost reduction project should not end with the presentation of the workshop results.
What matters is that responsibilities, next steps, verification tasks and decisions are defined. Implementation usually remains the company’s responsibility, but it can be supported methodologically and tracked.
The role of external facilitation
An external facilitator does not take over the team’s technical responsibility. Their task is to structure the methodological work, bring together different specialist perspectives, focus discussions on the relevant questions and prepare decisions.
Particularly in cross-functional projects, this neutral role can help to avoid local optimisation by individual departments.
Two documented projects illustrate this role: the Carl Zeiss Meditec project example: a facilitated online project under time pressure, with purely online team meetings and a very short time frame, and the thyssenkrupp project example: focus in special-purpose machine building, in which the team was repeatedly brought back from detailed technical discussions to what really mattered.
Cost reduction projects with Value Coaching
Value Coaching supports Value Analysis and Value Engineering projects in industrial companies. The approach combines customer requirements, Function Analysis, function costs, competitor analysis, creativity, evaluation and implementation.
The reference projects documented on this website show different applications of this approach. Specific project results apply only to the documented project in each case.
Next step
If it is not yet clear which product has the greatest cost optimisation potential or how the project should be scoped, a Project Potential Assessment is recommended as a first step.
Further reading
- Bringing R&D, procurement and production together in cost optimisation
- Roles in a Value Analysis project
- Cross-functional teamwork in Value Analysis projects
- Implementation: turning ideas into effective actions
- Systematic product cost reduction
- Project Potential Assessment: selecting the right projects
- 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
- Discuss your project: book an initial consultation


