Interaction Audit – test your page and create an objective diagnosis

Josh Williams from Hot Studio had a great speech at Web2Expo on reshaping ebay.

The two outstanding feature were:
he gave a definition of “feel” in “look & feel”
he introduced a well shaped method called Interaction Audit

The feel is an interaction groove - “It can be click-click-click oder clickp-hover-type or click-scroll-type – it does not matter, as long as you don't start to turn a telephone in an airplane cockpit.”
The target of controlling feel is not only to attract the user, but also to make him feel comfortable, so that he can reserve bigger parts of his mental bandwidth for the content of a site instead of it's technology.

In the interaction audit (which aims to check and harmonize the feel), they started with
* defining some example workflows: what do users do, what tasks do they perform on the way.
* that led to a task-activities matrix to find out similar activities in different tasks.
* Detailed descriptions of both were collected in a database
* The number and the number of variations in the interactions are now a criteria o quality (links, tabs, forms, mouseovers etc. - 16 different types of reactions/behaviours after you click on a link, 5 different types of forms ertc.)
* in addition to interaction inconsistencies, also task inconsistencies were analysed
* object inconsistencies as well.

This was a base that could be used to define targets, go through the enterprise universe and clean up.

What makes this so great?

It's all about structuring – shaping and describing a problem is maybe not solving it, but it's a good start to avoid it in the future.
There is no common taxonomy or reusable usecase for that – it's up to us to create the best practices and to find innovative ways and solutions.
As long as you don't forget your goals, there are never to many details – all those small pieces (if kept in a clear structure) will help you understand new problems that will keep arising every day.

How to evaluate content managementsystems for the intranet

What are the most important topics in an intranet architecture, what are the most important features for Content Managementsystems to be used in an Intranet?

I just sent out a Request for Proposal to a longlist of vendors and I am now about to prioritize all the defined requirements. What I came up with as a proposal for further discussion is

• basic technology first (if its supposed to be java it shouldnt be .net)
• compatibility, scalability, integration features (content, applications and users as well as import and export)
• support (slas, guarantees, personal skills and qualities, regional distance/availability)
• basic business requirements (multitenant, multilingual, if required)
• workflows, roles and permissions
• roadmap, strategy, partnering models with vendors
• licensing models, licensing costs
• other commercial issues
• additional business requirements

It may be a little strange that the commercial criteria are so low in the ranking. In my opinion, the licensing costs really hardly matter. Vendors will offer you discounts that they almost pay you for buying their system, they will always be cheaper than their competitor. Id they are not and there is really a difference – then you should be alarmed.
The real costs will come up with additional tools and integration efforts – thats why integration features are my number 2, and support is # 3. Support and the personal relationship determin, how fast your developers will work – this will depend on how good documentation and support are, but also on how much they like the system and its consultants.
Business requirements and workflows are # 4 and 5 because they are important, but you can still fix things that are not ok – as long as # 2 and 3 are granted.
The roadmap is nice to know – you should make sure that you and your partner are going in the same direction.
You will have to pay for it, yes. But once youve paid, its over. Thats whz licensing costs are only # 6. And if # 3, 4, 5 and 6 are ok, you will be happy to pay.

So dont worry too much about prices, dont look at the big players only, listen to your developers and do care about personal relationships on all levels. If you get along with developers, project managers and CEOs, the project will be smooth and great.