hey everyone clara here and chad
today we're going to share a tip on keeping
your user tests organized as well as how
to share feature work for development
after it's been tested
let's say you're looking to improve the
current experience of a flow and have
three different iterations you want to
test
you could put all three flows on a
single page using multiple flow starting points
or give each flow their own page
another option is to create a branch for each flow
we're going to test these
three different flows to understand
which option results in a better
experience and conversion when customers
are adding an item to their cart
after the tests have been run i'll build
out whichever of clara's designs we
decide to move forward with based on the
test results
we'll also be using branching for these
flows with each variation in its own
branch to capture any comments aid in
development handoff or reference back to
the explorations in the future
right now when a user adds an item to
their cart they are taken directly to
the checkout page
the first flow we want to test will show
a toast notification after the user
clicks add to cart
the second flow will have two options
add to cart only and add and checkout
the third flow will change the button
text upon clicking it
now that we have our three branches off
of the main file we want to start
preparing our prototypes in each of the
branches
with each variation prototyped our
researchers can now run user tests on
each of the branches to see how they
perform
meanwhile our main file still represents
what's live in production now while our
three explorations are all linked back
to the main file as a branch
one thing to be mindful of is that
anyone who can access the main file will
also be able to access any branches of
that file
this is the default setting for a new
branch though it can be updated like any
other file
though chad already has access to the
three branches because he has access to
the main file
i'm still going to explicitly send
invites from each branch so he can be
notified
clara shared the variations with me so i
have an idea of what the design team is
thinking and what we may end up building
these all look like great improvements
though here i'm noticing an
inconsistency with the icon in the add
to cart button
i'm going to let clara know that this
should probably be updated by leaving a
comment and tagging her
clara just let me know that she's
updated the design in that branch and
has resolved the comment
as with all prototypes in figma
prototype updates in your branch will
show up in real time and here we can see
that everything looks good with the
change that she made
now i'll stand by until i hear back and
any next steps for development
our researchers synthesized the results
and flow b ended up performing the best
once we archive the other branches
i'll go ahead and let the development
team know which flow we're moving
forward with
though the other branches have been
archived we can still reference them in
the future
i can see the history of the previous
iterations along with any comments that
were made in that branch
here i've been invited to the design
file of the successful branch
i can inspect the design to get what i
need in order to build this
in the event i'm unsure of how it
currently is in prod i could go out to
the site or
i could quickly switch back to the main
file and see the original design
after i've completed the build on the
code side i'll leave a note for clara
that we're going to merge these changes
in
and have it ready to go out to
production soon
i'll also follow up with her directly so
she can review the designs against
what's been built
i reviewed the work on staging already
and it's looking good
since this will be our new version
matching what's in production i'm going
to merge this branch that we used for
testing and development once the deploy
goes out
we now have a historical overview of
what was tested what worked and what
didn't
all of the comments made in each branch
are preserved within the branch and can
always be referenced again
the version history will also show me
when branches were created and merged
having a centralized space to view older
iterations can help prevent duplicate
work and avoid confusion for what is
current
we hope that this tip can help you keep
your files clean and easy to navigate
when it comes to testing and development
partnership thanks for watching we'll
see you next time