Here's a productivity technique I've been using for a month and has worked really well. It reduces distraction, focuses effort, and sets targets. It assumes most of your tasks accumulate as emails. I'll explain it in a short thread. ↵
Some of my inbox entries are big tasks that require a lot of thinking: e.g., correspondence with research colleagues on experiments, results, and papers. They take time and require me to engage deeply. Often interleave email, calls, and shared docs. ↵
But several things are small and, for external reasons, annoying. Examples: I need to: authenticate into a site, look up some info before replying, handle a few things similarly, add entries to a calendar, etc. ↵
These are "death by a thousand cuts" emails. There's a few a day. Each takes only 2-3 minutes to handle (maybe even less), but we know the cost of context-switching. These destroy my concentration, peace of mind, and joy. ↵
There's another category, which is personal email. They're from friends or acquaintances. I'd like to write a longer, personal reply, but really not in the middle of the workday when they're at the top of the mailbox. ↵
Traditionally, only 2 things I can do (often both!). Leave them in there, staring at me accusingly, distracting me, making me feel guilty. Or deal with them now, breaking concentration, feeling like I "got nothing done all day" (and maybe shorter personal mail than I wish). ↵
One more observation that is true of most of these: they don't need to be dealt with right away. This actually makes it worse, since you're ALWAYS wondering WHEN to deal with them. It's like a multi-arm bandit problem. The bandit robs us of time, concentration, joy. ↵
But they don't need to be done right away, right? Gmail Snooze: problem solved! Figure out when you want to do them, snooze until then, they come up then, deal with them at that point. Voilà! But that has not worked at all for two reasons. ↵
First: I was constantly having to think about *when* to snooze to. And often increasingly complicated over-thinking ("Tue PM? Wed night? Oh wait…"). My concentration was destroyed *just deciding when to snooze to*. ↵
Second: When it showed up, I wasn't necessarily ready. Something else may have come up (colleague needs urgent feedback, etc.). So now they're back staring accusingly at me. Now with extra Gmail meta-chroming saying the bandit is back. Even MORE stress. ↵
Third: They're in there with lots of other email. Those others are distracting me. And as I'm dealing with these, new ones are coming. It's all a big mess that is an even bigger source of stress. No better than before, heck, maybe even worse. Snooze was failing badly. ↵
Hopefully I have laid it out clearly enough that the answer is obvious to you, even though up front it wasn't to me. Here is my solution: a new Gmail label. (Before you pounce on the name, read on.) ↵
So when these little tasks come up, I eyeball them to check they aren't urgent (or even guess they aren't), and *MOVE them straight into that folder*. They're out of my inbox. Totally out of sight. (NB: I have the label always show, even when empty.) ↵
This has the benefit of Snooze, in that it's taken the message out of my current field of vision. Unlike Snooze, I didn't have to think about when to move it to: the label already says when. (One weakness: unlike Snooze, which automatically awakens messages, this does not.) ↵
Note that this now leaves Snooze to do what it does well: sleep messages until specific dates/times. E.g., I'm expecting a reply from X on Y, I can Snooze the thread until the time I want to be reminded about it. Alarm clocks ≠ folders; Snooze is an alarm clock, not a folder. ↵
Okay, so back to the folder. On the weekend, I make time to get through it. Note that if I leave things unread before putting them in the folder, the folder count shows me how many things are in there. Gives me some sense of the task list length. ↵
Here's the beauty of it. When the time comes, I go to that folder. I see ONLY what is in that folder. Nothing else. No other emails interleaving. No weird snooze color chroming. That folder is the stuff I have to get through. ↵
Think of how you might process paper mail. You don't check every letter as soon as it's delivered. In the evening, you pick up the mail and sort it. You might even accumulate it to the weekend. You then set aside time for it. Same deal here. ↵
My one goal is, "Weekend Work inbox" zero by the end. It's all got to get cleaned out. I'm allowed to move it somewhere else, add things to todos, make github issues, whatever. But it's got to be clear by the end. ↵
The biggest benefit is during the week. I ruthlessly move things into that folder. The annoying administrative things (e.g., authenticate to check this bill or sign off on that document or whatever) never distract. Most, I just *know*, without even reading, I can put off. ↵
In fact, I will freely put duplicates and more in there. E.g., I had several reminders this week about final grades. I was pretty sure I'd already put those emails in that label. Still, when new mails about it came, I moved them there anyway. ↵
I didn't even check whether they were duplicates. Didn't want the distraction. Didn't want to miss any, so I put them there. But if I found they WERE duplicates on the weekend, hey, it meant I had fewer things to do. Reader: there were several duplicates. Score. ↵
When I open the folder, I put myself in a "boring" state of mind. I know there will be lots of annoying little logins and clicks and pedantry. I might have a sports match in the background, or music, or a snack, or something. But what I've found is: ↵
Those tasks are not REMOTELY as annoying when I do them in their assigned "down" time as when they interrupt my flow. Flow state is so hard to get, details are so hard to hold in my head, they really hurt. ↵
During this weekend slot, they barely register: they're like a low-order numbness than a high-order pain. And I feel good that this enabled me to have a better past week, and by doing this, I'll have a better next week. I can actually feel the virtue. (-: ↵
Hopefully you can see that all the issues raised earlier in the thread are addressed by this process. I've been doing it for a month and it works great. Of course you don't have to do it on the *weekend*. You just have to set aside time to do it (just like paying bills). ↵
There is one criticism I know some of you have been itching to make (and have probably long since made): "Oh, look, US academia is so awful, it forces people to work on the weekends". I want to make clear this is a bad reading of my situation. ↵
US academia gives me the freedom to structure my time sensibly, and I aggressively take advantage of it. Most weekday afternoons I ride or run or do something else physical. I'm typically "out" minimum 1, almost always 1.5, often 2+ hours. (Plus showers, etc.) ↵
I choose to move some of that time to the weekend. There are weekend hours with family that are inviolate. In terms of exercise, weekends are often my rest days. So I "remix" my week and move some of those work hours to the weekend. ↵
I'm incredibly privileged to be in a time, place, discipline, and institution that let me figure out how to be most productive. In grad school, it meant working midnight to 6am. Now it means moving some week hours to the weekend. It's good, really. ↵
I appreciate that I have a lot of things going for me that let me do this. The parameters depend on lives of others: e.g., when my kid has chess. But the general *idea*, of blocking off time for "death by a thousand cuts" or personal emails, is one I intend to keep. ↵
If you try it and it works well for you, let me know. If you try it and it doesn't work well, all the more reason to let me know! I hope this is of some use. Help me make it better! Thanks and good luck. (-: •••
If you want to read this all in one place, skip this thread and go to my blog post:
parentheticallyspeaking.org/articles/bandi…
"Your Inbox is a Bandit"

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with ShriramKrishnamurthi

ShriramKrishnamurthi Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @ShriramKMurthi

25 Aug 20
This is a #BookReview of a book I wish I'd read a long time ago: @Ram_Guha's "India After Gandhi". If your Indian education was like mine, I think you'll want to read it. I also know this will irritate some of my Indian friends (but do read through). Here goes: [thread»]
Guha's premise is that Indian history has tended to halt at 1947 (or 30 Jan 1948). Everything after that is sociology or political science. He wants to fix that, and spends over 900 pages doing so. I found the book gripping and wanting more. »
My hunger was stoked by my so-called education in social studies. History and civics were about memorizing, not analyzing. I could name a 100 kings but not tell you what any stood for. We had a vague sense of an Indian nation, hundreds of miles wide but an inch deep. »
Read 28 tweets
15 May 20
@bodil This is how you know Racket is a production tool meant for real software engineers, whereas the student languages are obviously not. If it can't generate confused SO posts, it doesn't really exist in the professional's mind. Without struggle, there is no triumph. »
@bodil More seriously: over the years, I've come to feel that slightly inferior technologies are better — not in the Gabriel sense but because they create communities (of support and help) and ecosystems (of tools). It's my own theory of worse-is-better. »
@bodil Every "tool" is actually a "weakness", but it keeps a community together. There's a way for people to contribute. It's like a game that leaves little bonuses lying around. If a novice can make a small contrib, even better. They feel good, and now they've made a commitment. »
Read 6 tweets
11 Apr 20
@maxsnew @samth To begin with, imagine if someone wrote an article about education from the perspective of videoconf tools. You'd think that's a tiny part of what goes into education, and maybe this is missing the big picture. Ditto an economics perspective. »
@maxsnew @samth Why would an emergency shift to online "accelerate a permanent shift"? If you have a building problem and someone brings in a temp trailer, do people assume we'll stay in the trailer forever? But the very phrase assumes a strong trend that doesn't really exist. »
@maxsnew @samth This old trope about "online superstars" has been played out. This is what everyone thought about MOOCs, too. And yes, there's a bit of preferential attachment. But it didn't put everyone else out of business. »
Read 25 tweets
7 Feb 20
I see increasing calls for conferences to allow remote presentation. This is a terrible idea that will ultimately lead to good things. Some thoughts. »
I understand the motivation. Travel is expensive. Visas are hard. CO2 is a thing. Harder still with mobility/health issues or living far from the action. And they're gatekeepers. »
But here's the thing. Conferences are not primarily meant as write-only media. It's in the very name (roots: conversation, getting together). Focusing on talks misses most of the value. »
Read 11 tweets
31 Jan 20
@yminsky @hillelogram I'll do my best. Here's my story. I was asked to teach upper-level software engineering many years ago. How hard can it be, I thought. I do SE, I publish in all the major SE confs, this should be easy. I got about a dozen SE books to read over winter break to design my course. »
@yminsky @hillelogram Something happened to me that NEVER happens to me. Middle of the day, deep in the middle of SE books, I was falling asleep. Like actually going out. I knew I couldn't in good conscience use such a book with my students. As this kept happening, I was panicking. »
@yminsky @hillelogram Then I realized the problem: it's all abstractions up front. (And more than a bit of what Spolsky calls architecture astronautics.) It was clear that if I began my classes the same way, I would kill my students. Had to find another way. »
Read 15 tweets
30 Nov 19
@krismicinski @tikhonjelvis Deeply controversial opinion. I love EOPL and was "raised on it", but I don't love it the same way any more. It's a great book *for people like me* (going on to get a PhD in PL). Not AT ALL sure it speaks to the "coder on the street". »
CC @AustinZHenley @tomgilray
@krismicinski @tikhonjelvis @AustinZHenley @tomgilray I wrote PLAI as a response to that (plai.org). It *intersperses* uses of concepts with their definition, and *precedes* use before definition. (Hence App followed by Impl in title.) Need to motivate these ideas for students. »
@krismicinski @tikhonjelvis @AustinZHenley @tomgilray A driving principle in my PL education thinking has been, "How do I successfully communicate with the other 90%?" That is, the 90% who won't go on to get a PhD in CS (10% is probably generous, maybe 1% will…so more like other 99%). They are NOT LIKE US. »
Read 24 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!