Boundary activities and readiness for ... - Projekti-Instituutti
Boundary activities and readiness for ... - Projekti-Instituutti
Boundary activities and readiness for ... - Projekti-Instituutti
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Research methodology <strong>and</strong> data<br />
point, all these issues were coded in the interview transcripts by connecting<br />
the quotations with the corresponding codes. The next step in the analysis<br />
was to dig deeper into the associations between the central constructs, to<br />
create case-specific descriptions of these phenomena <strong>and</strong> to compare the<br />
cases in the cross-case analysis. These tasks were in the focus during the<br />
third phase of the analysis.<br />
3.5.3 The third phase of the analysis<br />
In the beginning of the third analysis phase, the data was again divided<br />
based on the three cases, <strong>and</strong> case-specific analyses were conducted to<br />
characterize the studied phenomena in each case. The categorizations<br />
created during the second analysis phase provided a framework <strong>for</strong> this<br />
analysis. Firstly, the identified aspects of the program-parent organization<br />
boundary were analyzed by examining if <strong>and</strong> how they appeared in each<br />
case. The overall boundary strength of each case program was also<br />
characterized. A same kind of an analysis was conducted <strong>for</strong> the indicators<br />
of <strong>readiness</strong> <strong>for</strong> change program implementation, describing whether each<br />
identified aspect of <strong>readiness</strong> was present in the cases at the end of the<br />
initiation <strong>and</strong> planning stage. While in cases Center <strong>and</strong> Chain two rounds<br />
of interviews had been conducted, the assessment of <strong>readiness</strong> <strong>for</strong> program<br />
implementation mainly relied on the data from the latter rounds of<br />
interviews. In Bureau, the only round of interviews was conducted when the<br />
program had just moved to the implementation stage, so <strong>readiness</strong> <strong>for</strong><br />
program implementation was judged based on the situation at the time.<br />
During the third phase of the analysis, the boundary <strong>activities</strong> were<br />
analyzed in more detail <strong>and</strong> their associations with <strong>readiness</strong> <strong>for</strong> change<br />
program implementation as well as the related contextual factors were<br />
examined. For the purpose of this analysis, a spreadsheet <strong>for</strong>mat was<br />
chosen <strong>and</strong> Microsoft Office Excel 2007 was used as a tool. The data set<br />
coded in Atlas.ti software during the second phase of the analysis was<br />
revisited, focusing on the identified boundary <strong>activities</strong>. All quotations<br />
referring to boundary activity were copied into the MS Excel spreadsheet.<br />
One row in the spreadsheet was dedicated to each of these quotations. For<br />
each quotation referring to a boundary activity, the following issues were<br />
coded to the spreadsheet in separate cells: the actual quote from the<br />
interview, the pseudonym name of the corresponding case, the interview<br />
identification number, the type of the boundary activity, the possible<br />
second type of the boundary activity, a short description of the distinct<br />
boundary activity, the actor who had per<strong>for</strong>med the activity, the target of<br />
the activity (e.g. top management/employees in general), the perceived<br />
effect on the <strong>readiness</strong> <strong>for</strong> change program implementation, <strong>and</strong> the<br />
possibly related contextual factors. Furthermore, an additional data field<br />
96