For many goals, the once-a-day deadline is a good level of granularity.
For some goals, multiple increments would seem more appropriate.
Let’s say I have the goal of completing 8 Pomodoro sessions per day, with a deadline at 4pm. This will take 4h. I have to start at noon to have a chance of making the deadline, but if I start this late, I have to complete all eight sessions back-to-back, can’t eat anything, can’t take any other breaks, etc. You might say “just start earlier then”. That is indeed what I would like to do, but my Akrasia will push the start-time closer and closer to 12pm (if I wasn’t so akratic I wouldn’t be using beeminder in the first place).
Multiple deadlines per day (a waterfall for a single goal) would mean being able to space the work more evenly between, say, 8am and 4pm, allowing for lunch breaks and other gap-filling activities in the meantime.
Has anyone encountered the same issue with some of their goals and found a good workaround?
Using the API, one could probably make a script which does two things:
(a) Given a do-more goal, it automatically adds multiple checkpoint-goals which all have the same original rate, but both the roads and deadlines are shifted w.r.t. each other.
(b) Each data point added to the original goal should be automatically “forwarded” to all checkpoint-goals.
One could of course do (a) manually, but there are tricky aspects to it, such as ensuring the checkpoint goals stay in-sync after a derailment.
Any thoughts on how to go about this?