I think this is the other thing you come to realize quickly. Using outside developers means you’ll never anyone who will really be able to capture the pulse of your institution — especially at a smaller, low-budget school — because they don’t have the time. They’re going to cut corners, they’ll do generic things and try to make your school fit into them.
I get that. But it doesn’t mean we’re happy.
So if you’re the forward-thinking web guru, you’re already thinking to yourself, “this is okay for now. But I’m already thinking about our next redesign officially. Because this is underwhelming to me.” But when you’ve spent too many years in first gear, trying to go from first to fourth isn’t advisable even if you want to.
Once I got that through my head, it was easier to evangelize the benefits of what we were getting. And lucky for me, there weren’t too many gripes about it. In this case, I kept the committee small. Just the PR/Marketing office, the President (since we report to him), some IT folks and an ad-hoc committee created mostly to help us legitimize a lot of the web decisions which were already being made for the larger community to take the heat off of more than a few people.
This process was actually relatively easy. Because despite the changes we ultimately made, they didn’t deviate much from the final design we have now. From the mockup phase to the development phase on their side, is truly the most painful part of the process. Because you spend a whole lot of time in neutral…