A lot of modern web development involves implementing workflow, but what sort of gaps are there in typical development and how can they be covered? How can you ensure that things get done and nothing gets lost between workflow steps?
It's easy to tell when a process has encountered and error, but much harder to tell if it hasn't started when it was supposed to. The more quiet the process the less likely people are to notice it's not even running, so it's important to have mechanisms that ensure things that are supposed to start do actually start.
Sometimes a problem can hide in plain sight, especially if the mechanism for warning you about it is something like a regularly scheduled email. If you don't notice the email immediately or delay dealing with it sometimes you can completely forget it's even there, even if it's sent to you every day.