How Bad Typography Can Help You Solve Problems
Last night, I attended my first Refresh Pittsburgh meet-up, held at the local tech startup incubator, AlphaLab. Refresh Pittsburgh is an informal group of designers and programmers, looking both to network and to learn from one another (and their occasional guest speakers). Although I'm not a designer, per se, I *am* a creative type (or so I like to claim), so I enjoy hearing how other creative types solve their problems.
Yesterday's guest speaker was Samantha Warren of Viget, a design firm in Washington DC. (She also blogs here. She gave a kick-ass presentation on bad typography, and how (and why) it can kill your web experience. And then she showed how she would have redesigned one horrible site in particular, taking us step-by-step through both her technical AND her theoretical processes.
What I appreciated most was seeing her decision-making process, and learning HOW and WHY she arrived at the conclusions she did. Sometimes, she realized her initial presumptions or goals were incorrect midway through her process, so she backtracked to redesign her end product. Fellow speakers and presenters of the world, take note: knowing that a speaker can admit to being wrong, and then seeing the steps she took to fix things, made me trust her (and her process) even more.
In the end, the two lessons that stuck in my head most clearly were:
* (Samantha's intentional lesson): Don't let the details (like typography, design or even functionality) drive the project; let the PURPOSE drive the project, and the details will fall into place.
* (Samantha's unintentional lesson): When presenting, always make sure to include the URLs of any interesting sites / services you might mention. If you catch the audience's attention, they'll want to know how to learn more.
Other cool tips and tidbits you may know (but I didn't):
* Ms. Warren considers the 3 pillars of web typography to be: Legibility, Hierarchy and Expression.
* A gent named Jakob Nielsen developed a design concept called the F-Pattern, which (counter-intuitively, if you ask me) seems to make sense.
* Ms. Warren suggests designers evaluate all information on a webpage in terms of order of importance, and then allocate the proper typographical weight and direction of attention as required.
* Use phark or siffr for image replacement -- which, as a non-designer, I can barely even understand, but I suspect some of you know what she's talking about (and it seemed important).
* Texture, texture, texture.
If any of this sounds interesting to you -- or if you suspect you would have learned more by actually attending the meet-up (rather than reading my shoddy secondhand journalism), perhaps I'll see you at the next Refresh Pittsburgh event?
Image by ErokCom.