Whittle Down goals

The canonical Whittle Down use case is reaching Inbox Zero — this goal type was even once called Inbox Fewer. But it's useful for other things too!

When should I use a Whittle Down?

Whittle Down goals are best used when you're trying to whittle down a backlog over time. Similar to an Odometer, you'll want to know your daily total backlog size, which you want to be reducing over time.

Common examples: managing inbox size, reading Pocket articles, grading assignments, watching downloaded movies, completing lessons in a MOOC.

Why can't I set my rate while I'm setting up my goal?

When you create a whittle-down goal, it starts out flat. Once you've set it up, go to the "Commitment" tab of the goal:
Text says: "Commitment Dial: Dialing your red line means changing your commitment starting a week from now. This will adjust the final segment of your red line graph, so if you already have graph changes upcoming, you might want to use the more powerful graph editor to make changes to your commitment." Below, a stepper allows you to select the rate per day, or you can just enter the number you want if it isn't an integer. The "Commit" button sends us your changes. Below there's a button to "Change goal date and goal value", which opens a more sophisticated rate editor.
If you want to get rid of 10 units (e.g. emails) per day, then enter -10 in the rate box. If you want to make sure you don't have to get into negative numbers of emails, click on "Change goal date and goal value". That will open up this editor:
"Commitment dial", showing the more advanced editor where you can set two of "goal date", "goal value" and "rate".
You can only edit two of those fields; the greyed-out field is auto-calculated from the others. So if you want to do -10 emails per day until you reach zero, set the rate to -10, and then set the "Goal value" field to 0. The goal date will be greyed out and it will automatically calculate the day you hit inbox zero!
"Commitment dial", showing another example where the greyed out field (date) is auto-calculated, while the user has picked 0 for the goal value and -10 for the rate.
If you derail in the meantime, the goal date will be revised to take into account the setback.

(These examples show the units as books, and if that's what you're tracking then we strongly suggest you're actually a bit more conservative and set a rate of 0.1 per day, or whatever matches your reading pace!)

How should I enter data for a Whittle Down?

Beeminder needs to know your current total of whatever you're beeminding each day, e.g. the number of emails remaining in your inbox, not the number of emails you archived today.

So for example, say I have a goal to clear out my inbox over time, and I've set my rate to -10 emails per day, and I had 500 emails in my inbox at the start of the goal. I archived 20 emails on the first day, putting me at 480 emails in my inbox, so I submitted a 480 to my graph. The next day, I archived 30 more emails and get to 450 remaining, so I submitted 450 to my graph. The next day, I only dealt with 5 emails, so I submitted a 445. And so on.

After those three points have been submitted, the graph will look like this:

Example graph showing that the data has been entered as 500, 480, 450, and then 445

I'm below my bright red line — doing better than my goal rate! Cool.

What happens when I reach 0?

If your graph is configured to end at 0, the goal will end once you also reach the end date (either the one implied by the rate and the end total, or the one you set specifically). You need to stay at 0 until the end date, so watch out if you're using any kind of automatic data reporting! Once the goal ends, you can restart it if you'd like to maintain a certain maximum value.

If your goal doesn't have an end-total set, your graph may continue decreasing, eventually asking you to get to a negative total. This is usually not possible, of course! You can prevent that by configuring the goal to end at 0, or setting the rate to 0 at the backlog size you want to maintain. If your graph is asking you to do something impossible, contact support and we'll help you get that sorted out.

Example of a goal that's set up with a goal date and goal rate, meaning you have to reach negative numbers of email:

"Commitment dial" example where "goal value" is the greyed-out field, so the rate of -10 means you have to reach -28530 emails total by the goal date.

To fix that situation, in the screenshot below the goal date is set to 2022-03-15, and the goal total to 0. The rate will be automatically calculated, and the graph will end when I reach 0 emails remaining and the date is 2022-03-15.

"Commitment dial" where the goal date and goal value are set, and the goal rate is auto-calculated, so you have to reach 0 emails by 2022-03-15 at a rate of -9.15 emails per day

What happens if I need to restart my count at a higher number?

If the goal has ended or been archived, you'll be prompted for your current value when restarting, and we'll start your graph in the right place.

If the goal is still active, you can use Take a Break or the Graph Editor to schedule a jump in the graph at least 7 days in the future. When the line jumps, you can input your new count safely. Or if you need to derail because you should've kept up with it (we've all been there), you can just enter the new figure and allow your goal to derail. Your slope will automatically resume from that higher point after the derailment.

How can I pause my Whittle Down goal temporarily?

This is easy to do on a Whittle Down! Using the Take a Break section in the Stop/Pause tab below the graph, first pick the dates that you'll be away, then set the break rate to 0. This will make your graph flat at that time, so you don't have to make any progress until it starts sloping down again. Don't forget, you need to make the change seven days in advance.

You'll need to make sure that no data enters the graph while you're away. If an automatic data source enters a value that lands above your bright red line, even on your break, you will derail. This is definitely not legit and we'll sort it out in support, but stopping the data source will prevent it from happening in the first place! If you're using our Gmail integration, you might want to select a label you know will stay empty, for example.

Why did I derail when I had 15 safe days yesterday?

Whittle Down goals are not incredibly forgiving when your data value can bounce up and down a lot. The "safe days" estimate Beeminder uses assumes that your data moves in one direction only. But things like your inbox size can increase as well as decrease, so the "safe days" estimate may be blown away if you receive an unexpected deluge of emails that takes you over the limit.


Keywords: inbox fewer, non-cumulative goals

Still need help? Contact Us Contact Us