Hello - it’s been a minute hasn’t it!?
The current status of the Chrome extension is “Under Review.” I gave my extension permission to access all urls (because any url could be entered to the Google Sheets document), and this leads to a longer review time. I don’t automatically see a way around this because asking someone to add the url permission to the code every time they want to add a site to the rotation is not ideal. Not only is this inconvenient, but it would also make things a lot slower because the extension would have to be submitted to the Chrome Web Store for review every time someone adds a url… 😅
I also have been working on the company calendar webapp. I spent a lot of time implementing user authentication. I then wanted to access the Microsoft shared calendar via the Calendar API. However, it turns out that this API only works with online accounts and not on-premise accounts. I thought a solution to this would be to make the company calendar email account an online account - but we are checking if this is plausible.
I got to shadow Anna, who’s a UX Designer, in Munich. I got advice to ask as many questions as I could - and I did just that. I sat in on her meetings, listened carefully, and asked her questions after the meetings (so as to not take the time of too many people). One thing I found really interesting is how a certain logo or a certain phrasing impacts users’ actions. It made sense to me that these changes could influence the time it takes a user to click a certain thing, but I never thought that it would significantly cause or deter someone from executing an action.
Related to this, Anna, Sebastian, and Max were talking about the exit rate of the Review page. The exit rate is the rate of users who exit the HolidayCheck website from the Review page. They wanted to compare the exit rate of this page when reached via 2 different logos. How many people come to this page by clicking the old button (old logo and old wording) and exit HolidayCheck (as in, they were surprised by or not interested in what they saw) versus those who come to this page by clicking the new button (new logo and new wording)? I think that’s really interesting and quite powerful… What can we do to better inform the user where they are going? What can we do to avoid misleading a user? These are all things that I have experienced from the user side, so it’s interesting to think how my actions can change based on these details.
I also learned about what Anja does. She’s a UX Writer, which is profession I had never heard of before coming to HolidayCheck. It’s such an important job because it entails creating the dialogue between the website and the user. In a way, this dialogue forms HolidayCheck’s “personality.” Do we want to be more formal with our urlaubers - or more personal? These things are discussed every day, and sometimes many days’ worth of work results in just a few sentences. I know I said this before, but I find it really interesting to see the work that goes into creating these interfaces and learning about how slight changes can really affect a user’s decisions.
After this, I was able to talk to Christian, a Visual Designer. I learned a lot about the structure of his work - from the creative side of using Figma to collaboratively (in a Google Docs manner) create designs, to actually rolling out a new design. Between these two ends, a lot of testing takes place to measure how one design affects the users’ actions versus another. Christian shared that testing many things may take years to reach statistical significance. And since he has been at HolidayCheck for about 4.5 years, Christian was also able to share that design decisions were made without any data on how users react, prior to the use of AB tests. Here’s a short dialogue that took place after I learned this:
Me (curious): What happened if you chose a feature that resulted in a worse conversion rate?
Him: It never happened ¯\_(ツ)_/¯
Me (almost a software engineer, who must test everything): 🤯
I also got to watch 2 recordings of the user tests which were super interesting (only one was entirely in English). It was quite cool to see how the users react to specific features, especially those who use certain features differently than I do. For example, I would always choose the specific dates of travel, never the duration. It was even cooler to see how Anna and Susi carried out the tests. They start out with some background information about the tester: what type of holidays they usually go on, with whom they usually travel, how they pick their destinations, where they usually book their holidays, etc. Then there is a disclaimer that they will just be using a prototype so not all features are working - and the product is what is being tested, not the user. I think it’s easy to make it feel like an interview/interrogation, but Susi and Anna did a nice job of keeping the users comfortable and the environment casual - of course while extracting as much information as they can from the users.
It would have been interesting to watch an older person’s interview (there was one but unfortunately it was in German) because I want to know what features are used more/less among those people. For example one younger user shared that he did not like how he couldn’t choose 3 people and 2 rooms. The prototype gave the option to call HolidayCheck, but he said he was hesistant because he rarely has a good experience with calling and talking to a representative. The other user said she would call - although she would expect to be able to choose 2 rooms. In my case, I would be hesitant to call - especially in the case that I am just browsing the hotel list and not yet ready to book.
Throughout the week, I learned a lot from the UI/UX “team.” I learned that the jobs accross the UI/UX area rely very heavily on data, which is something that I did not consider prior to this week. I got more insight on what the developement teams are working on and their relationship with the designers, researchers, and writers. We also played kicker and Georg and I were undefeated!!!!! (until we weren’t). I quickly re-learned that I am not so good at kicker 😄.
Unfortunately I caught a cold and was OOTO on Thursday and Friday, so some meetings are being postponed until next week. But it was a great week spent with these people - and a very nice change of pace. Next week I will be with the marketing team. Until then! 👋
Hello - it’s been a minute hasn’t it!?