Challenge Summary
Welcome to Client Partner Survey Solution Wireframe Challenge. In this challenge, we are looking for your wireframe expertise in coming up with the initial flow for the Partner Survey. This Survey helps partners to share their working experiences with a client in relation to a product or group of products by filling out a dynamic questionnaire form.
At the end of this wireframe challenge, we are looking to have a complete solution for the User Experience and flow of the pages.
Round 1
Your initial wireframes for the below Scenarios
- Scenario 1
- Scenario 2
Any notes/comments about your solutions for the Client.
Round 2
Your Final wireframes for the given requirements with all Checkpoint Feedbacks Implemented
Any notes/comments about your solutions for the Client.
The purpose of the challenge is come up with a wireframes that gives us solutions for user experience based on a few scenarios given below.
Client has a portal where their partners will login and enter information related to their experience working with a client in relation to a particular product (or group of products). Once the partner completes the form, a questionnaire will be generated, which will go out to the client and ask them to confirm that the partner did indeed work with them on their products and comment on how well the partner did.
IMPORTANT! General Considerations:
- We are looking for your ideas in how to drive users through lots of questions in survey form.
- Think on how to create an intuitive user experience.
- How will a user knows the number of questions that will be asked in this survey?
- What are the action items (Save, Next, Previous, Submit etc) that need to be shown in this form and when should these be shown?
- Should we allow a user to save the data that was already entered by them? or at what point in the form should the user be allowed to save the data?
Wireframe Pages/Scenarios:
Below are few important issues that need to considered while creating this survey form.
Simple Forms:
Let’s assume a simple form, where partners has only couple of questions
Scenario 1:
In this survey form, user answers one question and followed by another question.
- How should this simple scenario be shown?
- How will a user know, how many questions will be asked in this survey?
- What are the action items (buttons, etc) that need to be shown in this form?
- Should we allow a user to save the data that was already entered by them?
- It could be simple form with two straight forward questions like shown in the attached flowchart.
Complex Forms:
Now let’s assume a complex form, where there could be anywhere from 1 to 50 questions, depending on the answers that the partner provides to the questions.
1) There could be many questions in this survey form and depending on the partners answer to the first question may determine whether there will only be one question required in order to complete the form. Alternately, the partner’s answers may mean there are 20 or more answers required. Need to show flow for all of these options.
2) We don’t want the user to have to click “Submit /Next” for each answer i.e. based on the answers from the partners and the next questions context should determine whether next question should be shown on the same page or ask the user to click next and move to the next step to see more questions. Think on how this can be shown in your wireframes.
3) We also need to consider that if there is NO submit until the end of the form and there ends up being 50 questions.. What if the user goes back and changes one of the early questions and accidentally ends up deleting all of the work he/she has just done on the subsequent 40 questions? i.e. we need to consider how user error might come in to play on very long forms, where questions directly relate to subsequent questions in the form.
4) A Wizard might be an option, where there are MANY questions to complete (so the user can get a feel for how many more questions will be in the form and also to add “submit / save” so they cannot accidentally delete a ton of work) however, there may only be 1 or 2 questions.. In which case a wizard would not make sense … so (idea to consider) maybe the first set of questions determines whether the form becomes a wizard or stays a single page of questions?
Scenario 2:
We would like you to come up with a scenario where the partner encounters 1-50 questions like the mentioned above.
- Come up with a scenario where the user has to go through complex forms, scenario 3 should help you get started on this.
- You need to consider the four points mentioned under the Complex forms and implement them in your wireframes
- We are looking for your ideas in how to drive users through lots of questions in survey form.
- How should this complex scenario be shown?
Scenario 3:
Please go through the sample scenario which we have shown in the attached flowchart and create a wireframe based on that.
Assume the partner starts with one questions with 3 possible answers (B, C, D).
- If B or C is chosen as the answer then we show another question with X, Y as answers. Choosing X shows three more questions. Choosing Y shows another question with 4 possible answers (Alpha, beta, gamma, and theta). Choosing Alpha or beta - shows another 4 questions. Choosing gamma or theta will show a question with 3 options (theta, epsilon, and zeta). Choosing Epsilon shows one more question final question which marks the end of the form. Choosing theta or zeta shows no more questions
- If D is chosen then show another question with 3 possible answers (10, 20 and 30) that shows more questions for each of the options before submitting the form.
In addition to the above three scenarios, if you have any other scenarios, please do show it in your wireframes.
Target Audience
Client’s Partners
Judging criteria
Your submission will be judged on the following criteria:
- User experience
- Completeness and accuracy of the areas of functionality and content
- Any additional scenarios which you come up with
- How well your wireframes provide a consistent user flow and clear information architecture for the application
Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.