You are browsing the subject "Business and Strategy" in which 17 posting(s) was found
Selling an initial user centered design process to customers can be a challenge. Here are two brochures from IBM, showing how it can be done. They both focus on business objectives and explain the purpose and outcome of the individual steps in the design workflow.
Some punch lines from the brochures:
"Want to make the most of the e-business opportunity? Easy does it."
"…an unhappy customer is somebody else's customer."
"The marketplace practices natural selection. People will, naturally, select the easiest way to do something…"
"There's nothing more expensive than a poorly received solution."
|The brochure Mastering the obvious|
|The brochure ...but can your users use it?|
Henrik Olsen | September 20, 2002
If you are in need of arguments for investing in usability, this article from Aaron Marcus and Associates, Inc. will provide you with lots of cases to use for predicting likely quantifiable benefits and ROI. The article is a collection of examples and statistics from the literature on how usability has increased revenue, reduced development costs and improved user effectiveness.
Henrik Olsen | September 01, 2002
Few companies set goals for improving site experience, and haphazard design and development processes keeps them from discovering and correcting the causes of user experience problems.
According to a report form Forrester Research, firms can boost revenue, lower support costs, reduce development waste and affect customer satisfaction by setting specific goals for improving user experience, modeling costs, and estimate benefits.
The report gives some examples on how to measure ROI on design investments and ways to prioritize fixes.
Henrik Olsen | August 26, 2002
The Dotcom Survival Guide from Creative Good was published in 2000 but is still relevant and revealing. The 103 pages report shows how dotcom’s can survive by focusing on the customer experience, make it easy for customers to find and buy products, merchandise more effectively, and measure and improve the conversion rate.
The report includes reviews of thirty-one dotcom features, teaching by example the good and bad ways of creating the customer experience. Here you’ll find good and bad examples of registration, merchandising, navigation, labeling, product comparison, size charts, search, shopping charts, checkouts, and fulfillment.
It also has a case study describing how Creative Good doubled a client’s revenue by improving the customer experience.
|Download The Dotcom Survical Guide (PDF)|
Hernrik Olsen | June 13, 2002
According to an article from WebWord all available research proves that the return on investment in usability is high for all stakeholders.
Usability has the benefits of:
- Reducing time to market
- Reducing testing and quality assurance costs
- Reducing sales costs
- Reducing production costs
- Improving customers' return on investment
Some key findings:
- Usability has demonstrated reductions in the product development cycle by over 33-50%
- 63% of all software projects overrun their budgetary estimates, with the top 4 reasons all related to unforeseen usability problems
- 80% of maintenance is due to unmet or unforeseen user requirements
|The article A Business Case for Usability|
Henrik Olsen | May 20, 2002
Users' expectations of a product depend on the maturity of its market. In the article "Market Maturity" the usability research company User Interface Engineering (UIE) explains how software products go through four stages of maturity. This product evolution is comparable to the life cycle of many products and is similar to the development we have seen on the Internet until now.
|The article Market Maturity|
Henrik Olsen | May 16, 2002
According to John Robb from Userland Software traditional knowledge management has spend too much attention on existing stores of knowledge and too little on creation and distribution of new knowledge.
Using the concept of weblogs for knowledge management is an effective way of sharing and storing valuable information inside a company. With knowledge logs (k-logs) employees can add their knowledge to an Intranet through a personal log and exchange ideas, revise documents and even manage projects.
The idea of k-logs is interesting, but I tend to agree with the skeptics. K-logging seems to be a step back from the discussion forums that most companies with an Intranet have. Knowledge management is a joint effort whereas k-logs are individual. With forums you can share, store, discuss and enrich information in a collective context.
|What is a k-log? - an interview with John Robb|
|Responses to the interview|
Henrik Olsen | May 12, 2002
Research and Statistics (39)
Research and statistics on user behaviour, trends, demographics, technological issues, etc.
Methods and the Design Process (35)
Design techniques and development workflow.
Resources and Tools (35)
Sites, journals, mailing lists, software, and other useful stuff.
Tips and Guidelines (30)
Recommendations and design guidelines.
Reviews and sample chapters of books of interest to the interactive design community.
Fun stuff for the interactive design community.
Business and Strategy (17)
Strategy, marketing, merchandising, ROI and the like.
News, Weblogs, and Magazines (14)
News, weblogs, and magazines of interest to the interactive design community.
Cases and Examples (9)
Case studies and examples of good and bad design.
Interviews of interest to the interactive design community.
Browsers, HTML, frames, Flash etc. and their impact on usability.
Communication and Visual Design (4)
Communication, Visual Design, Information Design, Graphic Design, branding and the like.
Organisations involved in the interactive design community