{"id":519,"date":"2020-05-12T16:30:31","date_gmt":"2020-05-12T15:30:31","guid":{"rendered":"http:\/\/joseviso.com\/?p=519"},"modified":"2020-05-12T16:30:33","modified_gmt":"2020-05-12T15:30:33","slug":"introducing-ux-in-a-company","status":"publish","type":"post","link":"https:\/\/joseviso.com\/introducing-ux-in-a-company","title":{"rendered":"Introducing UX in a company"},"content":{"rendered":"\n
Over one and a half year ago I decided to take on a new and exciting challenge and joined a company to start working in a brand new product where I was going to be the only UX designer<\/strong>.<\/p>\n\n\n\n The title of this article might be a bit misleading as I wasn't technically the only UX designer in the company, but our Aberdeen division is a \"mini company\" itself specialised in Asset Integrity Management software. As you can imagine this presents most of the challenges of introducing UX in a company. <\/p>\n\n\n\n I joined a team that had been evolving a piece of software for the last 30 years and they had never worked with a UX designer before. Design wasn't in any important discussion until that point and nobody had heard of things such user testing<\/em>, prototyping<\/em>, user research<\/em>, Sketch<\/em>, Figma<\/em> or similar. <\/p>\n\n\n\n This situation represented an interesting anomaly (no pun intended working on such industry) for a Scandinavian company where design has a big site in the table.<\/p>\n\n\n\n This has been a really interesting time, full of challenges but extremely rewarding. I wanted to take this opportunity to highlight some of the key things I have learned:<\/p>\n\n\n\n Pick your battles<\/strong><\/p>\n\n\n\n It's important to identify high value low hanging fruit<\/strong> or things that can easily be done and will create a lot of value for the final users or will solve some of the important issues identified.<\/p>\n\n\n\n For example, in our case one of the most cumbersome and painful parts of our software was the way in which the users would filter information. This presented many issues but the main one was that there wasn't a good visibility of what filters had been selected.<\/p>\n\n\n\n Some minor tweaks to this area made a massive impact for final users, avoiding them having to click multiple times to see what was actually selected.<\/p>\n\n\n\n Bring value<\/strong><\/p>\n\n\n\n One of the first things I started doing early on was to prototype things to help the team understand and visualise requirements<\/strong>. Until that point I really had wanted to start using Figma<\/a> but never had a chance and I realised that was the the perfect moment and it became my main tool. <\/p>\n\n\n\n Reading and hearing so much in the community about Figma I had really high expectations but after start using it full time it absolutely met them going even beyond. Everyone started really liking working with this tool as they felt it provides an excellent way of sharing and communicating designs. And personally, I found it extremely appropriate for quickly mocking-up, sharing and validating ideas.<\/p>\n\n\n\n