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.
Indicators of<br />
<strong>readiness</strong> <strong>for</strong><br />
change<br />
Descriptions Illustrative quotes<br />
(To illustrate the program’s situation at the end of the initiation stage, the quotes are from the second<br />
round of interviews, unless noted otherwise)<br />
Resources (continued from the previous page)<br />
Dedicated<br />
program team(s)<br />
with explicitly<br />
committed,<br />
motivated<br />
members<br />
Visible senior<br />
management<br />
support <strong>and</strong><br />
involvement<br />
Receptive<br />
environment<br />
<strong>and</strong> prepared<br />
recipients of<br />
change<br />
Autonomy<br />
Legitimate<br />
position in the<br />
organization<br />
Authority <strong>and</strong><br />
autonomy to<br />
realize change<br />
Overall<br />
<strong>readiness</strong><br />
Many complained that there were too few committed resources<br />
<strong>for</strong> the program work. There were no full-time program<br />
participants (program manager allocated 70% <strong>and</strong> program<br />
coordinator about 20% of work time to the program).<br />
The initial program owner had left the organization, <strong>and</strong> the other<br />
top managers were unable to decide who should take the<br />
responsibility <strong>for</strong> the program. The program participants<br />
complained about the top management’s lack of commitment.<br />
The environment was described as immature in terms of program<br />
management <strong>and</strong> large-scale internal change ef<strong>for</strong>ts. The<br />
organizational culture promoted individual expertise <strong>and</strong> high<br />
unit boundaries, <strong>and</strong> did not support cross-functional<br />
collaboration.<br />
The program lacked a clear position in the organization, <strong>and</strong> it<br />
was not perceived as a legitimate actor but rather as a threat<br />
towards the existing order.<br />
The program manager <strong>and</strong> his team felt that they lacked authority<br />
to engage resources in the program <strong>and</strong> to proactively plan <strong>and</strong><br />
realize changes. The steering group members felt that they had<br />
sufficiently authorized the program team <strong>and</strong> they were waiting<br />
<strong>for</strong> the program to demonstrate progress.”<br />
The overall <strong>readiness</strong> <strong>for</strong> change was poor, <strong>and</strong> the program<br />
seemed paralyzed.<br />
Sub-program manager: “Doing this in addition to other duties, many other tasks, is a problem in our<br />
organization … That’s why these initiation <strong>activities</strong> have taken so long. Not until our latest meeting<br />
did we agree on finalizing the sub-program plan. Obviously these things could have been done much<br />
faster.”<br />
Peripheral program participant: “I think the program has taken a step backwards. It was first launched,<br />
but then challenges appeared. It proved difficult to organize it so that all people or even all units that<br />
were invited or persuaded to take part would contribute.”<br />
Peripheral program participant: “Our top managers have of course been [committed] to this when they<br />
established this, but I suspect that they may not currently be actively involved.”<br />
Peripheral program participant: “[Top management] should secure a certain position <strong>for</strong> this program.<br />
Coordination should stem from the management group level… Top managers should be aware of the<br />
program contents, but currently their motivation is not at its best.”<br />
Program core team member in round 1: “A stronger management approach is required: the program<br />
should be led more firmly ... The problem is in our culture: the program management approach has<br />
not been internalized. …I fear that this will remain a modest ef<strong>for</strong>t of a h<strong>and</strong>ful of people, <strong>and</strong> the<br />
strategic dimension <strong>and</strong> top management support will remain absent.”<br />
Peripheral program participant: “Regarding this program management, I have sensed that we have<br />
many people … who doubt whether there really is room or a need <strong>for</strong> program management in our<br />
management system.”<br />
Program manager: “There have been political interests or fears that this kind of a larger program<br />
would aim at altering the power relations among the top managers. It is quite a mess.”<br />
Peripheral program participant: “Could it be that the program managers feel their position is not clear<br />
enough, in relation to the management group <strong>and</strong> the board.”<br />
Program manager: “I wish my m<strong>and</strong>ate was confirmed. We should agree on that <strong>and</strong> on my<br />
authority… In my view, top management should confirm my position <strong>and</strong> support me in it.”<br />
Top manager in round 1: “I’m wondering whether [the program’s managers] have what is needed <strong>for</strong><br />
this kind of a program … The position of [a program manager] is very contradictory, <strong>and</strong> most often<br />
the mistakes that are made in program management in [the public sector] relate to granting a <strong>for</strong>mal<br />
position but not providing the required instruments.”<br />
Peripheral program participant: “I wonder whether [the program] is at a halt. … I think it should be<br />
activated, it is not visible enough.”