04.01.2015 Views

Learning Across Sites: New tools, infrastructures and practices - Earli

Learning Across Sites: New tools, infrastructures and practices - Earli

Learning Across Sites: New tools, infrastructures and practices - Earli

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

For EARLI members only.<br />

Not for onward distribution.<br />

Noticing the past to manage the future 125<br />

adopted in which participant observation was combined with the in- depth study<br />

of a core activity, resulting in ethnographic data, video- recordings <strong>and</strong> a collection<br />

of work documentations used in the activity. The general insights gained through<br />

the observations were used to select “hot spot” activities (Jordan & Henderson,<br />

1995). In our case, the shift- change meetings were seen as such a core activity in<br />

the internal work of achieving continuity <strong>and</strong> collective knowing. In the following<br />

section, the ethnographic observations (field notes) have been used to make a<br />

description of the organizing aspects of work continuity. The video data <strong>and</strong> the<br />

documentation collected (covering the morning <strong>and</strong> day shift changes from one<br />

week) are used to give a concrete description of the actual work of shift changes.<br />

Each change of shifts consists of two meetings; one between incoming <strong>and</strong> outgoing<br />

shift leaders, <strong>and</strong> one shortly after between the starting shift leader <strong>and</strong> the<br />

engineers starting their shift. This arrangement resulted in 27 recordings, varying<br />

in length between a few minutes up to the twelve- minute time limit, which totals<br />

160 minutes of video. Interaction analysis (Jordan & Henderson, 1995) was used<br />

when analyzing the video along verbatim transcriptions. The shift reports used by<br />

the participants in the activity were also used as a resource for the researchers in the<br />

analytical process. To ensure the anonymity of the participants <strong>and</strong> the company,<br />

fictive names of individuals <strong>and</strong> technological systems are used.<br />

The helpdesk <strong>and</strong> the organizing of activities<br />

The helpdesk team studied consists of 15 persons who operate around- the- clock at a<br />

Swedish site of a large multinational manufacturing company. The responsibilities of<br />

the team include surveillance, running <strong>and</strong> maintenance of global systems including<br />

expert support of user problems. Problem- solving at all hours requires the team to<br />

work in shifts. Job sharing of this sort implies that the support engineers are highly<br />

dependent on each other; they take over each other’s tasks, <strong>and</strong> have to be familiar<br />

with the total range of activities the team is responsible for. Conditions like these<br />

stress the need for continuous access to the collective knowing of the team.<br />

The helpdesk resides in one corner of a large open- plan office. On the wall there<br />

are clocks showing current time in countries around the world. Below, monitors<br />

show server statuses. There are sets of four desks where the support engineers work.<br />

Desks <strong>and</strong> computers are shared in ways that enable the shifts to sit together <strong>and</strong><br />

not dispersed in the office area. This is an informal mechanism of significance for<br />

sharing knowing between support engineers circulating between shifts. Securing<br />

redundancy <strong>and</strong> overlap of both people <strong>and</strong> information is characteristic of this<br />

setting <strong>and</strong> achieved by means of several strategies; resources, <strong>and</strong> thus potentials,<br />

for work continuity are features built into the everyday practice.<br />

Documentation <strong>and</strong> the doing of case work<br />

Documentation is a vital aspect of support work. All troubleshooting tasks the team<br />

deals with are documented as cases in a web- based case- management software.

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

Saved successfully!

Ooh no, something went wrong!