A lot of people think designers just make things pretty. We don’t. First and foremost we solve problems. Problems that usually start with a question and, sometimes, we need to ask ourselves if we’re asking the right question.
I just wasted a lot of time answering the wrong question.
Almost a month ago the CEO of my company, Scott Abel sent me an embeddable video of an interview he had given. He wanted the interview to appear on our website but he wanted to know if we could do so without using the interviewer’s Flash player.
Well, a quick investigation found the interview posted to iTunes in MP3 format. Problem solved, right? Well, no. Next we had to secure permission to post the audio. This took a week and a couple of emails. Then we had to decide where we wanted to post it. News section? Our blog? Somewhere in our community? The item fell off the radar for another week.
Last Friday it came back on the radar. The decision was to post it to the news section. I checked with our server admin to see if we needed to post it to Fileburst or if we could just host it ourselves. I wanted to wing it because I didn’t think there was much chance of it getting a lot of traffic. He was the (correct) voice of reason: multimedia files go on Fileburst.
Next discussion: headers. Did we want it to play immediately, force a download or leave it up to the user. We didn’t want too many concurrent connections to bog down our Fileburst server if the file saw a sudden burst of popularity, so force the download.
While he was uploading the file I went back to the iTunes podcast to see if I could avoid the whole hosting/serving issue altogether. I had an ITPC link to the podcast’s RSS feed but that forces people to use iTunes. Replacing the ITPC protocol with HTTP pulled up the standard RSS screen. Using that requires people to be familiar with RSS and RSS feed readers.
In the description of the feed was a direct link to the MP3 file. But the MP3 autoplays in the browser with no context and no obvious way to download and save it. And you can’t download it until it finishes loading anyway, adding yet another layer of confusion. Not the best user experience. And, what happens if the owner decides to move where the MP3 file is hosted?
So now I can serve up the ITPC link, the HTTP link or a raw link to the MP3 but each solution has drawbacks and none of them provide a particularly compelling user experience.
It was while mulling those options that I experienced a particularly lucid moment.
I went to the website of the company that did the interview and found where they posted it on their site. It has a descriptive title, some lead copy, a picture of our CEO, and links to play it in the browser, download it, subscribe to the RSS feed or subscribe to the iTunes podcast.
The worst part is that we always link to the source webpage.
This was a very simple issue that was turned into complex one because I never stopped to ask if I was asked the right question. I just tried to answer it.