Challenge Summary
Welcome to the ZC Supplier - Supplier Scenario Design Concepts Challenge. In this challenge, we are looking for a new user experience and intuitive workflow to be followed by a supplier using our application. We are looking for you to think about this within the context of responsive design that can adapt to all platforms – computer, tablet, mobile.
We are looking for you to provide design concepts and click-path solutions based on the provided Supplier user story. Review the Supplier user story and think about how a user would interact with this application - how do you reduce and simplify the click-path?
You DO NOT need to redesign the entire application - focus only on the Supplier user story. Work within the provided application design guidelines (attached).
In this challenge we are looking for DESIGN CONCEPTS on improving the Supplier user experience.
Round 1
Submit your design for a Checkpoint feedback:
1. Requisitions List Page (Desktop & Mobile)
2. Submitted Candidates Action Page (Desktop & Mobile)
- Provide us with a click diagram of your design to help explain your design
- Notes.jpg: Any comments about your design for the Client
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
Round 2
Final Design plus any Checkpoint feedback:
1. Requisitions List Page (Desktop & Mobile)
2. Submitted Candidates Action Page (Desktop & Mobile)
3. Requisitions Details Page (Desktop & Mobile)
4. Submit Candidate Page (Desktop & Mobile)
- Provide us with a click diagram of your design (see reference)
- Notes.jpg: Any comments about your design for the Client
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
Challenge Description:
ZC is a contingent-workforce management and pay-rolling vendor. We have a web-based application that is used to facilitate the hiring and management of a contingent workforce. It is a highly customizable application that is utilized by thousands of users working for, or on behalf of, hundreds of different ZC customers.
Users of this application fall into one of 4 roles:
Program administrator – The ZC user that is overseeing the process for the customer.
Customer manager – The person trying to fill open positions with contingent workers. He/she creates job requisitions, selects and interviews candidates, and approves time and expense for contingent workers.
Supplier/Recruiter – Representative of an employment agency being utilized to fill open positions. He/she submits candidates to job requisitions, oversees the entry of time and expense for hired workers, and monitors the payment of invoices by ZC.
Resource/Worker – The contingent worker. He/she submits time and expense reports.
The goal of this challenge is plan the click-path design around how the requisition and candidate management functions for the Supplier Role could possibly look and work.
Business and Design Problem:
The current UI is having a negative impact on customer retention. The issues communicated to us thus far include:
- Too many clicks!
- Not intuitive – a user arrives on a page and they are not sure what to do next
- The design fails to take advantage of the ava
- Inconsistency between pages
- Important items are below the fold
Business Need:
The purpose of the UI redesign is to create a best in class user experience for our users. The new UI needs to help ZC attract and retain customers.
What we want our users to feel while or after using our system is:
- Clarity, not confusion
- A sense of accomplishment
- ‘That Was Easy!’
- A desire to continue using our system
User Story:
1) A Supplier receives an email notifying them that a new requisition has been posted. The email contains the hiring company, the job title, and a copy of the requisition. (notes: requisition list landing page and how they take action)
2) The Supplier logs in to the application and sees a list of open requisitions. They click into each requisition to see details. Note that details displayed vary by customer, but include work location, job description, schedule, pay rate, required skills/certifications, start/end dates, education, and background check requirements. The supplier can do any of the following for each requisition:
- Accept – indicates intention to submit candidates.
- Decline – indicates intention to NOT submit candidates and removes the requisition from their list.
- Submit one or more candidates.
3) During candidate submittal, Supplier may:
- Submit a new candidate that is not in the application database – uploading their resume and entering all required information. (Note that required fields vary by customer)
- Select from an existing list of candidates already in the application database using search criteria such as location, availability, resume key words, desired pay rate, certifications, and competencies.
4) At any time after submittal, Supplier can withdraw a candidate or resubmit (modify details of submission, e.g. pay rate).
5) If the customer manager is interested in the candidate, the Supplier gets an email requesting an interview. The Supplier can decline, accept, or send a request for a different date/time.
6) If the customer wishes to hire a candidate, Supplier gets an email that an offer is extended to their candidate. Supplier can accept it, decline it (essentially withdrawing the candidate), or submit a counter-offer.
Screen Sizes:
We would like to see your design for Responsive layouts (see Branding Guide for Desktop and Mobile design)
Desktop & Tablet: 1024px x 768px
Mobile: 320px x 480px
Design Concept Goals:
- Focus on the provided user story - how do you fix the “too many clicks” issue? How do you keep important information above the page fold?
- Suggest how the Supplier should interact on these screens
- Think simple but effective solutions!
Supporting Documents:
- Use the colors and brand from the attached Branding Guidelines (Branding Guidelines.pdf.zip)
- Use the provided screenshot as your base and design the Supplier experience within it (Screenshots.zip)
Screens:
1) Requisitions List Page:
Review the User Story. A user arrives here after receiving an email and they click to go to this page
- User should be able to see a list of all requisitions by customers.
- If user clicks on a requisition he should be able to see the details of the requisition.
- The supplier can do any of the following for each requisition:
A - Accept – indicates intention to submit candidates.
B - Decline – indicates intention to NOT submit candidates and removes the requisition from their list.
C - Submit one or more candidates.
2) Requisitions Details Page:
- The details displayed will vary by customer, but it should include: work location, job description, schedule, pay rate, required skills/certifications, start/end dates, education, and background check requirements.
- The suppler can do any of the following for the requisition:
A- Accept – indicates intention to submit candidates.
B- Decline – indicates intention to NOT submit candidates and removes the requisition from their list.
C- Submit one or more candidates.
3) Submit Candidate Page:
During candidate submittal, supplier may:
- Submit a new candidate that is not in the application database – uploading their resume and entering all required information. (Note that required fields vary by customer)
- Select from an existing list of candidates already in the application database using search criteria such as location, availability, resume key words, desired pay rate, certifications, and competencies. (Note to capture the search experience)
- At any time after submittal, supplier can withdraw a candidate or resubmit (modify details of submission, e.g. pay rate).
4) Submitted Candidates Actions Page:
Actions are:
- withdraw
- update details, resume, documents
- reply to interview request - accept, decline, suggest new date/time
- respond to an offer - accept, decline
Important:
- Keep things consistent. This means all graphic styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance.
Target User:
- Supplier
Judging Criteria:
- How well you plan the user experience and capture your ideas visually
- Cleanliness of your graphics and design
- Your design should possible to build and make sense as a tablet application
Submission & Source Files:
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Submit JPG/PNG for your submission files.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD file, or Adobe Illustrator as a layered AI file.
Final Fixes
As part of the final fixes phase you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.
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.