Hide table of contents

I've heard that if you've said something twice, you should write it down. The past few years I've had multiple career advice calls, mentoring calls, and one-on-ones at EA Globals about operations[1] and management in EA. I've set up a substack called 'Said Twice' to practice writing (feedback is very welcome!!) and to have a place where I can write down things I've said at least twice. The Career conversations week on the forum gave me the final push to actually finish some drafts and publish them here and on my substack. This is my first post, see here for my second one!

--

I love working with other people. I’m the most focused and have my best ideas when talking out loud, and I often rely on others to hold myself accountable. However, I work on a small team where we have each our own separate responsibilities, and so most of the time I work alone. The past five years I’ve found some workarounds that I thought I’d share. I use them daily at my job to cover parts of what I enjoy about working with others: talking through difficult issues out loud with someone else, building on each other’s ideas through brainwriting, delegating tasks that I find hard to do myself, and being held accountable by others.

1. Have meetings with myself (ideally walking)

Whenever I get stuck on something, or notice I'm struggling to wrap my head around a difficult issue, I schedule a meeting with myself. Most often, this means I go on a walk with my over-ear headphones and talk out loud, pretending I'm on a meeting call with someone else. If you worry less about what others think of you, you can of course do it without the headphones. 

I start the walking meeting by stating the purpose: “Why are me and myself meeting?”, “What are we hoping to get out of it?”. Sometimes it’s not clear what the purpose of the walk is, and in those cases I start with the questions: “What’s on my mind at the moment?” and “What’s holding me back from making more progress on the projects I’m working on?”. 

I then talk around the chosen topic(s), while I summarise the progress I make throughout the walk. I end the meeting by stating what we've decided and any next steps, which I write down as soon as I come back from the walk. 

I prefer using a familiar route for these meeting walks, so that I'm not distracted by having to find the way or look at new things. The walks last between 10-45 minutes, depending on how much me and myself have to talk about. I sometimes just talk to myself in the office or at my desk when I’m working from home, but I find that I’m more easily distracted inside — especially if I have my computer in front of me.

A very similar concept is rubber duck debugging, which you might be familiar with. This is more common for people working in tech where e.g. someone developing a program will go through their code line by line to figure out where the bug is, talking out loud to a rubber duck sitting on their desk. I personally have a crocheted turtle that my sister gave me that I use for this purpose:

Photo of a small crocheted turtle on a desk

2. Brainstorm (or -write) with myself

If I want to brainstorm ideas or options, and don't have anyone to do it with, I brainwrite. I do this for all kinds of tasks, and of different sizes. I’ll sometimes use it when I feel stuck with how to respond to an email. I’ve also used it for identifying possible goals and metrics for my work or our team. I mostly do it on paper or use my reMarkable, but you can also do it in Word or Google Docs. 

Here’s how I brainwrite with myself:

  1. Identify the exact topic I want more ideas on or options for.
  2. Create a mind map with the chosen topic in the middle.
  3. Set a timer for 2-5 minutes, and write down as many ideas as I can.
  4. Take a short break, e.g. get something to drink, walk around the block, go to the bathroom, do some stretches.
  5. Do a second round of 2-5 minutes where I either build on my previous ideas, e.g. add more details, or write down new ideas.
  6. When the time is up, if I feel like I have more ideas and thoughts, I’ll do a third round with another short break in between.

There are two important benefits to this technique. Firstly, setting a timer gives me some pressure and reduces the risk of spending too much time on the task. I also find that I produce more ideas through having a time pressure, as it lowers the stakes or amount of time I can spend to think whether it’s a good idea or not. Secondly, taking a break before adding new ideas allows me to reset my mind, and I find that it increases the chances of me coming up with additional ideas if I had just done it in one go.

3. Delegate to my other selves

I sometimes think of myself as three different people at work:

  • “Morning Eirin” who is confident, find it easy to make decisions, and can take on ughy or difficult tasks.
  • “Post lunch Eirin” who is easily distracted and is great at doing menial and small tasks.
  • “Afternoon Eirin” who gets in deep work-mode and can work on the same thing for hours.

I find it useful to "delegate'' different types of tasks to these three different versions of myself. If there’s a difficult email or a decision I need to make that I’m not sure about, I’ll leave it to “Morning Eirin” to figure out — she’s a lot more decisive and assertive. If I have multiple easy emails or admin tasks, I’ll assign them to “Post lunch Eirin” who might do them while listening to a podcast, watching a comedy show, or listening to the same one song on repeat (my current go-to song is a cover of Simply The Best by Billianne). “Post lunch Eirin” finds that listening to something or watching something helps her stay motivated as it directs all her non-work thoughts to one thing. If I need to work on a bigger project, I’ll carve out time later in the day, e.g. by moving meetings or going someplace where there are few distractions, and let “Afternoon Eirin” give her full attention to it.

For me, this technique helps me delegate a task I don’t feel as well-equipped to do at the time, which I might’ve delegated to other colleagues instead if I worked in a bigger team. 

