kirabug’s idea files

Wow, I have been flat-out busy the last two days.

Yesterday, the conference session on Visual design for the web (check out the nifty podcast) I attended started at 8:30 and ran until 5:30 — with generous breaks to keep us all sane, but most of the break time was eaten by things like waiting in line to use the bathroom and waiting for the elevator.

(Quick elevator aside: I’m in a hotel with no less than 26 floors. I’m on floor 21. The conference is on floor 2. If you want to get on the elevator to go up, the easiest way is to go downstairs to the lobby via the escalator, and push the up button from there, because despite the volume of folks at the conference, it’s still easier to catch the elevator at the floor it almost always has to touch on a “down” trip. Once inside, we’ve been playing “elevator bingo” — we won earlier today by loading a full row (floors 5-6-7) on one trip. I’m hoping to see us win with a column sometime before we leave. As for catching the elevator going down, rule 1 is wait patiently for it to arrive, rule 2 is wait patiently some more, and rule 3 is once you’re on board you’ll be stopping on every floor, so wait patiently. Patience is a virtue I don’t have, so it’s been a challenge.)

The session was highly interactive and quite interesting, though, so it wasn’t a challenge to get through it. And I feel a lot better about the basics of visual design and the idea that I can have an intelligent conversation with a visual designer and not make quite as much of a fool of myself.

After the session, some of the guys I work with and I met some other PhillyCHI people that are also at the conference, and we went out to dinner at Cambridge Brewing Company. The food was good and the conversation was excellent. It was a relief that we didn’t spent the entire time talking about user experience, but instead spent most of our time on more pressing topics, like “Why hasn’t Anne ever been on a subway before this week?” and “How old do they potty train kids in Brazil?” and the weather in Chicago and how the Phillies were doing. I had a great glass of Riesling wine, some sweet and spicy wings, and a butternut squash soup that was just sublime.

The weather here has been crisp — definitely fall in the air — but not cold, so we’ve been able to walk back and forth to restaurants and the like without any issues. It’s been quite nice.

Anyway, got home to my ivory tower and turned on the Phillies game, and at the time we were winning 2-1, which was awesome. I talked to Nighthawk on the phone for a bit and then chatted with my sister online, and the Phillies were going downhill and more downhill, until the score was 5-3 and I was just waiting for a horrible loss. Not having the energy for it, I shut the TV off and instead did some desk work and fought to stay awake.

When I’d just about finished that, I decided to go to bed, but my curiosity about the game was killing me. I finally killed the cat and checked out the Phillies search feed on Twitter (which is filled with folks tweeting all throughout the games) and discovered that holy shit, the Phillies had tied the game. I turned on the extremely sexy flat-panel LG tv in my room just in time to watch Matt Stairs park one, putting the Phils ahead. Well, there was no sleeping after that until the game ended, that’s for sure.

I didn’t drag my sorry butt out of bed until almost 8:00 this morning and barely made the first of the 90-minute mini-sessions today, but once the day got started they were pretty damn awesome. And also flat-out. Watched a session, then a break, then another session, then a lunch with other information architects, then the keynote, then what was supposed to be an ice cream social, but my head said no. My sinuses said “hey, moron, we want water and pain drugs or you pay.” Two tylenol sinus, a bottle of water, and a power nap later, and I was back on my feet for the final session. By then it was 5:30, so we were done, right?

Wrong. After that, there was a really cool social down in the ballroom, where we ate totally excellent pasta and other foods (jerk fajitas, olive bar type doohicky, lots of little desserts, oh, and alcohol) and chatted with existing and new friends about what we’d learned and how everything was going. I had a great time and overate, of course, so when that finally broke up at 7:30 I was stuffed and feeling icky and exhausted.

I seriously considered hitting the pool but I’m not confident I have anything appropriate to wear over my suit and I’m 100% sure I don’t have the confidence to haul my fat ass through the halls and 17 floors down the stops-everywhere elevator in just the swimsuit. Plus, I was raised by a Coast Guard vet so I’ve got a natural aversion to swimming without a buddy because I’ve got the kind of luck that would make me the only person in the history of Information Architecture that drown to death at a conference.

