Subscribe to this blog RSS

Diagnosing need versus want

One shortcoming of most relevancy predictor engines is the inopportunity to help a user decide if they need something or they might merely want something. What is the opportunity to change this? Right now, all prediction engines are based on a common idea: a thumbs up/down rating, or a rated score (say, 1-10 or 1-5). I forsee the chance to introduce a 2D rating system that can allow users to rate items based on real need (1-10) and desire (1-10). This engine would allow for people to create wishlists, too!

Imagine if I buy eggs and I say I rate them a 9 in terms of need, but a 6 in terms of desire. A 2D engine is incredibly more complicated to manage, but report generation should be as simple as the other functions. By telling users what else they might need, but also what they might want, it can really make life easier for both the user as well as family and friends of the user, especially at Christmas time. If you know that brother Joe wants a new bike, but needs pants, you can prioritize your gift-buying. You might also get insight into what Joe MIGHT want or need, without Joe even realizing it. Talk about a surprise gift!

Digg this article

Leave a Reply