[22] in Staff Recognition
Minutes from the June 23, 1992 Meeting
daemon@ATHENA.MIT.EDU (Cecilia d'Oliveira)
Tue Jun 23 18:32:51 1992
Date: Tue, 23 Jun 92 18:32:24 EST
From: cec@MIT.EDU (Cecilia d'Oliveira)
To: thanks@MIT.EDU
The fifth meeitng of the group was held on June 23 from 12:00 to 1:00.
Everyone was present.
We began by discussing the IS luncheon as an example of a recognition
program. Comments follow:
-managers seem to get a disproportionate share of the recognition
-people can get demoralized if they are overlooked esp. if they already
feel unappreciated
-group recognitions lumped together people who participated in small ways
and people who did major things.
-group recognitions are probably always difficult in that there are central
people and then there are people on the periphery and there is always the
question of where you draw the line.
-liked the seating arrangements and the nametags
-seemed to be a strong bias toward Athena-related things this year
-was good to mention people's names upfront in the individual recognitions
as it saved people from squirming around in embarrassment.
-some people get embarrassed and uncomfortable about being recognized.
We then reviewed the revised statement of goals and requirements. We
agreed to revise the requirements again to include two additional points:
-the program should strive to avoid making people feel uncomfortable.
-the program should provide equal opportunity for all DCNS staff to be
recognized for their accomplishments including student and hourly staff.
DCNS-affiliates (individuals from other IS, MIT, or external organizations)
should also be considered eligible candidates for recognition within our
program.
We then began a discussion of specific examples of things to recognize in
each of the three broad recognition categories (milestones, consistently
good, extraordinary). The purpose of this discussion was to begin to
develop a shared understanding of we each thought might be worthy of
recognition in each cateogory.
We spent the remainder of the meeting brainstorming a list of potential
"milestone" recognitions. These follow:
Introductions of new platforms into Athena
RS6000
DECstations
Maxines
Merger of .eagle into other p.o.'s
NFS > AFS Conversion
Kerberos V5 Conversion
end of sys pack delivery via RVD
phaseout of the last 750s
End of chaos.net
Complete deployment oif all new equipment running new release
Completion of Personnel LAN
Beginning of AppleTalk service on MITnet
Patriot going online
First project (Phaedo) to use Orange Project
First DOS product to Beta test
DEC contract signing
Release 7.4
Office moves
Registrar project - S.I.S.
As we discussed these we indicated why we thought these were worthy of
recognition. This rationale might eventually turn into criteria so we
decided we should try to capture this for each example as we go along.
Examples of rationale included: gets us into a major new service area
(appletalk, DOS product), new way of doing our business (Phaedo in orange),
breaks new group for MIT (SIS), marks a major milestone in MIT computing
technology (750s, chaosnet, new platforms, end of RVD, NFS to AFS).
We decided that next week we will continue the brainstorming by bringing
examples of the other two recognition categories. We will especially try to
capture the "why" as we build these lists. Once we have a good list of
examples then we will step back and see if we can construct a set of
criteria or a framework.
