Arro’s onboarding process consisted of three critical phases, each with the own challenges and dropoff risks:
Through the onboarding flow, usability testing revealed customers’ disinterest in reading verbose instructional copy and the tendency to skim through screens that didn’t contain specific calls to action. Therefore, the flow underwent significant analysis by the team—supplemented by comparative studies—to streamline its contents and lean on commonly understood design patterns rather than expository copy.
The team structured Arro’s backend architecture as a modular system, where individual components could be optimized as needed without disruption to the overall business processes. Customers’ onboarding would weave much of this architecture into its flow, including many external partners to handle such critical tasks as:
Arro's onboarding process involved a lot of complexity and consequence for the company's future. Only by means of intensive team collaboration, customer engagement, and experimentation were we able to design and build an optimal flow (at least with the pre-launch knowledge and wisdom we could muster). Through increasingly large product releases following this design, we would analyze usage and experiment further, testing the variables presented above and many more.