MT260 Unit 4 Norms Observation Example

Closed by 4:30 and Nobody Wrote It Down: A Unit 4 Norms Observation at a College IT Help Desk

[Student Name]

Purdue University Global

MT260: Group and Organization Dynamics

Unit 4 Norms Observation

[Instructor Name]

[Date]

The college, its help desk, the technicians and every incident are composite and illustrative; names are replaced by roles; the sources cited are real.

The Setting and the Observer

The help desk at a composite community college serves about 9,000 students and 600 staff. Six technicians work the desk, answering phone calls, walk-in visits and online tickets. Their supervisor sits in an adjacent office and reviews a daily report of tickets opened and closed. The writer has worked at the desk for two years and observed for four weeks in October, recording incidents in a notebook at the end of each shift. The writer told the supervisor and colleagues about the course assignment; no one asked to be left out, and names in this paper are replaced by roles.

Observing one's own workplace has limits. The writer is part of the group and may miss norms that feel natural or misread ones that feel unfair. To reduce this, the paper counts a behavior as a norm only when the writer saw a reaction to someone departing from it.

How a Norm Was Identified

Forsyth (2019) defines norms as the shared standards that describe how group members should act and that the group enforces, often without stating them. A habit that nobody minds breaking is not a norm. The test used here is the reaction: if a departure from a pattern drew comment, teasing, correction or silence, the pattern was treated as a norm.

Seven Norms

Close tickets before 4:30. On most afternoons, technicians close or reassign open tickets between 4:00 and 4:30, even when more work remains. The daily report the supervisor reads is generated at 4:30. When the new technician, in his second week, kept working tickets until 5:00, two colleagues joked that he was "making the rest of us look bad" and one showed him how to reassign unfinished tickets to the next morning. He stopped.

Never take an item from the senior technician's faculty queue. The senior technician handles requests from a group of long-serving faculty members, often by email rather than through tickets. When a part-time technician picked up a faculty member's projector request from the shared queue, the senior technician told her, politely but firmly, that he would take it. She apologized.

Eat lunch at the desk. Nobody takes a lunch break away from the desk during the semester's first six weeks. A technician who left for a forty-minute lunch in week two returned to find his phone queue reassigned and a colleague remarking that it had been "a busy hour."

Answer the phone by the third ring. When a phone rang four times, the technician nearest it was expected to pick up even if busy with a walk-in. Twice the writer saw someone call out "phone" when it reached a fourth ring.

Do not discuss the supervisor's decisions at the desk. Complaints about scheduling or policy were made in the break room, not at the desk where students could hear. A technician who criticized a new password policy at the counter was told quietly by a colleague to "save it."

Log every walk-in, even quick ones. Walk-in visits that took less than a minute were still logged as tickets, because ticket counts appear in the daily report. A technician who skipped logging a quick password reset was reminded by two colleagues on the same afternoon.

Help a colleague with a student who is upset. When a student raised their voice, the nearest free technician moved to stand beside the colleague handling them. This happened four times, and the one time no one moved, the technician involved mentioned it at the end of the shift.

Why the Group Enforces These Norms

Feldman (1984) proposed that groups enforce norms for four reasons: to help the group survive, to make members' behavior predictable, to avoid embarrassing interpersonal problems and to express the group's central values and identity. The seven norms sort clearly.

Survival: closing tickets before 4:30 and logging every walk-in protect the daily report, which the supervisor uses to judge the desk. A low close rate or a low count could invite scrutiny or staff cuts.

Predictability: answering by the third ring and eating at the desk make coverage reliable during busy weeks.

Avoiding embarrassment: not discussing the supervisor's decisions at the counter keeps disagreements out of students' view, and leaving the faculty queue alone avoids awkward competition with the senior technician.

Central values: helping a colleague with an upset student expresses the desk's sense of itself as a team that looks after its own.

The 4:30 rule exists for the report, not for the students waiting in the queue.

What the Norms Cost

Some of these norms help the desk and its users. Others protect the group at the users' expense. Reassigning unfinished tickets at 4:30 makes the daily close rate look good, but students with problems at 4:15 wait until the next morning. The faculty queue gives a few long-serving faculty faster service than students get. Hackman (2002) notes that groups often develop norms that protect them from outside judgment rather than norms that serve the people they work for, and two of the desk's norms fit that pattern.

How New Members Learn the Norms

None of these rules appears in the desk's training materials. New technicians learn them through the reactions described above, usually within their first two weeks. The new technician who worked past 5:00 said later that nobody told him about the 4:30 close, but by his third week he was reassigning tickets with everyone else. That speed is typical of how groups pass on norms: a small correction, often delivered as a joke, is enough.

Limits of the Observation

Four weeks in October may not represent the whole year; norms about lunch, for example, may relax after the first weeks of the semester. The writer's presence may have changed behavior, and the writer's own position, as a two-year member who follows most of these norms, may have made some rules invisible. A second observer would strengthen the findings.

Appendix: Observation Log Summary

The full log records twenty-three dated incidents in two columns, what happened and how others responded. Selected entries:

Oct. 6: new technician works tickets past 5:00; two colleagues joke, one shows him how to reassign

Oct. 9: part-time technician takes a faculty projector request; senior technician reclaims it

Oct. 14: technician takes a forty-minute lunch away from the desk; phone queue reassigned, comment on return

Oct. 21: technician criticizes password policy at the counter; colleague says "save it"

Oct. 28: student raises voice at counter; nearest free technician moves beside colleague

References

Feldman, D. C. (1984). The development and enforcement of group norms. Academy of Management Review, 9(1), 47-53. https://doi.org/10.5465/amr.1984.4277934

Forsyth, D. R. (2019). Group dynamics (7th ed.). Cengage.

Hackman, J. R. (2002). Leading teams: Setting the stage for great performances. Harvard Business School Press.