COULD vs. SHOULD
If there were one thing that will trump any COULD versus SHOULD debate in a strategy discussion it would be HAVE TO.
How many of you have found yourselves in a situation where no matter how hard you try to discourage a client from using a new, “cool” online tool, you wind up “just giving it a try?”
We COULD
Recently, a major luxury automotive manufacturer offered Rovion intros (you know, the little video people that step out in front of the site and talk to you) to its dealers, free of charge. One of our clients happens to be one of those dealers and so…now that we CAN do it SHOULD we do it? First off, we’re starting this entire process backwards. Instead of setting a goal and identifying tools, which will help us achieve that goal, we’re starting with a tool and creating a goal so that we can use the tool.
So what is the goal? Make it easy for visitors to find what they are looking for.
At first look, the homepage (which we did not design) is already packed with more information (I’m counting thirty different elements) than one person could process during a twenty-minute lunch break. So, I ask myself, who is visiting this site, what are they looking to do and how is a video of the dealer popping up in the bottom corner going to make it easier for them to do whatever it is they intend on doing?