UX, User Experience designer will thoroughly analyse the user/user types and will have large quantity data about the user – Persona, Profile and their tasks on the app.
With all these overwhelming info, you are slightly lost on how to begin the design work? and where to start?
Clutter on the table and clutter in the mind. I get the feeling.
There is no way you would want to go wrong in design or oversee important features, as you will also have developers waiting for a couple of interface design to start their development work. You would probably prefer to avoid future edits and updates too.
Don’t get carried away by everybody’s urgency and start somewhere with such little clarity on where to start.
Invest time and organise your data before you commence design work. Share your chart/graph with your colleagues and discuss with them. Be very sure on what you doing. This way you are confident and you become the product/app.
When I say, ‘become the product’, I mean, these exercises increases your awareness about the product and you know the flow – in and out.
Also another advantage is, if ever things fall apart and blame falls on you, you can defend yourself.
Great clarity here builds strong foundation.
Organise and prioritise user tasks on a graph – ‘Importance Vs Frequency’. Something like the image shown below.
Start design work at high frequency/high importance segment. This way, you create breathing space and design flexibility for yourself.
This will make sure you cover all important and essential tasks right in the beginning.
The freedom to design is high in the beginning of the project cycle. Adding features by the end of project may become difficult. If need arise, omitting low important features at the end of development cycle will not cost much for all – you, product and stake holders.
If you don’t organise user tasks and miss out something important and try to fit that feature on the last leg of product development, when design freedom is low, it may leave a crack.