EM360 Digital Blog

26 Feb 2016

Evaluate Your Product

There are a lot of star­tups out there cre­at­ing great prod­uct design. But how are you sup­posed to eval­u­ate inno­va­tion?

John Long at The Ship’s Log has 3 sim­ple ques­tions (and sub-ques­tions) to ask when con­sid­er­ing your prod­uct.

Is it Usable?

And now for the sub-ques­tions!

Is the heart of the appli­ca­tion easy to use?
Are the entry points (land­ing pages, signup, etc.) straight­for­ward?
Will the aver­age cus­tomer under­stand how to get start­ed?
Is the copy used in your appli­ca­tion help­ful, instruc­tive, and intu­itive?
What are the com­mon pit­falls? How can you design the appli­ca­tion so that those are nev­er expe­ri­enced?

Is it Cred­i­ble?

Cred­i­bil­i­ty isn’t nec­es­sar­i­ly the VeriSign certificate—think pol­ish. Does your prod­uct have the cred­i­bil­i­ty that makes some­one want to use your appli­ca­tion because of the way it looks and feels?

“Cred­i­bil­i­ty is about dress­ing to impress. If the cus­tom fit­ted suit and gold watch don’t impress your clients and help you become a real, viable busi­ness then you’ll have spent valu­able time and mon­ey cre­at­ing some­thing with no val­ue.”

Is it Easy to Change?

No prod­uct design is per­fect; expect to get some cus­tomer feed­back and need to make spur-of-the-moment changes. Look out for:

Cram­ming too many func­tions into one screen.
Using tech­nol­o­gy in key places that is not well sup­port­ed by the major­i­ty of browsers.
Try­ing to achieve desk­top-cal­iber con­trols.
Mak­ing fea­tures Javascript-heavy that could be pure HTML.
Using an exces­sive num­ber of images (pure HTML is much eas­i­er to main­tain).

[From labs.openviewpartners.com]


Write a Reply or Comment