I am software developer. During last five years I have tried to grab knowledge from various technical areas and from colleagues. And now I landed up in a company where the people in my team are either have only manager role/ scrum master, QA's, BA's' and developers with only a few years of experience. But in technical discussions, all of them have a say about implementation, bandwidths, timelines, even though they are unaware of what the path is going to be for development of certain features.
Now the thing is whenever some issue comes up in our project, I can hear the other developers in the team/ members discussing the various reasons that why that may have happened, passing their own judgement. However at that point in time I listen to them silently because I have seen people getting offended when you try to correct them. However when the dust settles, I do add my opinion to the discussion.
The actual problem lies in the fact when you provide them with a solution, then the people with the knowledge gained from the little Google search start challenging your knowledge and suggest that we should go with the other solution without understanding the problem completely. As a result one more task gets added in my list, to explain the pros and cons of the other approach.
Now My Question is how to handle such challenges, the challenges which are raised by people in your team having no knowledge of your domain and still you have to politely explain to them why the approach you suggest is the best/better then the approach they suggests, (even though they are unaware of the domain.)
Should I be answerable? Or Should I take part in the conversations? Or just let them discuss, and let them maintain the essence that they know it better.