Organizing for Servitization

Examining Front- and Back-end Design Configurations

Jawwad Raja, Mehmet Chakkol, Mark Johnson, Afmad Beltagui

Research output: Contribution to journalJournal articleResearchpeer-review

83 Downloads (Pure)

Abstract

Purpose: Research suggests that to structure for servitization, organizations should separate their front- and back-end units by reference to high vs low contact activities. However, these prescriptions are overly simplistic and largely based on anecdotal evidence that fails to account for context. The purpose of this paper is to explore the design decisions taken by organizations in support of servitization.
Design/methodology/approach: A large-scale exploratory case study was conducted, consisting of embedded cases in three divisions of a UK-based, global manufacturing firm.
Findings: Each division provided different combinations of offerings (i.e. product-, use- and result-oriented). The findings suggest that front-end/back-end configurations differ according to the offering and can exist concurrently within the same organization, challenging the assumption that different configurations within an organization are not possible. The findings show that underlying contextual factors, such as the complexity and temporality of the offering, as well as the power of the customer, have implications for the structuring of servitizing organizations.
Research limitations/implications: This is a context-specific, qualitative case study conducted within a large original equipment manufacturer, yet the findings are analytically generalized.
Originality/value: In identifying the relevance of different design decisions in terms of customer contact, decoupling of activities and grouping of employees, the findings challenge the extant view that organizations simply split activities between the front- and back-end functions. The research identifies an additional design configuration – integrated project teams – involving a dominant customer dictating organizational interfaces. This research exposes the need for further investigation into how to organize for servitization in project-based contexts.
Original languageEnglish
JournalInternational Journal of Operations and Production Management
Volume38
Issue number1
Pages (from-to)249-271
ISSN0144-3577
DOIs
Publication statusPublished - 2018

Keywords

  • Servitization
  • Case study
  • Front- and back-end units
  • Integrated project teams (IPTs)
  • Organizational design
  • Solutions

Cite this

@article{87d6e6c96a6b480887372631306dae04,
title = "Organizing for Servitization: Examining Front- and Back-end Design Configurations",
abstract = "Purpose: Research suggests that to structure for servitization, organizations should separate their front- and back-end units by reference to high vs low contact activities. However, these prescriptions are overly simplistic and largely based on anecdotal evidence that fails to account for context. The purpose of this paper is to explore the design decisions taken by organizations in support of servitization.Design/methodology/approach: A large-scale exploratory case study was conducted, consisting of embedded cases in three divisions of a UK-based, global manufacturing firm.Findings: Each division provided different combinations of offerings (i.e. product-, use- and result-oriented). The findings suggest that front-end/back-end configurations differ according to the offering and can exist concurrently within the same organization, challenging the assumption that different configurations within an organization are not possible. The findings show that underlying contextual factors, such as the complexity and temporality of the offering, as well as the power of the customer, have implications for the structuring of servitizing organizations.Research limitations/implications: This is a context-specific, qualitative case study conducted within a large original equipment manufacturer, yet the findings are analytically generalized.Originality/value: In identifying the relevance of different design decisions in terms of customer contact, decoupling of activities and grouping of employees, the findings challenge the extant view that organizations simply split activities between the front- and back-end functions. The research identifies an additional design configuration – integrated project teams – involving a dominant customer dictating organizational interfaces. This research exposes the need for further investigation into how to organize for servitization in project-based contexts.",
keywords = "Servitization, Case study, Front- and back-end units, Integrated project teams (IPTs), Organizational design, Solutions, Servitization, Case study, Front- and back-end units, Integrated project teams (IPTs), Organizational design, Solutions",
author = "Jawwad Raja and Mehmet Chakkol and Mark Johnson and Afmad Beltagui",
year = "2018",
doi = "10.1108/IJOPM-03-2016-0139",
language = "English",
volume = "38",
pages = "249--271",
journal = "International Journal of Operations and Production Management",
issn = "0144-3577",
publisher = "JAI Press",
number = "1",

}

Organizing for Servitization : Examining Front- and Back-end Design Configurations. / Raja, Jawwad; Chakkol, Mehmet; Johnson, Mark; Beltagui, Afmad.

