let me dig this topic out after some time.
I hate Beeminder notifications. Once in a while I turn them on back again and after a few days I notice the same pattern: I learn to ignore them pretty fast, and I turn them off again.
The reason is simple: they are too simplistic. I’ve had an elaborate “ladder” of goals with different deadlines for some time now, though I don’t rely on that now anyway, since I devised my own nannybot. Currently it is also quite simplistic (it’s only a paper-and-pencil solution for now), but I plan to make it into an app (though this is a big project and will have to wait). In fact, my solution is pretty elaborate even now – here are a few highlights.
It is pretty tightly integrated with Beeminder, on two different levels.
A. I have a bunch of ongoing projects (“creative writing”, “coding (for side projects)”, “studying” and “translation work” are the main/most time-consuming ones). They all have a rate of 20 minutes per day and max safety buffer of 4 days; some of them are weekends-off.
B. I have a Beeminder goal called “ps” (as in “productivity score”), with a rate of 8 “productivity points” per day.
Every day (almost) I prepare a list of 12 bullet points - tasks for the next day. There are a few kinds of those tasks, but most of them fall roughly into these two categories:
A. “do X, any time next day”. Obvious.
B. “Spend some fixed timespan (usually one «tomato», i.e. 25 minutes) of work for some project, though not necessarily in one go, until some fixed time”.
I have a weekly schedule, crafted so that I can actually manage it and it matches my wife’s schedule (she’s a teacher, until recently we’ve had only online classes in Poland, soon it will be part online, part offline, so I’ll have to modify my schedule). For instance, on Mondays I do coding from 515 to 615 (two “tomatoes”), then creative writing (from 645 to 715 and from 745 to 815). And yes, these are AM hours . Notice how I have a 5-minute buffer for things like making myself some tea, a visit to the “debugging room” (a.k.a. bathroom) etc. (I can also start at e.g. 505 to have a larger buffer, and I sometimes do it.). Notice also two 30-minute breaks – the former one is for groceries and the latter one is for preparing the room for my wife’s classes (our bedroom doubles as her workspace during the working hours). Then I have an unplanned chunk of a few hours (breakfast, caring for my 4.5-yo son etc.), then again: 1100–1130 coding for my day job and 1130–1200 translation work. When my wife finishes her classes (about 1330), I have some time to prepare to work and I leave for the office. There, I have three tasks: doing 90 minutes of work until 1700, another 90 minutes until 1900 and 45 minutes until 2000. (Incidentally, this means that I work less than average on Mondays.) These make for 9 tasks, so on Monday I have 1 free slot for whatever comes up. (Two slots are for special everyday tasks: closing my laptop for the day until 2145 and going to bed until 2215. Since I can’t enter a Beeminder datapoint after I closed my laptop and phone, these tasks go formally to the next day’s batch, so if I manage to close my laptop until 2145 and go to bed until 2215 on Monday, I get 2 “productivity points” on Tuesday.)
So, here’s why Beeminder could not work as a nannybot for me:
- These tasks are different per day of the week. On Tuesdays I don’t do creative writing (I’d love to, but there are only so many hours in a day!), but I devote some time to studying instead.
- The precise hours also change per day of the week – my wife’s classes start at 800 on Mondays, but 850 on Tuesdays, so I plan my timeboxes accordingly.
- All these tasks are flexible – sometimes we have a doctor’s visit or something else comes up, so I need to change the schedule for this day. And I can’t really do that on a week’s notice (like I’d do in Beeminder), since these things sometimes come up with 1–2 days’ notice only.
This system also has some shortcomings. The idea of 12 points per day is nice, but the number really should be variable – but my brain’s computing power is limited and I decided to go KISS with this analog solution. Also, the number of productivity points per task probably should vary depending on the effort needed (although not in a linear way) – see above why I haven’t implemented it. Also, I’d love to gamify this even more with bonus points for completing tasks ahead of time (by some amount decided earlier). Again, a bit too complicated for now.
So, does anyone like this solution? Any suggestions? Also, any volunteers to try out a nannybot-type app supporting such a use-case if/when I actually start working on it?