A simple job has one loop, but many a times a job to be done has many subloops.

Ex: keep the garbage out in the morning. It has one loop. You keep the garbage outside and the job is done. This is a simple job. It has no dependency, nothing out of your control.

Ex2: Send a weekly report to the team. Loop 1 - ask the data team to send you the raw numbers, Loop 2 - Data team sends you the numbers, Loop 3 - you process the numbers in the right way to show to the team, Loop 4 - send the report to the team. This is a multiloop job and loop 2 is a dependency, which is outside of your control. This becomes more complex as you go up the corporate ladder. It peaks at mid management.

What works for me is to create tasks or loops for all the jobs and try to close those loops, one loop at a time. Every loop has to have an owner and ETA. Sometimes I am the owner and for some loops someone else is the owner (like the data team in ex 2). Another important note, where many fail, is if you are not going to meet the ETA, inform the person expecting for the loop to finish (and all downstream loops) about the reason why it is delayed and what the new ETA would be.