![]() |
| No need for exact change to ride these city buses |
The woman at the museum gave us directions to get back to town. I think she was telling us where to catch a colectivo, but we found a parada instead. There was one bus stop on one side of the road, and we needed to go in the opposite direction. A man on his daily walk stopped to talk with us (turns out, he had been to Minnesota for his work in venetian blinds making) and confirmed that the bus coming in the opposite direction would stop for us. And it did. The driver let us cross in front of it as though we were getting on a school bus - and let us on.
I want to remember these first rides. In the grand scheme of things, it isn't a most significant story or a grand adventure. But they made me think about simple systems that are so obvious to people who use them every day, but not always obvious to newcomers.
- It's easy to not ask the basic questions when there is a language barrier. Actually, it's usually pretty easy to ask the question - it's being ready to understand the answer that can make asking the question difficult.
- Figuring out how a system works with a language barrier in play means that actions are taken based on understanding anywhere from 20-50% of the information given, and filling in the gaps by interpreting hand gestures and doing some guesswork. I had fun with it that day, but it can be really, really tiring. And easy to avoid.
- The system (in this case, public transportation) was not that complicated in the end, but it wasn't always obvious. For example, it's not obvious that "standing up" is the signal one uses to get off the bus. It's a one-time and easy thing to learn, but it's not obvious.

No comments:
Post a Comment