02.07.2015 Views

Boundary activities and readiness for ... - Projekti-Instituutti

Boundary activities and readiness for ... - Projekti-Instituutti

Boundary activities and readiness for ... - Projekti-Instituutti

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Discussion<br />

change. The program appeared to be driven on a vacuous path of<br />

accumulating confusion <strong>and</strong> inactivity (Ericksen & Dyer, 2004). Due to the<br />

lack of committed managers <strong>and</strong> other resources, the continued lack of a<br />

shared vision <strong>and</strong> the program’s inability to establish a strong enough<br />

position in the organization, Center’s program was prematurely terminated<br />

<strong>and</strong> largely considered a failure.<br />

In line with Ericksen <strong>and</strong> Dyer (2004), who proposed that a team may be<br />

led to a vacuous path due to the lack of initial key resources in terms of a<br />

clear task, ample time <strong>and</strong> adequate skills, unfavorable contextual<br />

conditions may provide an explanation why Center’s program could not<br />

establish a solid base <strong>for</strong> change. Following the idea of a vicious circle, the<br />

lack of boundary activity in Center’s case can be interpreted as both a cause<br />

<strong>and</strong> a symptom of the poor progress of program initiation. The findings<br />

provide support <strong>for</strong> previous research on team development (Ancona &<br />

Caldwell, 1992a; Ericksen & Dyer, 2004) by showing that during the early<br />

program stage, it is not enough <strong>for</strong> the program’s key managers to<br />

concentrate on problem solving <strong>and</strong> planning. The managers also need to<br />

build a solid base <strong>for</strong> the program by involving different stakeholders<br />

through a skillful use of boundary <strong>activities</strong>. Awareness of the program<br />

must be built <strong>and</strong> the program must be legitimized, which builds shared<br />

commitment to implement the program. Similarly, visible support from top<br />

management <strong>and</strong> other central stakeholder groups must be ensured.<br />

The other two cases, Bureau <strong>and</strong> Chain, provide examples of successful<br />

program initiation <strong>and</strong> illustrate the related virtuous path (Ericksen & Dyer,<br />

2004). Lending support <strong>for</strong> the proposition by Choi (2002), on the virtuous<br />

path the internal <strong>and</strong> external <strong>activities</strong> of the program support each other<br />

<strong>and</strong> play complementary roles in taking the program closer to its goals. The<br />

two cases show how successful program initiation may originate at the top<br />

management level, which instantly provides initial legitimacy, or<br />

alternatively at the lower organizational levels, in which case the program<br />

needs committed advocates whose early boundary <strong>activities</strong> engage the top<br />

managers in the program.<br />

In successful program initiation, the early mobilization of the program<br />

focuses on establishing initial legitimacy <strong>for</strong> the program, creating a shared<br />

intent, <strong>and</strong> ensuring the resources required <strong>for</strong> taking program planning<br />

further. In<strong>for</strong>ming <strong>activities</strong> are also needed to communicate the program<br />

launch decision across the parent organization. Legitimating <strong>and</strong><br />

committing <strong>activities</strong> continue to engage the central stakeholder groups in<br />

the program. Additionally, linking <strong>activities</strong> create purposeful connections<br />

with the parent organization. When the program has established or ensured<br />

205

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!