🧙♂️
Wizards: UX Question
Hi, I am designing a wizard that would be used by customers to setup/connect their organization. My question in short is "what is summary step"?
1
1
For the wizard, there are lets say these steps:
1. Plan selection
2. Infra settings
3. Account configuration/connection
4. Summary
1 & 2 - require a GET API call, basic.
3 - this requires user to login via Google/Salesforce/etc
ques: should I make the POST call to setup their organization immediately after 3 & then show the result in summary. Or, should I show summary of past 3 steps and then when they "submit" wizard - I setup the org. (also, any link to article would help a lot!) Thanks!!
him
I’m invested now but confused. Elaborate more??
frunkad
(not so necessary context: I work at a backup & restore company, and there's a wizard to start backing up Salesforce data)
So, my team here says: "Summary should display what has been created. As soon as user completes step 3, we should create the organization & start backing up. Step 4 is to show it got created successfuly"
him
replied
Darshan
(not so necessary context: I work at a backup & restore company, and there's a wizard to start backing up Salesforce data)
So, my team here says: "Summary should display what has been created. As soon as user completes step 3, we should create the organization & start backing up. Step 4 is to show it got created successfuly"
And what’re you confused about?
frunkad
My ideology: "Because the wizard itself has a step pending (Summary step), we cannot create the organization. High-value steps like "creating org" should be last step of wizard or "submit wizard" action. Summary should show what the user is about to create with the wizard"
should the actual high value creation part happen before summary or after summary?
him
Why not show summary and also show a progress of org creation?
frunkad
well its something like this:
I am thinking of renaming "Summary" to "Review" to avoid all confusion
him
replied
Darshan
I am thinking of renaming "Summary" to "Review" to avoid all confusion
Good call
Darshan
well its something like this:
Ui can be better 😁
frunkad
LOL -
1. I ain't the designer
2. It's a B2B product
3. Too many people to convince for basic sane UI changes.
(this is all I could bitch, tho its a great product)
🤟
1
🤟
1
him
replied
Darshan
LOL -
1. I ain't the designer
2. It's a B2B product
3. Too many people to convince for basic sane UI changes.
(this is all I could bitch, tho its a great product)
Can help with some feedback if you want me to meet your seniors and discuss about the ‘design’ side of the product