You've found the archive. Have at it.
Posts Tagged ‘design’

Simplicity as Innovation

This morning I came across this article on netbooks in my feed reader and a quote at the end of the first page really stood out. “In the process of creating a laptop to satisfy the needs of poor people, she revealed something about traditional PC users. They didn’t want more out of a laptop—they wanted less.” That’s a pretty profound statement that all designers should consider when making a product or design.

There is a sweet spot between simplicity and complexity, a sort of supply-demand curve for an effective design. Although netbooks are cheaper to make and would see increased demand because of that, the constraints of having to make the product cheaper for a specific demograpic enabled innovation. That innovation opened up the product to a mainstream audience.

As designers, we should embrace restrictions and constraints. It’s the essential difference between art and design. I’ve talked about simplicity a bunch of times in previous posts, but this article has illustrated that simplicity can also be an innovation.

The Laws of Simplicity

A couple weeks ago I was given a copy of John Maeda’s book “The Laws of Simplicty” and it synthesized a lot of my previous design philosophies. The first law that he talks about, the law of reduce, is one that I have long believed to be one of the most important rules for designers. Design is about subtraction more than addition. This is one of the hardest things to teach because designers are creative and make things, but unless it solves the design problem, adding things to a design is more about ego.

Should Designers Do Their Own HTML/CSS

There is a great debate going on over at 37 Signal’s Signals vs. Noise blog. They flat out say designers should code their own HTML/CSS. I agree for the most part, but there are exceptions to everything.

I work for a very large company and it would be impractical for the visual designers to code all their work. At some point it makes sense to hand the coding responsibility off. I do think their needs to be a close relationship between the designer and the person who is doing the coding. Also the designer should get code approval.

Command Shift 3

Just noticed that this site is ranked in the top 100 out of over 11,000 sites on Command Shift 3. Wow super surprised. Those of you unfamiliar with Command Shift 3, it’s basically hot or not for web site designs. Its a fun site and has some really good use of the meta data provided by the voting. Sites are also ranked by related tag, so this site is currently 20th in designer and 3rd in simple. So cool, be sure to check out the site and participate.

3 Design Education & Career Tips

From time to time I get emails from people asking about design education & career advice. I have a different perspective on this topic because my path was different than most designers. I went to a small art school that was primarily an illustration & sequential art school called the Kubert School. The school did not offer a degree, but I learned a lot in a short period of time. After completing the program, I felt that I learned a lot but wasn’t equipped to do a real world job.

Design Rhythm Nation

Blogs and blog-like designs have become so commonplace, it made me ask the question “What interface traits make blogs successful?” By far the unifying quality is design rhythm. Blogs break a lot of the early web design convention, like pages being too long or the fear that people will not scroll past the fold. So why is this approach more accepted and used today?

Talent is Hard Work

Wow, I just read this article called “The Nature of Talent” over at Freelance Switch and I couldn’t agree more with its author. I’ve been feeling and saying this for years about how people perceive talent. It’s a great article on the subject and I’ve added my two cents below.

Talent and creativity is not some magic fairy dust, it’s hard work. I’ve had many people over the years say “you’re talented” and I’m always gracious and accept their compliment,