Josh Work Articles Michigan IT Randomizer feature added to Google and Exchange calendars

Michigan IT is pleased to announce that a new randomizer feature will be available on April 1, 2022, for both the U-M Google and Outlook calendar applications.

The randomizer uses AI to scan a calendar to determine the best place to jam in another meeting, but without the hassle of a person needing to view their own calendar. Users will be able to simply click on the randomizer button to be pleasantly surprised at the day and time the meeting shows up. For those who like chaos, the randomizer button will shake up their calendar so every minute of every day is an unexpected thrill.

Image of two side-by-side calendars, Microsoft Exchange on
the left and Google Calendar on the right, with their respective
logos overlaid, and a button marked 'RANDOMIZE' in the center
between them
(Rachael Wojciechowski)

"Zoom at U-M has allowed all of us to seamlessly schedule meetings back-to-back for over two years now. My calendar is so busy that I rarely have time to get up for a bite to eat. But that's fine because I don't like getting up anyway. I just use my drone to deliver food right to my mouth," said Spring Cantrip, lead performance support analyst. "I look forward to being pleasantly nonplussed by what's next on my calendar. Standing meetings are so 2019."

Josh Boffola, administrative assistant, is excited to try it out. "I regularly schedule meetings for 25 people. I'm sure I will appreciate being able to do this with the just press of a button. After all, it's March 762, 2020. It's about time that we have this feature. It'll be interesting to see how many people's schedules actually line up, and then how many of these meetings just shift to email. After all, most meetings could've been an email anyway."

A required, instructor-led My LINC course will soon be available and additional details are available on the project website.



Back to my articles and books page
Back to my work page
Back to my home page

Last update Apr01/22 by Josh Simon (<jss@clock.org>).