“It’s not about the technology.”
I hear this meme invoked all the time at “museum tech” conferences nowadays. Indeed, I myself have said this a bunch of times when developing (or at least contemplating) a new content-based technology project at the Museum. A big drive in my work at the Met has always been to get constituents talking about the content first and foremost, and worrying about the technology platform(s) later. (Aside: Nancy Proctor makes this point better than I do in her recent Museums and the Web paper The Museum Is Mobile
.) This hasn’t always been an easy task, as often it’s excitement about the technology that has caused the constituent to contact me in the first place, but I have nevertheless always endeavored to put content first and tech second in any discussions about a possible project.
But…
This approach only goes so far, and we need to be careful about where and when we apply it, lest our thinking become too prejudiced. My concern is that thinking this way causes us to act as if content is always inherently platform agnostic, which is rarely true.
I think the issue here really is context, which is unique for each technology platform, even when the content is similar. A kiosk has the context of a museum around it, a mobile device has the context of location, the web has the context of (possibly) no context at all. Each of these situations demand different approaches to developing, filtering, and presenting content.
I don’t mean to say that the “it’s not about the technology” idea has no value–it’s still a bad idea to jump into a project with no reason for being other than exciting technology. However, we do need to be cautious about understanding the nuances of each platform, and adapting our content strategies accordingly.
Word.