A Wizard guides users through registration, enterprise setup and shop setup

[drummer83]

What is the need / problem?

As Instance Managers we see many new users signing up but never finishing the enterprise and shop setup. We believe that one reason is the complexity of this process which requires reading the user guide or using other resources like video explanations. We need a Wizard to guide users through the setup process, asking them for all information needed to open the first shop including first products.

Which type of users does this problem affect (and how many, if known)?

• Hub Managers (MCFEs)
• Producers (with and without shopfronts)

In Germany only a quarter of the newly registered enterprises finished the enterprise and shop setup. And this was achieved by very personal and intense support by our onboarding team.

Potential solutions that will solve the problem

Similar to the registration process a user interface is required which guides users through the following steps, asking for required information and explaining what it is used for:

• registration (already covered)
• setting up enterprise information (partly covered)
• setting up payment methods
• setting up shipping methods
• setting up permissions
• adjusting shop settings
• adding first products
• opening first order cycles
• ... more?

Links to videos for these steps could provide additional help.

The details of the required information should be defined during the inception process.

Connected wishlist and discovery discussions

Also related: https://github.com/openfoodfoundation/wishlist/issues/222 Discussion on slack: https://openfoodnetwork.slack.com/archives/CG7NJ966B/p1651037635519829?thread_ts=1651037635.519829&cid=CG7NJ966B

Additional context

Is Papercut or feature candidate?

Add papercut or feature label to answer the question. If you are not sure, don't worry product team will cover :-)

[lin-d-hop]

After a very useful discussion on slack it became clear that the actual problem we are trying to solve is that: New users fall off the registration process because they don't know what to do next after the registration wizard.

Originally the Dashboard page was made to help users see what to do next. However it's not very helpful at the moment. Perhaps we can improve the UX of the Dashboard page to bring it back to the use it was intended for? I've put some ideas in this document.

The reason I propose something like this rather than a full blown Wizard (as in registration process) is: a) A wizard means building and maintaining a second UI that does the same thing. Thus this UI should be as small as possible b) We want people to start using the actual app as much as possible now, so let's get them into the pages they'll be using often (including the user guide). c) I think we could create 1-3 papercuts that would do all of this. This means that we could actually deliver an improvement. The pipe is currently totally blocked for anything bigger than papercuts for some years, unless we can recruit.

[lin-d-hop]

Hi @drummer83 Is the above a potential solution to your needs? If so I can explore getting it into potential papercuts so that DE might be able to select them (once you are a core instance).

[lin-d-hop]

Hi @drummer83 I'm working on a new funded features round and wondering if there is something here I should include on updating the dashboard to help people registering for the first time.... WDYT?

[drummer83]

Hi @lin-d-hop, thanks for your effort and for following up!

I totally understand your points about maintaining the wizard as a second UI and that the only way to get things done would be using papercuts. And I also like the approach of making people use the actual pages of the backend rather than a wizard. Still I think providing links to the user guide only is too high a barrier for new users.

What would you think about adding a help section below the navigation on all (important) admin pages which can be opened (default for new users) and closed (by experienced users). This is kind of an integrated wizard, inspired by your dashboard improvement box. Provided content could be:

• What needs to be done on this page to get the enterprise setup done?
• How can this be done (short version)?
• Link to user guide for more detailed information
• Link to video explanation
• Link to previous and next steps

I will provide a mockup, if you think this could be a way to go.

Could this still be papercut size? The code would be the same on every page. Content would be provided by community (I could drive that).

Regarding your proposals in the document:

• Redirecting users to the dashboard --> I like it!
• Improving the dashboard --> I like it! --> Content and design to be defined
• Improving visibility of admin area --> I like it! --> Proposal: When logged in, the banner (asking to register) could be used to display 'Go to admin to set up your shop' on main page, shops page, and others. Better ideas?

Let me know what you think!

[RachL]

Not a papercut :(

[audez]

I'm 300% with adding a "first steps helper" in the dashboard that would really help users to set up their shop and spare us a lot of support time. I agree with the criteria of Lynne doc. It could look like a kind of integrated wizard, where there is a "done" button at each step that is clicked by the user, as proposed by Lynne. I think something like this could be great:

IMO providing them with critical info and links to the different admin tabs would be awesome, so they can get used to the interface and know where to find the info. I think it's good to provide them with a link to specific parts of the user guide in each step, but not making it too visible so they don't feel "forced to" open the user guide, thus they can set up their shop as quickly as possible, and not get lost in the guide.

Ideally the displayed text and steps would be different for shops, hubs and profiles. Ideas of text: https://nextcloud.coopcircuits.fr/index.php/s/bC8pzF6sNaSw9gk

I would be favorable to display the "classic" dashboard only when they're done with the "first steps helper".

What do you think?