Creating personas and fictional representations of our target users. This, along with qualitative preliminary research helped us build empathy with the audience, identify exactly what they need from ChargeERP and guide our design decisions from start to end.
We tried to incorporate multiple attributes like the needs, goals, behavioural patterns of our target audience in the user persona.
Considered user stories to be a way of expressing software features as a solution to user needs rather than a requirement document. After our preliminary user research (qualitative - online surveys, telephonic and in-person conversations) we came up with user stories for every single pain point faced by our target audience and mapped them to potential solutions we could come up with.
This helped us narrow down on the feature set (listed below) and build exactly what our target audience needed. We also drafted a few core principles and planned to adhere to it so that we set product vision and mission right.