What do you do if your boss disagrees with your engineering design proposal?

Either convince or get convinced. Approach must to convince and make understand the proposal. If mentor is not getting agree then discuss and understand about the disagreement for implementation in the proposal to come to mutual agreement.

Provide your boss with uninterrupted time to express their concerns fully. Demonstrate active listening by focusing on understanding their perspective and underlying issues. Consider their constraints and insights from experience before responding. Prioritize respect and comprehension to address concerns effectively.

In this dynamic and competitive era, it is not uncommon to experience disagreements or varying approaches within a similar project environment. Encountering a disagreement presents an opportunity to explore uncharted territories and uncover aspects that could potentially contribute to optimizing or enhancing the project's scope. Actively listening to all points and concerns raised during a proposal is always a valuable practice. It enables us to identify any aspects that may not have been included in our checklist or initial assessments. By actively listening, we can gain a broader perspective and potentially address concerns that may have not been considered initially.

When my boss disagrees with my engineering design proposal, I prioritize active listening to understand their concerns fully. I seek clarification, present supporting data, and offer alternative solutions if needed. Seeking compromise and following up ensure we reach a mutually agreeable solution, aligning with project objectives and organizational goals.

After thorough examination of my Boss's point of view if I am convinced that I have better alternative, then the homework for the preparation of alternative is must. That can be in the form of data sheet, design, summary of important key numbers, etc. My boss is not egotistic (which is rare quality to be found in bosses, yeah I know ;)), so if my analysis is correct, he will be easily convinced. Most of the time, while being a competent engineer himself, the argument brings the best results. We come up with solution far better then his or my design.

Be curious. Ask questions to fully understand the other person's perspective. In truly seeking to understand the rationale behind their position it may expand your perspective and change your opinion. By your example the boss may also decide to be more curious about your rationale.

Honesty and transparency in your communication and collaboration. You need to first understand before you can discuss. So, ask questions and LISTEN to the answers. Don't just hear and move on, really listen to their position. When you both understand and are open, collaboration is really exciting and productive.

Seek clarification by asking targeted questions to fully understand your boss's perspective. Delve deeper into specific areas of concern to uncover underlying issues. Ensure mutual understanding and alignment by addressing any misunderstandings promptly. Demonstrate commitment to finding effective solutions that address all concerns raised.

I check his idea and compare and try to clarify which idea is correct I do nt accept and follow boss without accepting and clarifing

I think that everyone has their own viewpoint and brings things to the table to consider. I suggest you listen to their concerns and clarify if you took their feedback into consideration for your design. There may be something you hadn't thought of before that is valid and you may like to incorporate a solution to the problem at hand.

I have about twenty-five years of experience making engineering designs for oil and gas applications. I am not an engineer by education. I am trained as a physicist. I learned engineering on the job by following design manuals and engineering practices. When bosses disagree with the engineering design presented, the concerns relate mainly to cost (too conservative design), engineering mistakes (not following the rules), or concerns about operability or maintenance. Many inexperienced engineers make the mistake of advancing their design before receiving guidance and confirming expectations from the boss and other stakeholders.

A data-driven approach can be used to communicate causes and effects within a design. Data analysis is a powerful tool to develop understanding and information of the "what, how, and why". This may be useful in convincing key stakeholders - but the key skill of persuasion will lie in the presentation, discussion, and alignment of stakeholder understanding. This will enable a powerful discussion to make an informed engineering and business decision.

it's important to first understand their concerns and perspective. You can try to address their objections by providing additional information, data, or alternative solutions. Ultimately, the goal is to reach a consensus that aligns with the project's objectives and requirements.

Present data supporting your design proposal with clarity and objectivity. Utilize simulations, calculations, or case studies to validate your approach effectively. Highlight how your design meets project requirements and goals through clear evidence. Demonstrate the feasibility and benefits of your design to sway opinions and garner support.

I have found that it is easier to give them the information that I have that they may not have seen yet. And then I offer a solution that I can agree with.

Present alternative proposals that address your boss's concerns while still aligning with project objectives. Incorporate feedback received to demonstrate flexibility and willingness to collaborate. Ensure alternatives maintain momentum and prevent project stagnation. Emphasize the commitment to finding viable solutions that meet both objectives and feedback.

If my boss rejects my proposal I will offer another alternative solution because I believe that the solution doesn't depend on the idea it depends on the execution of the idea, and we have multiple ways to solve the problem so I proposed multiple alternatives and challenges of execution behind it so It becomes easy to make a good decision.

There are two types of manager technical and non technical. For non technical manager we have to explain full scenario of the project, why this design is needed and what is the benefits if we go with the proposal. For technical manager you need to be accurate with your design proposal. Listen to them what are all the cons with the proposal we made and why it's not suitable. Explain your design proposal how it's benefit for business, specification, cost and time

