The user experience (UX) of purchasing anything from the current Stowe Online Store is confusing and frustrating. To solve this issue I created a prototype of a web app that makes purchasing things a painless and quick experience. I optimized this process for desktop and touch-devices.
The site I redesigned is ( As of 2016 ):

The very first thing I did was write down a process flow diagram of how to order something from the store.
I began to consider how different types of people would use the site I create. I then created some flow diagrams based off of how different types of users would experience the current site. Scenarios Here
After creating some flow diagrams I began to get a bit more in depth with it. I created detailed personas and ran through even more process flow diagrams to map out how each of these different types of individuals would experience the current site.
My Revised Process Flow Diagram for The Original Site:
I began researching websites that had good/decent shopping experiences with products similar to my store. I then mapped out the whole process with yet more process flow diagrams to help me better understand what works and what doesn't. This allowed me to make better decisions when it came to my own site. Competitor Sites
I researched other websites that used a shopping cart so that I could examine processes and organization that worked well. Screen Shots Here
-Clear site navigation -Easy item & price comparison -Clear requirements (ESC) -Speed / quick process -Simple account creation -Simple log-in/guest check out -Easy to read/scan -Mobile-friendly -Clear distinction between passes -Easy refill option -Clear benefits for each age group -Contact information provided -Fewer pages for checkout (layout) (guest option) filtering (what to buy, prices, quantity) -assign name on page at once for ticket (multiple) -compare prices/tickets -edit in cart -shorter process for reloading card -fix descriptions -show season dates
-Abandoned cart -Frustration / confusion -Visual clutter -Hierarchy issues -Too much / too little information
The Flow Diagram for My Site:
Once the interactive mock-up was complete, I did some user testing to see how easily people could utilize my site and the site's functions.
*1."You are an existing user who wants to ski for a day. You want to login and then reload your ( already owned ) Evolution Stowe Card." *2. "You are a new user who has no desire to make an account. You just plan to buy a ski ticket for one day and never return." 3. "You are the father of a family of five. You, your wife, and three children want to buy season passes for all days of the week. No one has an account or Evolution Stowe Card yet. However, you do not desire to make an account today." *4. "You are a new user who wants to ski for three days. You do plan to come back though, so you decide to make an account. You have to rent ski equipment for the days that you will be going. You do not own an Evolution Stowe Card." 5. "You are an existing user who is too lazy to login. You have been there before and just want to quickly reload you and your wife's Evolution Stowe Card with tickets for a day." *These are do-able on mobile as well. ( and were tested on mobile )
I did not encounter any major issues. However my tester had minor trouble finding the login, but found it quickly enough. They also noted that older users might fight it hard to read such tiny text on mobile.