Having an idea of what is known and not known in a solution can shed a light on approaches. It’s more possible for known (existing) solutions to go through the

Having an idea of what is known and not known in a solution can shed a light on approaches. It’s more possible for known (existing) solutions to go through the phases of waterfall for a rewrite. Where unknown solutions exist, using agile to get the vectors correct and signed can help a great deal. I have learned from experienced PMs how even agile waterfall loop where each step of waterfall itself is an agile undertaking can be beneficial in some cases. A rewrite can represent getting something much better than it is in a different way. A rewrite can represent getting something much better than it is in a different way than developers who may want to start from scratch to relearn the lessons of the past and develop technical debt in a new way. Of course to be optimistic how you both experienced and new developers will be open minded to listen to approaches they might not be used to, and not assume that if they haven’t seen or understood a way forward it doesn’t mean there isn’t understanding in why things were done in a certain way. Needing to feel significant from a coding project maybe worth some introspection - empowering users to benefit from software is most important. Tech should work for users and not the other way around to validate developers for finding a novel way to solve a problem that doesn’t move the needle for them