Hoherberg Ski School - Reservations Wireframe Challenge

Welcome to the Hoherberg Ski School - Reservations Wireframe Challenge

Hoherberg is in their first step for the development of their Ski School Application. In this challenge, we are looking for you to refine the existing wireframes, specifically around the Reservation section. We have provided extensive client feedback on the existing wireframes and need to you to take that new information and incorporate it and/ or change the user flows to accommodate any new requirements.

Good luck and let us know any questions in the forum.

Round 1

Checkpoint Submission Requirements 
Initial Hoherberg Ski School - Reservations Wireframe for these following features: 

1. Reservation Check in
2. Create New Reservation
3. Reservation Booking
4. Reservation(s) Booking Summary & Credit Card Processing
5. Note: Submit as much application features as you can for early review. 

Round 2

Final Submission Requirements
Final Hoherberg Ski School - Reservations Wireframe for these following features: 

1. Reservation Check in
2. Create New Reservation
3. Reservation Booking
4. Reservation(s) Booking Summary & Credit Card Processing
5. Private Lesson Customer Reservation
6. Notifications

Note: please address Checkpoint Feedback for your Final Round Submission
We are looking to update and/ or redesign sections of the reservation portion of the application. The client has provided pretty detailed information and feedback about what they would like to see based on the existing wireframes. We would like you to take that feedback and direction from the client and incorporate it into the existing wireframes. We are also open to reworking or redesigning parts of the Reservation section if it makes sense and there are better UX flows and processes.

Reservations Requirements

• Reservations Check-in needs improved based client feedback
• Reservationist need able to see what instructors have checked in/checked out
• Reservationist need able to see a status of an instructor (checked in, on assignment, at lunch, on break, out sick, etc) This is a very broad view of what the instructor is doing without giving too much detail to their schedule. Defaults to today - needs to include times and ability to switch from today to a different date. 
• Reservationist level ability to be able to check in an instructor. But not be able to edit or view their schedule.
• Increase number of reservation records displayed. Want more visibility in a single view 
• Need easy calendar date selection tool
• Display clear date/time information for each selected reservation. 
• Check-in allows processing of one record at a time 
• Client Check-in needs to be flexible, because not all clients will check-in. Sometimes a client checks-in with their instructor.
• Multi-day reservations dont need to check-in every day
• Need ability to set later start time, assigning a new product, because client running late
• Instructor becomes available if a reservation is cancelled
• Create New Reservation needs better UX to guide reservationist through the process
• Add new Product Name Availability widget
• Add Reservation Order progress steps
• Reservation Order will require an order view, like an online shopping cart experience
• Booking Summary & Credit Card Processing
• Need ability to add comments . Allows reservationist to include additional information
• Policy Explained Checkbox. To confirm that the reservationist explained the check in and cancellation policies to the client
• Need ability to edit, delete, or waive booking fee for each reservation order line item
• Confirmation of successful transactions
• Create flow for Private Lesson Customer Reservation
• Create flow for Group Lesson Customer Reservation
• What do Notification look like for Reservationists

Challenge Inputs
Previous Wireframes

• We are sharing the original wireframes as context and to build upon.
• You are more than welcome to use the existing wireframes as a starting point, but it's important that you include all of the new client feedback and requirements. This may require doing extensive rework to the existing wireframes.

Information Architecture Document

• This IA outlines the entire future state of the application
• Note: this IA document does NOT match the "Previous Wireframes" shared above. You will need to make sure you are using this IA doc for the correct navigation and subpages/ sections
• Some features element that will be useful for “Reservations” flow: 
  • Today Staff
  • Reservations Schedules/Check-in
  • Reservable Products
  • Product Inventory
  • Skier Data Capture
  • Booking Fee (credit card processing)
  • Group Lessons
  • Client Profiles

Reservations Requirements & Feedback

• For this challenge, you need come up with new UX flows and layouts that merge the reservations requirements and IA document stated above
• Check provided document to help you recreate existing wireframe to align with client directions: 
  • Reservation Check-in
  • Create New Reservation
  • Reservation Booking
  • Reservation(s) Booking Summary & Credit Card Processing
  • Private Lesson Customer Reservation
  • Notifications

Let’s discuss any questions you have about the challenge requirements in the forum

Screen Size

• Desktop: 1440px(w) & height up to your design

Target Audience

• Reservationist

Judging Criteria

• User experience and information architecture
• Easy of use of Reservations 
• General layout and functionality
• Includes all requirements

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
Wireframes should be built in Plain HTML/CSS/JS or you can generate from Axure application. Other option is using Sketch with Black/White theme.
The resulting files are not critical in this Challenge. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.

Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file

Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.