[blowski]

This is definitely a problem I run into. I’m having a team meeting about Project X, and someone mentions that a particular task is waiting for something from Project Y.

The only way I’ve found to handle this is manual. Note the dependency in the meeting notes, then process the notes after the meeting creating relevant todos elsewhere. But that’s only maintainable if you don’t have a lot of work on at the same time, or a lot of dependencies - and we find ourselves back at lean.

Too much work is too much work, and no amount of automation is going to fix that. Furthermore, life is messy, and there is no universal way of structuring that mess. The more mess there is, the harder it will be to live with it. So reduce the mess to the point you can live with it, rather than trying to structure it.