Like we do every two weeks, Ingressive had another Tweetchat session with our twitter community and Flox Dairo was our Tweetchat guest for the week. Florence Dairo also known as FloxDairo is a UI/UX Designer at OneFico, owner of Paylater. It’s an opportunity for tech founders, tech enthusiasts, developers, and designers in our community to gain in-depth insights on the importance of Design Processes.
So, we'll basically be chatting about "The Importance of Design Processes".
Kindly use the hashtag "#IngressivechatWithFlox" and "@" my handle and Ingressive's for any question along the line. I will answer all at the end of my session.
When it comes to design, the strength lies heavily on the steps taken to create the final result than the final product, itself.
Please bear in mind that there are more than one possible solution or thoughtful approach to solving your clients' problem…(so feel free to come up with your process 😉).
The attempt at solving the given design problem demonstrates how empathic the designer is willing to be on behalf of the client.
That said, a design process is a series of steps that helps you (as a designer) define, plan and produce a product your building. Product in this case are applications (mobile and web apps).
Having a design process allows you to be efficient and focused on creating the best product possible. It also allows you design based on facts and not assumptions.
There are different ways of approaching new projects and it is advisable to create a process that works for you. Most importantly, it is advisable to have a process that is strong and flexible enough to accommodate different clients and problems.
I start by "Exploring" the problem...analysing and expanding my knowledge through UX research (collecting as much relevant information as possible at the early stage int the project's lifecycle through user surveys and user interviews <for primary data>)
This gives me an idea of my users, their needs and visions. Then (no.2) "Focus"... I combine my findings and facilitate scoping exercises such as personas, user stories and product maps. This allows me decide how my users will move through the app.
Then I move on to creating "Wireframes" (LowFi and MidFi). In order to ensure that you are designing the best possible experience for your users,
it is advisable to create bare bones of the app (no colours, no photos or icons just boxes and lines) to show the placement of where things would be without getting distracted by how things look.
Then to HighFidelity "Visual design" and Interaction design (ie. animations and transitions). At this stage, you can use fonts, add colours, images and icons. You can basically give your app an identity that brings it to life.
The last stage of my process will be "Usability analysis" and "Production design". Create and test prototypes. Along all stages of your process, it is advisable to always test your design decisions made.
Then finally create style guide and asset slicing. This allows you accurately ship your designs to your engineering team for production.
So, Why is all these really important? Really. 😑
Primarily to cater for your users. UX research gives you more information about your clients' users and their competitors.
With a clear design process, you can establish realistic project deliverables and deadlines with stakeholders of the project. They know what to expect and when...thereby eliminating needless miscommunication.
It decreases the risk of failure. There's a lower risk of having a failed product after carefully and thoroughly gathering your findings to create the product as opposed to pushing pixels first.
It allows you to be more efficient and transparent when designing. Efficient in the sense that you know the next step to take (and you're not just chasing your tail) and you can clearly trace back your steps. Transparent, in the sense that all (major) stakeholders on different teams are involved and can collaborate easily at anytime. There are a lot of amazing tools that encourages collaboration.
When it comes to design, Figma is the best at bringing in major stakeholder to give inputs at every stage of your design. This saves time and effort.
In conclusion, there is no one way (or process) to get through a project. It is advisable to come up with a strong and flexible design process which clearly shows what you need and caters for different clients' problems.