{"id":335,"date":"2012-04-25T21:59:41","date_gmt":"2012-04-26T05:59:41","guid":{"rendered":"https:\/\/sheldon-hess.org\/coral\/?p=335"},"modified":"2012-04-25T21:59:41","modified_gmt":"2012-04-26T05:59:41","slug":"death-by-doodle","status":"publish","type":"post","link":"https:\/\/www.sheldon-hess.org\/coral\/2012\/04\/death-by-doodle\/","title":{"rendered":"Death by Doodle"},"content":{"rendered":"

\"\"<\/a>Scheduling is generally acknowledged to be a messy process. It is what we developer\/geek types refer to as a “Hard Problem.” (I’m pretty sure it’s actually an “np hard problem,” but why risk overstating it?)<\/p>\n

But I find myself really irritated by the current “solution” that I and most of the library world seem to utilize: Doodle<\/a>. Don’t get me wrong; Doodle’s great. It converts time zones automatically, and if you sign up for a free account, it gives you the option to add “I can meet at this time if we really need to, but please don’t make me” (“if need be,” they call it) to your polls. It’s fantastic!<\/p>\n

\"\"<\/a> But I just realized that I have created multiple Doodles for the same week, and, in filling them out, I’ve potentially made one of them a lie, once the meeting time is set. That’s happened to me before, and it was awkward. It’s why I’m such a stickler for filling them in quickly: if everyone Doodles (yeah, it’s been verbed) in a timely manner, Doodle-overlaps are a little bit easier to avoid. Once one meeting is set, I can head over to the other Doodles I’ve filled out and change them. If, on the other hand, all of my Doodles languish, then my schedule fills up, both with Doodle-things and with other things, and I end up scheduled for multiple things at once.<\/p>\n

It’s a very first-world problem, but there you go.<\/p>\n

It annoys me extra, because I even have this problem internally to my workplace. A workplace that has Exchange<\/em>.<\/p>\n

Why is Exchange (or Google Calendar or any online calendaring solution with the option to share) different, you might ask? Because you (hypothetical coworker) can decide to set up a meeting, and you can add me to your invite and then start looking at times, and you can see my and everyone else’s free\/busy time within the invite, in real-time. There’s no chance of my accidentally lying about meetings, like on a Doodle poll, because there’s no delay; you’re looking at my actual<\/em> free\/busy time. And as soon as your meeting is scheduled? Bam, it shows up on my schedule as a busy time, so other people won’t schedule over it.<\/p>\n

\"\"<\/a><\/p>\n

The reason we don’t use Exchange to its fullest potential (read: at all), in my workplace, is that some people keep their calendars on paper. And I get that it’s hard to change how you do your work, mid-stream. I’m venting, here, not recommending that we all be forced to go on Exchange. (I’m not even on Exchange, right now; I’m on Google Calendar. You can see my free\/busy time right here<\/a>. But I’d switch to Exchange in a minute if everyone else would!) It wouldn’t even solve all of the problems with external-to-our-organization Doodling. But it’s so wasteful<\/em> to spend all of this time sending out polls, waiting for people to respond to polls, bugging people who don’t respond, correcting polls when new meetings come up, and apologizing (and restarting the scheduling process, sometimes!) when two polls come back with the same time chosen. <\/p>\n

I’m not saying it was always seamless when I scheduled meetings as a consultant (where we all used Exchange). People had so many<\/em> meetings that there often were no<\/em> times when everyone could meet. And we’d just meet anyway, without a couple of people, or they’d come in late. And the world didn’t end. But librarian culture is so different—people get mad that they “weren’t told” about things, when they miss meetings. We have what is, on a good day, a consensus culture. (On a bad day it’s a veto culture.) And this might vary by workplace, but I’ve noticed, in mine, that when someone comes in late, we spend a lot of time rehashing. So it seems like, in libraries (as opposed to IT consulting firms), this whole scheduling issue is a much bigger deal, AND<\/em> it’s harder. <\/p>\n

I dunno. Does anyone else have this problem? Or is it just that I’m on too many teams, committees, work groups, etc.? <\/p>\n","protected":false},"excerpt":{"rendered":"

Scheduling is generally acknowledged to be a messy process. It is what we developer\/geek types refer to as a “Hard Problem.” (I’m pretty sure it’s actually an “np hard problem,” but why risk overstating it?) But I find myself really irritated by the current “solution” that I and most of…<\/p>\n

Continue readingDeath by Doodle<\/span><\/a><\/div>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[55,20,28,31,33,36],"tags":[],"class_list":["post-335","post","type-post","status-publish","format-standard","hentry","category-communication","category-engineering","category-librarianship","category-new-librarian","category-politics","category-scheduling","entry"],"_links":{"self":[{"href":"https:\/\/www.sheldon-hess.org\/coral\/wp-json\/wp\/v2\/posts\/335","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sheldon-hess.org\/coral\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sheldon-hess.org\/coral\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sheldon-hess.org\/coral\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sheldon-hess.org\/coral\/wp-json\/wp\/v2\/comments?post=335"}],"version-history":[{"count":0,"href":"https:\/\/www.sheldon-hess.org\/coral\/wp-json\/wp\/v2\/posts\/335\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sheldon-hess.org\/coral\/wp-json\/wp\/v2\/media?parent=335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sheldon-hess.org\/coral\/wp-json\/wp\/v2\/categories?post=335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sheldon-hess.org\/coral\/wp-json\/wp\/v2\/tags?post=335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}