• ProductNation Network

    Capability -> Functionality -> Usability

    The capability to build something – a product or a solution – is, but, just the start of things. Capability is needed to build a product but capability is not what gets your product to be loved by your (potential) customers.

    One leverages capability to create a functionality (call it a feature, if you may). This functionality is created based on a broad understanding of the market needs e.g. one needs a mode of transport to go from one place to another. That is a broad market need. Based on this realisation, we set about building our solution. Depending on how one has understood the problem, the solution may result in producing a physical product like a new kind of cycle or a service, like a cab-hailing service.

    This can be called creating the functionality.

    But this too is not enough. With functionality, one has expressed his/her understanding of the problem and to a great extent how one’s own perception has influenced the solution. When one goes a step further to get into the specifics of particular user needs (as compared with the broad market needs that I mentioned a bit earlier), then one starts to look at the usability or, as I prefer calling it, the usefulness of the solution.

    To understand the user’s needs one needs a deep understanding of human behaviour itself. More specifically, one needs to observe and understand human behaviour in specific situations. So while one can build functionality based on a market need, to build usability, one needs to really observe and understand the user.

    Being a keen observer, I notice multiple things and many times I find myself wondering at the thought that went behind creating that experience. An interesting example is this wash basin that I found at a major sports store.

    Numerous times I have been a witness to a mis-aligned combination of tap, tap knob, wash basin and basin outlet. I am sure you too have. This one ranked among the top. The tap was actually hidden away. Did the person who put this thing together, have the capability? Yes! Did s/he understand the general market need? Yes! Did s/he really think about the user while building this? I would say, No? Or maybe, s/he did not care enough. But I am sure you get the point of usefulness.

    In our own experience for the past 2 years, we have build multiple hi-tech features, cracking complex technical problems, patting ourselves on the back for being the geniuses that we are. But we realise that this is just a demonstration of our capability and what we can build from here is mere functionality until we get into the skin of the user. Of course, when I say user, each solution could have multiple, each with his/her own whims and fancies and hopefully a few common universal traits.

    At RobusTest, on a daily basis, we try to bridge the gap between functionality and usability. Reminds me of something that I learnt in school about a variable tending toa value. In our case, on the number line between functionality and usability, we are striving towards usability – which is a constant goal but never completely reached.

    The same should apply to any product/service and may well, be that small tweak that may get you that product/market fit that you seek.

    Guest Post contributed by Aishwarya Mishra, Robustest

    Creating a company brand — outside a product brand
    Two Years of iKen : Wins and Lessons.

    Tags: , ,

    May, 18
    2017
  • Copyright © 2013 - 2017 iSPIRT foundation | All rights reserved | Powered by iGenero and Netsolutions

    Read more:
    Disruption of Chit Funds and the Role of the India Stack
    Disruption of Chit Funds and the Role of the India Stack.

    Chit Funds are indigenous financial institutions in India. It is a mechanism that combines credit and savings in a single scheme. In a chit fund scheme, a group of individuals come together for a predetermined......

    Close