SPALTEN

Revision as of 15:38, 9 February 2021

Author: Felix Dressel

This page is under construction

Abstract

The SPALTEN problem-solving process was initially published in 2002 by Albers et al. as a method which is universally applicable to any sort of problem in product development and project management.^[1] SPALTEN can be adapted in condition and complexity to any problem. Its strength is to gather and analyze the given situation as well as to create, rate and select possible solutions. The method also enables the user to divide one big problem into smaller ones. Consequently, it is easier to manage the problem and work out a solution.^[2] It is confirmed, that due to its flexibility, engineers are able to apply SPALTEN throughout the entire product development process as well as across multiple other activities in project management.^[3]

The term SPALTEN was designed as an acronym representing its different steps (in German). The method is structured by seven working steps, each of which can be carried out with different subordinate methods.^[4] The seven steps are:

1.(S) Situation Analysis

2.(P) Problem Containment

3.(A) Alternative Solutions

4.(L) Selection of Solutions

5.(T) Consequences Analysis

6.(E) Make Decision and Realization

7.(N) Recapitulate and Learn

Big idea

Application

Limitations

Annotated bibliography

References

1. ↑ Albers, A., M. Saak, N. Burkhardt, and D. Schweinberger (Eds.). 2002. Gezielte Problemlösung bei der Produktentwicklung mit Hilfe der SPALTEN-Methode
2. ↑ Albers, Albert, Nicolas Reiß, Nicola Bursac, and Jan Breitschuh (Eds.). 2016. 15 Years of SPALTEN Problem Solving Methodology in Product Development
3. ↑ Saak, Marcus. 2006. Development of a concept and of a prototype for a computer-aided tool for the efficient employment of the problem solving methodology "SPALTEN"
4. ↑ Albers, Albert, Nicolas Reiß, Nicola Bursac, and Jan Breitschuh (Eds.). 2016. 15 Years of SPALTEN Problem Solving Methodology in Product Development