Insights: The Case for Use Cases
Website design to some people is a little like a secret, magic box. You tell someone what you want and then presto-change-o, out pops a website, champagne falls from the heavens, and you win all sorts of awards and are gratified by the applause of your peers and colleagues. It never works that way.
It actually takes a lot of foresight and planning to build a website that meets the strategic needs of an organization. At the risk of oversimplifying, doing this requires understanding:
- what the organization's needs are (and hopefully what they should be),
- what their audience's goals are,
- figuring out where the two meet,
- how to make sure the audience knows about it, and
- how to ensure an easy, mutually satisfying transaction
This week, in my second-ever Click Here blog post, I wrote about one of the methods used to plan a website that accomplishes these goals.
If you're on the agency side, hopefully it will give you some ammunition for explaining to clients the time and effort it will take. If you're on the client side, this may give you a little peek into the magic box.
They say a magician should never reveal his secrets, but happily, as this article will clearly show, there's no magic to what I do. - Cam Beck
Related Blog Posts:
Comments