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 />
Q8 (Bureau, project participant): “Of course, when the same people do similar<br />
tasks in the line organization <strong>and</strong> in the project, it is very difficult to identify<br />
whether it is project work or line work.”<br />
Compared to case Center, the program management approach caused less<br />
confusion in Bureau, where there was a long history of systematically<br />
managed internal projects. Still, internal change programs of this<br />
magnitude had never been implemented. Many interviewees recognized<br />
that the program involved a mode of working that was distinct from the<br />
traditional work mode of Bureau. As an example, one program participant<br />
characterized the differences in the mode of working in the following way:<br />
Q9 (Bureau, middle manager of a central unit involved in the program): "One<br />
noticeable difference in the work methods is that in [the program] we have<br />
clearly sought <strong>for</strong> partnerships <strong>and</strong> partner companies, <strong>and</strong> we have<br />
outsourced larger entities than be<strong>for</strong>e."<br />
Bureau’s hierarchical organization structure <strong>and</strong> the organization’s<br />
fragmentation into separate, strong units were reflected in the change<br />
program as indicators of an authority boundary. The responsibilities in<br />
Bureau’s program were mostly clear <strong>and</strong> well-defined, but they were largely<br />
dictated by, <strong>and</strong> restricted by, the authority structure of the line<br />
organization. One support team manager described:<br />
Q10 (Bureau, support team manager): “The implementation of a large program<br />
is a huge challenge in a functional, hierarchical organization such as ours. In<br />
principle, the program or project manager’s resources <strong>and</strong> authority are<br />
precisely as high as his or her position in the line organization.”<br />
The original program manager <strong>and</strong> the original program owner utilized<br />
Bureau’s <strong>for</strong>mal decision-making hierarchy <strong>and</strong> gained the required<br />
authority by actively lobbying <strong>for</strong> top management support <strong>for</strong> the program.<br />
When the top management was convinced about the need <strong>for</strong> change, the<br />
program was granted substantial authority. Thus, the authority boundaries<br />
evolved during the early program stages due to actions of the key program<br />
actors.<br />
The geographical fragmentation of the Bureau’s organizational units was<br />
also manifested as physical <strong>and</strong> spatial boundaries, providing challenges<br />
<strong>for</strong> cooperation during program planning. In Bureau, virtual<br />
communication tools were quite actively utilized to maintain contact<br />
between the geographically scattered units. Such tools were also utilized in<br />
the program work.<br />
Related to a temporal boundary, the findings in Bureau resembled those<br />
in Center. Some peripheral program participants in Bureau stated how it<br />
was hard to find time to participate in program planning due to other<br />
122