You are currently visiting the test version of the radboud Dspace repository. To access the production instance, you can navigate to: https://repository.ubn.ru.nl
The relation between openness and closure in open strategy: Programmatic and constitutive approaches to openness
Publication year
2019Author(s)
Publisher
Cambridge : Cambridge University Press
ISBN
9781108424868
In
Seidl, D.; Von Krogh, GT.; Whittington, R. (ed.), Cambridge handbook of open strategy, pp. 326-336Publication type
Part of book or chapter of book

Display more detailsDisplay less details
Editor(s)
Seidl, D.
Von Krogh, GT.
Whittington, R.
Organization
SW OZ RSCR CAOS
Languages used
English (eng)
Book title
Seidl, D.; Von Krogh, GT.; Whittington, R. (ed.), Cambridge handbook of open strategy
Page start
p. 326
Page end
p. 336
Subject
Anthropology and Development StudiesAbstract
Two facets are all but universally present in current works on Open Strategy. First, while being aware of and addressing challenges and dilemmas associated with openness in strategy making (Hautz et al., 2017), increasing openness is mostly perceived as normatively good, as an ideal that should be achieved. Generally speaking, studies on openness in strategy making focus on different forms and degrees of collaboration with newly invited actors and on the potential benefits of Open Strategy by generating more and more suitable ideas (Whittington et al., 2011; Stieger et al., 2012; Aten & Thomas, 2016). Even when tensions and dilemmas of greater openness such as "compromising speed", "undermining competitiveness", or "burdening wider audiences with the pressures of strategy" (all taken from the overview in Hautz et al., 2017: 302) are discussed, these are considered limitations or hurdles to be overcome for achieving the desired greater openness.
This item appears in the following Collection(s)
- Academic publications [244578]
- Faculty of Social Sciences [30295]
Upload full text
Use your RU or RadboudUMC credentials to log in with SURFconext to upload a file for processing by the repository team.