show how far we have come in just a short amount of time.
Web applications are coming into their own. GMail is now Googles center piece (after Web Search).
For many of us it's now an essential tool in our lives. But was only released a few years ago.
Accessing Community from our Apps
We want to allow customers to access product forums and blogs from our software applications.
- Shift+F1 links to a Page in a Google Group (Each SW page has a corresponding web page).
Customers can vew pages but not edit. Customers can post into the discussion group area.
- A limited RSS Feed reader built into the applications to access our blog.
- Links to the product Blog associated with the SW application.
- Click to view the blog in your browser.
- Icon flashes when new posts are detected.
More notes on our latest UI designs here: UI/UA Design
Follow the Leader
We talked about Microsoft showing leadership in this area.
MSDN (MS Developer Network) – Community wiki
- MSDN now allow customers to annotate their developer help. MS developers call it an embedded wiki. Anyone can add text.
- They started small and slowly opened it up to partners and now to general community. No real problem with spammers.
- For legal reasons community content and MS content (which gets shipped on DVD) are visually set apart by coloring the community area green.
- As you can imagine the size of the MSDN web site has increased dramatically.
If my figures are correct - In 2006 2 million pages; In 2008 they are now approaching Wikipedia in size (40 million pages).
Feed back on the web is an invaluable tool. It allows a "Continuous Improvement Cycle" where Microsoft can review community input and update documentation and product in the next update/revision cycle.
So this slide shows that feed back comes from many sources. And allows a cycle of continuous improvement.
Application design – No Dead Ends
Another one of Microsoft's catch cries is "No Dead Ends".
Customer experience is frustration if they get stuck and can't solve the problem.
So here the Microsoft help team remind us that it all starts with a well designed Software User Interface.
The UA (User Assistance) esscation path should not leave the user at a dead end.
Notice that community is in there before support? The aim is to free up support and let the customer try and
fix their problem by using the product FAQ pages, Forums, Wikis and the like.
Continuous Publishing Model
Windows and Office help are now On the web (Online) (although Offline help is still an option).
This allows MS to continously make improvements to the help documentation (and the application) via good customer feedback.
This cycle of gathering feedback and re-publishing they call their "Continuous Publishing Model"
Full article: http://helpware.net/aphelp/review1b.htm#Continuous_Publishing
A MS Story
Recently the MVPs talked to the Microsoft MSN Web department, which published over
40,000 web pages. Each author in the team was given several thousand web pages
to maintain. By examining the web stats, they found that only 70% of the
pages were never read. They removed all these pages and
never received a single complaint. Next, they reorganized the FAQ page
order so that popular pages were moved to the top of the list, and support calls were reduced
- Google Groups (forums) are worth looking at. Free and reliable.
- The web offers opportunities to form tighter feedback loops with customers
- More satisfied customers get answers quicker (less frustration).
- Research shows that forming early customer relationships (in the dev life cycle) means loyal enthusiastic customers. Who then tell others of your product.
- The Microsoft experience can teach us much.
- Software applications should link our customers to web apps as seamlessly as possible.
- We need to design smarter sofware that helps connects us with customers, and customers with each other.