The recent push on UX and Usability is mainly about following a “flow” based approach towards product development.
If we first resolve the user goals and objectives of using the software, then understand how well he/she can perform those tasks as end-to-end workflows, the rest pieces of the puzzle magically fall in place. The flows would question the importance of certain features and in turn validate the concepts – for or against. This form of thinking really breaks down the entire problem into manageable building blocks – thus improving the overall process for all stakeholders.
Developers get more clarity on relative importance of system features and are thus empowered to prioritize accordingly. Designers can plug in their blocks of user interface designs, based on the overall road map more efficiently. The entire ecosystem hence functions properly with less ambiguity.
User experience can be obtained only by connecting the dots with analyzing the users and their tasks – through flows. Complex business problems are easily solved with this approach. For product companies, it’s imperative to use this approach even if the realization is a bit late. In fact, almost certainly, this approach will pave the path for a rapid delivery, with higher user adoption. On the other hand, not taking this approach would make the product have weaker links/features/screens/unwanted steps – all of which will contribute towards lower adoption.
Think. Only flows.