Hot, well, warm on the heels of our storage finder, we have recently deployed the new server finder, which replaced a previous incantation of finding functionality which was held together by hello world string and was somewhat creaking at the edges. The new server finder is based on the architecture we developed for the storage finder - they are, in fact, 2 renditions of the same finding platform - and so leverages the features that make it so worth the investment of effort.
As with the storage deployment, the key to making the server finder successful was, well, a number of things, but the main thrust of our efforts was defining the data architecture that make the relationships between product groups, products and product attributes a meaningful one. This can only happen with some Herculean efforts being undertaken by our publishing teams in conjunction with the product marketing teams, who really understand what is important and relevant about the products they market. Really, the finder itself is just a layer of abstraction on top of the data set underneath, and in theory (as we are at pains to try and progress), can be applied to any well-structured data set. What matters, is whether the data that a customer, user, or casual visitor is presented with, and the methods they can use to interrogate that data, enables them to reach an appropriate destination. In other words, they might know where they want to go, they might have a vague idea, or they may have no idea at all, but if we've done our job as well as we should be doing it, the directed searches and filters that the finding platform utilizes should provide a the equivalent of a product sat-nav, but avoid the 18-wheelers that get grounded on hump-back bridges in the middle of Hertfordshire on the way to the new Tesco Express.
Probably an analogy too far there, but it is by way of illustrating that the key to the finding platform is the data that it manipulates. I mean, we did a number of detailed usability trails, with various rapid and high-fidelity prototypes, struggled over the tiniest nuances of labels and gradients, fought compromise on page region refreshes and a followed number of other noteworthy user experience best practices, but in the end, if we built our application infrastructure on top of a taxonomy akin to a river bed full of shopping trolleys, we'd only be providing half a solution, which, in fact, is no solution at all.
We've still got a number of things to work on that didn't make it into the first release, such as enabling product comparisons across products and, more difficult, across product in different product families, but take a look for yourself and let us know what you think. Comments are more than welcome, especially ones that are nice.

portal where they'll have to find a place next some anatomically altered engineer masquerading as Wolverine in an
web design coven in order to prolong delivery (you see how straight I'm delivering that), but because I really dislike
bangwagonesque all-seeing 'i', it's the BBCi. The BBCi brand, label, bucket, whatever, was around for many years as a catch-all bitriquadquin-media expression of anything vaguely digital. Stands to reason that when they finally delivered their TV-ondemandonlineovertheweb player that it would fall under that broad BBCi category of products, even though they don't really call it that anymore. So, why not just stick the 'i' at the front? Viola!. iPlayer. Nothing to do with
A few weeks ago, we put together a servers overview page, so that we could do that story telling, provide sensible paths into product areas, uplevel featured products, show off some great customer success stories, and, yes, tell you what our servers actually are. It's a delicate balance on these pages between getting the story out there and providing a quick route to the products, but I think we managed it pretty well. I say 'we', but, of course, it was the good folks in the product marketing teams that pulled all the content together (kudos Carlos & Lisa), and our publishing team that managed the tricky icky problem of integrating the new content with the existing server finder (heroics from Jing). I just did the bit where I say 'you'd be better of with a
So all hail
Its probably unfair to pick out Forbes, as there's any number of article-based sites out there which adopt this style of page format. I say, 'adopt this style', but what that really means is 'crams as many ads into the available space', even if they are those circular ads which are published by, and point to, yourself. I guess I still hanker after solid design frameworks and excellence in user experience, but as the channels on the internet converge with the channels on TV and other media, it's predictable that the demands for return on investment drive the content model. Perhaps I should be tipping my hat to the page designers who manage to actually squeeze some content into these pages, notwithstanding the requirements for ad placement, cross-marketing, subscription targets and everything else. That is a real user experience challenge, albeit not one I'd like to have to take on.
But how do you know what's new and where do you expect to find that out? When you're looking at something the scale of sun.com and trying to determine customer behaviours for a given page type, it's not alway a simple task to predict. You might be the kind of visitor who would casually visit the sun.com home page and, not unreasonably, expect to see anything newsworthy enough, that you might be compelled to actually invest time in, to be present right there. You might be more specific than that. You might be the CTO for an SMB or some other suitable market research defined acronym pairing, in which case, you'd probably know that we've got a place
We've got a new place for Small and Medium Businesses on sun.com.
from a) the blogs.sun.com comment system and b) the sun.com postmaster replying to bounces from the comment system sending to people who don't work here anymore, that were all rather, well, polite in their spamness.
associated with one person. We'll probably lose 80% of our regular readership that linked to the old URL in a feed reader or added a link in their del.ectab.le bookmarks or just have it favorited, but I'll be sure to put an enormous blinking message on the old blog, to try and redirect folks here. If nothing else, it'll show us if people actually read the other one, rather it being popular through automated referrals.