Build a combined Track and Submit flow on the FE, so we can use it to run our very first A/B test.

[anmurali]

Problem: The vast majority of signups are unengaged. Paid adoption from top or bottom up leads only happens when users are engaged with the product and derive value from it.

Hypothesis: The time it takes for a person to make a decision increases with the number and complexity of choices available. Presenting users with too many options can lead to decision fatigue, making the user experience overwhelming and less efficient.

Test: The Global Create menu is by far the most obvious and accessible option a new user explores to do something. Let’s make it a smaller, focused list that allows a user to pick one out of a very small set of choices. Instead of asking the user to decide between tracking and submitting an expense, let’s present a create expense that after the expense is manually entered or scanned allows the user to select what they want to do with that expense in the moment.

Metric: conversion in this test would be number of people that create an expense / number of people that see the create expense option Vs sum of the number of people that track or submit an expense / number of people that see track and submit as separate options in Global Create

Notes: We are already cleaning up the GC menu #47274 so we focus the user on a smaller set of realistic actions. Once we do that, we should be ready to test an idea @shawnborton proposed, which is to use one single combined flow that allows the user to first create the expense and in the next step decide to either save it for now or submit to someone.

Let's get started on building this and just put it on a beta for now and don't show it to anyone not on the beta. That way, when we finish cleaning up the GC and figure out how to set up the test, we can turn it on accordingly to the variant audience.

• Just track this for now would basically mimic the track expense flow
• Choosing someone to submit it to would then follow the submit flow

[shawnborton]

Updated mock would look like this:

cc @Expensify/design

I think this would be a good place to start. Then I think separately we should really follow up and make some improvements to the tracked expense experience, to make it easier to send a tracked expense somewhere after you indicate that you want to save it.

[dubielzyk-expensify]

That looks good to me :)

[grgia]

I can help move this forward - will assign for now to track but need a bit more context

[grgia]

@anmurali @danielrvidal
Curious how this would work. Is it % of all users? Or a subclass of users?

[anmurali]

@grgia how we actually deploy the test is still actively under discussion here. Cause we gotta adopt a framework that we can use repeatably over time. I think for now we could develop this variant, and put it behind a beta?

[grgia]

Yeah that works @anmurali. Do we have a doc or something this links to so I can get more context?

Is the A test just the current FAB/Global Create menu?

[grgia]

I pushed a PR for the beta. Can I get confirmation that this is ready to be built so I can get one of our external agencies on it?