Every year I try to attend as many industry conferences as possible, but over the years I’ve become more selective about which ones I go to. I find them to be incredibly valuable and insightful, but they also cost money and take time, so I grade them pretty hard. This year I had the pleasure of attending several UX-focused conferences. Each was great in different ways, and I came away leaving inspired each time, and wanting to share some of the lessons I learned, so I wrote this blog post.
My last post focused on the Information Architecture phase and our method for establishing the client goals, website metaphor and site elements through investigation and science(!!!). It is with this information that we will construct the website wireframes for the client's review. If you are unfamiliar with wireframes, they can be generally described as stripped-down "sketches" of what the site will look like before beginning the more formal design and development phases.
Creating a website can be likened to making a custom car or house, but with a few quirks. A website is not only supposed to be an efficiency-enhancing tool for the person or organization that paid for it, but also a reflection of the organization's persona and agenda. Creating a visual and interactable representation of these concepts takes a significant amount of creativity and testing. The job of any web shop should be to work extensively with clients to pull out exactly what the group's goals and needs are for the web and to translate them for the internet.
We here at Kalamuna believe in the power in science, and aren't in the business of making leaps of faith in regards to web development. We try to avoid superficial "let's hope for the best" scenarios with all projects, and aren't interested in putting ourselves or our clients in painful situations.