Prodict design for Melio Payments

Melio’s mission is to help small business manage their payouts by providing a smart B2B payment solution tailor-made for their needs. Melio's digital accounts payable and receivable dashboard provides a single, integrated tool that allows small businesses to transfer and receive payments quickly and easily, giving oversight and control over cash flow, eliminating late payment costs, and saving time.
As a lead product designer of the company's main product in it’s early, market-fit stage, I had the oppurtunity to structure the initial use journey (Onboarding & Progressive onboarding flows) and core features such a Single payment and Batch payments flows. 

Case studies:

Riskified website 2019 view site

Visual concept & data visualization for Riskified’s new website. The design challenge was to exaplin multiple complex processes with a few easy to understand visuals using a consistent and minimalistic visual language. Created in coloboration with Riskified’s design team.

Riskified is a B2B fraud-solution company in the eCommerce field. Riskified uses behavioral analysis, elastic linking, proxy detection and machine learning to detect and prevent fraud.

Solution-overview page

Data visualization design & animations

Bizzabo Networking Solution

Bizzabo is an all-in-one event-planning solution designed to help organizers create business events of all types, including in-person, virtual, and hybrid events. 

The Event Experience OS is an open platform that allows event experience leaders to manage events, engage audiences, activate communities, and deliver powerful business outcomes. The new platform is aimed at restoring aspects of human interaction and networking lost in the translation to the virtual world after Covid19.

Bizzabo’s Networking solution

The scheduling tool designed to coordinate and support virtual, hybrid, and in-person meetings My goal was to streamline the scheduling process while accommodating attendees' challenges including event agendas, different time zones, and personal availability preferences. There were also mental challenges to overcome, such as the motivation gap between meeting organizers and attendees. In order to accomplish that, I structured a user journey that takes attendees through a non-binding exploration of their networking goals and fields of interests. Attendees can then bridge the virtual gap and reach out in order to connect.

Product OKR

Enable each event attendee to attain their individual, professional and personal networking goals, when communicating and connecting with people, at every event they attend. In addition, help attendees to manage and deepens those connections before, during and after the event.

Products suite 

1:1 chat Attendees can easily search or filter to find peers to connect with through 1:1 messages on The Venue.

Real-time Meetings A real-time video meeting to recreate that feeling of spontaneously bumping into someone new at an in-person event.

Scheduled Meetings Attendees are able to set their calendar availability during the event and use AI-driven scheduling to seamlessly book scheduled 1:1 meetings with other event attendees.

1:1 Chat and Meeting solutions 

Schedule meeting solution

Discovery process and product vision 

Deco payments User app

Deco is a B2C payment solution, that provides legitimate customers a way to pay for their purchase on spot, in case that their card was denied by the bank. After the order is submitted, the users has 2 weeks to login to the user-app, apply a payment method, and pay for their orders. 

Deco offers two possible payment flows: “Schedule payment” and “Installments”. This app is a mini-app, due to the fact that in most cases there the user visit it only once, when they sumbit the payment.

Team: B2C Product manager, PMM, Design
My role: Lead designer, full product ownership

a. User journy

b. Product evolution

CASE STUDY Establishing Deco “One pager” app

Business challenge

As the product evolved and new solutions were launched, we required to re-think the user app so it can serve different customers that has completed different flows (Schedule payment / Installment ). Also, there was an inefficient in-app payment proccess that we wanted to simlplify and improve.

The preliminary work took place on several levels:


In addition to user’s feedback after the checkout event,  We partnered with a big fashion retailer and conducted an online survey that was sent to users who used our product during their purchase. Users were asked questions such as: Are the business offer and terms of service clear? Is the experience smooth? Would you use Deco again in the future?

We sent it also to default users (=who did not returned payment), along with “good” users that paid us back for their purchase.My goal was to characterize the users and to understand whether they are “opportunistic”- single time users that were caught up in the product by chance, or do they have potential for being returning users that will use our product on several occasions.

C. User Survey-  quotes


Survey takeaways

  • Customer lack of familiarity with our brand raises trust concerns
  • Customers are overwhelmed with accounts and don't want to use another service
  • Urgency moment is a big factor in user’s decision
  • Not all customers understand the product flow


I mapped all the possible flows & entry points to the product, including emails. The goal was to shed light on the key action the user is asking to perform while they entering the app.

D. User lifecycle 


  1. Deco user portal is unusual; the way the flow is structured, users basically don’t need to go inside it in case that everything goes well. (“Happy flow”)

  2. The urgency to access the app will only occur when something in the process of a specific order fails

We came into a conclusion in which the main view of the app should be a single order view i.e the current user order that is currently processing 

Schedule payment flow

Installments flow

Language & styleguide


Riskified web app

Riskified’s customers and app users are e-commerce merchants. The app provides them full transparency on Riskified’s decisions over their orders as well as supplementary data on segments of interest.
There are two types of end-users:

1. Administrators
They want to get a general overview on the orders transferred to Riskified, approval rates and decline reasons for each order.

These users mostly use the dashboard view.

2. Customer support
They are in contact with the merchant’s customers and their job is to perform actions related to specific orders such as submitting chargebacks, filing disputes over Riskified’s decisons and so on. These users are more exposed to the “Orders” tab which allows access to a specific order’s view and actions related to it.

1/ Dashboard tab

2/ Orders tab

3/ Declined-order view

Case study: Post decline flow re-design

Riskified protects e-commerce merchants against fraud by approving safe orders and declining fraudulent and risky orders. Merchants can view these actions with Riskified’s web app. “Post decline flow” is an in-app action that allows merchants to file a request for reexamination of a declined order if the merchant believes it to be non-fraudulent.

There were some factors that made us to re-think current flow design and optimise it:

  1. New functional requirement - for each merchant:
    such as “No contact” scenario, and an “Override decision” flag
  2. Custom configuration for each merchant:
    not all users have access to the same flow or have the
    same mandatory sections as others. The flow needs to be customised in an easier way.
  3. Current UX/UI is not appropriate- Horizontal form is not intuitive and requires  high maintenance and optimisation for each user.

  • What are the users’ pain points?
    • Frequently used actions are complicated to perform
    • Want more self-service solutions instead of contacting support

Main users workflow: What is the user flow until he arrives to the current task and after he finishes it?

    1. Call center agent - After / during the communication with the customer, agent goes to the webapp,
      searches for the order and opens the acti
      1. 2. Fraud agent - Manual review queue Reviews order Finds new information Opens the PDF action

    • Per each functionality/task performed in UI:
      • Frequency of each feature in the flow - Daily
      • Cost of mistakes - Contact information and decline override are critical
      • Relative Importance and Hierarchy - This is the most “important” action in the webapp

    Key Success Factors:
      • Reduce number of tickets to support
      • Ability to deprecate the old feature
      • Ability to customize the form
      • Increase usage

    Design summary:
    1. I redesigned the action to be a sectioned vertical flow, that is easy to be customized per user.
    2. The from is fixed-sized, with a sticky footer.
    3. I exported the “Override decision” checkbox to be positioned on the footer so in will be constantly revealed. That in porpuse to avoid misunderstandings in cases in which merchant have a default choice active (on/off), and only two mandatory inline sections. (In othe words: So they won’t click the “Sumbit” btn before the went threw all the information provided.)
    Old design

    New design