10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Sep 08, 2009
In the article entitled Apple vs. Microsoft – A Website Usability Study, Dmitry Fadeyev, co-founder of Pixelshell, compares Apple’s and Microsoft’s web sites from a usability perspective, and Apple is the winner. Scott Barnes, PM at Microsoft, agrees with him and suggests the problem is because various site sub-domains have different management.
Fadeyev uses 7 criteria to compare the web sites of the two major players in software industry, Apple and Microsoft:
Sure, it’s broken down into bullet points, but the font is small and there are hardly any images to differentiate between the items. As it stands, there is little to attract me to make me want to read through this content because it’s just, well… boring.
After you’ve read the headline you can proceed to read the marketing blurb below, which leads nicely into a call to action signup button for the free trial. If you’re not interested in the trial, there are more features below to persuade you, each one ending with a “Learn more” link to a more detailed feature page. This leaves no dead ends and keeps the user browsing.Fadeyev studied Share Point’s web site and remarked the top area which grabs reader’s attention, but considers the large amount of content information as a drawback.
Too much variety causes visual chaos on the page, with each different colored or bold item competing for your attention. In this case, the page really needs to be simplified to make it easier for the viewer to process.
Apple’s website aesthetics closely mirrors that of its product line. The navigation bar looks like it’s crafted out of aluminum and features gentle gradients and indented text.Fadeyev considers Microsoft’s site “pretty good, but pretty good just isn’t enough. There are plenty of inconsistencies and a lack of polish, which puts Apple ahead in this area.”
There are also plenty of reflections and minimalist design elements. Apple has always worked on unifying the look and feel of its interface across its entire product line, from the hardware to software, and their website is no exception.
Could you tell that this is a Microsoft page if you took away their logo? Custom graphics, styles and color palettes across all the Microsoft sections help little to maintain a coherent brand image on the web. …
It’s really an ecosystem of websites hosted under the same domain and therefore it doesn’t get the benefit of consistency that Apple has. The brand image is also terribly fragmented making it impossible to define what a Microsoft site looks like.
Overall, Fadeyev considers Apple’s web site as a winner, while Microsoft suffers mostly because of lack of consistency.
Scott Barnes, Product Manager for the Rich Client Platform team at Microsoft, agrees with Fadeyev on “the majority of the points and have arrived in many ways at similar conclusions to the author.” He recently took ownership of the Silverlight’s web site and wants to change it.
The current version of the site is not one we as a team are content or happy with. We can do better, and we will, but its posts like this that help me navigate the best approach with regards to user experience and information architecture. …
Keep it Simple, Don’t make me think – are the mantra for my next version of the site and it was blog posts like the one mentioned that simply help.
Barnes considers that Microsoft’s sub-websites lack consistency because they are managed by different teams:
A centralized approach for outward site would be optimal, as then the team(s) in question have clear definitive guidelines and also we as a company are able to do a more uniform qualitative analysis on end user behavior.
However, given the political environment within the company and no one division really owns the entire site(s), I honestly don't see a realistic reform.
Tim Anderson also comments on Fadeyev’s study and makes some observations regarding Microsoft’s website:
- It’s hard to get past the marketing blather to clear information
- Too many links lead to menu pages with further links – sometimes it feels like an endless loop
- I found lots of information in the future tense, clearly prepared before launch and not updated
- Regionalisation is poor. You can start on the UK site but end up with pricing and availability information applicable only to the US
- There’s a Technet site as well as a general site and the differentiation is not clear. I suppose the general site is meant to be more business/marketing focused, but there’s plenty of overlap
- In general pages are too busy with each one offering a splurge of choices
- Some things are just inherently confusing – like the CAL policy, which has four different types of CAL (user and device in combination with standard and premium) that can be mixed and matched: you can use standard CALs with SBS Premium if they are not used with “Premium features”. Whoever dreamt that up has never worked in a small business.
While Apple’s site is an example to follow, Microsoft’s website clearly needs improvement. Perhaps the best way to do it is to start having the entire site under one control, designing a common look and feel for all sub-sites, or at least placing them under different domains like Silverlight does.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
Transforming Software Delivery: An IBM Rational Case Study
Complimentary Gartner (Hype Cycle for Cloud Security Report)
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
1 comment
Watch Thread Reply