4. Productivity check-ins

I’ll admit that it doesn’t always work like this — some days or weeks are more or less productive than others. Some days, only “Post lunch Eirin” shows up, and I need to use other techniques. One thing that’s really helped me to have fewer full weeks of unproductivity are weekly productivity check-ins. The past couple years I’ve had a 30 min productivity check-in with the same person almost every week. 

We each have our own checklists that we go through, and we then take turns talking about whatever is useful to talk about that week. We use a Google Spreadsheet as some of the questions we check in on ask us to put in a number (you’ll see below), and it makes it easier to compare over time and create charts. We also use conditional formatting on the number responses (good score is green, bad score is red), to make it more obvious how we’re doing. 

Here’s my checklist:

  • Have you done your goals since the last check-in?
  • On a scale from 1-5, how motivated do you feel? (1 = not motivated, 5 = very motivated)
  • On a scale from 1-5, how tired or drained do you feel? (1= very tired, 5 = not tired at all)
  • On a scale from 1-5, do you feel like you can say what the most important projects you're working on are? (1 = not at all, 5 = I have full control)
  • On a scale from 1-5, is there anything you're worried about, or might be falling through the cracks? (1 = a lot, 5 = nothing)
  • On a scale from 1-5, to what extent are you doing things someone else could be doing? (1 = a lot, 5 = nothing)
  • Are you procrastinating on anything? Do you know what the roadblocks are, and are you working on removing them?
  • What are you most proud of last week?
  • What lessons did you learn this week that you’d like to share?
  • What do you not want to do / any ugh fields / anything you feel ashamed about?
  • Are there any habits that aren’t serving you well?
  • Anything else you want to discuss that isn’t covered elsewhere?
  • Goals for next time:

Here are a few direct quotes from our spreadsheet that will give you an idea of the things I bring up every week:

  • Working on something this week that feels like such a big project and like I need to set aside a bunch of time to work on, but it’s hard to get started and I’ve kept postponing it. I think the size of the project is making me procrastinate. I should reduce the size!
  • I feel like I don't have enough time to do all of my tasks this week, and yet I want to do all of them. What should I do?
  • So many emails 😢 How can I get to inbox zero?? (this one comes up a lot)
  • There are some smaller todos that come out of our meeting that it’ll take me days to do when I could’ve just done them during the meeting or right after. I want to set aside 5 min after each meeting to get through as many todos as I can.
  • I'm considering deleting TikTok again, I’m spending a lot of time on it. Won't for now, but want to check in next week on whether I should.

Sometimes the thing that helps the most is just writing down what I’m feeling and thinking about, and from that I’ll figure out what the solution is. My productivity partner will also ask great questions such as “How important is it?”, “Is that actually true?”, and “What would you tell someone else in your position to do?”. Very often she’ll also provide useful advice from a time she struggled with something similar. 

We have our check-ins on Wednesdays at the same time every week, though move them if necessary. I’m confident that having these check-ins have increased my productivity on average, and because of them I very rarely have more than half an unproductive week. 

If you’re looking for someone to do these check-ins with, I recommend starting with people who are in similar roles to you. My productivity partner and I have similar backgrounds in EA community building, and both our jobs involve a lot of admin tasks and project management. It’s not necessary to have similar roles for this to be useful, but it means we can to a larger extent give each other helpful tips and share lessons learned. That being said, the biggest factor is definitely just having someone who expects you to meet up every week who’ll ask you questions about your productivity. 

  1. ^

    By 'operations' I mean project management and administrative work.

Comments7


Sorted by Click to highlight new comments since:

(huge missed opportunity not using the lonely Pablo meme as the splash image for this post imo)


 

I did consider calling it "four coping mechanisms if you're lonely at work" 🙃

Thank you for sharing these! I'm probably going to try the first three as a result of this post.

Thanks for taking the time to write this, Eirin! I love the "if you say things twice, write it down" rule from your other post. I'll think about setting something like this up for myself.
And I like the idea of having a productivity check in.

This is stellar advice! What's wild is, I have accidentally stumbled on each of these techniques at various points and just never really consciously identified the technique, which meant it wasn't repeatable at will. This post really crystallizes important options for me; definitely feeling some sheepish "shoulda figured that one out" combined with relief that you did it for me. THANK YOU.

Tori
1
2
0
1

Thanks for writing this! I love the walking meeting with yourself idea.

Great post; I enjoyed it.

I've got two things to say, the first one being that GPT is a very nice brainstorming tool as it generates many more ideas than you could yourself that you can then prune from, which is nice.

Secondly, I've been doing "peer coaching" with some EA people using reclaim.ai (not sponsored) to automatically book meetings each week where we take turns being the mentor and mentee answering the five following questions:

- What's on your mind?
 - When would today's setting be a success?
 - Where are you right now?
 - How do you get where you want to go?
 - What are the actions/first steps to get there?
 - Ask for feedback

I really like the framing of meetings with yourself, I'll definitely try that out.  

