{"id":833,"date":"2017-02-06T21:30:16","date_gmt":"2017-02-06T21:30:16","guid":{"rendered":"https:\/\/aciref.org\/?p=833"},"modified":"2017-02-06T21:30:16","modified_gmt":"2017-02-06T21:30:16","slug":"three-ways-to-productivity","status":"publish","type":"post","link":"https:\/\/aciref.chpc.utah.edu\/?p=833","title":{"rendered":"Three Ways to Productivity"},"content":{"rendered":"<p>\t\t\t\tAs someone with a lot to do at work (tickets! meetings! reports! documentation! workshops! community-building!), I often consider how I can optimize my work time. Like a good scientist, I try lots of approaches and some of my experiments are more successful than others.\u00a0 This post describes three &#8220;success stories&#8221; &#8212; using a simple technology, finding a time management system that works for me, and embracing a reproducible workflow.<\/p>\n<h2>1. Sign In Sheet<\/h2>\n<p><strong>Problem<\/strong>: New user accounts are tracked in our account management system, but it was difficult to track who was coming to office hours.<\/p>\n<p><strong>Solution<\/strong>:\u00a0 We now have a clipboard with a sign-in form at our office hours table and we have researchers fill in the date, their name, their department, and why they&#8217;re here.<\/p>\n<p><strong>Advantages<\/strong>:\u00a0 Now it&#8217;s very easy to enter that information into a spreadsheet and use it for reporting.<\/p>\n<p><strong>Unexpected advantages<\/strong>: If we&#8217;re very busy at office hours, having researachers sign-in gives us a way to interact with them immediately and give them the reassurance that we know they&#8217;re there.\u00a0 When we become free, we can then check why they came so that we&#8217;re primed to start interacting with them.\u00a0 Also, if we don&#8217;t recognize someone on sight (which happens, when you meet with hundreds of people in a year!), we have a cheat sheet.<\/p>\n<blockquote><p>Lesson learned: Sometimes a very simple, &#8220;non-technical&#8221; solution can have a really big impact.<\/p><\/blockquote>\n<h2>2. A Plethora of Post-Its<\/h2>\n<p><strong>Problem<\/strong>: Until a few months ago, I used a planner for my day-to-day task management.\u00a0 Meetings and appointments were scheduled through my calendar, but I would write down individual tasks in my planner by hand.\u00a0 However, I was frequently overwhelmed by tasks and\/or ran out of space in my planner.\u00a0 It was hard to know where to put ongoing tasks that were either &#8220;do as necessary&#8221; or &#8220;need to be done, but could wait until tomorrow.&#8221;\u00a0 I ended up re-writing many medium\/long-term tasks from day to day, or even week to week, just to make sure I didn&#8217;t forget about them.<\/p>\n<p><strong>Solution<\/strong>: I independently arrived at an approach that already exists &#8211; <a href=\"https:\/\/en.wikipedia.org\/wiki\/Kanban_board\">a kanban board<\/a>.\u00a0 In my implementation, each task gets written up on a post-it note and placed under the appropriate category.\u00a0 <a href=\"https:\/\/aciref.chpc.utah.edu\/wp-content\/uploads\/2017\/02\/IMG_20161104_173953.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-834\" src=\"https:\/\/aciref.chpc.utah.edu\/wp-content\/uploads\/2017\/02\/IMG_20161104_173953-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" srcset=\"https:\/\/aciref.chpc.utah.edu\/wp-content\/uploads\/2017\/02\/IMG_20161104_173953-300x225.jpg 300w, https:\/\/aciref.chpc.utah.edu\/wp-content\/uploads\/2017\/02\/IMG_20161104_173953-1024x768.jpg 1024w, https:\/\/aciref.chpc.utah.edu\/wp-content\/uploads\/2017\/02\/IMG_20161104_173953-768x576.jpg 768w, https:\/\/aciref.chpc.utah.edu\/wp-content\/uploads\/2017\/02\/IMG_20161104_173953-1536x1152.jpg 1536w, https:\/\/aciref.chpc.utah.edu\/wp-content\/uploads\/2017\/02\/IMG_20161104_173953-2048x1536.jpg 2048w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a>I use 4 categories:<\/p>\n<ul>\n<li><span style=\"text-decoration: underline;\">To Do<\/span>: Anything that *needs* to be done in the next few weeks (tickets + user follow-up, special requests, action items from meetings, planning for workshops, reports at the end of the month)<\/li>\n<li><span style=\"text-decoration: underline;\">Delegated<\/span>: Items that I&#8217;ve handed off to someone else.<\/li>\n<li><span style=\"text-decoration: underline;\">Done<\/span>: Completed work!<\/li>\n<li><span style=\"text-decoration: underline;\">Dreams<\/span>: Things I want to do but don&#8217;t have time for (or are not currently prioritized)<\/li>\n<\/ul>\n<p>As items are completed, delegated or de-prioritized, I move them around the board.\u00a0 I also have a &#8220;working space&#8221; at the bottom of the wall where I put the items I want to complete that day.\u00a0 Uncompleted items get left for tomorrow or moved back into the general &#8220;to do&#8221; area.\u00a0 At the start of every week, I throw away my &#8220;Done&#8221; post-its (after writing my weekly effort report) and begin again.<\/p>\n<p><strong>Advantages<\/strong>: Because I&#8217;m using one space, I don&#8217;t need to keep re-writing things when they&#8217;re not done (or urgent).\u00a0 The creation of a category where I can put all my good ideas (&#8220;Dreams&#8221;) reassures me that I won&#8217;t forget about them, but it also takes away the urgency\/guilt of not accomplishing them right away.<\/p>\n<p>This system has also helped me prioritize my work by putting everything on &#8220;one page&#8221;; I can quickly scan my wall and ask &#8220;What <em>has<\/em> to be done today?&#8221; and select those tasks for my working area.\u00a0 And while I may run out of space someday, for now, I can usually write down even small tasks to make sure I won&#8217;t forget to do them.<\/p>\n<p>One psychological benefit is the visual evidence (as post-its flow into the &#8220;Done&#8221;\/&#8221;Delegated&#8221; categories) that I am getting work done.\u00a0 If there aren&#8217;t any &#8220;Done&#8221; post-its after a few hours at work, it usually means that I need to break down a bigger task into more, smaller post-its or actually write down some of the day-to-day work I&#8217;m doing.\u00a0 There&#8217;s also something victorious about emphatically moving a post-it into the done category &#8211; much like crossing out items in a list.<\/p>\n<p>Keen eyes may note that this system is also similar to the <a href=\"https:\/\/trello.com\/\">Trello<\/a> project management system (with &#8220;boards&#8221; and &#8220;cards&#8221;).\u00a0 This physical model works better for me because it&#8217;s more flexible, accommodating my particular style of map-like processing.<\/p>\n<p><strong>One disadvantage<\/strong>: It&#8217;s not very portable.\u00a0 I&#8217;ll sometimes put the post its on my laptop if I&#8217;m moving to a new location for the short term and need the reminder for what I&#8217;m working on.\u00a0 Also, for people who like lists and lots of structure, this may be a bit too chaotic!<\/p>\n<blockquote><p>Lesson learned: Find a system that works for you (planner, calendar, email), no matter how strange it looks.<\/p><\/blockquote>\n<h2>3. Reporting with Rmarkdown<\/h2>\n<p><strong>Problem<\/strong>: I was not getting around to finishing our monthly activity reports. The reports were wordy, it wasn&#8217;t clear where to put certain items and I had to do a lot of manual work to produce the underlying data.<\/p>\n<p><strong>Solution<\/strong>: This was a multi-part solution, but the biggest change was to move to a more &#8220;template&#8221; report by using the Rmarkdown\/Knitr features of R and RStudio.\u00a0 As part of this transition, anything that could be scripted, was.\u00a0 A sample of what this looks like now is here: https:\/\/github.com\/ChristinaLK\/facilitation_reports<\/p>\n<p><strong>Advantages<\/strong>: It&#8217;s still a lot of work to create the monthly report, but now I have a set of clearly defined steps to follow:<\/p>\n<ul>\n<li>Run scripts to create monthly data analysis<\/li>\n<li>Run scripts to create weekly breakdown of compute hours<\/li>\n<li>Finish entering user engagement data<\/li>\n<li>Add individual stories or events in 3 clearly defined sections<\/li>\n<li>Render<\/li>\n<\/ul>\n<p>One advantage to this approach is that it requires my data to be more organized and better formatted, an effort that has been supported by point 1 in this post.\u00a0 \ud83d\ude42<\/p>\n<p>It&#8217;s also just fun &#8212; there&#8217;s a thrill to clicking the &#8220;knit&#8221; button every month and producing a pretty fancy-looking report with minimal effort.<\/p>\n<blockquote><p>Lesson learned: Structure your data! Automate repetitive tasks! Make your work reproducible!<\/p>\n<p>Thanks <a href=\"https:\/\/software-carpentry.org\/\">Software Carpentry<\/a> and <a href=\"http:\/\/www.datacarpentry.org\/\">Data Carpentry<\/a>.<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>As someone with a lot to do at work (tickets! meetings! reports! documentation! workshops! community-building!), I often consider how I can optimize my work time. Like a good scientist, I try lots of approaches and some of my experiments are more successful than others.\u00a0 This post describes three &#8220;success stories&#8221; &#8212; using a simple technology, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-833","post","type-post","status-publish","format-standard","hentry","category-experience"],"_links":{"self":[{"href":"https:\/\/aciref.chpc.utah.edu\/index.php?rest_route=\/wp\/v2\/posts\/833","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aciref.chpc.utah.edu\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aciref.chpc.utah.edu\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aciref.chpc.utah.edu\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/aciref.chpc.utah.edu\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=833"}],"version-history":[{"count":0,"href":"https:\/\/aciref.chpc.utah.edu\/index.php?rest_route=\/wp\/v2\/posts\/833\/revisions"}],"wp:attachment":[{"href":"https:\/\/aciref.chpc.utah.edu\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=833"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aciref.chpc.utah.edu\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=833"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aciref.chpc.utah.edu\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=833"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}