Tuesday, December 3, 2013

on specificity

when we were trying to find a suit for my dad when my sister got married, there wasn't much of a plan. I mean, there wasn't a particular style or look we were going for. we didn't really have a great understanding of what might be the right thing, other than it should probably be a bit, like, summery. but beyond that, we were at a bit of a loss. so we thought we should consult the expert in these matters. a tailor.

having explained to the best of our ability exactly how we thought my dad's suit should manifest, having stumbled over at least half an oxford english dictionary and a couple of rogets, we alighted on a deafening silence, accompanied by an awkward gawping stare, waiting, almost reverently, for said tailor to deliver a verdict. and when he spake it felt as like it were the very voice of heaven cascading over our heavy shoulders. and he did spake unto us thus: "you need something a little..." yes? "...a little..." go on? "well..."

"unstructured"

...

"let me show you"

actually, it was the perfect description of what was required. I can't really describe to you how the suit looked, but I think you can get an idea from that single word. but it isn't the word that made the difference. it was the acknowledgement that specificity in of itself wasn't the thing that was providing any clarity. it was using the right language based on the context that made the difference. and he just made that word up. but it was exactly the right word at the right time, based on the information he had.

I am the least academic person I know. I'm a terrible intellectual and appallingly unintelligent. do I know tufte? no I don't know tufte. have I been getting away with it as a user experience designer for ten years? maybe. but you can't personally say that unless you've worked with me and I've disabled comments for anybody who has worked with me.

I've done good things though. I have apparently made clients happy. I haven't changed the world. I haven't set out to. but to the best of my abilities I design for the user based on the evidence I have. much like the tailor. I really don't know whether I'm using a taxonomy, an information architecture, a flow diagram, a blueprint, a journey map, a haynes manual, a cognitive disentropy matrix or whatever. I could really not care what those things are and the limits or constraints of what they're supposed to communicate.

but I'm good at finding the word. and if I can sit in a room, with a pen and something to use it on, then I can probably show you what I mean. and that's about as specific as it gets.

No comments:

Post a Comment