Stéphanie Walter is a Luxembourg based UX designer, currently working at the University of Luxembourg as the Visual, UI, UX designer. With over seven years of experience, Stephanie has worked with Université de Strasbourg and web and mobile agencies.
Tell us about your journey as a UX designer?
Stéphanie: "I started working in the industry as an intern in Germany where I was supposed to build a website for energetic solutions. That took me three months instead of six, so they gave me some other tasks to do which included designing an iOS app. And this is how I discovered mobile and product design. I was very excited about making the product better for the users but did not know how. So I started looking for articles online on usability and discovered the field of User Experience Design.
After two years and a half, I came back to France to work for a web agency. Agencies are often hired in the middle of the project, where a lot of strategic and user related decisions have already been made. Most of the time I was asked to build wireframes and design mockups. I tried to do my best but selling and enforcing a user centered design process proved to be quite challenging for many projects in the agency. Fortunately for not all of them. I was able to apply a more user centered process for more product oriented projects (mobile apps for instance) where we were involved from the start and could help the client make the right decisions. I kept on learning by reading a lot of articles and attending conferences. I also read a few books on UX methodology and also on psychology, design thinking, emotional design and gained more practice on those projects.
I think that the important thing is to try and practice whenever you can. Even a small 10 minutes chat with a user, or a perfect guerilla user test will help you get some information about your users and help you progress as a UX designer."
How is your work experience at the University of Luxembourg?
Stéphanie: "It’s fascinating. For instance, I work with my team on a project where we apply user experience methods to design collaborative learning spaces for students. It’s nice to see how you can use those methods in other fields than digital interface design. It’s also challenging to work in a team with researchers and not people in the web industry: priorities in a University are entirely different from when I used to work in a web agency for instance."
How important is the visual response by a mobile app?
Stéphanie: "I think the visual response is significant, especially on mobile apps. If you don’t provide visual feedbacks to users, they might wonder why the app is not responding and think it is broken. Visual responses help a user to understand that everything works fine. They can also help in building beautiful transitions between pages (material design does a great job with that) and make the user wait time shorter. Finally, a visual response can be a nice way to add some delight in your apps, from subtle transitions to even bigger animations."
Project iVelhop Gif
Tell me about the most challenging project you have ever worked on? How did you approach the challenge?
Stéphanie: "The most challenging project was a website and an iPad app for music teachers. They would take a short recording of instrument practice sessions with their iPad and send these videos to the students through the platform to help them practice the same at home. The videos would be posted on a schedule so that the students will get them buffered throughout the whole week. We were only working on the website (the platform sending the videos) and another agency was working on the app. The budget was small, and so were the delays. I wasn't involved from the start, and we were not able to do proper user research.
It began with the developer, building an HTML CSS PHP prototype that would be used as the “base” for the discussion on functionalities. He sometimes came to me for some usability advice, but I was working on two other projects at the same time, so I was not much involved. I just had time to give some basic advice. After some weeks, the HTML prototype, built with no real specs and changed multiple times based on the client's wishes and potential users' feedback made everything complicated. I tried to help them by building a clear, structured user flow with all the different types of user profiles possible. It helped a little bit. The project went on: after the prototype phase, they applied a UI template on top of the HTML (no budget for design, remember). Meanwhile, I met with the agency that developed the app. They would take care of the functionalities, and we would apply the same UI kit on top of the app.
A few months later, they sent us a demo of the app. Something was wrong. Users had to take the videos in a first tab, then go to a second tab to put those videos into a bundle, then go to a third tab, find the bundle and schedule the 'video sending' for the week. The app was not usable; this user flow made strictly no sense. When we asked the agency, they told us that the app was based on their iPad framework and could not change it (well this could mean re-building the whole app, and the client did not have the time or budget for that). I nevertheless did some paper guerilla user testing to try to find some solutions to the main issues without rebuilding the whole thing. We proposed a few things to try to improve this a little bit, but we were not confident that users would be able to use it.
We exported the mockups, and the client presented them to some users to test the app. And what happened was what we feared: nobody was able to complete the task. We were able to negotiate one full day of the budget to re-think the whole user flow.
We threw away everything built for the app developers. We started with the teacher’s needs (and not with their framework possibilities this time) and were able to have a fully functional user flow involving fewer steps than the first one. We presented this to the client and the developers. Everybody around the table agreed that it worked better. We decided to build a prototype and put it through a user test the week after. We started discussing user recruitment. It was a win for me. The developers left the room. Then the client got a phone call. It was the developers of the app, who, remember, were totally on board with the new workflow 15 minutes before when they were in the room. They apparently explained to the client that it would take another two months if we change the workflow because what we propose was not compatible with their framework. Of course, they never told this when they were in the room. This felt like backstabbing. And this was it, the end. The client could not wait for another two months; he wanted to launch as soon as possible. Bye-bye user testing, bye-bye new user workflow, they decided to launch the app as it was.
As I said, this is still my biggest regret so far. I regret not being involved from the start because of budget limitations and other factors. I think I should have insisted more, fought my way around the table. But I was less experienced than I am today. I think this is also how you learn that sometimes, deadlines and client’s priorities don’t always align with the work you wish you were able to do. And I also consider it my most challenging project."
Few responsive designs by Stephanie
Where do you look up for inspirational mobile design patterns?
Stéphanie: "Usually, I start by checking at the OS guidelines. Both Android and iOS propose some excellent documentation. This helps me to make sure that I will not break any user habits. Then I usually do a competitor benchmark, and it helps me understand what other people do, also what I should not do. When seeking for specific inspiration regarding patterns, there are a few sites that can help :
Of course, there’s also dribble, but it has become more of a showcase of what crazy things designer can imagine than of inspiration for real projects, so I usually take a look but try not to focus too much on that."
What is your approach to design a perfect mobile app?
Stéphanie: "Firstly, I try to understand user needs: ask support for pain points, meet users and interview them, check analytics, a mix of quantitative and qualitative data is always good here to understand what they need and how can I successfully address those needs. Building personas and empathy maps based on those data will help the team gain empathy towards those users. I would then work on the user journey and user flow. How Will a person use my app? In which context? What kind of screens does she need? How are those screens linked to each other? Are there any issues, things that can be improved? How to make her journey easier? etc.. Then comes the prototyping phase: I’m more comfortable with sketching concepts on paper, it helps me to explore more theories than if I open a design tool on a computer. I try to build prototypes and test my hypothesis on real users before digging in the “ visual design phase.” There are a few tools like Invision or Marvel apps that will help you build click-through prototypes you can test online. Once everything works fine in the prototype, it’s time to choose colors, fonts, icons and all the graphical details of the interface. I usually prepare mock-ups but also a detailed style guide to help developers’ work. This is also usually when I decide about animations and transitions between the different items and elements. Animation plays a significant role in user experience, especially on mobile. I try to test the prototypes or mockups whenever possible in early stages of the process as well."
Can you share some of your best Mobile designs?
Stéphanie: "Unfortunately, I worked a lot in the B2B industry on apps that are not in the official stores so I can’t share the native apps designs. But I did some nice things in responsive web design on Nordika Travel for instance."
What strategy do you use to make your mobile app onboarding process better?
Stéphanie: "I like the idea of progressive disclosure. I think it’s easier to teach user in context, once they played a little bit with the app and are familiar with the concepts than to give them a big “here is a tour of what you can do and how you can do it.” Of course, this depends on the type of app you have. But in context, small help messages are always a good thing."
What is the future of Mobile UI/UX?
Stéphanie: "It looks like we try to connect more and more devices and IoT to our mobile phones. So I guess we will have to make sure the user experience will stay consistent on all of these devices, whether they are directly connected or in standalone mode. There is also a growing part of the world population using mobiles as their primary access to the internet. And those people might not have the last super powerful devices us designers and developers tend to have. So I’m delighted to see that the browsers are improving a lot and that a lot of functionalities like geolocation but also offline support, notifications, etc. are starting to be available in browsers.
As a designer which social channel is your favorite?
Stéphanie: "Twitter, even though 140 characters is sometimes complicated to deal with, it’s perfect for quick replies and finding useful links. Stack Exchange is also a good place to discuss usability and UI patterns with other people in the industry."