client login

SaaS, RIA, and User Experience Blog Postings RSS atom


November 13, 2008

Where should you innovate in application design? - Part I

Posted by Paul Giurata

I recently had a discussion with a colleague about where to innovate when designing an application or SaaS.  He was pitching a new client that kept repeating how they wanted an innovative design. But they defined innovative as a revolutionary new way for people to think about task X, with a dazzling Flash interface full of bells and whistles.  

The problem he faced (and something every user interface design firm encounters) was whether he should tell the clients what would create the best application or if should he just deliver what they said they wanted. He chose to advise them to do what would be most effective to increase user productivity and application usage - i.e. build the application around universal (not revolutionary) conceptual models and implement a UI that uses effects & interaction as a way to reinforce appropriate behaviors rather than just “dazzle.”   We will see if he gets the contract.

In any case, it got me thinking that it would be intereting to write about where innovation really matters and where it really should come in to play when defining a application. 

Consumer applications lead in innovation

It’s instructive that last week, during the Cloud Computing panel at the Web 2.0 Summit, Google’s Dave Girouard (manager for Google’s enterprise business) talked about how the innovation delivered in the consumer world is so far ahead of what is available in the world of enterprise applications. Girouard was not talking innovation in terms of new functionality, razzle-dazzle,  or new technologies. By innovation he specifically was referring to enhanced user experience that makes it easier for users to accomplish high value scenarios and that drives increased usage.

Application designs are built in layers

When you evaluate any application, you see the design is built on several layers. Each of these layers represents a point where there is the potential for innovation. But there are some layers where the business value to innovate is more compelling than at others.  This is particularly true for SaaS application design, where the value of innovation is defined primarily on the ability to increase the usage and adoption of the solution by customers (new or existing).

Application design is built on several layers

In next week’s post I will describe the business proposition for innovation at each layer.

Recent SaaS Blog Entries

2008 in review: developments that rocked the world of user experience
Dec 29, 2008

Finding the sweet spot - when is it a perfect match between client and provider?
Dec 15, 2008

Use multi-disciplinary teams to design enterprise RIAs and SaaS
Dec 03, 2008

Innovation in user experience and application design - Part 2
Nov 20, 2008

Where should you innovate in application design? - Part I
Nov 13, 2008

Two birds with one stone:  SaaS application design and business process reengineering
Nov 05, 2008

Don’t stay the course
Oct 30, 2008

SaaS and Outsourcing
Oct 23, 2008

Location, Location, Location - a mantra relevant to SaaS
Oct 16, 2008

The right conceptual model will increase SaaS adoption and reduce support costs
Oct 08, 2008

Scary economic times - how can enterprise IT survive?
Sep 30, 2008

Enterprise RIAs close the performance gap between on-premise software and SaaS
Sep 24, 2008

View all blog posts

Contact Us

New Business
1.650.678.6743
1.800.313.7874

Media and Speaking Contacts

Silicon Valley Main Office
Catalyst Resources
1700 South El Camino Real
Suite 404
San Mateo, CA 94402
Voice: 650.655.6700
Fax: 650.655.6701