You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although our eventual goal for this round of test is to expose the updated plans grid through the main onboarding flow, we should make sure whoever sees it upon signup will see the same on in the logged-in /plans page.
The text was updated successfully, but these errors were encountered:
southp
changed the title
Trail Map:A user who see the new plans grid should see the same one in the logged-in /plans.
Trail Map: A user who see the new plans grid should see the same one in the logged-in /plans.
Apr 19, 2024
We don't have the prior art of this logic –– in several previous experiments that we showed the same treatment changes both in /start/plans and the logged-in /plans, we simply rely on the experiment assignment. However, that's not such a generalized functionality described here. It can also get in the way of the internal test actually, where people would just want to see the new grids by enabling a feature flag 🤔
To limit the scope, what do you think if we update this issue as the following?
Move this item to the 2nd milestone as part of the A/B test logic.
Update the description as: "A user who is assigned to the control/treatment group should see consistent plans grid design both in /start/plans and in the logged-in /plans"
Project thread: pau2Xa-5Ol-p2
Summary
Although our eventual goal for this round of test is to expose the updated plans grid through the main onboarding flow, we should make sure whoever sees it upon signup will see the same on in the logged-in /plans page.
The text was updated successfully, but these errors were encountered: