Applying personalization also become espeically tricky on retail websites and web applications. Personalization in retail websites have to satisfy both the retailer and customers.
For e.g. retailers want to promote the latest electronic gadgets to increase their profit, but at the same time provide a way to dispaly the right products that customers are looking for.

So taking retail website as an example, when you apply a personalization technology to provide better user experience for the customers, think about personalization can be easily managed by the retailers and provide the right content for the customers.

ji

Thanks for the comments. You make a good point about the complexity associated with personalization of customer interfaces. Retail website personalization requires carefully balancing what implicitly (versus explicitly) derived data you leverage in manipulating the experience.

We’ve all heard stories of Amazon’s early (an ongoing) work in this area — Your purchase of a baby shower gift two years ago doesn’t necessarily imply that you have a child. Many factors are involved — perhaps one approach would be to give greater value to explicitly collected information or “scoping” implicitly collected data.

Each app is different. And many solutions require revision as time and consumer patterns vary.

Thanks again,

Chris

I strongly believe that this was due to their inability to figure out exactly “what to do” rather than their inability to do it. In many cases, these businesses were probably overspending on technology and underspending on design.

check out Rashmi Sinha’s paper:
http://www.rashmisinha.com/recommenders.html

ji

If analysis paralysis doesn’t kill a project, it certainly has the potential to kill its momentum. I think you can often attribute an organization’s hesitancy to make “stake-in-the-ground” decisions on raised expectations when expensive software (and a costly implementation) is involved.

I also realize that many companies treat guidance by consultants and vendors with caution — finding ways to overcome this kind of barrier is important but frequently difficult.

Ji,

Thanks for contributing the URL.

I think this is a good articule to help define goals and issues to consider before considering a solution.

Thanks for the comments. Personalization (PZN) in intranet sites, particularly Human Resource-type, service sites can be a very valuable tool. You want to focus on the natural progression (stages) and cycles of an employee’s experience.

Stages: Employees start out as “new hires”, become “mentors”, eventually “pre-retiree” and “retiree”. That’s a super simple progression; you can probably come up with other stages (for example optional stages like maternity leave or sabatical). For each stage, what an employee requires of an HR site may change. The new hire needs help filling out their benefits forms, may need keys to the office, a badge, etc. The employee about to retire needs help designating a successor, transitioning their 401K or pension plan, understanding their stock (option) plan, etc.

Cycles: Over the course of a year, employees need different things from your HR site. At the beginning of the year they may need help compiling their goals and filling out self/peer-reviews. At the end of the year, they may require information for open-enrollment/benefit submissions. Just before summer, they may need help filling out vacation requests.

The information you need to implement this type of PZN may be implicitely or explicitely derived… for example, you may know (or have access to) each employee’s hire date, recent promotions, etc. So, you know how long they’ve been with the company, if they are a recent management promotion, whatever. You’ve also got a corporate calendar…

Mix this with explicitely provided data — prompt the user mid-summer about whether they plan on altering their healthcare benefits this year… if yes, you may start introducing healthcare service documentation to the site, send out reminder emails, etc.

Carefully applied PZN can take into account the stage of an employee and natural cycles in their job, adapting the user interface, and presented content, to the set of potential tasks.

….but, make sure you don’t place boundaries around the information your employees need to do their work and feel “taken care of” as members of your organization — PZN, especially if it alters navigation or visible links, can hide or orphan content making the experience confusing.

Chris

1. Designing Information Spaces: The Social Navigation Approach
(expensive book, but if you are familiar with sites like “friendster” or “tribe”, this book will provide good ideas/tips. Pay special attention to chapter on collaborative filtering).

2. Word of Mouse: The Marketing Power of Collaborative Filtering
(written by guys who started/associated with a company called Netperceptions and University of Minnesota Group Lens project guys, easy to read book on marrying personalization technologhy for the the real world…it’s about time they wrote this.)

Best regards.