Imagine you want to get to know someone and you can ask only five questions. What would you ask? What would you most want to know? Obviously it depends on the context--you'd ask different questions of someone you're dating vs. a job interviewee vs. a customer vs. someone your daughter is dating. But I wonder, should the questions we ask our users be that different from the ones we'd ask our dates?
You know the feeling: You follow a near-random trail of blog links and land on the post that solves your big business problem. You randomly flip through a physics book and find next week's sermon. You're shopping for discount dog food when you find your dream date. It's the powerful charm of the iPod Shuffle ("How did it KNOW that's just the song I needed to hear right now..."). It's serendipity.
People pay attention to graphics. They respond to graphics. They learn from graphics. If you want your readers/learners/audience to "get" something as quickly and clearly as possible, use visuals. And you don't have to be a graphic artist, designer, or information architect to put pictures in your presentation, post, or book. This post is my first attempt to categorize the kinds of graphics I do h
Do you have a stack of books, journals, manuals, articles, API docs, and blog printouts that you think you'll get to? That you think you need to read? Now, based on past experience, what are the odds you'll get to all of it? Half of it? Any of it? (except for maybe the Wired magazine) So you let the stack of "things to read" pile up, then eventually when the pile gets to high you end up tossing ha
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く