In normal circumstances, network designers actively create disaster avoidance or disaster recovery as part of their development process.
As a network consultant, you are more often called to be a part of problems or issues where a major event, outage, critical failure, overload, resource exhaustion, or whatever the current problem is, and your role is to develop pathways to a solution.
This is broadly known as disaster participation.
Of course nobody wants to be participating in a disaster and the term is a negative inflection on the fact that the situation should not have occurred. However for a consultant this is a lucrative form of work and as an engineer, often the time when there is much to be learned, new technologies to adopt, and new inflection points in the gross IT development cycle of that business.
So while disaster participation is a bad thing, it usually has a positive impact overall. And that’s kind of sad.