0

I am stuck into two situations: I designed the wizard attached below for Signup Purpose but inside dashboard user will be "posting job" and post job has few steps as well. So using the same Wizard for job posting is fine or should I introduce new wizard style?

Sign Wizard

1

Aim for as few patterns as possible, applied consistently across the application.

Assuming your original design (the Signup wizard) has been tested, and meets the acceptance criteria (success metrics) for your app, you now have a pattern which helps a user:

  • navigate a series of meaningful steps and inputs which rely on a specific order (either for implementation purposes/constraints, or to align with a users understanding) to create a new object in the system (an account in the first example you have).

Since you've now established a successful implementation of the Wizard pattern, don't make the user learn another interaction pattern to achieve a similar outcome if possible.

| improve this answer | |
  • I completely agree with you sir. But don't you think if user see the same wizard pattern second time when posting a job, they might think this may be an error because the layout structure would be exact same but the content would be different. User will notice layout structure first i guesss than content. – Anas Nasir May 18 at 5:55
  • One thing about ux, is there's no absolute rules :). That said, limiting the interaction models allows users to focus on the the use of similar patterns, so when they go to post, they'll see a series of steps, vertically aligned, where they'll read about which step comes next. – Mike M May 19 at 1:10
  • Thanks Mike, this helps a lot. – Anas Nasir May 19 at 7:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.