Wireframe Checklist
2 Comments
Last month I gave the uninitiated a crash-course on wireframes. In the comments to that post, a former colleague, Kevin Lloyd, said that he was going to use the post as a kind of checklist for reviewing wireframes. Before that comment it hadn't occurred to me to create a checklist and apply it systematically, but in one of those 'no-duh' moments it struck me that it's something I should have been doing all along.
10 Omnigraffle tips you might not know (plus one bonus!)
4 Comments
Over the past four months, I've been using Omnigraffle as my go-to diagramming app. During that time, I've collected a small set of tricks that make wireframing and diagramming easier.
If you're a grizzled 'graffle veteran or someone who reads manuals, some of these might be old hat. But maybe not – so check them out.
Continue reading "10 Omnigraffle tips you might not know (plus one bonus!)"
UX 101: The Wireframe
6 Comments
If you develop web sites you're probably pretty familiar with the wireframe, and if you're a user experience designer you're probably rolling your eyes at yet another post about what a wireframe is and what it's good for. If, on the other hand, you're not involved in the mucky details of site design and development, wireframes may seem a little mysterious. If that's you, you're not alone. The fact is wireframes are commonly misunderstood by stakeholders, especially when they're new to the web. I regularly have to explain to clients what a wireframe is, how we use wireframes, and sometimes, why they should pay attention to them. If you're new to wireframes, I'm here to get you up to speed on what a wireframe is and how to read one. If you already know all about them, maybe you can use this post to educate your stakeholders.
Using Remember the Milk as a Capture and Coding Tool
0 Comments
Built as a to-do list, Remember the Milk is surprisingly capable as a qualitative analysis tool.
Continue reading "Using Remember the Milk as a Capture and Coding Tool"
Plan a Content Strategy and Go Places
3 Comments
Now that the web world has largely bought into information architecture and interaction design, we're starting to realize what we've always known: content is king. Coming up with a good information architecture is critical for any site, but you can't design a great information architecture without having a solid handle on the information you're architecting.
It seems pretty obvious, right? Unfortunately not everyone gets it – yet. It's not like these people don't think content is important. They know it is; they just haven't been convinced that there's any reason to put structure around the process of defining it. So, how do you convince someone that content strategy is important?
I've started likening developing a content strategy to planning a trip. Whether you're going on a honeymoon or creating a site about bicycle maintenance, you're planning to be somewhere you're not right now.
When planning a trip there are three high-level questions that need to be answered:
- Where are we going?
- How will we get there?
- What will we do once we're there?
Let's give the analogy a little workout.
Recent Comments