A productivity system can create work of its own: choosing a label, updating a status, starting a timer, then doing it again when the next task begins. The useful question is which decisions need your judgment and which actions could follow information you have already provided.
There is a story about potatoes that captures that distinction.
A story about potatoes
A farmer hired an extraordinarily efficient worker.
On the first day, the farmer asked him to saw logs. By evening he had sawn more logs than anyone the farmer had ever hired. On the second day, he repaired fences just as quickly.
So on the third day, the farmer gave him what looked like a simpler task. He led him into the cellar and pointed to a pile of potatoes.
"Sort these into three piles," the farmer said. "The good ones we sell. The decent ones we keep for seed. The bad ones go to compost."
At the end of the day, the worker came upstairs and said, "I quit."
The farmer was shocked. How could someone who handled the harder jobs so easily struggle with sorting potatoes?
The worker explained:
Sawing logs and fixing fences is fine. But this potato business is decision after decision after decision.
The effort hidden in a simple task
Sorting potatoes looked like lighter work. But each potato required a fresh judgment: sell it, plant it, or throw it away.
The story draws a useful distinction between effort spent doing something and effort spent repeatedly deciding what to do.
In knowledge work, the surrounding questions can be just as familiar:
- Should I reply to this message now?
- Do I need to update my status before the call?
- Did I start the timer for the right project?
- Am I still signaling availability after finishing work?
Some of these decisions matter. Others ask us to maintain information our tools already have.
Two accounts of the same work
Suppose your calendar contains a client call followed by proposal writing. Changing your Slack status for each block repeats the intended context in a second place. If the call moves, that second account needs updating too.
Calendar-driven Slack status can remove that repetition by using the event you have already created to update your status.
Calendar-based time tracking can use the same context to categorize time, leaving you to review changes rather than enter everything again.
Decide once where a rule is enough
A useful automation rule might say: during a matching client call, communicate that you are occupied; outside working hours, apply the boundary you configured. ModePilot uses calendar events, schedules and mode rules for those kinds of transitions.
Keep an override for the unscheduled urgent review, the early finish or the meeting you leave halfway through. Automation earns its place by reducing repeated administration while leaving judgment with you.
The potato story offers a practical test for a workflow: which choices help the work, and which choices exist because the system keeps asking us to repeat ourselves?
