Impact of organizational identity as an institutional context on resource integrationĭesign/methodology/approach – The thesis makes use of interpretive
The purpose of this thesis is to conceptualize and to empirically investigate the Institutional arrangements that shape the resource integration processes mayĮmerge, leading to imperfect value co-creation or even value co-destruction. Typically not harmonious with each other, at least partial misalignments of the Reference to the resource-integrating actors. Specifically, the different organizational identities provide institutional frames of Successfully for all partners, not least because many projects are characterizedīy sometimes dramatic failures with respect to costs, duration, and scope. The question of how resource integration for value co-creation can be shaped With respect to the participating firms building a service ecosystem. That several supplier firms participate in their development and delivery.Ĭonsequently, such project networks are characterized by a great heterogeneity The qualitative and quantitative scope of many project networks requires Purpose – Project business represents a large part of the business-to-business Our findings shed new light on the role of breakdowns and decoupled collaborative paths in programs oriented at contributing to system transformation. Over time, these navigating practices promoted progress towards program objectives via multiple parallel collaborative paths. These are aligning contexts, prioritizing contexts, and adding contexts. We identified three practices of context navigation that actors used to integrate the program into multiple parent organizations and address emerging incongruencies among contexts. We draw on a qualitative field study of an interorganizational program designed to help transform the Dutch healthcare system. Because system transformation programs can only succeed when changes are implemented by multiple organizations, an increased understanding of integrating programs in multiple contexts is needed. This paper unpacks how actors navigate the multiple organizational, interorganizational and industry contexts that are associated with system transformation programs for addressing wicked, societal problems. The findings suggest that in both cases the management responses altered across time and evolved depending on the salience of the institutional pressure, through the interplay with 1) regulative, 2) normative, and 3) dynamic cultural-cognitive forces, resulting in cycles of project legitimacy. This paper provides the institutional fields' contextual detail and deepens our understanding of temporal institutional complexity that bound large-scale project arrangements. The qualitative secondary data analysis of two High-Speed rail projects in Spain and The Netherlands is based on semi-structured interviews, observations, and document analysis. Given the industry as the field-level institution, this study explores how two project organizations experienced the industry changes, its influence on the arrangement of large-scale projects, and the management response used to legitimize these arrangements. AppDataProvider or CarPageDataProvider to keep your App/page components clean.Heeding recent calls for more studies on the relationship between projects and institutions, this paper reports on a collaborative case study to shed light on the recursive relations of large-scale projects and their institutional fields. If you're using lots of providers together you can always extract the logic into a separate component e.g. For example I'd prefer `const cars = useContext(CarsContext)` over `const app = useContext(AppContext) const cars = app.cars`.
#Multiple contexts have a path of code
Using a single context may make a components dependencies much less obvious and code more verbose.
Will having a large single context make your life difficult when writing tests, storybook stories etc? Would it be beneficial to use the context independently? Perhaps a cars page would just use CarsProvider, a users page just uses UsersProvider, and a car owners page uses both providers.
#Multiple contexts have a path of update
Do different parts of the contexts data update independently? If so then using a single context may degrade performance and UX due to unnecessary re-renders. Is the data related? If not it'll probably make sense to have separate contexts. I'd generally lean towards lots of smaller providers but it depends on the context (pun intended) of what data you're providing.