Running this by hand, I capped grouping at two levels, domain and project, and I told you to do the same, because in a spreadsheet, deeper nesting is a maintenance nightmare. Every level you add is more columns, more lookups, more places for the structure to break when you reorganize.

But two levels was always a compromise, not some reflection about how work is shaped. Real work nests deeper than that. A launch contains a marketing work stream which contains a campaign which contains a set of emails containing the one you need to write today. Flattening all of that into “project: launch” loses information, the campaign’s importance, the workstream’s impact, all the inherited weight that should flow down to the task at the bottom.

The app removes the cap because it maintains the tree for you. Projects hold sub-projects, as deep as your work actually goes, and the blend flows down through every level automatically, the same logic as before, just not limited to two rungs. You’re no longer forced to pretend your work is shallower than it is. And crucially, the maintenance cost that made deep nesting impossible by hand, it’s gone, because you’re not maintaining columns and formulas anymore. You just put a task under its parent, and the tree takes care of itself.

There’s a companion relief here, one that may sound small but changes how you work. In the app, any task can become a parent on the fly. You write “repaint the fence,” and then you realize it’s really three things, scrape, prime, paint. In a spreadsheet, promoting a task to a grouping is manual surgery: new rows, re-pointed lookups, re-checked formulas. In the app you just add the children, and the task becomes their parent. Your structure grows to match your understanding of the work, in the moment you understand it, instead of forcing you to decide the whole shape up front.