How to launch your project (in the right direction), a Building Program Template
Collaboration + Speed = Results Now!
GAPPA
2012 Annual Conference
Presenters
• David Sims
Macon State College
• George Flynn
Flynn Finderup Architects
• Lars Finderup
Flynn Finderup Architects
Agenda
• Brief Project Overview
• Campus Perspective and Illustration
• Methodology
• Case Study
• Lessons Learned
What is Programming? • A document developed to defining the
project’s:
• Scope (functions and space needs)
• Quality
• Cost
• Time
• An agreement between administration and users as to what will be built
• An opportunity to build consensus!
Traditional Programming Approach • Committee Interviews
• Leave Campus
• User Interviews • Leave Campus
• Reports to the Committee • Leave Campus
• Revise report to Committee • Leave Campus
• Report to Administration
• Leave Campus
• Revise report to Administration
• Leave Campus
• Rethink the approach
• Leave Campus
• Meet with users
• Leave Campus
• Report to Committee
• Leave Campus • Revise report to Committee
• Leave Campus
Accelerated Programming Approach
• Do all the same things as the traditional approach but
Don’t LEAVE the Campus!
Benefits • Lasts weeks, not months.
• Interactive: administration, users and architects (ideally program manager and CM if selected)
• Requires all participants to set aside concentrated blocks of time
• Fewer changes, Less rethinking
• Builds Consensus
"This is the best programming process I have ever been
involved with“ Pres. Jeff Allbritten, MSC
Methodology • Ground rules:
• Establish an Executive committee with authority
• Establish a Steering committee with representation across “party lines”
• Participants must be committed to participating at their assigned time
• It all falls apart when an important (or perceived to be important) party fails to show up.
Methodology continued • Process:
• Conduct interviews on a specific schedule on concurrent days
• Conduct interviews with groups rather than individuals
• Establish specific duration for interviews
• Report back to the Steering committee each day
• Campus: • Campus Administration
• Department(s) Administration
• Department(s) faculty
• Students
• Facility/Plant Operations
• Programmer
• Architect • Associate Architect
• Specialty Consultants
• Cost Consultant
Who should participate?
• Primary campus contact (member of Executive committee)
• Program Manager
• Construction Manager
• Board of Regents (or regulating authority)
Who else should/could participate/observe?
• Information Gathering and
Setting the Vision • Steering Committee Interview
• Overview of campus vision
• Establish expectations
• Confirm steering committee
• User Group Interviews
• Lunch
• User Group Interviews
• User Group Interviews
• Individual Interview
• Programmers’ work time
Schedule
Day 1 9:00 - 10:30
11:00 - 12:00
12:00 - 1:30
1:30 - 2:30 3:00 - 4:00 4:15 - 5:15
5:15 - ?:??
• Information Gathering continued • Steering Committee Report
• Observations
• Anticipated Issues
• User Group Interviews
• User Group Interviews
• Lunch
• User Group Interviews
• Steering Committee Update
• Leave campus
Schedule Day 2
9:00 - 9:30
9:45 - 10:45 11:15 - 12:15
12:15 - 1:45
1:45 - 2:45 3:15 - 4:00 4:00
• Programmer’s Independent Work • Develop Programming Documents
• Vision Statement
• Space List
• Room Data Sheets
• Room Diagrams
• Space Adjacencies Diagrams
• Cost Analysis
• Distribute draft of Space List and Cost Analysis via e-mail
Schedule 1-2 weeks
• Space List/Budget Drafts • Steering Committee Review First Draft
• Lunch
• Programmers’ Internal Work Session
• Steering Committee Review 2nd Draft
• Programmers’ Internal Work Session
• Steering Committee Review 3rd Draft
• Programmers’ Internal Work Session
Schedule Day 3
9:00 - 11:30
11:30 - 1:00
1:00 - 2:30 2:30 - 3:30
3:30 - 4:30
4:30 - 5:30 5:30 - ?:??
• Data Sheets and Adjacencies • Steering Committee Review 4th Draft • User reviews data sheets/adjacencies
• User reviews data sheets/adjacencies
• Lunch
• User reviews data sheets/adjacencies
• User reviews data sheets/adjacencies
• User reviews data sheets/adjacencies
• Leave the Campus
• Pick up changes, polish and publish
Schedule Day 4
9:00 - 10:00 10:30 - 11:00
11:15 - 11:45 11:45 - 1:30
1:30 - 2:00 2:15 - 2:45
3:15 - 3:45 4:00
1 Week
• Challenges • New President
• Tight schedule
• Tight budget
• User Groups • President Cabinet
• Student Services
• Recreation Staff
• Student Government
• Student Users
• Plant Operations
Case Study- MSC Recreation and Wellness Center
1. Get the real decision-makers in the room 2. "Everything has been said but not everyone has said it." Let
people talk they need to be heard and they need to hear themselves.
3. Every space must be accounted for with an assigned area; there
are no “free” spaces. 4. Program every space that is requested, regardless of whether or
not you think you can get it in the budget. 5. With all the information on the table users will make good
decisions and compromises that they would not have made before starting the program.
7. Link every space to a cost. There really are no “free” spaces. 8. If Design and Construction Teams have been selected, both
need to be in the room.
Lessons Learned
Contact us: Macon State College
David Sims (478) 471-2782
Flynn Finderup Architects
George Flynn 770-859-0907
Lars Finderup
770-980-0550
QUESTIONS?