connecting*the*dots

The making of…

I tag like a 15 year-old kid in the South Bronx with a box full of Krylons and a yard full of freshly sandblasted cars.

I tag like I just got jumped by a handful of punks who made the mistake of letting me follow them to their trailer park homes adorned with freshly cleaned aluminum siding.

I tag like I get told who I am, what I’m supposed to believe and how I’m supposed to act on a daily basis.

I go all city, hoping that one day, the vehicles I’ve touched get stitched together to form a complete sentence.

I tag because I saw you leave your mark and it was dope.

I tag because I know how to freeze, watch TV and (kinda) avoid the kissing bugs.

I tag because the words I drop in time will find a way to form a cohesive rhyme.

I tag because the world may be getting smaller, but it’s damn sure not coming together.

I tag your name, your spot, your position, your mood, your frame of mind when it’s too hard for you to see it for yourself.

I tag the expected terms of modern constructs.

I tag the post-modern undercurrents of miscellaneous descriptors.

I tag my tags so that when structure is forged out of chaos, you’ll know how to find me.

I tag so that it’s me you won’t be looking for.

When I tag, I’m regurgitating the meal I’ve caught for the chicks in my roost.

When I tag, I feel one with the universe of the collective unconscious.

When I tag, I can see the pillars of control quaking in their foundation.

When I tag, I experience therefore I understand.

When we tag, anything is possible.

————

Tag! We’re It! Part II
Tag! We’re It!

I’m really liking where the Amazon UI is heading.

Not to say that their interface has been devoid of good design decisions over the past 9 years. I mean, they were the first e-commerce company to truly leverage collaborative filtering, essentially taking advantage of The Long Tail of online consumerism, long before the terminology was officially anointed within the context of new media. Just getting those features into the interface — placing more eyes on more products — drove the business model and the promise of the New Economy circa 1998.

But crafting the balance between user search, participatory and discovery scenarios within the interface was definitely an afterthought. As a matter of fact, at one point in time, it seemed that Amazon had little concern for any interaction design considerations within the interface at all, satisfied to add features within a scroll-driven, hierarchical construct to no end.

Well, that has seemingly changed. Check out a new test version of the product page:

Am I the only one standing up and applauding? The interface now completely supports the common needs of all users at a point-of-purchase.

1. Clearly display the product price & savings
2. Show the product itself
3. Provide the ability to purchase it or add it to a Wish List
4. Then provide the ability to move into search, participatory or discovery scenarios

Amazon reduced the cognitive friction of the previous interface
by removing the bookend columns of contextual navigation and by moving only the highest priority scenario features (reading reviews and looking inside/searching the book) under the primary sales window. The affordance for the DHTML window on the product image needs to be increased, as it is currently one of purely learned behavior, but the simplicity of the new interface does wonders in focusing my attention.

Take a look at the old interface in comparrison:

For someone that has reached the conclusion of their search or discovery scenario, the shopping experience is now set up for the user to determine price feasibility, drop the product into their cart and either head for checkout or continue to discover.

For someone who’s in the midst of a discovery process, the interface hasn’t changed for the worse, as an anchor link still drops the user down to user reviews. It’s now just better placed. The interface continues to present other collaborative filtering information below the fold. With these smart design decisions, Amazon now finds itself in a position to add elegant customization, because elegant design parameters have been established.

The Amazon jungle is evolving, and in very smart fashion. In my book, that’s pretty cool.

What do you instantly think of when you read the word "fence?"

Unless you’re my friend Fleur (she’s a fan of the romantic sports), you probably lean towards the world of "things that stick in the ground and enclose other things" and you would be correct in thinking such, as fences do just that; they enclose, divide and protect areas and organisms for various purposes. Now, if we can agree to such a broad (yet particular) definition, we should be able to agree that fences define parameters of use, for if one can’t get past the fence, one can’t engage with anything outside (or inside) of its parameters.

So why am I fixated on the definition of a fence? Well, a good deal of tactical user experience design within authenticated environments is centered around the concept of defining parameters; as experiences that support specific goals rely on the thoughtful crafting of usage parameters. If that’s a vague concept, think about it in terms of designing site navigation behavior:

• Does the top/down navigation live in a consistent pane in the interface?
• If it’s located at the top of the screen, how does it behave?
• Does it expand onRollover or onClick?
• Does it display horizontally or vertically?
• Does it use rollovers for greater affordance?
• How does color and behavior reinforce the brand?
• Where is bottom/up exploration located?

Before we get too granular, let’s step back outside for a moment and think about how we might design the use of a fence in the real.

The placement of a fence’s corner posts could be determined based purely on property lines, or relative requirements based on the needs of the owner. The height of the fence, and its types of rails or wires, could be designed based on security requirements, or based purely on style. One thing is for sure; when these attributes are specified, usage parameters are in place and an experience is established. These specific choices define our cognitive perception of a fence that keeps sheep grazing within a field; a fence that protects property in the midst of urban renewal; a fence that surrounds a house at the end of a cul-de-sac.

Design is an iterative process, a constant remodeling based upon the objectives and desires of a business and user, and the perspective, and ultimately, the epiphany of the designer. But moving from good design to great design requires an effort of reduction to reach an elegant solution, where less is more and the complex takes form in simplistic presentation.

So the sheep are now grazing behind an elegant, rustic, utilitarian, wood fence. You’ve designed the perfect experience to meet the usage parameters of your client. Congratulations. But don’t pat yourself on the back for long. Your farmer client is now telling you that his sheep are going to be racing for cash on the property and that 25 other farmers are going to be using the property for similar, yet different purposes… and each are going to be equal owners, with equal say in decisions.

You now have 25 clients to please.

Parameters now seem passe, as each owner has slightly different needs and they’re starting to bicker. Your approach to good design (reduction and elegance), as applied to the original usage parameters, must now be redefined as well. So can you satisfy each of you client’s requirements with one static, structured, definition of a fence? Probably not, but that doesn’t mean design parameters go out the window.

An even more difficult challenge now lies on the horizon: How do you broker the creation of apropos usage parameters moving forward, through the creation of both useful and usable customization options? You need to meet their needs, but not by making "fences" too complicated or by coming in too close to their limited operating budget. How does one iterate the elegant reduction of the addition of customization?

Hmm… how indeed.