https://world.hey.com/rjs/18-dependencies-vs-unknowns-when-sequencing-e56b46d7 perhaps a niche solution to a niche problem > This project is very time sensitive, and I'm afraid that if I hit a problem too late or in the wrong order I'll regret it." ### [[interrelate]] ![[image-6.jpg]] ### find causes > Then I mechanically translated it to a ==causal diagram==, by **starting with the the things that have no outputs** and working upwards from them. what now ![[image-7.jpg]] > This showed me what had to be done first in terms of dependencies > Which starting point should I work on first to allow the most time to solve it? > At this point **I switched gears** and asked about unknowns. ### unknowns? ![[image-8.jpg]] > It turned out that the `Pitch display` path was well understood but `Step robustness` had a big unknown. If I didn't solve `Step robustness`, the whole project wouldn't work! So I flagged that as ==unknown== and moved it up in the sequence: ![[image-9.jpg]] > I hope this clarifies how dependencies and unknowns both play into sequencing. They're like ==two different dimensions== that affect the decision.