Food.ee
Product / UX
My Role: Senior Product Designer
Responsibilities: • User Interviews • Usability Testing • UI Design • Content Strategy
Context
Process and Discovery
We created our personas with two key principles in mind: keep them simple, and focus on roles rather than personality traits. We wanted to capture what users needed from the product — not who they were as individuals.
One thing that quickly became clear was the wide range of motivators. For some, they cared most about ordering and enjoying meals. Others were operational – focused on tracking usage and reporting performance.
Recognizing these differences helped us shape our communication, features, and support based on who we were talking to. It also ensured that all teams at Foodee stay aligned on what each user cared about most.



Foodee workflows were complex, and the full experience extended well beyond the product. Journey maps captured the key stages our users followed and highlighted opportunities and showed how the multi-stage process unfolds.
It uncovered opportunities for the service, and also showed the product team how we could keep users positively engaged during onboarding.

Solutions
The existing signup flow was adding noticeable friction and produced inconsistent results. In turn, these incomplete signup details created a lot of extra work for Foodee teams to correct.

Our most valuable features for large accounts were rarely discovered by users. If we expected to reduce the workload for our internal teams, we needed to make sure these features were found.
Our goal was to be clear, but not overwhelming, using subtle calls to action in order to showcase key tasks such as inviting their team, creating recurring meals, and confirming their orders right on the dashboard.
Our users wanted to explore, but our existing meal setup flow demanded too much information before you could see any restaurants. A logical approach in theory, but it was proving cumbersome and frustrating for users.

The only detail we absolutely needed was an address – everything else could be added progressively which would then narrow down their results. This gave our users much more confidence that we were showing them the entire set of restaurants.
Outcomes
What was most interesting is that like our users, our internal teams had diverse motivations as well. The Sales team was hesitant to change their onboarding process, the Development team favored (logical) rigid requirements over (illogical) user behaviour, and leadership didn't see the value in improving anything that was already built.
Getting buy-in across our stakeholders was an ongoing effort, which taught me a lot about how to present ideas that resonate with different audiences based on what they are hoping to achieve.