In: International Journal of Operations and Production Management, Vol. 38, No. 1, 2018, p. 249-271.

Research output: Contribution to journalJournal articleResearchpeer-review

TY - JOUR

T1 - Organizing for Servitization

T2 - Examining Front- and Back-end Design Configurations

AU - Raja, Jawwad

AU - Chakkol, Mehmet

AU - Johnson, Mark

AU - Beltagui, Afmad

PY - 2018

Y1 - 2018

N2 - Purpose: Research suggests that to structure for servitization, organizations should separate their front- and back-end units by reference to high vs low contact activities. However, these prescriptions are overly simplistic and largely based on anecdotal evidence that fails to account for context. The purpose of this paper is to explore the design decisions taken by organizations in support of servitization.Design/methodology/approach: A large-scale exploratory case study was conducted, consisting of embedded cases in three divisions of a UK-based, global manufacturing firm.Findings: Each division provided different combinations of offerings (i.e. product-, use- and result-oriented). The findings suggest that front-end/back-end configurations differ according to the offering and can exist concurrently within the same organization, challenging the assumption that different configurations within an organization are not possible. The findings show that underlying contextual factors, such as the complexity and temporality of the offering, as well as the power of the customer, have implications for the structuring of servitizing organizations.Research limitations/implications: This is a context-specific, qualitative case study conducted within a large original equipment manufacturer, yet the findings are analytically generalized.Originality/value: In identifying the relevance of different design decisions in terms of customer contact, decoupling of activities and grouping of employees, the findings challenge the extant view that organizations simply split activities between the front- and back-end functions. The research identifies an additional design configuration – integrated project teams – involving a dominant customer dictating organizational interfaces. This research exposes the need for further investigation into how to organize for servitization in project-based contexts.

AB - Purpose: Research suggests that to structure for servitization, organizations should separate their front- and back-end units by reference to high vs low contact activities. However, these prescriptions are overly simplistic and largely based on anecdotal evidence that fails to account for context. The purpose of this paper is to explore the design decisions taken by organizations in support of servitization.Design/methodology/approach: A large-scale exploratory case study was conducted, consisting of embedded cases in three divisions of a UK-based, global manufacturing firm.Findings: Each division provided different combinations of offerings (i.e. product-, use- and result-oriented). The findings suggest that front-end/back-end configurations differ according to the offering and can exist concurrently within the same organization, challenging the assumption that different configurations within an organization are not possible. The findings show that underlying contextual factors, such as the complexity and temporality of the offering, as well as the power of the customer, have implications for the structuring of servitizing organizations.Research limitations/implications: This is a context-specific, qualitative case study conducted within a large original equipment manufacturer, yet the findings are analytically generalized.Originality/value: In identifying the relevance of different design decisions in terms of customer contact, decoupling of activities and grouping of employees, the findings challenge the extant view that organizations simply split activities between the front- and back-end functions. The research identifies an additional design configuration – integrated project teams – involving a dominant customer dictating organizational interfaces. This research exposes the need for further investigation into how to organize for servitization in project-based contexts.

KW - Servitization

KW - Case study

KW - Front- and back-end units

KW - Integrated project teams (IPTs)

KW - Organizational design

KW - Solutions

KW - Servitization

KW - Case study

KW - Front- and back-end units

KW - Integrated project teams (IPTs)

KW - Organizational design

KW - Solutions

UR - https://sfx-45cbs.hosted.exlibrisgroup.com/45cbs?url_ver=Z39.88-2004&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx&ctx_enc=info:ofi/enc:UTF-8&ctx_ver=Z39.88-2004&rfr_id=info:sid/sfxit.com:azlist&sfx.ignore_date_threshold=1&rft.object_id=954921370616&rft.object_portfolio_id=&svc.holdings=yes&svc.fulltext=yes

U2 - 10.1108/IJOPM-03-2016-0139

DO - 10.1108/IJOPM-03-2016-0139

M3 - Journal article

VL - 38

SP - 249

EP - 271

JO - International Journal of Operations and Production Management

JF - International Journal of Operations and Production Management

SN - 0144-3577

IS - 1

ER -