Robert Bacal wrote:
> On 17 Dec 97 at 15:36, Glenn Rowe wrote:
>
> My concern is that
> > although we call them teams they are really groups of students. Hambrick
> > (1996) (sorry, I do not have full cite) wrote about the differences between
> > a management team and a management group. I am thinking that we may have
> > the same problem. We put a group of students together and then call them a
> > team. I am interesting in whether the rest of you struggle with this
> > distinction as I do and whether you have any ideas on how to enable groups
> > to become teams in a short three months.
>
> That was the point I was trying to make in an earlier post...that
> teams in universities are artificial with respect to workplace
> teams...the conditions of reward are different, the motivations are
> different, etc.
>
> Presumably the idea behind evaluating process in the classroom is
> that it "reflects reality", and we should be preparing students for
> reality. But there are profound limits on how real this can be, and a
> key question is whether the behaviour illustrated in the university
> setting has ANY relationship to that which will be shown in the
> workplace.
>
> As a hypothesis, is it possible that the behaviour exhibited in the
> university is a function of the environment/university system, and
> less an indicator of skill/ability/attitude that will transfer to the
> workplace?
>
> If that is true, what then are we evaluating?
>
> Is it similar to the idea that tests actually test test taking skills
> in addition to whatever else they test?
>
> PS. How's the weather out there, Glenn..we are breaking all records
> here on the unfrozen, balmy prairie.
>
> Public Sector Manager Newsletter Online is available at
>
http://www.escape.ca/~rbacal/psm.htm. Articles archive at:
>
http://www.escape.ca/~rbacal/articles.htm .
> Bacal & Associates
rbacal@escape.ca
I think we are protesting a little too much about the differences between teams
in business classes and those in workplaces. Of course there are differences
between "groups" and "teams," and there are many KINDS of teams as well. However,
if students are placed in groups for semester-long classes, and if these groups
are responsible for tasks and projects that are being graded on a team basis,
there is little difference between them and project teams that are also together
for finite times--from 2 weeks to a year or so--in a work setting. Now there is a
difference between a typical team in a work setting and a DEPARTMENT, in which
people are grouped together for the duration of their work in an organization and
can expect to interact with each other on a daily, sometimes even an hourly,
basis. However, the "teams" that my evening and weekend students come from at
work are typically groups of employees from different functional areas placed
together by management for a specific purpose and to accomplish specific tasks
over a set time-frame. To the degree that they are together for longer than a
year, perhaps a meaningful difference is introduced from their B-school
bretheren. Yet there is still much we can teach them through experiential
exercises, laboratory kinds of conditions, cases, and projects about effective
teaming. In some programs (one of ours), students are together in teams for 2 or
even 3 semesters in a row, though I recognize that is rare. Nevertheless, I think
we should be celebrating the differences that do exist because the most
meaningful of them allow us to try pedagogical techniques that are difficult to
enact in work settings where process is usually studied little, if at all. Now
all that said, we are not talking about student groups together for a class or
two here, either, because there are quite significant differences between them
and work teams.
Regards to all,
Bill
--
Bill Ferris
Professor of Management
Western New England College
Springfield, MA 01119
Phone: (413) 782-1629
Fax: (413) 796-2068
E-Mail:
bferris@wnec.edu