Oh programming

It's really hard going from a curricular approach to student learning back to a regular programming models with pillars and such. I think I've lived in this little dream world for the past few years where we talk about learning outcomes, strategies and self-authorship and I've forgotten that outside of my little dream world most people still think about programs and pillars and programming requirements. I really struggle with those models. The RAs' focus always seems to be on fulfilling those requirements. No matter how much I try to get them to assess the needs of their community and think about what they want their floor to learn from these experiences, we always get back to those pillars and how it'll fit into one of them. How many times last year did I try to tell my staff, "Don't worry about the requirements! Think about the students' needs first." But when there are requirements, students will think about them.

I can see the same trend here. My staff and I had quite the "lively" discussion about floor dinners and whether or not they should count as a program. In my mind, floor dinners should be happening anyway - everyone needs to eat, so why not eat with your residents once a week. Especially since we have a dining hall in the building! And what would be an easier strategy to build community?
But for the RAs, if it doesn't fulfill a programming requirement, it's not "worth" doing. They forget that there are other sections on their evaluation that talk about community development and the connections that they've built with their residents....

I guess what I really struggle with is the idea of the RA position being this check list:
1) Duty? Done.
2) Programming Requirements? Done.
3) Go to Staff Meetings? Done.

In my mind, the RA position should be so much more. It shouldn't be about what I am required to do but about what will be best for my residents. Yes, maybe I've completed the "required" number of programs already, but if I feel that my floor really needs some education on diversity, I will bring in a speaker or take them to a diversity workshop; maybe we have completed our community development programming requirements but if we haven't truly bonded yet, I'll think of some more ideas to bring the floor together.

And yes, I realize it's hard to think about the RA position that way when you are a busy, over-involved undergraduate. But maybe if we changed some of the structures (e.g. our programming models), we could help RAs think about the potential of their position a little more and strive to really do what's best for their residents.