Tom was right
For many years, I've had the good fortune to work with Tom Hoogendyk on web development. In one of our earliest projects, he had this pie-in-the-sky idea that he could get a group of faculty to think through how a website could be structured in an a priori way before beginning development. I suspected that it wasn't going to work out the way he expected and I wasn't surprised: they rebelled and we ended up just building it ourselves and getting feedback along the way—once they had something to react to.
When we did a redesign of the Biology Department website, we went through a similar exercise but, again, we had a hard time getting buy in on the navigation system. A number of faculty have never been happy with it and I think I've just realized why: Tom was right.
If you let people get away with not wrestling with the hard issues of how the overall structure should be organized, people who only look at subsets will always be unhappy and complain. When you look at the whole thing, there are shortcomings for how any individual subset is going to turn out, but you can balance those to some extent. But when you only look at the subset, you can't understand those tradeoffs.
- Read more about Tom was right
- Log in to post comments