Red Hatting a Website

redhat.jpg

No, this does not have anything to do with Linux. This is the Red Hat of the Six Hats, Six Coats metaphor. In the last post I discussed the Six Hats, Six Coats Blue Hat which has nothing to do with Microsoft. The Red Hat is about the closeness to the intuition of the user. It is about the implementation of your own system. What transactions are intuitive and what transactions are counter-intuitive.  I alternatively call this the Mechanical perspective, because it deals with the mechanism the Green Hat, Yellow Hat, White Hat and Black Hat end up creating.  Edward de Bono also calls this the intuition hat.

Red Hat, Green Coat: How do we lower the barriers to adoption?  Intuition.

Red Hat, Yellow Coat: Who navigates our site? How do you support each browser?

Red Hat, White Coat: Who accesses our data? What DDL and DML will you have to write?

Red Hat, Black Coat: Who uses our processes? What approach will be taken to coding?

Red Hat, Red Coat: Who are the personas we are serving? How do you achieve the site aesthetics?

Red Hat, Blue Coat: Who is setting our performance requirements? What can achieve your performance goals?

Each of these implementations has implications for your website design. It will impact the positioning and emphasis of each of your website’s elements as well as your website’s behavior when those elements are employed. It will affect the overall look and feel of the site. When you are working in the Red Hat perspective you are asking yourself, “How do I implement ‘business as usual’?” You will have dealt with all the possibilities in the White Hat perspective and all the probabilities in the Black Hat perspective. Anything that defies your user’s intuition will be escalated back up to the Black Hats as exceptions. If there is a trend in the exceptions it will be escalated up to the White Hats as a variance. If there is a trend to the variances it will be escalated to the Yellow Hats as a deviation. And if the deviation is great enough it will be brought to the Green Hats as an opportunity.

The Six Hats metaphor can be used for any system. I plan to branch out my examples over time.

Advertisements

Blue Hatting a Website

bluehat.jpg 

Blue Hat in the Six Hats, Six Coats metaphor deals with convenience.  Blue Hat is the first impression your traffic gets–convenience of goals, networks, data, processes, people and times.  When it comes to the web, if any of these aspects of convenience are not met you are going to lose traffic before anything is captured by your website’s system.  Let’s look at each of these aspects in turn.  Edward de Bono calls this the data hat.

Blue Hat, Green Coat:  When are the the goals of the site clearly communicated.   This is the message your evangelists are getting out and getting out often.  Be it an SEO or a customer.

Blue Hat, Yellow Coat:  When is the site navigated?  If your audience is getting a garbled presentation on their browser, they are not going to stick around to figure it out.

Blue Hat, White Coat:  When is the data accessed?  Tables of data that obfuscate information through redundancy cause users eyes to glaze over and their index fingers to click the back button.

Blue Hat, Black Coat:  When are the processes activated?  Maintain a sense of orientation as any action is executed or the user will abort.

Blue Hat, Red Coat:  When do the personas use the site?  Don’t be innovative if your users are averse to innovation.

Blue Hat, Blue Coat: When is performance required?  If you are taking too long to load flash or dowload data and traffic is cutting and running it’s time to consider communicating in different formats or increasing bandwidth.

This is Blue Hat for a website.  Blue Hat metaphors are equally applicable in any system you are working with be it business, government, not-for-profits, media or technology.