What’s not to like about flowcharts? They are capable of transforming a complex issue or process into something that is simple, cut, and dry. I love how they work, you respond to a question and you get an answer. Sometimes your answer leads to another question but eventually you get an answer. Order can be brought from chaos through a flowchart. Now, if there were a flowchart on how I should appropriately respond to my wife, I would use it all the time. Wait, let me refer to my flowchart on when to use flowcharts…okay, I’m not so sure it would really work well after all.
Wikipedia.org defines a flowchart as “a type of diagram that represents an algorithm or process, showing the steps as boxes of various kinds, and their order by connecting these with arrows. This diagrammatic representation can give a step-by-step solution to a given problem.” (I must admit I just used this definition of flowchart to add the word “algorithm” and the phrase “diagrammatic representation” to our searchable list of keywords that will surely bring hundreds of hits to IBD.)
Paul and I often get asked difficult questions like, What color should I use in this logo? Which is better, In Design or QuarkXPress? What is the best file format for my project? and Do you know where your children are? All of these would be easier to answer with a flow chart. So why not create a FC (that’s flow chart for the really cool) to answer the ever-present question of which typeface should I use?
Thankfully I didn’t have to do it. Twenty-two year-old graphic design student Julian Hansen has created one for us. You can view the full image here. The FC asks some great questions and at the very least conceptualizes the thought processes behind choosing a typeface. Of course, much like IBD, there is an insane amount of humor woven into the chart and it shouldn’t be taken literally. Though I specifically love the path to Futura and Frutiger, along with the questions that lead to OCR. Oh yeah, there is even a path to Comic Sans (though I think you know where we stand on that path).
I wish design decisions could be this easy. For years we have advocated that one of the most important areas for designers, non-designers, and interpretive designers to grow in is the ability to verbalize to supervisors, co-workers, and advisory boards on the reasons behind design decisions such as font selection. As the designer, if you can’t explain why you made a decision to foster support you shouldn’t expect support. Saying something like I just like it, or because I said so, only works with my wife.
If you haven’t created a FC in while take the time to do so. I use them in developing complicated PowerPoint programs, to map project progression, and as a way to conceptualize problem solving/solution finding. There are plenty of programs that more than likely already on your computer to help you with the process or you could always use free downloads such as SmartDraw. You could also go on with life, as a normal person.