Design files

HomeMaker - Service

A cloud-based system for handling issues regarding warranty and other building-related issues. 

The problem(s) you had to solve or the hypothesis you came up with for solving it
The problem was that the application is self had an old design that was designed by developers. A lot of information/instructions was missing, you didn't know what the system was doing or how it would respond to your actions. It came down to the fact that no one tested the product themself, just a team that couldn't speak Swedish tested it. This was something that I wasn't able to change.

Based on meetings and interviews with clients but also input from the team. The design was built on this to reflect new needs and wants from both business and users. 

Your specific role in the project and how you collaborated with others
I was the first designer ever in the company. On an agile team with three developers and the product owner. 

I was responsible for determining the overall design direction of the project, talk with users, while collaborating with the rest of the team. But also quality control and in-house tester. 

How you came to your proposed solution(s)
By gathering information both from interview and meetings with clients. But also from Customer success' helpdesk but also hot-jar. I added all this information to Productboard and could determine what was important and what was not important at the moment. This was a neverending project and was giving when you saw that you could make the right desition based on real data and insights. 

How your proposed solution(s) solved the problem
I introduced solutions for our product owner by referring to what we should focus next sprint. Validating claims and suggestions with and user-cases as the reason why. After that, I made design and handed it to development, after that testing and release. 

Challenges you faced, including design concepts that were ultimately not pursued
The biggest challenge was that working with a designer and user feedback was new for the whole company. It was not easy trying to implement all the good and useful tools you have it the organisation and team are not ready for it. I have to take things to step by step. 

But it still broke my spirit when I realised that the development team was not as agile as I imagen and that feedback after something have been developed was out of the question. 

How the project affected the users and the business
The implementation fo the new application when well we estimated that all the users should be in the latest version in 6 months. It only took three months, and it proves the experience and design of the product were easy and userfriendly. 

What I learned
I realize how difficult user feedback is to communicate with a team that not used to it. Also, when they're used to develop, external test and then move to the next thing. No real feedback loop and to implement it takes energy and hard work. It would be best if you always answered why you have come to a particular conclusion. 

Personally, the experience made me recognise that for me to grow it's important to be able to communicate and work where my insights are valued, and that the organisation is open to question its own assumption.