Again "the devil is in the detail" have a revised target meeting session with a scribe & minutes as "what he said & what was heard" may be different things.... document & agree alternatives in cost, tech, time / delivery, reliability (think long term op cost & lifetime management), ensure bosses role is documented as responsible for the deviations from original solution and make it clear to them that they are accountable for changes. Don't be argumentative, rather challenge & concede.

Achieving success in engineering means to be flexible and willing to see the project from all perspectives. Adding in constructive feedback into your design allows you to learn your craft more deeply and will help you to maintain valuable professional relationships that will support you through your career.

Life is a series of compromises as most married couples will tell you without compromise very few marriages will last. But there is fine line between compromising and simply caving in to other's preferences. Again this is a mine field even in my last role being brave cost me early contract termination, so caveat emptor but principles must be defended or we are simply spineless humans.

Seek compromise by integrating aspects of both your vision and your boss's concerns into the design. Prioritize maintaining the integrity of the design while addressing key concerns raised. Engage in open dialogue to find common ground and mutually beneficial solutions. Emphasize collaboration and the value of incorporating diverse perspectives for a stronger final product.

Là on touche la psychologie du projet, un projet doit séduire! Dans certain cas , la proposition est vouée à l’échec,. Il faut avoir la sensibilité pour sentir cela. Une parade consiste à faire une proposition ??suicide??qui sera taillée en pièces, & de présenter dans un second le projet auquel on croit. Cela fait un peu plus de travail mais il faut se donner les moyens de réussir.

To find compromises often requires great emotional intelligence and preparation. Issues are very often multifaceted, and during the discussion it should be taken into account that the same topic can be interpreted in different ways. Prepare your arguments, try to logically present your point of view, the situation and its consequences. Find the space to look critically at your own idea. Listen to other and be open. Try to find a common part, a combined idea. Pay attention to emotions as you search for a compromise. Be careful that they don't stand in your way of finding a solution. Sometimes it's useful to take a short break in the conversation, or divide it into parts. Find a common goal, it makes it easier to find a common path to it.

Be cautious with the nature of the compromise. All designs have compromise within them. But if you compromise on something like the design requirements, then you destined to fail. If you have well founded design requirements, then finding the compromise within the design to best meet all the requirements should be an intellectual pursuit based on fact.

Follow up by revising proposals based on discussions and feedback received. Schedule a follow-up meeting to further explore potential solutions and finalize decisions. Implement agreed-upon changes promptly to keep the project on track. Demonstrate professionalism and commitment to project success through diligent follow-up and action.

I think it depends on what is the reason the boss disagrees. It could be the boss has valid reasons or that the top management executives already made the verdict.

Collaboration and maintaining stellar relationships in business is what determines long term success in your career. Having a practice of following up with your desing process shows integrity and your willingness to respect your superiors opinions. These soft skills and demonstrating trust will follow you wherever you go in yout career.

Organise a Final Scope Framing meeting session with your boss a scribe & minutes as "what we said & what was heard" may be different things.... document & agree final design parameters clearly. Identify what minor changes you can authorise in a final comments round & what your boss needs to authorise in terms of "Orders Of Magnitudes" re: costs, integrity, delivery times etc. , Circulate to stakeholders for final comments within an agreed time-frame. Rarely any comments make much impact. Incorporate final comments and "reflect & learn" from this design & move forward to "The next phase"

Sometimes it is the period between reviews that allows people to better understand new information. It might be that your boss just need to think on the proposal. Hopefully, your company allows this time before making a final decision.

Dont have much to add but I think most Bosses need to keep their designation on the side while participating in a healthy argument with juniors/subordinates (if at all they want to participate in a "HEALTHY" discussion - which is mostly No). Generally when bosses begin to lose the argument, they throw their superior designation on the table and then it's over. So I have learnt not to argue with morons but at the same time keep my position safe through signed M.O.M.s, emails, letters etc. When all hell breaks loose later on, I don't want to be blamed.

In engineering, we have multiple ways to do one task. We all have different view to look at problem statement. There are high chances that our suggestion is not acceptable to managers or others. It would be good to hear their proposal and try to see which could be best option for the project. Explain your logic behind your proposal and make a healthy brainstorming session. We surely would reach solution where boss and rest all are aligned.

Consider the possibility that if there is a lack of agreement on the design that there is actually a difference in understanding of what the design is to achieve. No-one will ever agree on the best design if everyone thinks it is meant to do something different.

No design is done in isolation. As (Sr.) designers we review the requirements, come up with a concept then review that with the design group, including the operators, assembly techs, HSE, and manufacturing input. After that the comments will be incorporated into the detailed design. The client will be invited to comment in either concept or detail design phase. Once maturity has been reached a final design review will be done, with a go ahead resulting in drawings for quoting and manufacturing.