Monday, March 12, 2012

happy type

while the duplication of letterforms helps reinforce the feeling in the angry type sample, when it came to happy, it became more confusing. it still seemed happy to me, because i knew what i was looking for, but i had to realize that multiplied, overlaid text is a signifier for anger, no matter how happy it looked to me compared to the angry sample.

here's what happy looked like overlaid:

it's so swirly and curly and bubbly! but that overlapping just wouldn't do. so for this type sample, i took my artistic license to average the letterforms myself into one path each. i took this new alphabet and used it to create my happy typeface, again with the lowercase being a pre-happy and the uppercase being a post-happy alphabet, lending the caps to a new level of excitement.


here it is in action:



angry type

having improved my collection process, my prompts now go as follows:

1. please write the alphabet.
2. please tell me a story about a time you were (feeling).
3. please write the alphabet again.

i asked for both upper and lowercase, but in some cases, people's mistakes were very telling, such as the neglect of a lowercase during the angry experiment.

this is what everyone's angry handwriting looks look put together:


and this is the typeface i constructed utilizing a compilation of pre-angry samples for the lowercase and post-angry samples for the uppercase. the reason for this distinction being our use of capital letters for emphasis, so, in the case of someone being angry, caps are often construed as shouting or screaming.
this gives an example of type in lowercase and then an example of type in uppercase.

here's an example of the typeface in action, emphasizing a word using the caps system.

Thursday, March 1, 2012

information architecture reading

(oh my goodness, this reading was one of the most well-written things i've read in a while. it was beautiful.)

richard saul wurman begins his introduction with a metaphor almost resembling a fable, telling of a tsunami of information and data, constantly flooding and washing up bits and pieces. there are those that charge smiling and confidently into it, groomed by a lifetime of pretending to know what they are talking about. but the flood keeps redoubling. they can't just scoop information up and walk away with it, indiscriminately clutching it like they have something valuable. there's too much and no way to correlate it, but everyone pretends that they understand it, because we have grown up believing that to be unsure of ourselves, to ask questions and admit that we don't know things, is to fail.

what must happen is that someone look at it all, the information, and rather than assuming they should know what it means, really analyze it, make relationships, pull it apart and try to put it into a usable formation, arrange it into a meaningful pattern so that others can understand without faking.

those people are the information architects, and they're here to take graphic design back from the dropshadows and gradients.

pardon my french, but. "hell yes."

Wednesday, February 29, 2012

knitting book final reflection

we chose a small book size because it was conceptually relevant in the hand motion of reading a small book resembling the motion of knitting, small and intimate in your hands. it was a challenge to reinterpret all of our information into a smaller size, however, because it had previously been quite large. more to come.

Monday, February 27, 2012

I LOVE HATS.

hat collection! first, arranged by type of hat.


next, arranged by color.


then, arranged in order of perceived silliness/practicality.


Thursday, February 23, 2012

knitting research data visualizations

first, our revised personas:



then, our affinity diagram:


then, our task analysis:


Monday, February 20, 2012

info arch project one


i analyzed an online news source and reimagined how it could better function in terms of intuitiveness and customization. presenting: an icon-happy web-app for dallas news.