I'm not an expert but the little experience I have is that you need to stop helping them. That's how they learn to take responsibility and listen to what they w

I'm not an expert but the little experience I have is that you need to stop helping them. That's how they learn to take responsibility and listen to what they want to do and trust that intuition. You cannot share ownership, you need to trust before you can trust, it's a leap of faith. OR ---- SoA is a necessary evil for multiple devs.: That way you let everyone free, but they are 100% responsible; and if they face plant completely you can replace a part entirely. The trick is how to architect the structure: Replicate all services on all machines; they all call localhost; that way discovery is immediate and you can scale easy and read faults are both contained and tolerated. Write faults are never easy, so just accept them, nothing is perfect. 2 big hurdles to achieve that: - Your entire solution needs to be completely async., end-to-end = non-blocking on all servers and clients, even deployment. - Your data needs to be at the edges with relations to everything everywhere and unformatted = No SQL tables to alter. ---- Which you pick depends on your situation. In some ways you can think of these as before and after your kids move out.