More from eirine🔸
47
eirine🔸
· · 7m read
54
eirine🔸
· · 6m read
Curated and popular this week
Paul Present
 ·  · 28m read
 · 
Note: I am not a malaria expert. This is my best-faith attempt at answering a question that was bothering me, but this field is a large and complex field, and I’ve almost certainly misunderstood something somewhere along the way. Summary While the world made incredible progress in reducing malaria cases from 2000 to 2015, the past 10 years have seen malaria cases stop declining and start rising. I investigated potential reasons behind this increase through reading the existing literature and looking at publicly available data, and I identified three key factors explaining the rise: 1. Population Growth: Africa's population has increased by approximately 75% since 2000. This alone explains most of the increase in absolute case numbers, while cases per capita have remained relatively flat since 2015. 2. Stagnant Funding: After rapid growth starting in 2000, funding for malaria prevention plateaued around 2010. 3. Insecticide Resistance: Mosquitoes have become increasingly resistant to the insecticides used in bednets over the past 20 years. This has made older models of bednets less effective, although they still have some effect. Newer models of bednets developed in response to insecticide resistance are more effective but still not widely deployed.  I very crudely estimate that without any of these factors, there would be 55% fewer malaria cases in the world than what we see today. I think all three of these factors are roughly equally important in explaining the difference.  Alternative explanations like removal of PFAS, climate change, or invasive mosquito species don't appear to be major contributors.  Overall this investigation made me more convinced that bednets are an effective global health intervention.  Introduction In 2015, malaria rates were down, and EAs were celebrating. Giving What We Can posted this incredible gif showing the decrease in malaria cases across Africa since 2000: Giving What We Can said that > The reduction in malaria has be
LewisBollard
 ·  · 8m read
 · 
> How the dismal science can help us end the dismal treatment of farm animals By Martin Gould ---------------------------------------- Note: This post was crossposted from the Open Philanthropy Farm Animal Welfare Research Newsletter by the Forum team, with the author's permission. The author may not see or respond to comments on this post. ---------------------------------------- This year we’ll be sharing a few notes from my colleagues on their areas of expertise. The first is from Martin. I’ll be back next month. - Lewis In 2024, Denmark announced plans to introduce the world’s first carbon tax on cow, sheep, and pig farming. Climate advocates celebrated, but animal advocates should be much more cautious. When Denmark’s Aarhus municipality tested a similar tax in 2022, beef purchases dropped by 40% while demand for chicken and pork increased. Beef is the most emissions-intensive meat, so carbon taxes hit it hardest — and Denmark’s policies don’t even cover chicken or fish. When the price of beef rises, consumers mostly shift to other meats like chicken. And replacing beef with chicken means more animals suffer in worse conditions — about 190 chickens are needed to match the meat from one cow, and chickens are raised in much worse conditions. It may be possible to design carbon taxes which avoid this outcome; a recent paper argues that a broad carbon tax would reduce all meat production (although it omits impacts on egg or dairy production). But with cows ten times more emissions-intensive than chicken per kilogram of meat, other governments may follow Denmark’s lead — focusing taxes on the highest emitters while ignoring the welfare implications. Beef is easily the most emissions-intensive meat, but also requires the fewest animals for a given amount. The graph shows climate emissions per tonne of meat on the right-hand side, and the number of animals needed to produce a kilogram of meat on the left. The fish “lives lost” number varies significantly by
Neel Nanda
 ·  · 1m read
 · 
TL;DR Having a good research track record is some evidence of good big-picture takes, but it's weak evidence. Strategic thinking is hard, and requires different skills. But people often conflate these skills, leading to excessive deference to researchers in the field, without evidence that that person is good at strategic thinking specifically. I certainly try to have good strategic takes, but it's hard, and you shouldn't assume I succeed! Introduction I often find myself giving talks or Q&As about mechanistic interpretability research. But inevitably, I'll get questions about the big picture: "What's the theory of change for interpretability?", "Is this really going to help with alignment?", "Does any of this matter if we can’t ensure all labs take alignment seriously?". And I think people take my answers to these way too seriously. These are great questions, and I'm happy to try answering them. But I've noticed a bit of a pathology: people seem to assume that because I'm (hopefully!) good at the research, I'm automatically well-qualified to answer these broader strategic questions. I think this is a mistake, a form of undue deference that is both incorrect and unhelpful. I certainly try to have good strategic takes, and I think this makes me better at my job, but this is far from sufficient. Being good at research and being good at high level strategic thinking are just fairly different skillsets! But isn’t someone being good at research strong evidence they’re also good at strategic thinking? I personally think it’s moderate evidence, but far from sufficient. One key factor is that a very hard part of strategic thinking is the lack of feedback. Your reasoning about confusing long-term factors need to extrapolate from past trends and make analogies from things you do understand better, and it can be quite hard to tell if what you're saying is complete bullshit or not. In an empirical science like mechanistic interpretability, however, you can get a lot more fe