I am renting camera equipment for an upcoming trip, and I found the user journey to be kind of interesting. I will first detail my journey for renting the equipment, talk about challenges I had with the site, and then talk about how I came up with a pricing model that should enable a new UI design.
- Search around for equipment on the site.
- Contact the shop (via email) to confirm the availability for the trip.
- Discuss options back and forth via email.
- Agree on equipment selection and visit site.
- Search for equipment again and add them to the cart.
- Each item needs to have the duration selected. Options include things like 2 Nights, Weekend, Weekend 1-Night, 1 Week, 10 Days, 2 Weeks, 3 Weeks, and 4 Weeks. There are double the number of options because for every selection there is one “with insurance.”
- At checkout, you specify the date range for pickup and drop off.
- Input Credit Card, and complete the checkout process.
- I have a particular date range in mind for my trip. I want to pay for what I use, but I can only select from the list the dates. I can either agree to overpay and trust them to reduce the charge or underpay and pay some difference at pickup.
- I don’t know what lenses are compatible with which cameras. As a result, the first body I picked wasn’t compatible with the lenses I was planning to rent. The email conversation went well and resolved this pretty easily.
As a person looking to rent a camera I want to be able to input my pickup and drop off dates so that I can pay for the days I’m renting.
I created a table for the camera body I planned to rent using Google Sheets. Then, I benchmarked each “discounted” value compared to the 1-day rental. I came up with this chart, which then I used the trend to create a power series through the points.
Now that we can easily calculate the cost of equipment based on the 1-day rental and the number of days we can create a new UI that will allow users to select their rental dates and see exactly how much they need to pay.