[comp.admin.policy] Due process

russotto@eng.umd.edu (Matthew T. Russotto) (06/06/91)

In article <1991Jun5.234114.18168@milton.u.washington.edu> fetrow@bones.UUCP () writes:
>
> I have a slightly different perspective on this. "Due Process" should always
>be around, at least as a backup to informal procedures (e.g. a student
>ombudsman) but it doesn't (in my experience) speed things up to invoke them.
>It doesn't fix a place with bad communication and bad attitudes (at least not
>by itself).

Nope.  But it can stop the stomping of students by administrators-- no matter
what their attitude.
>
> Of course I'm writing from the luxurious vantage point of someone who knows
>virtually all the users of our system with an office right off the main terminal
>room. It gives the place more of a "team" feel than the "us and them" often
>(but not always) seen in larger installations and helps keep the communications
>channels flowing (it helps a lot to be able to see how customers interact with
>the machines).

Quite a different vantage than that of a system admninistrator who works in
an office two floors down and in a restricted access area.
--
Matthew T. Russotto	russotto@eng.umd.edu	russotto@wam.umd.edu
     .sig under construction, like the rest of this campus.