All case descriptions follow the schema proposed by vom Brocke and Mendling (2017)*. Authors should use the provided Springer Template to describe their cases following this structure.
Each case description should be preceded by a structured abstract briefly summarizing the essence of the case:
- Situation faced (approx. 100 words)
- Action taken (approx. 100 words)
- Results achieved (approx. 100 words)
- Lessons learned (approx. 100 words)
The title and abstract should include the name of the company or organisation.
All case descriptions follow a unified structure that makes their insights easily accessible and transferrable to other contexts. Following this structure, case descriptions will be short and sharp with only 5.000 to 8.000 words overall (which equals 10 to 15 pages in the Springer Template). The unified structure helps writing case descriptions (for authors) as well as finding the most interesting parts of the cases (for readers).
The proposed structure is as follows:
- Introduction – What is the story of the case? Please give a brief narrative of the entire story to make people interested in the case. Summarize the key figures of the company. (approx. 500 words)
- Situation faced – What was the initial problem situation? What situation led to the action taken? Please try to specify the context of your case as to needs, constraints, incidents, opportunities, objectives, or other? (approx. 500 – 1,000 words)
- Action taken – What has been done? What measures have been taken? Which methods and approaches have been used? Please try to be factual in this passage with no judgement or evaluation, which is to come in the subsequent sections. (approx. 2,000 – 2,500 words)
- Results achieved – What effects could be observed resulting from the action taken? This could be changes in performance as well as qualitative statements from employees, customers, or other business partners. To what extent did expected results materialize and to what extent were expectations not met? (approx. 1,000 – 2,000 words)
- Lessons learned – Reflecting the overall case, what can others learn? Please derive around five lessons learned, which are grounded in the case and which are interesting for other to take as an example. (approx. 1,000 – 2,000 words)
Accompanying case materials (such as company presentations, teaching materials, etc.) are optional and can be handed in with final acceptance of the case. The actual name of the case company must be mentioned both in the title and throughout the manuscript. We strongly prefer author teams including co-authors from both academia and the focal case company.
Authors should provide references to key concepts that are used for describing the case, the definitions of the methods used or adapted, and contextual information on the company and industry. The editors have developed a reference framework to support a shared terminology in the book. Further references to seminal articles from the literature are welcome. Authors might also want to highlight in which way theirs results are in line or not with what has been described in other work.
All in-text and references should be formatted following the guidelines provided by the Springer Basic Author Date style. The style is available in all major citation management systems such as Citavi, EndNote, or Mendeley. A full description of the citation style including in-text reference and the reference list can be found here. For Endnote users, the Springer Basic style can be downloaded here.
* vom Brocke, J. and Mendling, J. (2017) Frameworks for Business Process Management: A Taxonomy for Business Process Management Cases, in: J. vom Brocke, J. Mendling (Hrsg.), Business Process Management Cases: Digital Innovation and Business Transformation in Practice, Springer 2017.