In the spreadsheet, I let a task wait on one other task. One blocker, because tracking several by hand gets tangled fast. But real work isn’t that tidy. You can’t ship the release until the code is merged and the docs are done and legal has signed off. Three blockers, and the thing is eligible only when the last of them clears.

The app handles a task blocked by many, and it updates eligibility live as each blocker completes. The task stays hidden, out of your way, until the moment the final blocker is checked off, and then it surfaces on its own. You never went looking to see if it was ready. It told you. That’s the same “hide what isn’t actionable” principle from Part 3, just no longer limited to the single-blocker case a spreadsheet could manage.