Secret ingredients to quality software

Do you conduct Market Research via the Web?

Last updated by Andrew Campey on 13 Apr 2017 05:34 am (over 4 years ago) See History

Why write code when you may not need to write any at all? In every industry Market Research is conducted before a product is developed. Why is IT any different? Doing Market Research focuses the product on the right set of people so you can satisfy their needs. If you can't connect the dots between the work you do and how it helps the customer, consider investing your time elsewhere. Market Research bridges the gap between the techies and the users.

A great way to get feedback on upcoming projects is by putting specs of upcoming projects on the web and inviting user comments - not forgetting to acknowledge their contribution. Often Surfers will tell you what is needed to make the product great instead of just good, or you may be told that there is already a program out there that does the job. You should also spend two days looking for similar products and speaking to users about the features. Since the specs are full of screen captures, this allows us to think of our end-users and increases the likelihood of creating a great product which our users love.

Who comes first? The Technology or the User? I even wonder about Microsoft, they've built this great .Net Core technology but shoehorn a user interface and experience onto the framework so the user experience is compromised. What great products are designed this way? Do tailors measure their clients after the suit has been sewn together? I'm sure Microsoft spend heaps of time and money discussing the specs amongst themselves, but I believe they should've put the interface/Images on the web so that experienced users could voice their opinion and offer suggestions early in the product cycle. Instead we wait for the beta versions - if you offer a suggestion now, there is no time for it to be implemented as the shipping deadline is too close. The only contribution we can make at this stage is finding bugs!

So balance engineering, business and usability, put your specs on the web, keep them updated with changes, and listen to your users!

Adam CoganAdam Cogan

We open source. This page is on GitHub