lmcguire wrote:(3) Room Reservation vs. Announcements: The calendar serves both functions. Room reservation demands that calendar items be created as early as possible in order to ensure the room is reserved.
The HPGL in my ward announced a ward progressive dinner to the ward council. The bishopric asked if he had added it to the calendar. He responded that it wasn't needed because the dinner was not being held in the meetinghouse. He thought the only purpose of the calendar was to reserve the meetinghouse. He didn't understand that the calendar can also be used to send notifications to the members of the ward. He also did not understand that the calendar is an essential and required part of the annual ward history.
But details of an activity aren't known until much later, after the calendar is forgotten, so details are never added / updated. Room reservation may require more strict rights, or at least priorities (with notifications when someone's reservation is denied / revoked / trumped by a higher power). Calendar announcement changes don't need such strict rights, nor prioritization or "trump" handling / notification.
This is the biggest problem I saw with holding an annual calendaring meeting. The ward/stake council creates place-holder events, but never fills in the details. Even worse, since the last person to update an event becomes the owner of the event, everyone asks that person for the details of the event during the week prior to the date of the event. I can't tell you how many times I had to shrug my shoulders and tell people I know nothing about the event despite the fact that my name appeared as the owner of the event.
I think the STS should do everything in their power to ensure church tech tools are known and people with rights (or data) are well trained (unless that's not actually one of their official responsibilities - I actually have no clue what these folks are supposed to do and have never knowingly seen one)...
Well, I tried, but not many people were interested in being trained. Oh well.