<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Katarina Petrov on Medium]]></title>
        <description><![CDATA[Stories by Katarina Petrov on Medium]]></description>
        <link>https://medium.com/@katarinapetrov?source=rss-c872f375dbbe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*wg81TcjCLRentdCl.png</url>
            <title>Stories by Katarina Petrov on Medium</title>
            <link>https://medium.com/@katarinapetrov?source=rss-c872f375dbbe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:25:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@katarinapetrov/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Delivery Hero Vendor Portal: Building UX Design Foundations]]></title>
            <link>https://katarinapetrov.medium.com/from-understanding-the-first-major-user-frustrations-on-dh-restaurant-portal-to-launching-a-bdb893143f0d?source=rss-c872f375dbbe------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdb893143f0d</guid>
            <dc:creator><![CDATA[Katarina Petrov]]></dc:creator>
            <pubDate>Sat, 05 Feb 2022 14:34:21 GMT</pubDate>
            <atom:updated>2024-08-30T10:21:45.673Z</atom:updated>
            <content:encoded><![CDATA[<p><em>(Berlin, 2020-present day)<br>My role: As a Design Manager I helped grow the initial team and define design-related processes together with the team. I lead design processes within the following complex projects and initiatives.</em></p><h3>The beginning</h3><p>In early 2020, after five and a half years spent in a lovely Mjam (Delivery Hero Austria) team, I was transferred to a new team in the Central Delivery Hero in Berlin.</p><p>It was super exciting to take on the responsibility of helping to grow a new design team and improve the UX of the then-existing Delivery Hero Restaurant Portal (Vendor Portal (VP)).</p><p>I was ready to put all of the learnings from my previous role and position to the test. The challenge was accepted!</p><h3>Discovery 01: Product Map Analysis &amp; Results</h3><p>Back in 2019, Portal growth has been <strong>already accelerating</strong> — new features due to the increase in development capacity were built, new countries joined, and centralization was happening.</p><p>But, the current solution for Vendor Portal UX Design, <strong>with no UX Guidelines and Principles for designers in place, </strong>was struggling to keep up with these new requirements. Designs for the features were developed and scattered across the globe.</p><p>As our product was growing, more people and teams were involved. This as well <strong>increases inconsistencies across the brands and features </strong>leading to unnecessary extra effort from developers and a broken experience for users.</p><p>Here is an example of how the Restaurant Performance section looked like in two regions, both using Vendor Portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6NdjAQ1-h1npIia5" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fqsWrpaE1_zrii_5" /><figcaption>Same feature, similar content, a different design solution</figcaption></figure><p>Another thing I noticed was there was no shared understanding of what the <strong>big picture of the product </strong>looked like and what can be learned about user frustration just by taking a look at it.</p><p>So, as one of the first collaborative projects as a new Design Team, <strong>we mapped out the entire product</strong> with all of the pages and user flows included.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UixAjreLQ6OGsfqhPPiteg.jpeg" /></figure><p>During this study, all of the designers collaborated to identify the<strong> most critical visible usability issues </strong>the users had to face.</p><p>Here’s what we learned just <strong>by mapping the Vendor Portal:</strong></p><ul><li>complex and misleading navigation system,</li><li>confusing information architecture (eg. no logical arrangement of or order of the main sections)</li><li>inconsistent UI patterns and lack of conventions,</li><li>a lack of guiding user flows, often leading to Blackbox (eg. Menu confirmation during onboarding)</li><li>no solution for different importance levels for different user groups</li><li>no. of clicks needed to complete a simple task was huge (Vendor performance plugin where the user needs several clicks to see visualizations)</li><li>a lack of actionable and insightful information and navigation types</li><li>a lack of support and feedback</li><li>insightful and unhelpful data representation,</li><li>a lack of brand representation,</li><li>poor mobile experience</li><li>noncompetitive user experience</li><li>frequent overlapping features and lack of cohesive experience with the other DH products</li></ul><h3>Discovery 02: Desk Research Results</h3><p>After we successfully mapped out the most visible usability issues, we documented them and took them as a great start to understanding user needs for the first time. Before 2020 in the Vendor Portal team there were no existing Product teams, therefore just a handful of user interviews or tests were conducted.</p><p>To gather as much as possible feedback from a few previous research studies, we conducted <strong>desk research to collect learnings from the past</strong>.</p><p>This method completed our learnings with a deeper understanding of user needs.</p><p><em>As a user ….:</em></p><ul><li><em>I’m confused about where to go to find the information I need</em></li><li><em>I find the navigation system very misleading and complex, so hard to use</em></li><li><em>I find it hard interacting with UI due to inconsistent components and patterns</em></li><li><em>I feel like I need to spend too much time on the portal when I just need to find the information fast and complete the task I need</em></li><li><em>I think I’m getting a lot of redundancy and unnecessary information</em></li><li><em>I want everything to be super simple, easy to use, and mobile-friendly</em></li><li><em>I want the data in all reports to be consistent</em></li><li><em>I want to be told how to improve, not just look at numbers and charts</em></li><li><em>If I buy a marketing promotion, I want to know whether it had an impact or not</em></li><li><em>I always need an expert to help me with using Vendor Portal</em></li><li><em>I need to spend a lot of time &amp; effort learning how to use Vendor Portal</em></li><li><em>I think VP is not competitive: Wolt has many better features!</em></li></ul><p>Having completed the research we felt we had enough information to proceed to the next step — <strong>setting a new much-needed set of UX Guidelines and Principles for designers to use when they need to make critical decisions about what they’re building.</strong></p><h3>Defining Vendor Portal UX Principles</h3><p>The design team ran a workshop to define the first set of VP UX Principles. We followed the framework described by <a href="https://articles.uie.com/creating-design-principles/">Jared Spool</a>.</p><p>We couldn’t agree more on the guidelines provided by M. Spool on <strong>how to create</strong> <strong>great UX principles</strong>:</p><p><strong><em>01. Principles are guiding phrases, rather than statements or global phrases</em></strong></p><p><strong><em>02. Principles are research-driven: they are giving us guidance to create the right solution to user frustrations</em></strong></p><p><em>03. Principles distinguish your product from competitors</em></p><p><em>04. Principles can be revisited and reversed overtime</em></p><p><em>05. Principles need to be constantly discussed &amp; tested</em></p><p><em>06. Principles are aligned with stakeholders</em></p><p>After closely reviewing tho most current and critical user frustration we formed guiding phrases answering the following question:</p><blockquote><strong>If you were to guide someone in the future to make your product better, what would be the rule of thumb you’d give them as guidance?</strong></blockquote><p>The question enabled the team to reframe user frustrations to <strong>guiding phrases.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-Y2879H_q5AdeLzgcB6hw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1HEGKpcJH4KMFc3bakBrHw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1_vK4GwFan2zgOGYjlkbGA.jpeg" /></figure><p>As a result of a one day workshop the team, specifically focusing on points <strong><em>01</em></strong> <strong>and <em>02</em></strong><em>, we </em>were able to define and align on <strong>the first set of unrefined* UX principles:</strong></p><p><strong>01. Know your audience<br></strong>Always design by keeping users in mind and celebrating local knowledge and cultural nuance for users and our teams.</p><p><strong>02. Insights over raw data<br></strong>Always present meaningful information (insights) over raw data for users to make further decisions.</p><p><strong>03. Design for habit<br></strong>Always design self-explanatory products by establishing familiarity through following existing patterns.</p><p><strong>04. Respect user’s time<br></strong>Always lead the users towards completing the task as quickly as possible with easily digestible solutions.</p><p><strong>05. Friends at first insight<br></strong>Always design to empower the users’ sense of ownership of their experience.</p><p><strong>06. Aim for better</strong></p><p>Constantly refine and improve designs in order for them to continue to create the best value for our users.</p><p><em>(*Unrefined UX principles are still a work in progress and are planning to get finalized and refined in Q2 2022)</em></p><h3>Design Focus Day</h3><p>There were still a few things left to be defined before we kicked off the first UX redesign of Vendor Portal features and plugins.</p><p>As mentioned Vendor Portal teams were growing and more and more designers were joining teams and starting collaborating on UX improvements.</p><p>After we got UX Principles ready for designers to use when building the product, we still needed to define a direction a designer should take when they start taking that path.</p><h4>Aligning on Visual Design Language</h4><p>The design team cleared out a day in their calendars for a Design Focus day. We took a day to discuss and develop design directions we would own and use when designing new features.</p><p>The goal of defining Visual Design Language was not only <strong>to align on one shared language, to build a product with clarity and without friction </strong>but also to provide a more cohesive user experience to our users who were using some other already existing products.</p><p>We aligned on a few more rules to a new Design Language with a few designers from another DH Restaurant Partner&#39;s team in a separate design session. They are building different products, but often share the same users as Vendor Portal.</p><p>The result of alignment in multiple sessions was in the first foundations of Visual Design Language to follow:</p><ul><li><strong>We create a consistent experience </strong>by following existing patterns as much as possible</li><li><strong>Our UI is straightforward.</strong> We don’t hide information. We highlight important details. We create a sufficiently guided and supportive experience</li><li><strong>We think of our users. </strong>We ask them. We test. Our visuals show different types of people.</li><li><strong>We keep our designs clean </strong>and simple by using lots of white space and focus.</li><li><strong>We keep our users informed </strong>about what is going on with clarity.</li><li><strong>We always provide relevant and actionable insights</strong> to the vendors</li><li><strong>Anyone can use our application.</strong> Even with slower internet connections and old devices.</li><li><strong>We design for multiple global brands </strong>and support localization.</li><li><strong>We always keep accessibility in mind</strong></li></ul><h3><em>Chardonnay — Vendor Portal Design System: Changing The Strategy &amp; Final Decision</em></h3><p>By defining UX Design Foundations for the ever-growing teams, now we were ready to provide a more autonomous process to help designers AND developers collaborate better.</p><h4>The history</h4><p>Six months prior the Central VP Team proposed to focus on <strong>creating new re-designed portal components and start including them into low maintenance plugins managed by the Central team</strong>.</p><p>All Global Teams agreed it’s time to build a robust Design System because:</p><ul><li>A <strong>new design system</strong> is geared towards taking designers and engineers away from having to reinvent the wheel every time by <strong>keeping things consistent and reusable.</strong></li><li>A new, <strong>modern design language for Vendor Portal</strong>, is determined to <strong>take it away from the early 2000’s design</strong> style.</li><li><strong>Purpose-built </strong>with components and patterns<strong> specifically for Vendor Portal users and use cases.</strong></li><li><strong>It’s designed for use by <em>all</em> Portal web-app products teams </strong>(including NCR, Stores, etc)</li><li>We need a comprehensive and ever-evolving <strong>Figma library driven by user research and the team’s needs</strong></li></ul><p>They even gave it a name: <strong>Chardonnay Design System</strong></p><p>In addition, other Global plugin teams <strong>could also suggest their own solutions and contribute</strong> towards creating components that are heavily used by them.</p><p>This would slowly result in the development of the entire<strong> design system</strong>.</p><p>Although the team was aware of specific constraints of the proposed execution plan, <strong>it</strong> <strong>still appeared there will be more challenges along the way.</strong></p><h4>The Challenge</h4><p>The<strong> plan to roll out component by component for the main central plugins was a considerably sufficient short-term plan</strong> for the central team, but the project was developing too <strong>slowly for it to achieve its objectives in the foreseeable future and serve all global teams in considerable time. <br></strong>It was still lacking a<strong> long term vision and clarity in certain important areas</strong>:</p><ul><li>How will Central and Global teams collaborate in contribution to DS in the future?</li><li>How long will it take to start using the DS?</li><li>There was no clear ownership of the project and a lack of dedicated resources to make fast progress.</li></ul><p>The challenges the team was facing made <strong>the circumstance to build a strong and sustainable design system in a short time, less and less achievable.</strong></p><p>Consequently, the team decided <strong>to take a step back to explore alternative directions </strong>which would potentially get us an effective DS in a very short amount of time.</p><h4><strong>Exploring alternative directions</strong></h4><p>In addition to existing goals, we also wanted to ensure that the design system we use is available to all the teams <strong>much sooner while still being able to improve user experience and address business outcomes at the same time.</strong></p><p>We were considering two directions to achieve that.</p><p><strong>Option 1: Accelerating approach </strong>would require a dedication of all resources to the project for a limited amount of time to achieve fast progress. The risk of this approach was creating a possible bottleneck on other projects and development.</p><p><strong>Option 2: Adopt an existing DS,</strong> <strong>provided by another Delivery Hero team.</strong> We assumed adopting a mature DS, providing all required principles, guidelines, components, and flows, then adding VP specific components and patterns to it by the VP teams, would be the right direction to meet our new expectations and still ensure we are providing the right experience to our end-users.</p><h4>Decision-making map</h4><p>We spoke to<strong> multiple DH teams who had already developed and implemented design systems </strong>or are using some type of frontend libraries and tried to assess each of them against our core expectations:</p><ul><li>Can we <strong>reuse</strong> rather than create a new design system yet again?</li><li>Is the DS mature and <strong>exhaustive </strong>enough to be immediately reusable (Does it already cover most patterns and components we need?)</li><li>Would we get sufficient <strong>support </strong>to use the design system (which teams are using it? What is their collaboration and contribution model? How can we leverage their expertise?)</li><li>Is it easy to use for our <strong>technical </strong>teams? (Does it cover our platform &amp; technologies, is it easy to use, is it lightweight to create a fast page load and navigation)?</li><li>Is it <strong>fit for purpose </strong>for our product, users, and usage context (e.g. desktop-only internal apps, native mobile B2C, B2B, etc)</li><li>Is it immediately <strong>ready to use</strong>? Speed and fit of initial delivery (we want it now)</li><li>Can the DS support <strong>multi-brand </strong>products (e.g. variable brand color and graphics)?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iZVEp7qDTfkWwB3jQDHg3A.jpeg" /><figcaption>Design decision map</figcaption></figure><h4><strong>None of the systems we investigated could provide the expected benefits</strong></h4><p>We had to rule out two systems quickly because two of the teams hadn’t built a standalone DS.</p><p><strong>We investigated more deeply two remaining Design Systems:<br><em>Armor</em> Design System build to accommodate internal DH applications and<br><em>Bento is </em>built for consumer-facing apps,<em><br></em> but found that neither was a good solution for us.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*vn_tODC-6cqDa-bwGim90A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*GnMMGd8XT2hZJFTA8V3eJw.png" /><figcaption>Armor Design System (left), Bento Design System (right)</figcaption></figure><p>While both existing Design Systems <strong>were mature and could be immediately reused, there was no certainty that the different DS owners will be committed to supporting or prioritizing our requirements.</strong></p><p>If we’d have specific needs that fall outside of what the adopted DS can currently support, we will be required to align with their contribution model or DS roadmaps. Dependencies would be introduced as our priorities would need to compete with that of other squads that do not build for VP.</p><p>If not, we may need to build custom components based on the adopted DS. <strong>This results in additional work that negates the benefits of adopting their DS.</strong></p><h4><strong>Final decision: In parallel, an investigation of ways to improve Chardonnay showed significant promises</strong></h4><p><strong>Ready to use:</strong> Most of Vendor Portal was already built on top of <strong>Material-UI by the majority of teams,</strong> an open-source UI component library for React framework. <br>While the Material UI isn’t specifically made for VP type of users, it’s battle-tested, robust, and can be customized, restyled to the extent we need. Using it as a base would provide an acceptable solution very quickly.</p><p>All components missing in the <strong>existing Chardonnay can be picked from Material UI initially, and we can customize them </strong>initially or over time if they are not fit for the purpose.</p><h4><strong>How Do We Do It: </strong>Short-Term Execution Plan</h4><p>To implement the Chardonnay design system and, in the process, to update the visual styling of Vendor Portal <strong>we split the execution plan into a few phases</strong>:</p><p><em>Phase 01</em>: <strong>Chardonnay team will import generic Material UI components</strong> into the Chardonnay library to fill up the gap of missing components within the existing frontend library</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lO0bDVBVvfqVCv1c" /><figcaption>Phase 01</figcaption></figure><p><em>Phase 02: </em><strong>Global teams install the generic Material UI components</strong> from the Chardonnay component library. Where possible, any custom-developed components should be replaced with Material UI components. Teams slowly start using custom components that are going to be more available in time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sk3Z1aDPguhKIR6dWixbAA.png" /><figcaption>Phase 02</figcaption></figure><p><em>Phase 03:</em> <strong>Chardonnay team updates cross-plugin components </strong>from generic Material UI to custom Chardonnay style</p><p>Global teams <strong>work to restyle any plugin-specific custom components</strong> in the Chardonnay visual style</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sc_UEQRp09jc-UK3" /><figcaption>Phase 03</figcaption></figure><p><em>Phase 04: </em>When most of the cross-plugin components are available in Frontend Library and most of the plugin-specific components are customized based on Chardonnay Design Direction,<strong> side nav and app background are switched to white and localized brand colors are implemented.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lxwsuoqUbYmgGKf1" /></figure><h3>Showcasing New Designs</h3><p>While Design Team was still finalizing the last bits of new UX Foundations, <em>Reporting &amp; Insights team</em> already started incorporating the new design directions and a new design library into the process of revamping some of the Vendor Portal sections that needed the most urgent attention.</p><p>There is a lot to be demonstrated about the journey of achieving all the UX improvements showcased below. <br>But for now, let’s just focus on how the new UX design foundations, described in this story, helped us grow from a place like this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hHQTkh0P3aa0J6OX8PMlMA.png" /><figcaption>The old Reporting section</figcaption></figure><p>…into this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jOS7qYn2_QlRcwRgmz5bgQ.png" /></figure><p>I can now say the process of creating all of the new designs wouldn’t be as easy and efficient as it was because of the new UX foundations at hand:</p><ul><li>We had <strong>guiding phrases to follow </strong>when we were making critical design decisions</li><li>We <strong>were able to keep the consistency across different sections</strong> even in times when lots of new members joined newly created teams</li><li>We were able <strong>to stay focused</strong> on what’s important the most — <strong>the user and their needs</strong></li><li>We were able to <strong>keep the design clean and straightforward</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IEVDiGioghTtbuOZK3xpVw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZozqokRnU-XXR5QtzYTbhw.png" /></figure><p>The process of completing improvements to Vendor Portal UX Design is, by this day, still in progress. The same process is in place while maturing and evangelising UX Principles and Chardonnay — the design system. This story wants to simply demonstrate how the comprehensive design process can solve the future aspects of not only the ways how the product shall develop, but also how the collaboration between designers, developers, and stakeholders can significantly improve — all thanks to the simple foundation they followed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdb893143f0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mjam Assistant —a customized selection of your favorite restaurants in food delivery app]]></title>
            <link>https://katarinapetrov.medium.com/mjam-assistant-a-customized-selection-of-your-favorite-restaurants-in-food-delivery-app-52d89b49fdb8?source=rss-c872f375dbbe------2</link>
            <guid isPermaLink="false">https://medium.com/p/52d89b49fdb8</guid>
            <dc:creator><![CDATA[Katarina Petrov]]></dc:creator>
            <pubDate>Sun, 14 Feb 2021 15:44:51 GMT</pubDate>
            <atom:updated>2022-02-05T10:19:33.567Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Mjam Assistant —a customized selection view of your favorite restaurants in food delivery app</h3><p><em>(Berlin, 2018–2019)</em><br>All existing food delivery platforms offer a kind of restaurant discovery, customized to customers&#39; preferences. It can be for a specific time of the day, for example, lunchtime, so users can browse through affordable lunch offers from restaurants nearby. On other occasions, they can choose from a list of their recent orders, a favorite pizza from well know pizzeria. Or from a list of restaurants that don’t charge delivery fees.<br>Rarely do apps use complex algorithms to “remember” users’ preferences and display offers tailored to their taste and previous search.</p><p>When thinking of a typical situation when a person or a group choose to order food online, the usual ordering scenario would probably be somewhat like this:</p><p>A: Hey I am hungry.</p><p>B: Me too.</p><p>A: What do you feel like?</p><p>B: Pasta, you?</p><p>A: Pasta is ok, maybe pizza too, but please something fast.</p><p>B: Ok, but I don’t want anything shitty.</p><p>A: Well, how much money do we have?</p><p>B: It is ok, I have PayPal, and we can treat ourselves.</p><p>A: Ok. I can pick something on my way to work.</p><p>B: No problem, I will order …. Yay, our food is at the door in 20!</p><p><strong>But … it’s not always as easy as it looks…</strong></p><h3>The Challenge &amp; Discovery</h3><p>In several usability tests, we conducted with end-users of the Austrian food delivery platform, Mjam (in Vienna, 2017–2019), and from quantitative research, we observed repetitive usability issues and some troubling behaviors, when it came to <strong>the restaurant discovery phase</strong>, especially with new users.</p><p>Let’s have a look at some repetitive insights from the data we gathered:</p><ol><li>Users <strong>spend too much time ordering</strong> their food. Browsing the restaurant list, going back and forth to the menu page, took them <strong>in average 10 min</strong></li><li>They often complained about seeing <strong>too many restaurants not relevant to them.</strong></li><li><strong>On average 32%</strong> of app users who convert <strong>see 9 restaurants before making a decision</strong></li><li><strong>Only 8,22% </strong>of app users use <strong>filters to narrow down the selection</strong>, but <strong>from those who use them, 89% select</strong> the restaurant from the results.</li><li>Only <strong>12% </strong>of app users use <strong>sorting</strong>, but <strong>from those who use it 89% select </strong>the restaurant from the results</li><li><strong>52% trust the restaurants</strong> offered when <strong>filtered by super cuisine</strong></li></ol><p>The conclusion was when <strong>users choose to order the food they often find it very hard to find and choose the restaurant they like from the restaurant listing</strong>. They spend a lot of time browsing through the list and checking the menu offers on the menu page, repeating the process multiple times.</p><p>But from a few of those who choose to use the functionalities <strong>such as filters and sorting</strong>, the majority at the end selected the restaurant to order from, from <strong>the suggested list</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ScvBEwNzqdIS-Fr26zT0Dw.png" /></figure><h3>Defining pain points</h3><p>There were <strong>3 main pain points </strong>users had within the discovery process we could identify:</p><ol><li>There are<strong> too many restaurants on the list,</strong> most of them not tailored to customers preferences</li><li>It takes <strong>too much time</strong> to find the right restaurant on the list</li><li>There is <strong>no helpful way to discover restaurants similar to what</strong> they like</li></ol><h3>Hypothesis</h3><p>After the conclusion we believed we had a solution in our UX sleeve we wanted to test:</p><p>We assumed:</p><ul><li>If we present <strong>filters and available cuisines in a more prominent and more beneficial </strong>way, more of the new users, especially new, will <strong>find the food they like easier and faste</strong>r</li><li><strong>If customers are able to save their preferences so they can easily find restaurants matching their preferences next time, </strong>retention &amp; reorder rate could increase</li><li>If a <strong>limited number of restaurants based on their preferences </strong>is presented to the users,<strong> time to order will decrease and CVR will increase</strong></li><li>The number of restaurants compared in the discovery process will decrease when presenting <strong>a limited number of restaurants based on user’s preferences</strong></li><li><strong>A number of new restaurants</strong> will be discovered in a curated list of restaurants, based on given preferences</li><li><strong>USP</strong> → we will be able to convert more new users with the new flow because the food discovery is faster and better than with the competition.</li></ul><h3>Ideation and validation 0.1 — Chatbot</h3><p>As a result of the first ideation on finding the right solutions, we were experimenting with the adoption of a <strong>chatbot pattern</strong>. We thought it could bring the value of a friendly and interactive experience to get valuable information about users’ preferences when picking the right restaurant. The collected information would be used to generate a curated list of restaurants at the end of the flow.</p><p>The solution was tested on a group of Mjam new and recurring users in a usability test in Vienna. If the concept would get positive feedback, the plan was first to create<strong> an onboarding version for new users as MVP</strong> as a next step.</p><h4><strong>The main goal</strong> of the research was to gather <strong>feedback from users after they interact with the chatbot prototype and to understand if the idea of narrowing down the selection of restaurants after the user preferences were provided provides value to them.</strong></h4><p>While interacting with the prototype, they were asked questions regarding their food preferences, and based on their answers they were provided a narrow selection of the restaurants as a result at the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*9rsfn1JgqkjHoe9W48qJDg.gif" /></figure><h4>Conclusion</h4><p>Although all of the users really liked the concept and friendly chatbot experience, <strong>the length of the process was an issue for all of them.</strong></p><p>We immediately responded and presented an iteration of the concept to the second group of users the next day. A friendly but lengthy chatbot concept was replaced with a so-called<strong> vending machine concept:</strong> all of the preferences were accessible on one screen without any additional steps needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S31_SED0ViUSB_7eno7m-Q.png" /></figure><p>Users&#39; reactions to the updated version <strong>were positive</strong>. They responded the interface was intuitive, especially due to the simple interface and included visual elements.</p><p>Although the reaction to the new onboarding experience was overall positive, most of the users’ were<strong> less enthusiastic about the types of food preferences they had to choose from</strong>. Some of them felt there was not enough variety, the others just felt they are not relevant to them.</p><h3>User research 0.2 — Food preferences</h3><p>As a next step taken, we needed to redefine the types of food preferences that bring users the most value after being chosen.</p><p>In the current app, the filtering option was limited. Users could filter <strong>by type of cuisine, delivery cost, minimum order value</strong> — there was not much opportunity for curating the selection of restaurants.</p><p><strong>It was important to learn what are the most important choices users think about when they are ordering food.</strong></p><p>We already knew the most common, high-level food preferences when choosing the right food were:</p><p><em>Cuisine &amp; Food type (&amp; Dish)</em></p><p><em>Estimated delivery time</em></p><p><em>Food Quality</em></p><p><em>Price</em></p><p><em>Payment options</em></p><p><em>Delivery options</em></p><p>Since many users expressed they’d like to see more variety in that list, we added a few more such as<em> food type, menu category, ingredients, taste, and preparation style </em>and conducted <strong>a card sorting session.</strong></p><p>From the existing data we had, we could easily add the most popular cuisines and top-selling dishes to a new individual group — <em>Food Type group</em>.</p><p>The rest of the groups were a combination of data from restaurants’ menus and competitor’s menus analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ZK05uDyu-ZQ3D7Q5OD1SA.jpeg" /></figure><p>The goal was to learn what comes first to users’ minds when they start<strong> the discovery process when ordering food</strong>. <br>Understanding <strong>which category of the preferences provided is most important</strong> to them would help us <strong>build a more accurate step-by-step curating process and better selection results.</strong></p><p>The results showed most of the users would take this path below to narrow down their restaurant selection (<em>1-most important, 8-least important</em>):</p><p>1 — Cuisine</p><p>2 — Food Type</p><p>3— Menu category</p><p>4 — Time / Budget</p><p>5 — Menu category</p><p>6 — Ingredients</p><p>7 — Taste</p><p>8 — Preparation style</p><p>We had enough information to proceed to the next step —<strong> a decision tree.</strong></p><h3>Ideation — Bubble tree</h3><p>I believe some of the readers of this article might remember Apple’s Music onboarding. Do you remember that red and black bubble interface which enabled the user to enter their music preferences and save them?</p><p>As user was selecting their favorite genre and producers, they’d see more and more detailed preference suggestions coming in. The suggestions got more and more specific towards the end so that the final results were a very precise list of suggested artists and albums, tailored to users’ tastes.</p><p>Yes, you’re right … That was another existing pattern we wanted to recycle and test with our users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8MN85A0IWN88jaaaE9gjqw.png" /><figcaption>Apple Music app</figcaption></figure><p>As a first step, we created <strong>a decision tree</strong>, based on the results of <strong>the card sorting session</strong>, as a foundation of the new user flow.</p><p>The user would need to choose<strong> the type of cuisine first, which will trigger and display matching suggestions for the dietary choice as a next step, which would then reveal matching occasions and taste suggestions, followed and finished by the meal types…. We named the new feature Mjam Assistant. ❤</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pRstB0rvPTV9_0g05tQbVw.png" /><figcaption>First prototype with a new decision tree as a foundation for the user flow</figcaption></figure><p>I know it sounds a bit complicated. We were worried too. :)</p><h4>The challenge</h4><p>Besides. as estimated, very complex development of the proposed feature, another essential component was missing — <strong>proper dish tagging </strong>(eg. the dish on a restaurant menu is <strong>spicy and vegan</strong>), which, unfortunately, didn’t exist on our platform at the time. Due to the constraints, we learned about we needed to abort the Bubble UX initiative :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7IsZh_09dHE5VPOxEaQ3rA.png" /></figure><h4>Moving forward — Mjam Assistant MVP</h4><p>Nevertheless, unfavorable constraints didn’t prevent us from proceeding with iteration on the initiative and planning a new <strong>MVP version for the Assistant</strong>.</p><p>As we wanted to test the feature as soon as possible with less possible effort, we decided we will build Assitant with a simplified version of the preference flow.</p><p><strong>We provided a limited choice of preferences, created by the existing filters, with an additional <em>Save Filters</em> functionality in a new Onboarding user flow. <br>We’d introduced the new MVP only to users who use Mjam app for the first time. <br>After they complete the Onboarding flow, the preferences they’ve selected would be saved on Meins (<em>My Mjam)</em> page with a list of restaurants filtered out in the onboarding flow.</strong></p><p>The plan was to measure<strong> the number of users using the new functionality </strong>and<strong> the number of users selecting the restaurants from a new <em>Meins</em> page after they come back the next time.</strong></p><h3>User flow and UI design</h3><p>When users first open the Mjam app and enter their delivery address, <strong>they would trigger the Assistant</strong>. <br>Within the <strong>next 3 simple onboarding steps</strong>, they were asked to <strong>select their preferred cuisines and narrow down the selection by applying a few more filters in the next step</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HrKkmRwYAMvcMrlSxcnpBA.png" /><figcaption>Mjam Assistant MVP</figcaption></figure><p>All selected preferences were then saved in<strong> a new app section called <em>Meins (My Mjam)</em></strong>. As a result of saving their preferences, they could now see <strong>the top 10 matching restaurants on the list</strong>. They <strong>could always refine</strong> their saved preferences by easy access to the Assistant feature from that page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zJaeS1kWMkd9A4moKG34OQ.png" /><figcaption>Meins Section</figcaption></figure><p><em>After the launch of MVP we were super excited by the execution of the experiment and we started collecting the eagerly awaited data.</em></p><p>Unfortunately, the first GA numbers were not as encouraging as anticipated.</p><p>Although the experiment showed <strong>positive results across the whole funnel</strong> (users visiting a menu page improved by 2.83%, Users adding something to their cart improved by 3.5%, users placing an order improved by 3.6%), <strong>~70% of customers</strong> <strong>didn’t complete the assistant first step.</strong></p><p>There was a bit more <strong>encouraging data from analyzing those users who completed the Assistant flow</strong>. They seem to be more committed to placing an order and:</p><ul><li><strong>93% visit a menu</strong> (vs 70% on average)</li><li><strong>86% add the item to the cart </strong>(vs 60% on average)</li><li><strong>83% go to checkout</strong> (vs 75% on average)</li></ul><p>There seemed to be <strong>an improvement in engagement</strong> as expected:</p><ul><li><strong>95% of users</strong> who used the assistant come back to it at least once again.</li><li><strong>60% of those customers place an order</strong> (vs 35% on normal listing page)</li></ul><p>Since the results were more positive for the users who actually used the feature we decided to take a <strong>few more steps towards improving the Assistant experience:</strong></p><ul><li>Run user interviews to get <strong>more qualitative input</strong></li><li><strong>Promote Assistant</strong> to increase the discovery</li><li>Once the <strong>food labeling project</strong> is established; update the assistant to include extra information: allergies, spicy, vegetarian, vegan…etc.</li></ul><h3>Final step — Usability test on the live feature</h3><p>As one of the most concerning insights from the qualitative data was <strong><em>~70% of customers</em></strong><em> </em><strong><em>didn’t complete the assistant first step</em>, we wanted to understand why?</strong></p><p>In the following <strong>remote usability test with Mjam users </strong>we were focused on a few<strong> main topics </strong>below<strong>:</strong></p><ul><li>Why<strong> do most of the users skip</strong> the Assistant onboarding?</li><li>How<strong> they perceive saved filters</strong>? Do they notice this is related to the choice they made in Assistant?</li><li>Are the <strong>results of onboarding expected and relevant</strong>?</li><li>Meins: <strong>why more users don’t interact </strong>with the feature in Meins?</li><li>How <strong>can we increase engagement</strong>?</li><li><strong>Where would they look for</strong> the Assistant in the app?</li><li>Why more users<strong> don’t save their preferences</strong>?</li></ul><h4>The top insight we gathered from the research were:</h4><ol><li>All users are aware of Assistant <strong>but no one is using it actively</strong></li><li>They <strong>are not using</strong> Assistant because they <strong>don’t see a real benefit from it</strong> since <strong>it’s using the same filters</strong> as the ones available already available on the restaurant listing page</li><li>They would consider using assistant if filter selection would be based on more detailed/refined preferences such as <strong>dish level selection, dietary preferences, recommendations/popularity, new/upcoming, etc.</strong></li><li><strong>No bigger issues with UI design</strong></li></ol><h3>Conclusion</h3><p>Mjam Assistant as an <strong>MVP gave us a lot of insight and direction for the future development of the feature</strong>. It was clear that the feature would have a great value to all types of users<strong> if we provide a more refined set of preferences they could select from</strong>. The feature would be beneficial for the new users to <strong>help them discover restaurants they like faster</strong>, as well as for returning users to always return<strong> to their saved list of preferred types of restaurants</strong>.</p><p>But …. Unfortunately, before we could take any further steps to improve and complete the feature, some higher business decisions took place, and Mjam delivery platform couldn’t exist anymore after 2020. <br>Therefore a fully developed Mjam Assistant never saw a day of light. :(</p><p>Nevertheless, Mjam Assistant stays as one of my favorite UX projects I was working on with my team.</p><p><em>We achieved all of this together with the Mjam Product team, so thank you: Hesham, Antonia, Ola, Christian, and of course the amazing Mjam Tech team.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52d89b49fdb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving pick-up on food delivery platform, as the only option of business for restaurants in the…]]></title>
            <link>https://katarinapetrov.medium.com/improving-pick-up-on-food-delivery-platform-as-the-only-option-of-business-for-restaurants-in-the-932eefd2b9a0?source=rss-c872f375dbbe------2</link>
            <guid isPermaLink="false">https://medium.com/p/932eefd2b9a0</guid>
            <dc:creator><![CDATA[Katarina Petrov]]></dc:creator>
            <pubDate>Sat, 30 Jan 2021 19:58:36 GMT</pubDate>
            <atom:updated>2021-02-01T09:28:04.583Z</atom:updated>
            <content:encoded><![CDATA[<h3>Improving pick-up feature on a food delivery platform, as one of the few options of business for restaurants in the early lockdown</h3><p>During the first Corona crisis in March 2020, the Austrian government restricted the opening times of restaurants and even closed them for the public. Delivery — and possibly pick-up — was the main way of doing business for restaurants for an undefined period of time.</p><h3>The challenge &amp; discovery</h3><p>At Mjam, a food delivery platform in Austria, we were aware the pick-up experience in Mjam mobile app was not the best.</p><p>When a user selected the pick-up option there wasn’t any significant feedback on the screen. Restaurant tiles on the list were updated but nothing else really changed. Most of the time users didn’t realize they selected pick-up options or they forgot about it while browsing further.</p><p>Due to evolving lockdown situation, we wanted to provide better pick-up service for restaurants to help them survive the difficult times</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*OOCHdUWRtAvKD2b0sMDktw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*PnrjEkwBgH5emkExaLk0jw.png" /><figcaption>Two Restaurant list screens, representing unselected and selected Pick-up (Abholung) option.</figcaption></figure><h3>Insights from the data</h3><p>In late 2019 we already conducted qualitative and quantitative research on the pick-up topic. The qualitative research was combined from a usability test (Vienna, Austria) and a survey, both on Mjam website experience with users that had ordered pick-up before. The research also included an extensive competitor analysis, which also helped us take some of the right directions.</p><h4>The main additional insight we gathered were:</h4><ul><li><strong>The pick-up option</strong> can be hard to find</li><li><strong>Sorting by distance</strong> and comparing distances of restaurants should be easier</li><li><strong>Preparation time</strong> is still called ‘delivery time’</li><li>Wish the predicted <strong>pick-up time</strong> was more <strong>accurate</strong></li><li>Users often copied restaurants address to Google to get the direction</li><li>Users think that it’s most important that pick-up is <strong>easy to order, the order is ready when expected and </strong>there are <strong>no delivery / additional costs</strong> involved</li></ul><h4><strong>Google Analytics data showed</strong>:</h4><ul><li>Pick-up orders make up<strong> less than 1%</strong> of all our orders</li><li>Most pick-up orders <strong>come from apps</strong>, by far (Jan 2020: 2400 Apps / 100 Web)</li></ul><h3>User needs</h3><p>From our research above we identified these 3 main pain points:</p><ol><li><strong>Pick-up mode</strong> is confusing (mode selection, prep time, a distance of restaurant)</li><li><strong>Directions</strong> to restaurant</li><li><strong>Pick-up time is </strong>relevant and required information</li></ol><h3>Problem statement</h3><p>We could see the main problems were in:</p><ol><li><strong>Awareness and discovery<br></strong>Users had a difficult time <strong>finding the switching option</strong>, therefore entrance to pick-up mode was limited.</li><li><strong>Usability when selecting the restaurant<br></strong>When the restaurant was selected there was <strong>no way to see the distance</strong> between the user’s location and the restaurant or<strong> no sorting by distance</strong> option.<br>Users were <strong>unable to explore nearby restaurants</strong> or see their locations.<br>When visited the restaurant’s page after selected the pick-up option, there was <strong>no relevant information about the pick-up </strong>time and the distance to the restaurant.</li><li><strong>Clarity during checkout</strong></li><li><strong>Transparency and helpful information during order tracking</strong></li></ol><h3>Hypothesis &amp; Ideation</h3><p>According to other objectives on our Product plan and based on criteria of feasibility and viability we decided to focus on the first two problems first.</p><p><strong>We believed if we increase awareness and discovery of pick-up options by adding a better visual indication of the features and make the information about the pick-up more transparent throughout the journey, users would use the pick-up option more and therefore help the restaurant on our platform with their business.</strong></p><p>Within the short <strong>HMW ideation session</strong> we came up with a few potential improvements:</p><ol><li>Prominent switch for pick-up and delivery on RLP</li><li>Show a map with close-by restaurants</li><li>Sort restaurants by distance when pick-up is selected</li><li>Show distance to the restaurant on restaurant tile instead of the delivery fee and MOV on RLP tile and MP</li><li>Restaurant info should always show 1) address, 2) walking distance and 3) preparation time</li><li>Show info that order is pick-up (including address and distance) on Cart and Checkout</li></ol><p>In order to evaluate if this hypothesis is correct, we wanted to conduct an A/B test where part of our users will be able to see the improvements.</p><h3>Design</h3><p>After defining most potential solutions we created the first sketches and lo-fi wireframes and due to lockdown being on a full scale, tested them internally with colleagues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V0vIDNC28xNB7VMtewv3kQ.png" /><figcaption>Hand-drawn sketches showing first drafts of the map and more transparent displaying of information about the pick-up.</figcaption></figure><p>After a few adjustments, we created visual UI designs and a full prototype in Invision.</p><h3>Main improvements</h3><h4>1. Adding stronger visual indication when users select the pick-up option</h4><p>On the usability test, we understood users didn’t get enough visual feedback when they switched to pick-up mode, so usually, they were left confused, sometimes they didn’t realize they are already in the pick-up mode.</p><p>To solve this problem we decided to add an image generated from an actual map of users&#39; surroundings, placed above the restaurant list.</p><p>We assumed the visual indication of the map would provide clear information about the restaurants nearby and how can they reach them.</p><p><em>Later on, we conducted another experiment showing the map to all users, assuming the map would probably benefit all of them, not only the one who chose the pick-up option</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GFzcorcsqcjr_3Ke_I4vvw.png" /></figure><h4>2. Introducing an interactive map for a better overview of restaurants nearby</h4><p>The biggest improvement of the pick-up experience was adding the interactive map.</p><p>The interactive map provides our users to have a clear and friendly overview of the restaurants in their surroundings and the number of them. They can easily assess which one is the closest and go for it first.</p><p>Users were often mentioned they miss the map and google for restaurants to get the information about the distance instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R_-GBLBYQ5KzsjNVo0ZWPw.png" /></figure><h4>3. Simplified restaurant discovery</h4><p>For an easier restaurant discovery, we decided to use a pattern we observed in other applications during our competitor&#39;s analysis.</p><p>By selecting a dot on the map, which represents a single restaurant the view, users also get to see the fastest route to the restaurant.</p><p>At the bottom of the map, the restaurant information pops up, which provides the user an additional navigation option at the same time.</p><p>Information is now adapted to pick-up showing the distance and approximate time for the pick-up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*br-wL1s5w-FNDYBuN1aquw.png" /></figure><h4>Information about the pick-up is now transparent at every step of the journey</h4><p>Users were often confused about the clarity of how are they getting the food. Since the only indication of switching to pick-up mode was at the beginning of the journey. They tend to forget they selected it or they simply forgot after falling into browsing mode.</p><p>To solve that problem we added a clear indication about ht pick-up at every step of the journey: on the restaurant page, they could see the distance to the restaurant, pick-up time, and restaurant address in the header of the page. The same info was placed to the cart and the checkout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2JdodjdDFHqRxrDzJTet0Q.png" /></figure><h3>Final result</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FynDw7XYOtkc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DynDw7XYOtkc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FynDw7XYOtkc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c9783ffc8be727e06a6c5cfac9193aa5/href">https://medium.com/media/c9783ffc8be727e06a6c5cfac9193aa5/href</a></iframe><p><em>The changes in pick-up experience soon improved the numbers as expected</em></p><h4>Some of the first GA numbers showed:</h4><ul><li>Interest in the pick-up has <strong>grown by 250%</strong> compared to before the lockdown</li><li>Pickup orders<strong> grew by 133% </strong>compared to the best day before lockdown.</li><li>Adding the Map on Apps seems to have<strong> a positive impact on CVR</strong></li></ul><h3>Usability test on a live app and post-pick-up experience</h3><p>Additionally, we wanted to see how the improvements impacted the user experience when choosing the pick-up itself, so we conducted <strong>a remote user test on the live app</strong> and a <strong>post-experience test </strong>on Mjam users in Austria.</p><h4>Remote usability test</h4><p>For this test we set up remote usability tests for the first time, using tools like <a href="https://calendly.com/">Calendly</a>, <a href="https://zoom.us/">Zoom, </a>and very detailed ‘how to set up your devices’ guidelines.</p><p>We tested the pick-up feature on the live app, without placing the actual order.</p><p><strong>The goal</strong> of the test was to see if our hypothesis was correct and if the recent improvements made the feature more friendly and easier to use.</p><p><strong>The top 5 learning from the test were:</strong></p><ul><li>None of the users actually ever uses the pick-up</li><li>All users found the ‘Abholen’ button on the restaurant list right away</li><li>The map was clear and easy to navigate</li><li>Deliver vs. Pickup mode on RLP is clear, elsewhere not 100%</li><li>Some users want to see the restaurant located on the menu page</li></ul><h4>Post-pick-up experience</h4><p>For this type of test, we invited 4 Mjam users to order for pick-up and share their insights with us in a remote interview.</p><p><strong>The top 5 learnings from them were:</strong></p><ul><li>time showing on after order page is confusing, more users said it is not reliable</li><li>users like pickup as they can “control” when the food will be available for them, as they don’t need to wait for the delivery person to despatch multiple meals</li><li>they still select their restaurant by browsing through the list and not by choosing the interactive map</li><li>restaurant tiles in <strong>delivery mode could </strong>have a flag saying that they do <strong>pick-up</strong> also</li><li>users choose a delivery method in different places (address input, button on RLP, cart)</li></ul><h3>Further initiatives for improvement</h3><p>After looking in the gathered data it was clear that the overall experience was <strong>significantly improved</strong>. The design made the feature friendlier and easier to use.</p><p>More users were choosing pick-up as for of getting their food, but to be honest, a lot of that happened due to the restaurants closed for dine-in areas.</p><p>We also identified some small areas of improvement and to experiment on.</p><p>The worrying part was<strong> pick-up didn’t really <em>pick up</em> on a scale we hoped</strong>.</p><p>We still believed there is <strong>a lot more potential to it</strong>. In hope of increasing the share of pick-up orders and user frequency, we later had a few more brainstorm sessions. The main focus of the sessions was <strong>what moving us towards</strong> making pick-up a success,<strong> what is holding us back</strong> and <strong>how might we improve</strong> in these challenges.</p><p>But …. that is whole another topic to write about :)</p><p>Maybe in a new post sometime very soon.</p><p><em>I couldn’t achieve anything of the above without my dearest and the best Mjam Product team members, so thank you: Hesham, Antonia, Ola, Christian, and of course the amazing Mjam Tech team.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=932eefd2b9a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>