Treat conflicts like a co-op game—different roles, same mission. Focus on shared goals, like player engagement or market success. Clearly explain your design choices while staying open to their ideas. Prototype compromises to test solutions quickly. Collaboration isn’t about winning; it’s about leveling up together.

It depends on the partner's experience in development. If you know your stuff, they should respect your experience. If not, this isn't a proper partnership and will most likely hamper the project and prevent the product from shipping.

As a new entrant, I'll welcome as much input as I can get, but I do have a clear vision of what our game is and what it isn't. My biggest fear is entering into an agreement with an external partner that forces me to compromise that vision. Making sure the vision and goals are aligned at the start, contracting well, and keeping the vision front and center in every conflict, will hopefully ensure that common ground can be found. Always ask, "How does this design consideration serve the vision and goals of the game?"