remblanc remarks

bento method

Sep 30, 20244 min read

preface

bento method was originally devised by Francesco D’Alessio of the Tool Finder YouTube channel to pitch an iOS app that i bought but was severely disappointed by, as well as two paid time management courses ppl seemingly didn’t receive particularly well, especially given that he dropped the “version 2.0” of the course separately from the first one, pissing off plenty of people who bought the first one.

nebulous advice selling aside, this method actually resonated with me quite a bit, and i have managed to successfully incorporate it into my routine and have fun with planning out time using it.

since i am a cheapskate and i did not buy the course, my homebrew version of this method, as described on this page, might differ somewhat from the version described in the course. it is, however, based on my interactions with the official bento app, as well as the information i got from all the related content made by Francesco:

my understanding of the method is based on practical application of all the basics i have gotten from the app [the entire app is basic, honestly]: scheduling, task assignment and timetabling, etc., with additional experimentation being introduced after i found out what the gimmick of the 2.0 method is.

from my experience, this is a very good way to plan out work for a given chunk of time: it’s a solid foundation that offers just the right amount of precision to be easy to understand, with enough flexibility to plan the day without much effort involved.

method description

this method is intended to be used as a companion to an existing productivity framework: if you are just starting out and want to give this a spin, whip out your notes, or a to-do list, and keep a time tracker on the side [an ordinary timer may suffice, you can also employ pomodoro]

the primary concept of the method is a metaphorical representation of its namesake - bentō, a Japanese-style single-portion takeout meal typically sectioned into compartments of various sizes. as a productivity unit, a single bento consists of three tasks of various sizes, quantified in time assigned to it, either as a commitment to spend a set amount of time, or the time it takes to complete said task.

the rudimentary version of the setup goes as follows

  • split tasks at hand into large, medium, and small blocks [when I had a backlog, I used Eisenhower matrix for initial pass, then added new tasks manually, largely based on vibes]
  • set how much time each block takes [the “default” is 90 minutes for large, 45-60 minutes for medium, 30 or so minutes for small, but it is largely a suggestion that can be tailored to the areas big and small]
  • assemble a chunk of tasks with at least one from each [or just one of each, depending on how you feel]
  • tackle the tasks by picking each from a given block - depending on your energy, you could pick one of these three paths
    • Large → Medium → Small [dubbed “Eat That Frog”]
    • Medium → Large → Small [dubbed “Climb the Summit”]
    • Small → Medium → Large [dubbed “Slow Burn”]

the 2.0 version of the method slightly expanded the scope by introducing options to group more tasks into a single session: you can pick 5 or 7 tasks instead of 3, with two restrictions:

  • you should still pick at least one from each block, as in the original
  • you can pick no more than 2 tasks from a given block if you choose 5, or 3 tasks if you choose 7, e.g. if you have 5, you can go 1L-2M-2S, but not 1L-1M-3S

how i use the method

the official suggestion is to use Large for tasks that require maximum attention, Medium for medium energy/focus, and Small for easy wins/administrative tasks. I don’t really do that myself, instead spreading the tasks between something I know I need, something I know I want, and something that would be nice to have, and plan accordingly.

Graph View

Backlinks