jason lynes archives

Redesign alert: GarrettDimon.com gets a facelift, and reminds me of John’s recent refocus (both of which were inspired by Tufte conferences). I love this refocusing on better communication and presentation.. Something a lot of us can learn from..

posted by jason on Friday, Feb 16, 2007

What do you think of the new Happy Cog?

posted by jason on Wednesday, Feb 07, 2007

John has some really cool dropcaps going down over at his site, part of an MFA project..

posted by jason on Wednesday, Feb 07, 2007

Here at work, like many organizations, we have a slew of acronyms. Thanks to Randy, we can finally narrow down the possibilities. Click for definitions: FMAT, IMOS, ICS, TADD.

posted by jason on Wednesday, Feb 07, 2007

“One of the things that I think is interesting is we’ll actually see organizations and companies appointing what they refer to as a CEO or Chief Experience Officer. And that Chief Experience Officer is supposed to have a view across all of those experiences… When we look at what’s going to be happening, it is absolutely huge.”
Lou Carbone, author of Clued In: How to Keep Customers Coming Back Again and Again, in an interview with Jesse James Garrett

posted by jason on Wednesday, Feb 07, 2007

Smile! (via)

posted by jason on Tuesday, Jan 30, 2007

“Please read the whole article and be familiar with Ted’s conclusions about client specs. Be prepared to discuss his point and your opinion thereon at the beginning of class on Wednesday.”
an assignment this week to read Ted’s Tooth Fairy article for the VT1300 Communication Design class at Dixie College

posted by jason on Monday, Jan 29, 2007

Some very compelling design over at Humanized for their new Enso product. It’s like Quicksilver for your PC. Also handy: the Humanized Reader.

posted by jason on Friday, Jan 26, 2007

“You cannot copy the internet (nor TV programming) and expect success on mobile. The mobile is the newest mass media. It is as different as the internet was from TV, or TV was from radio. You need to understand what works.”
Tomi Ahonen, in a massive but enlightening response on Authentic Boredom

posted by jason on Friday, Jan 26, 2007

Design requires communication

Cameron linked over to D. “CMYK” Keith’s recent article on Tips for a better design review process, a topic on which I’ve been collecting thoughts to discuss here. The act of presenting, explaining, and defending your designs before stakeholders and customers should be a skill to be mastered by every great designer.

Design is communication. It requires it. Great designers should be excellent communicators, whether that be visual, oral, or written. Designers should dress well and accurately communicate with their personal presentation (which is our answer to Jason Fried’s question about suits). Designers’ homes and offices are often well designed and organized (tho painting kitchens Orange Toffee is questionable, Paul). The language and verbal presentation of a designer should also be refined and should communicate their message in a way that can be understood by that specific audience.

And the ability to stand in front of two or several dozen stakeholders and defend your design is one that is required anywhere design is critical (really anywhere you’re being paid for your design).

I recently experienced this in one of our biweekly prototype reviews, where new designs are presented and approved. Our designers are business analysts, visual designers, interaction designers, user researchers, information architects, and in this case, orators. I presented a section of the web application to a room of 20 or so top-level executives in one of the Church’s departments, and was tasked with explaining my design choices, defending those decisions, and mediating a roomful of helpful and not-so-helpful suggestions (sometimes from managers with little or no experience in that specific field).

Keith outlines good tips to becoming an excellent defender of design, and I’ll apply a couple of them to our work here:

And I’ll add one more to this list:

Design reviews are a must! They will strengthen your design and give you the critical feedback to make your work truly useful and impactful. What’s more is you’ll gain a confidence in your work that is impossible to gain elsewhere. Welcome and embrace these chances to elicit feedback and use them as reasons to make sure every design decision is completely bulletproof.

With these tips in mind, head into your next review prepared to communicate. Your design, your hours of hard work, require it.

posted by jason on Tuesday, Jan 23, 2007

From Usability News, Reading Online Text: A Comparison of Four White Space Layouts. Very interesting study on how readers comprehend and digest content online.

posted by jason on Monday, Jan 22, 2007

Which is the prototype?

I got a funny request today, one that illustrates how cool our software development process is. The Lead QA on my project (let’s call him Blackbeard) asked me to put a watermark on my prototypes so he can tell at a glance that he’s looking at my prototype and not the actual working software. With multiple tabs open, it’s hard to tell which is which. And that is precisely the point! So I’m adding a watermark.

We’ve also been asked recently to put real data into the prototype to aid in the user feedback loop. My fear is without the tell-tale fake data we put in, our users might run into the same problem!

Our process we’ve developed here at the Church has the Interaction Designer working out all aspects of the user interface and feature set in a high fidelity (XHTML/CSS) prototype before the developers ever see it. This way, stakeholders and users can see what they’re actually going to get, not some bloated bullet list of hard-to-understand functions and use cases.

We then sit and work closely with the developers and QA to make sure what we’ve promised visually is being fulfilled in the working software.

The downside, it seems, is when the actual app is too close to the prototype and everyone gets confused.

posted by jason on Monday, Jan 22, 2007

rubyonrails Ruby on Rails 1.2 is out! Check that link for tons of info about the release. We here grabbed Agile Development with Rails and Rails Recipes, both of which teach from this newest release (yes, we’re designers who also code). In related news, Prototype 1.5 was released simultaneously today, and with a new site to top it off.

posted by jason on Thursday, Jan 18, 2007

Another from Bea’s trip, from her trek into Sikkim.

posted by jason on Wednesday, Jan 17, 2007

posted by jason on Wednesday, Jan 17, 2007

Bea has been showing us photos from her 16 week trip to India and Nepal. Check out her journey on this map. Awesome.

posted by jason on Wednesday, Jan 17, 2007

A tip from Gilbert: when designing forms with horizontal labels in a liquid layout, prevent your required *’s from wrapping by placing a   (instead of a normal space) between the word and star, like this:

posted by jason on Wednesday, Jan 17, 2007

Our own Gilbert Lee has released yet another stunning piece of work. This week he and his wife Carol welcomed their third daughter, Elena, into their home. Congrats Gil and Carol! To say that we value families would be an understatement. Take as much time as you need, friend. We’ll see you soon.

posted by jason on Wednesday, Jan 17, 2007

Gilbert is speaking Thursday night in downtown SLC on “Interaction Design for Developers” over at the CFUG meeting. Do drop by and give a little heckle if you can. He’ll be signing printouts of PlainSimple.org. Bring your own.

posted by jason on Wednesday, Jan 10, 2007

From CNN Money, How Apple kept its iPhone secrets. Even wives and children were kept from the news, and even many top Apple execs saw the iPhone for the first time yesterday.

Related: Cameron says the iPhone won’t revolutionize the mobile web landscape just yet.

posted by jason on Wednesday, Jan 10, 2007