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.
Results<br />
Q42 (Center, top manager): ”The current managers of the program apparently<br />
feel that they would have needed more guidance, more work <strong>and</strong> guidelines<br />
from the management group. But as a management group member myself I can<br />
say that all other programs, good programs, do that work themselves: they<br />
create plans <strong>and</strong> then get them accepted. It cannot be so that you just sit still <strong>for</strong><br />
1.5 years, wondering why the top management does not provide you with the<br />
instructions…”<br />
During the second round of interviews, the program should already have<br />
been in implementation, but it still could not demonstrate viability. The<br />
perceived lack of <strong>readiness</strong> of Center’s program is in line with the decision<br />
to terminate the program prematurely, which was made a few months after<br />
the second round of interviews. Although there had been some advances<br />
<strong>and</strong> some small-scale effects stemming from the program, Center’s change<br />
program was concluded to be more or less a failure.<br />
In terms of <strong>readiness</strong> <strong>for</strong> change program implementation, case Bureau<br />
showed a very different story. Firstly, the program seemed to have acquired<br />
a shared intent, at least <strong>for</strong> the most part. Early program initiation <strong>activities</strong><br />
in Bureau had aimed at providing rationale <strong>for</strong> the change through a<br />
systematic current state analysis. This phase was largely considered<br />
successful, resulting in a shared underst<strong>and</strong>ing of the need <strong>for</strong> change: all<br />
seemed to agree that Bureau’s current IT management was outdated <strong>and</strong><br />
required renewal. The participative approach of the second phase of<br />
program planning, implemented as a series of workshops, had also resulted<br />
in a high-level vision <strong>for</strong> the program, which was shared at least by those<br />
involved in planning. People seemed to have a common view of the purpose<br />
<strong>and</strong> main goals of the program. The general planning phase resulted in an<br />
overall plan <strong>for</strong> the program. One of the interviewees described the<br />
situation in the following way:<br />
Q43 (Bureau, manager of a central unit involved in the program): “There are still<br />
some issues, even major ones, to solve, but the program’s main principles, goals<br />
<strong>and</strong> plans have been commonly accepted.”<br />
After the centralized planning phase, more detailed planning was left to the<br />
project teams. Key actors of different projects had varying views about<br />
whether the level of detail during the general planning had been sufficient<br />
<strong>and</strong> whether the instructions <strong>and</strong> guidelines given to the project teams had<br />
been specific enough. As a result, some projects were unable to come up<br />
with detailed plans in the original schedule. The following quote describes<br />
the situation:<br />
Q44 (Bureau, manager of a central unit involved in the program): “It would have<br />
been better if the projects had been able to concretize their plans in more detail.<br />
It would have made the follow-up easier <strong>and</strong> also decreased the number of<br />
142