Learning Resources

Abstract: Book review: Making Computers Work For Adminitrators. Edited by Kenneth C. Green and Steven W. Gilbert, New Directions for Higher Education #62, San Francisco: Jossey-Bass, Publishers, 1988.

Abstract: Book review: Improving Education Environments for Adults, by Nancy K. Schlossberg, Ann Q. Lynch, and Arthur W. Chickering. San Francisco: Jossey-Bass Inc., Publishers, 1989.

Abstract: Book Review: Managing Faculty Resources. G. Gregory Lozier and MIcheal J. Dooris. editors. New Directions for Institutional Research, Joseey-Bass Inc., Publisher, Number 63, Fall 1989.

Abstract: Book review: Planning and Managing for Higher Education Facilities. Harvey H. Kaiser, editor. NEw Directions fro Institutional Reseacrh, San Francisco: Jossey-Bass Inc., Publishers, Number 61, Spring 1989.

Abstract: In this article, we discuss a method for developing and writing scenarios for a college or university. We begin by reviewing the general literature on scenarios; we then detail a scenario development project at Arizona State University. This project, conducted in 1988–89, was Arizona State University's first institution-wide, futures-based planning and scenario development effort. The focus of the project for Arizona State University was planning and programming for affirmative action. An outside consultant facilitated the group-process portion of the project and instructed university staff in scenario development. Staff in the university's Office of Institutional Analysis then developed and wrote a set of three scenarios to guide the university's affirmative action programming and planning during the decade of the nineties.

Abstract: This study identifies causes of failure in the design of campus performance facilities and summarizes planning and project management strategies that have resulted in successful projects. Failure consists mainly of cost overruns, functional nonperformance, and user disappointment. These instances of failure are most often attributed to programming rather than design. Common programming problems are placed in the following categories: (1) "Expectations too vague," (2) "Lack of architectural program detail," (3) "Unwillingness to understand compromises," (4) "Misunderstanding the economics of audience size," (5) "Understanding the impact of site on budget," (6) "Making the smaller facility less versatile," (7) "The expense of 'statement' lobbies," and (8) "Value engineering begins too late." Common design problems are also discussed and are placed in the following categories: (1) Internal zoning, (2) HVAC problems, (3) Poor analysis of site lines, (4) Inspection problems, and (5) Client noninvolvment in trade-offs. Within each of these categories, more specific examples are given and suggestions made. The article is based on the author's presentation at SCUP-24 in Denver, Colorado, on July 24, 1989.