But one of the great things I hadn’t really considered about Tang Soo Do when I first joined is that you can literally do it anywhere, so instead of swimming I cleared a spot in my room and did the basic stretches and kicks and punches that we do to open most classes. It was a little difficult to warm up without a kihap on the kicks (which I figured might freak out the other folks on the floor) but I pulled it off. Now I’m feeling a lot better, much less achy, and willing to sit down and be a geek for a little while.

So… my poor iBook laptop (the Dread Pirate Roberts) with its 933 MHz PowerPC chip and its 1.12 GB of RAM has been processing video and Dreamweaver downloads for me all evening and I think it’s about ready to throw itself out the window. I’m taking some down-time and reveling in it while I can, because it’s back to full speed tomorrow morning.

Scott McCloud worked with the Google Chrome development team to create a comic that explains how Chrome works.

(Chrome is their new web browser. The beta is Windows only at the moment.)

It’s probably one of the best visual presentations of sandboxing, multithreaded applications, and other similar software architecture features I’ve ever seen, and it’s worth your time to read — if not because you’re interested in new web browsers, than because you’re interested in communicating complex ideas simply.

Someone at work sent me this one - it’s worth the read.

Happiness as Your Business Model.

*edited to take out the embedded code that doesn’t work worth a damn on IE. frackin’ crap browser.

Doc Holds Fourth: Questions to ask for any UX project was posted to one of the information architecture mailing lists I’m on. If more folks thought about these things before even building a website, the web would be a much nicer place to be.

Two Things Design Experts Do That Novices Don’t are two things I need to learn to do.

Now here’s a nifty tool!

WAVE - Web Accessibility Evaluation Tool

WAVE is a free web accessibility evaluation tool provided by WebAIM. It is used to aid humans in the web accessibility evaluation process. Rather than providing a complex technical report, WAVE shows the original web page with embedded icons and indicators that reveal the accessibility information within your page.

Finally, a quick way to see exactly how badly your poorly-designed website is getting mangled by screen readers.

First, I think I might have actually found a way around the now-infamous elevator comic that has stalled Night Fugues for months.

Second, I spent a significant amount of time today harassing my fellow Information Architects about a Boxes and Arrows podcast that implied there was a difference between storyboards and comics, at least as far as the artifacts of the design process are concerned. Since I’m coming from the comic side of that dichotomy I thought it would be important to know the difference between a “design” comic and a “normal” comic, especially since I thought storyboards were comics. A storyboard is a piece of sequential art that expresses design and behavior of a system through a story that provides insight into the user’s mental/emotional state, which pretty much defines “comic” , so what the heck?

A conversation with my mentor led me to a conversation with another excellent IA, which led me to a printout of a presentation from this year’s IA Summit discussing how you could use a comic instead of a storyboard to present design ideas. That presentation was done by Kevin Cheng one of the creators of OK/Cancel, a design-oriented webcomic I’ve been reading for years, and it recommended the same books for writing comics to express design that I own in order to improve my comic production skills — Will Eisner and Scott McCloud and company.

So, having read the presentation and worked with storyboards for design (even though I’m not first-hand familiar with either one from start to finish) I’m willing to take the chance and summarize the difference between a storyboard and a comic when it comes to design.

Storyboards are comics by the definition of any comic author anywhere. But in storyboards, the panels generally concentrate on the screens and their functionality, business and user goals, and similar sawdust-flavored information.

A comic (as stated above) is is a piece of sequential art that expresses something through the act of telling a story. A comic (like any piece of fiction and some nonfiction) is generally showing the growth of the main character through their interaction with other characters, their environment, or themselves. A comic visually provides insight into the user’s mental/emotional state as well as that interaction with their surroundings.

A design comic (which is where we use the comic to express the design of a piece of software) keeps the same character focus that we find in standard comic strips and comic books. It uses sequential art to express high level design ideas (probably pre-wireframes) to add clarity to the growing user scenarios and situations, and share the user’s growth through the
story.

Or to sum up really quick and easy, storyboards are a) more likely to be higher fidelity detailed designs or wireframes, b) more likely to express business goals and user goals in the margins instead of in the comic, and c) really really boring to read.

*Updated 4/24 at 7:12 am when I not trying to type on the iPhone while falling asleep, and thus could correctly link and close tags.