No items found.
March 17, 2021
read-time

COVID, Skiing & why your customers aren't responsible for your system

The Ski Hill's Inconsistent System: How Poor Design Affects Customers

My "real" life sometimes overlaps with my 9 to 5 life in weird ways. Story time, stick with me I promise there's a purpose here.

Last week, as the good Canadian that I am, I took a few days off to go skiing. My partner and I wanted to do some alpine skiing the first day and skinning the following day.

Given that, you know, it's 2021 and Covid is still happening, there were limited tickets to avoid crowding (something I hope we continue doing after covid!), which you can purchase online before arriving. As instructed, I went ahead and purchased two tickets for the first day of skiing. One ticket for me and one for my partner, using my card (we have a robust expense splitting process).

Upon arrival, we received 2 plastic cards that had our tickets for the day pre-loaded at the ticket booth. Akin to having a bus pass with preloaded tickets, we could now have access to any lift by scanning our plastic cards.

I was impressed! Ski hills are not synonymous with technology. As with many things, covid forced them to review their ways and greatly improve their customer experience.

The next day, however, things went awry (and this is where I get to the point). Skinning tickets were not available online so we had to purchase them old school at the ticket booth. I gave the clerk my name after voicing what I wanted. She said:

"You have two profiles here, which is the right one?" to which I answered "ok, I'm not sure?". I had previously visited the mountain in person and given my information which was not deduped with my (new) online profile. After validating my address, she instructed me that I had "created two profiles in their system". I didn't know anything about their system!

After I wrapped up, my girlfriend asked for the same sort of ticket to which the clerk chastised her saying "your profile is tied to Aron, it has to be his credit card!". According to this mountain, my partner is not (and cannot be) independent of me.

This is my understanding of their system:

What's interesting to me is not that the system is poorly designed. It's how poorly prepared they were for probable use cases. For instance, what happens when you go from your parent's card (a profile attached to them) to your own (a full-fledged user with their own card)? What if you want to switch between the two? Do you carry around a bunch of non-descript cards guessing which one to use? Unless this mountain decides that online sales are the only way to purchase tickets, the majority of riders will eventually find themselves in this situation. From my (albeit brief) discussion with the clerk, the mountain seems wholly unprepared for this eventuality and that their customer's fault (and problem)!

More broadly, this type of patched-together system felt (and I'm sorry to say this) like a lot of no-code systems I interact with! The multiple logins, inability to update information, inconsistency among different CMS'. This includes the ones I've built (have you been to aatt.io?).

Yes, covid has been a forcing function for many businesses to digitize their processes. And those processes still have kinks to iron out—I'm okay with that. But no matter how shoddy our systems, let's not blame our shortcomings on our customers! Instead, let's talk to our customers to keep improving our systems/solutions (they're in this with us!). We can all do better!

Best

Aron

Want to improve your workflows?
Join 2,000+ others who get the 10% better newsletter in their inbox every two weeks
One more step: check your inbox to verify your email!
Oops! Something went wrong while submitting the form.
Written by
Giovanni Segar
Share article
Written by
Aron Korenblit
Share article
Related posts
August 11, 2023
Airtable adds AI, my thoughts
Airtable
Thoughts
May 14, 2023
What's Next For Me: Why I've Joined Webflow
Thoughts
May 14, 2023
Stripe Launches Apps: Every Tool Has Automations Now Part 4
No-code
Thoughts

Automate all the things

A weekly no-code automation delivered to your inbox (with thoughts on no-code every now and then)
Subscribe
Mar 17, 2021 by Aron Korenblit

COVID, Skiing & why your customers aren't responsible for your system

My "real" life sometimes overlaps with my 9 to 5 life in weird ways. Story time, stick with me I promise there's a purpose here.

Last week, as the good Canadian that I am, I took a few days off to go skiing. My partner and I wanted to do some alpine skiing the first day and skinning the following day.

Given that, you know, it's 2021 and Covid is still happening, there were limited tickets to avoid crowding (something I hope we continue doing after covid!), which you can purchase online before arriving. As instructed, I went ahead and purchased two tickets for the first day of skiing. One ticket for me and one for my partner, using my card (we have a robust expense splitting process).

Upon arrival, we received 2 plastic cards that had our tickets for the day pre-loaded at the ticket booth. Akin to having a bus pass with preloaded tickets, we could now have access to any lift by scanning our plastic cards.

I was impressed! Ski hills are not synonymous with technology. As with many things, covid forced them to review their ways and greatly improve their customer experience.

The next day, however, things went awry (and this is where I get to the point). Skinning tickets were not available online so we had to purchase them old school at the ticket booth. I gave the clerk my name after voicing what I wanted. She said:

"You have two profiles here, which is the right one?" to which I answered "ok, I'm not sure?". I had previously visited the mountain in person and given my information which was not deduped with my (new) online profile. After validating my address, she instructed me that I had "created two profiles in their system". I didn't know anything about their system!

After I wrapped up, my girlfriend asked for the same sort of ticket to which the clerk chastised her saying "your profile is tied to Aron, it has to be his credit card!". According to this mountain, my partner is not (and cannot be) independent of me.

This is my understanding of their system:

What's interesting to me is not that the system is poorly designed. It's how poorly prepared they were for probable use cases. For instance, what happens when you go from your parent's card (a profile attached to them) to your own (a full-fledged user with their own card)? What if you want to switch between the two? Do you carry around a bunch of non-descript cards guessing which one to use? Unless this mountain decides that online sales are the only way to purchase tickets, the majority of riders will eventually find themselves in this situation. From my (albeit brief) discussion with the clerk, the mountain seems wholly unprepared for this eventuality and that their customer's fault (and problem)!

More broadly, this type of patched-together system felt (and I'm sorry to say this) like a lot of no-code systems I interact with! The multiple logins, inability to update information, inconsistency among different CMS'. This includes the ones I've built (have you been to aatt.io?).

Yes, covid has been a forcing function for many businesses to digitize their processes. And those processes still have kinks to iron out—I'm okay with that. But no matter how shoddy our systems, let's not blame our shortcomings on our customers! Instead, let's talk to our customers to keep improving our systems/solutions (they're in this with us!). We can all do better!

Best

Aron

Automate All the Things
3K+
Subscribers
88
Issues
Enjoying the post? Get it in your inbox every Thursday
Last step: confirm your email!
Oops! Something went wrong while submitting the form.

Related streams

See all streams
No items found.