– 3
2. Define ‘team management.’ In your view, how should it operate?
In our experience, most students and many managers have a naïve view of team management or
empowerment. They view a team as ‘empowered’ or ‘not empowered’ – a full ‘on’ or full ‘off’
state. Students often pick up a value set that says that ‘teams are good’ and are equivalent to
organic organizational structures and processes. Similarly, this value set suggests that authority is
‘bad’ and is matched with mechanistic organizational structures and processes.
We propose a more sophisticated view that means you have to ask the question: in what parts of
the job will teams provide better solutions than a more mechanistic approach? As Quinn and
Spreitzer suggest, “the successful implementation of empowerment does not require a choice
between mechanistic or organic views. It requires something much more complex – the
integration of both” (Quinn and Spreitzer, 1997, 38). As the case points out, legal requirements
mean an individual must take responsibility for certain health and safety situations – an
organization cannot assign the responsibility to a team. As well, a team of AOs would have no
interest in being involved in some things – and perhaps should have little involvement. (For
example, the pricing decisions for the service provided.) Many decisions, by the nature of the
job, cannot be taken from the AOs without incredible damage to service delivery – such as the
treatment given to the patient on the spot; and many decisions require joint consideration. For
example, if SAAS were to purchase a new vehicle type, the organization would be foolhardy not
to include AOs in the decision process. However, even in this decision, it is difficult to know
who should have the final say over design. Could AOs recognize the financial restraints faced by
SAAS, or would they opt for a cadillac version of an ambulance, with technical frills that are not
needed?