2002
DOI: 10.2307/3094806
|View full text |Cite
|
Sign up to set email alerts
|

Capability Traps and Self-Confirming Attribution Errors in the Dynamics of Process Improvement

Abstract: Senge, seminar participants at MIT, three anonymous referees, the editor, Christine Oliver, and the managing editor, Linda Johanson, for their careful reviews and constructive suggestions.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

8
384
0

Year Published

2008
2008
2018
2018

Publication Types

Select...
5
3
1

Relationship

1
8

Authors

Journals

citations
Cited by 400 publications
(406 citation statements)
references
References 61 publications
8
384
0
Order By: Relevance
“…Current engineering brings quick and clear rewards (customer satisfaction, management attention), development brings reward with some delay (when the project is successfully completed), and bug fi xing and capability development have even longer and more obscure connections between resource investment and observation of results. Research has shown that people tend to learn the wrong lessons in the presence of delays and feedback complexities, often to the detriment of long-term options (Sterman, 1994;Repenning and Sterman, 2002;Rahmandad, 2008).…”
Section: Impact Of Alternative Resource Allocation Policiesmentioning
confidence: 99%
See 1 more Smart Citation
“…Current engineering brings quick and clear rewards (customer satisfaction, management attention), development brings reward with some delay (when the project is successfully completed), and bug fi xing and capability development have even longer and more obscure connections between resource investment and observation of results. Research has shown that people tend to learn the wrong lessons in the presence of delays and feedback complexities, often to the detriment of long-term options (Sterman, 1994;Repenning and Sterman, 2002;Rahmandad, 2008).…”
Section: Impact Of Alternative Resource Allocation Policiesmentioning
confidence: 99%
“…It excludes many factors that are important in fully explaining Alpha and Beta's evolution, and focuses on how a core set of inter-project feedback processes can lead to tipping dynamics and performance heterogeneity in software development. As such, this paper follows a rich tradition of using case studies and simulation models to build grounded theory (Glaser and Strauss, 1973;Davis et al, 2007) on dynamic social phenomena (e.g., Forrester, 1968;Sterman, 1985;Ford and Sterman, 1998a;Repenning, 2002).…”
Section: Analysis Processmentioning
confidence: 99%
“…This is not the first time that a conceptual model without detailed formulations has been represented with stock and flow diagrams in the literature. For another example, please refer to Repenning and Sterman (2002).…”
Section: Discussion and Future Researchmentioning
confidence: 99%
“…The original work by Repenning and Sterman described combining an inductive methodological approach with system dynamics modelling where the outcome was intended to provide theories concerning the failure of process improvement projects in an organisation (Repenning & Sterman, 2002). In their analysis they describe the organisations they study falling into a "capability trap", a dynamic hypotheses arising from the inductively generated system dynamics models created from their qualitative data analysis.…”
Section: The Start and Fizzle Of Organisational Changementioning
confidence: 99%