How do you manage the ripple effect when something changes mid-project?
(I'm currently learning about systems engineering so pls do help me out with this little doubt!)
Like let's take a scenario where you are working on a complex engineering project (infrastructure, defence, aerospace, whatever your field). Things change constantly right? Maybe a component gets redesigned, a subsystem spec gets updated, a client changes a requirement, etc.
My question is: what happens next?
How do you figure out everything else that change affects? Which teams need to know? Which designs, specs, test cases, or schedules are now potentially invalid because of that one change?
From what I've seen and heard, this is usually handled through meetings, emails, and a lot of manual checking. Do things still get missed? like maybe this is discovered weeks later in a review or meet, so how do you handle it?
Also, is this a real problem in your work? How do you currently handle such cases, like how do you ensure everyone is updated on the change and needs to work accordingly? Is this a tedious task or has anyone found a good system that actually works?