When we came across this blog posting by Dion Hinchcliffe, which discusses ways to actually implement Web 2.0 technologies to build a better relationship with customers. If you look at his top 5 items, they are indicative of the successful web companies of late- the most notable example is SalesForce.com releasing it's AppExchange initiative, which builds a platform rather than offering a product. Of course SalesForce.com is no doubt feeling some pressure from the open source competitor SugarCRM, but we think that the idea of creating a platform would have happened regardless. The possibilities for the product and the implications for the uses of it suddenly become much more far reaching and impactful. Its a great way to build a network of partners and overcome obstacles where the software may not have been purchased because it didn't satsify a customized need.
As both consumers and providers of products that have Web 2.0 components, we offer the following additional implementation techniques for way to effectively incorporate Web 2.0 into a solution:
1. Use Familiar Features. Don't innovate or try to improve on features or processes that users are most likely already familiar with. You may devise something very clever that replaces a traditional Excel download, or alert messaging, but if you stray too far from what users would be expecting, you will end up with a negative experience.
2. Allow for users to be of varying levels of experience with web technologies. For example: create a 'basic' and 'advanced' mode. The latter displays every feature you packed into your system- with the idea that features they don't need will not detract from their experience. The former would focus on the core features, with tips and help to increase their knowledge of the system as they require use of more advanced functions.
3. Being perfect with a few things is better than being good at many things. We will again use the SalesForce.com example, since it is timely and a perfect demonstration of the point. They focused on developing the best CRM system they could build. When it became a very solid, mature product with a good reputation and contained features that the majority of users were 100% satisfied with, they then developed the AppExchange platform. The benefits of the platform were as real 5 years ago as they are now- but it wasn't core to the offering. Web 2.0 may allow you to create features in products that have traditionally been a pain to use (calendering, email, etc.), but that doesn't mean that a few AJAX calls will result in a wave of acceptance.
4. Don't get stuk on a single type of interface. The only thing that is certain when it comes to UI design is that everyone's 'perfect' interface is different. So, the best way to accommodate the masses is to create several ways to accoplish the same task. Microsoft has been doing this for years (in MS Word, you can use the drop menus, the toolbar buttons, or keyboard shortcuts), but the Web 2.0 innovations make this a much greater possibility for web applications.
5. Consistency, consistency, consistency. Anyone developing with AJAX is creating the new standard for web applications. When HTML was first widely adopted, the web was a hodge-podge of pages with little in common with one another. Over time, certain things became standard: 'My Account' in the upper right, logos in the upper left, copyright info in the footer, etc. Keep in mind what the high-traffic sites are doing; its important to have consistency of feature behavior within your system, but it is equally important to ensure you are actively working toward that standard.
As with any step forward in technology, there will be many ideas formed, and only a few will be widely adopted. The ubiquity of the web allows us to constantly improve these ideas as we create new and interesting products. Don't be afraid to venture an idea to the market, but also be mindful of when it is best to go with an established idea.
Any other thoughts on Web 2.0 implementation techniques? The more we create and analyze, the better all of our experiences will be. We encourage other ideas you have.
