Broken Calendaring and Scheduling Experience
Posted: Thu Mar 15, 2007 10:11 pm
I believe the church recently hired some user experience experts. Here's a challenge for their team:
Situation:
User is told to use the ward website to schedule the building. They get a user account all set up on the ward website. They schedule it on the calendar. Ward website administrator, separate from the building coordinator, approves the calendar item. This gets emailed to everyone in the ward who belongs to the selected organizations. Coincidentally, the Wednesday night building coordinator receives this and wonders if maybe she doesn't have to do the calling anymore because she was totally out of the loop on the approval. In fact, only the calendar item was approved. Even though the person who scheduled the event thought she was reserving it, she wasn't. The calendaring and scheduling systems are orthogonal. The website administrator sees a problem brewing and introduces the initial user to the Wednesday night building coordinator, only to find out that there is some other unknown building coordinator for other days since it is a shared building. Discussion ensues as people try to reverse engineer the website in their heads with varying levels of success to figure out what's going on. The Bishop gets looped in. He then talks with the other Bishop to find out who it is. That other Bishop indicates he thought the ward website would handle building scheduling automatically on a first-come-first-serve type of basis, but apparently the website does not eliminate the need for someone to do this busywork administrative task.
I apologize if this situation description is confusing, living the experience in real time can be even more disorienting, especially for normal everyday users without a technical background.
It seems that all that's really needed here is a secure page that lists the names, phone numbers, and email addresses of the building coordinators. That would at least provide parity with the ward bulletin experience of times past. Even better would be to automate the whole process and free up a member to devote more energy towards some other form of personal ministry, like their family.
I am looking forward to seeing what the user experience gurus at headquarters can come up with to smooth out this experience.
Situation:
User is told to use the ward website to schedule the building. They get a user account all set up on the ward website. They schedule it on the calendar. Ward website administrator, separate from the building coordinator, approves the calendar item. This gets emailed to everyone in the ward who belongs to the selected organizations. Coincidentally, the Wednesday night building coordinator receives this and wonders if maybe she doesn't have to do the calling anymore because she was totally out of the loop on the approval. In fact, only the calendar item was approved. Even though the person who scheduled the event thought she was reserving it, she wasn't. The calendaring and scheduling systems are orthogonal. The website administrator sees a problem brewing and introduces the initial user to the Wednesday night building coordinator, only to find out that there is some other unknown building coordinator for other days since it is a shared building. Discussion ensues as people try to reverse engineer the website in their heads with varying levels of success to figure out what's going on. The Bishop gets looped in. He then talks with the other Bishop to find out who it is. That other Bishop indicates he thought the ward website would handle building scheduling automatically on a first-come-first-serve type of basis, but apparently the website does not eliminate the need for someone to do this busywork administrative task.
I apologize if this situation description is confusing, living the experience in real time can be even more disorienting, especially for normal everyday users without a technical background.
It seems that all that's really needed here is a secure page that lists the names, phone numbers, and email addresses of the building coordinators. That would at least provide parity with the ward bulletin experience of times past. Even better would be to automate the whole process and free up a member to devote more energy towards some other form of personal ministry, like their family.
I am looking forward to seeing what the user experience gurus at headquarters can come up with to smooth out this experience.