 Welcome, my name is Maria and I'm a project leader in Absalon and today I'll be talking about conductive effective user tests. I would like to start with telling you why I believe this topic is important and also what I actually mean by user tests and then I will follow up with some good practices. I think that including users into the development process is a game changer because in the end we are building a solution for them and they will decide if it is a success. They will decide if this is helpful for them and intuitive to use. And when I'm talking about user tests, I'm talking about one-on-one meetings that they have with the users when we already have something that we would like to share. It doesn't need to be a final solution, it can be, for example, a POC. And this meeting usually consists of three parts. First, I'm asking the user about his or her daily work, then I'm asking the user to perform actions in the application and I'm observing it. And then I'm gathering general feedback from the users. Now I will follow up with some good practices. First, try to not wait until the product is good enough. I know it can be very hard to share something that you feel is not perfect and you see a lot of things you could improve but it is worth it because otherwise you can spend a lot of time developing something which won't be used because of some assumptions that you made at the beginning. I would even go a bit further. I think that sometimes it's good to dedicate time to create a POC and showcase the POC to the users to gather early feedback. And I think that SHINee is a great tool to create such POCs because of how fast you can develop in it. And I would like to share a case study with you. Some time ago, a client came to us and asked us to create quite complex React Python application and in the end we decided to start with a POC in SHINee to validate his idea first. And we had only two weeks to create this POC. And I have to tell you that it exceeded my expectations for sure because we were able to not only create good looking application with the car functionality implemented, but also we were able to mock a lot of other functionalities. And it allowed us to show this to the user and gather feedback. And to learn a lot of things that we needed to change in the final design. And later on, when we were implementing the application in React Python, we could already implement those changes. And otherwise, we would need to wait a few months at least to gather this feedback and then probably rewrite a significant part of the code. So I encourage you that when you have a situation that you know that your final solution is quite complex and it will take some time, just try to start with the POC with a lot of functionalities mocked and already start gathering feedback from the users. The next three points will be mostly about the second point of the interview. So the time when the user is interacting with the application and the rest of serving it. So first, try to limit the explanation to the minimum. I know it can be hard sometimes when you see this user struggling. But those are the situations that you should observe and note down and make sure that you know how to avoid them in the future, how to change the UI or implement some changes in the features in the application. Another point will be to ask the user to perform business actions. So try to avoid questions like, could you go to the right top corner and change the value in the dropdown to Poland? It is much better to ask a question like, could you please try to display data for Poland? Because then you know if it's easy for the user to find this dropdown and also to filter on Poland, for example. And you can implement some changes if it's not. Then ask the user to speak aloud about their thinking process and expectations. Because only then you can truly understand what is happening. As an example, a user can open a tab and he can tell you that, oh, I opened this tab because I expected some advanced charts here. But I can only see a table which is not very helpful for me. And now you know that you need to change something. You can change the tab name or add these advanced charts if needed. And the last part is about gathering feedback. So try to ask open not leading questions. So try to avoid questions like yes or not. And try to not lead the user with your question. So the worst example would be starting with a question like, don't you think that this solution is great and it will really help us? Because then it will be very difficult for the user to give you some constructive feedback and criticize the solution. That's all I would like to share today. Thank you so much for joining me and see you on the Q&A session. Thank you. Goodbye.