Arsthbt

You've expressed your idea clearly and they decided they did not want to accept your decision and this bothers you. Well of course it bothers you. You've made an excellent case for a particular technology to be used and they flat out denied it.

Though remember that politics are always at play, and you cannot understand all the underlying reasons behind any given decision. Even if this were not the case, you should always keep in mind that it isn't a direct attack on you, nor is it saying that you are incapable of making good choices in this matter.

As a programmer myself, you learn to go with the flow and respect the decisions of your colleagues, even if you disagree. Fight the battles that deserve fighting for, when you think that it would be a seriously bad choice otherwise. Being a team player is every bit as important as making the right technical choices, and you should learn to trust in your colleagues just as they should learn to trust in you.

However, this only addresses the inward issue. If you feel that a mistake is being made, then the proper approach is to make it clear first and foremost to your colleagues, and should they not agree, with your boss directly. It need not be a personal vendetta, but rather something you're making clear. After this point, you cannot be held accountable for potential problems which may result from this (though they can still ask you to fix it).

TL;DR - Try to pick your battles, but not at the expense of trust from your fellow colleagues. If you absolutely must object to a decision, simply make it clear, and then continue to be a team player.

Edit: In light of your edited question, then I suppose not much can be done. If perhaps you are the expert in this regard, then you could put in an argument that in such matters, you should be given full control (but strictly for technical issues such as this). Though if I understand you correctly, that isn't the case.

So the next best thing is trying to make their proposed solution work as best as possible. While it can't be your idea, at least you can make it work well, and there is some small satisfaction in this. It would be ill-advised to sabotage the idea to prove your solution correct. Ultimately, they are co-founders, and so you must respect their decision just as they must respect yours should you and another co-founder agree on something which the third does not.

It's a completely understandable reaction and a human one.

You know you tried to influence the decision making process, you tried your hardest, and things didn't end up as you think they should.

What I find with a lot of things is if I understand everybody wants the best outcome, it makes it easier for me. If I can work with a bunch of people who are committed to everyone understanding the pros and cons of each solution, that gives me confidence that on average, the best solution is often decided.

Often what it comes down to is a slight disagreement in perceived importance. For instance, one person may think performance is more important than code clarity.

You have to remember, the best teams operate when there are disagreements. If you have a team of "yes men" as a team, you are not likely to do great work. So there will often be somebody that's a bit disappointed. But the team not deciding to go down a path doesn't mean everything you said is wasted. Quite often it will stay at the back of people's minds.

As you point out, once a course of action is decided, you do have to commit to it. If you have concerns, you should explore how they may be mitigated within the context of the decided solution. But you shouldn't compromise your team.

Also, something to keep in mind, often there are a lot of non-technical reasons why the best solution is not followed.

You will get used to this, just as I have.

how do you deal with this conflict once it has been decided that this is something that must go ahead, if you feel strongly against the change?

My way of dealing with this is considering what my role in the company is. Am I there as a developer? As an analyst? As a team lead? As a project manager?

If I'm the developer (which I surmise you are), then you never had "decision making power" to begin with. You simply had some decision making privilege that was extended to you because someone (with actual power) chose to follow your decision.

Edit: you mention the three of you are co-founders, but the answer remains the same. You don't have any power, only a majority of you wields any power. In this case, you are not part of the majority.

If you're not holding the wheel, you're not steering the ship and thus cannot override the decision that is made by whoever is holding the wheel. You can ask them (which you did), but they can ignore/deny/disagree with your request. Not your circus, not your monkeys.

You informatively raised a concern, it was ignored. Accept the outcome and follow the plan as agreed upon. You and your two colleagues are there as a team, not as a darwinian competition.
Even if you were right, the other two developers clearly did not think so and will have to make the mistake before they realize it was a mistake. Everyone does what they consider to be the best thing, until they understand that it's not actually the best thing. In some cases, that means having to learn the hard way. This can apply to either you or your colleages, only time will tell.

If you want to be the one steering the ship, you must first be in a position to do so. But if you're unable to deal with things not going your way, I'm apprehensive about your compatibility in a leadership role, as it entails much more compromise than outsiders seem to think it does.

I find that this severely impacts my mental state (either by making me feel less motivated, agitated, angry/frustrated, or what have you), and I'd like a solution.

The short answer, in the words of Disney's Frozen, let it go. That's easier said than done, but it will boil down to this.

Look inwards and ask yourself why you care so much that you're willing to die on this particular hill. Is it because you only want to do things your way? It is because you are unwilling to learn a different way of doing things? Is it because you have a different appraoch to developing and abhor the alternative?

How can you be sure that you are objectively more correct than the others? If you are, then why did you not used that irrefutible evidence to make your case before the vote?

Never lose sight of the big picture: you're an employee of the company, and you're there to do the work the company tells you to do (within the boundaries defined in your contract). You don't get to decide which work you get to do.

Let it go, and accept that when someone else overrides your decision, the consequences of that decision fall on them. You are not personally responsible for the company's wellbeing against the company's own wishes.

I strongly disagreed with the chosen outcome, which was settled based on majority (we're a team of 3 co-founders), and so I'm not sure how to reconcile the feeling of having to do work to support a path I don't agree with.

First of all: you agreed to a vote, you partook in a vote, and now that the decision hasn't gone your way, you're wanting to pipe up about it. At first glance, I would consider whether you're being a sore loser here.

The fact that a vote needed to take place suggests that the decision was not unanimous, which inherently means that someone was always going to "lose". This time, it is you. So you have two options: you accept the outcome, or you don't.

Imagine if everyone who didn't get their way did not accept anything other than what they wanted. How much progress do you think you'd make if the other two developers blocked you every time one of them did not agree?

As a real world example, imagine if everyone in a democracy had veto power over everyone else, and you could only get things done when every citizen unanimously agrees. Nothing would ever get done.

If you do make a fuss, and let's say you even manage to get your way eventually, you will be known as a sore loser and unwilling to work in a team or compromise. All of these observations will be much more detrimental to your career than the minor benefit of being right.

Simple concept: "feeling" is not a driver for a change (or lack thereof). It is a fact driven event. Given there are enough facts to support the change, it'll happen, despite you like it or not.

You need to learn how to work with a team, and also need to learn, how to adjust yourself with a rejection. Remember this: you don't "own" anything in a team discussion, you are a participant.

There are reasons, valid reasons, for any proposal being accepted or turned down. There are ways to showcase your disagreement and providing the proofs, like, having PoCs, SWOT analysis result etc, getting angry or frustrated or agitated is not one of them. At end of the day, not up to you to make the final decision, so let it go.

Direct your "anger" or "frustration" towards a positive side: For example,

• Do better homework on the topics being discussed next time.


• Invest more in finding the downsides of the other proposed solutions, and also present ideas which promise to solve the downsides you have identified. In other words, don't just point out the shortcomings, also find ways to mitigate them.


• 
  

  Do not try to "compete", rather "collaborate". Don't expect everyone to accept what you propose, and at the same time, don't blindly reject everyone else's idea because you have one of your own.

  
  
  

  Compare, collate and collaborate - that way you may find every idea has some contribution from your own.

  
  

Addressing this solely from the psychological stance asked for, I find there are a few things that help me get over a "bad choice" (in my opinion).

The first is simply a little time - if I have to start coding the "wrong thing" immediately, my mind is replaying all of the arguments against this, not trying to see the best way to create it. Usually if I can put it off for a day or two, I've accepted the decision and am more relaxed about it, particularly after sleeping on it (so my brain stops the cycle of "but the reasons against it are x.... y.... etc")

Second, there can be a feeling that your opinion wasn't heeded or that you are powerless because you can't change this decision. Going back to the code and doing something else that I do want done (that has been agreed or I have the power to choose) can help me feel back in control and that I am contributing good changes to the code-base.

Third, when I do come to designing/coding the required change, I am looking into how to make it work as smoothly as possible ("even if it's wrong we're going to do it well"). Trying to maximize the benefits that were used to make this decision and reduce what I saw as the problems with it helps to get me invested in making this solution work and usually I find I get to the point of "not the best decision, but actually not as bad as I thought".

Although the other answers provide fair points, let me explore a possibility that seems to me it was not properly considered in some of them.

I have 20+ years of experience as a developer and until last year I never had any issue with the outcome of design sessions. Usually, such sessions would end like this:

• My solution was accepted verbatim (10%)


• My solution had flaws and it was improved by the team or merged with other solution (50%)


• There was a better solution from someone else (40%)

The accepted design represented an overall view of the team and at least I never had a trouble going forward with it, because I always thought we got a good solution on the end.

However, last year I joined a team, composed of people from different backgrounds, that were working together for 6 months beforehand. They had a complete different set of priorities in their thinking, that clashed directly with mine most of the time.

For me, their designs were brittle, hardcoded and somewhat inflexible. For them, my proposals were fancy, over-engineered.

It was very hard for me to accept, for example, to create a parser engine whose outcome would depend on the name of the json file. I tried to explain to them that we would have more advantages having metadata inside the json instead of simply relying in its name, but the collective decision was that asking the users to create additional fields was unnecessary.

Then they decided to create the code without unit tests, instead having integration tests to check everything end-to-end (3 minutes of execution time). And then came several other decisions that I couldn't simply agree with.

For almost an year, I tried to reason with them. I applied several suggestions from the agile coaches of the company, asked fellow engineers to evaluate if I was wrong in my assessments, suggested to do spikes to compare solutions with facts not opinions, among other strategies, including taking 3 soft skills courses to see if it would help.

With time, some situations arose that showed them the problems in our solutions, and eventually they recognized that some of them would have been avoided with a "fancy" design. But most of the time, I was still the absolute minority in the design sessions.

In the end, I asked and changed to another team. that solved the issue for me, but it is not the case here for you.

In your case, I would suggest:

1. are the decisions so bad that you can't live with them? Can you try to tolerate them to see if time can show the chosen design was not the best one?




2. in your relationship with these other founders, can you openly tell them how you feel about this?




3. try some soft skills courses, to see if this can enable you to better communicate your ideas




4. can you bring somebody else to support you? being only founders, this may be impossible or awkward, but I don't know your environment. a professional coach, for example, may assist/mediate your discussions and help you see the social dynamics happening while you make decisions

As others have said, what you're feeling is normal, and understandable.

First and foremost, I'd assume good faith from everyone else. Second, I'd ask for more information about people's reasoning. And third, use that information to help you in the future.

To elaborate, first and foremost, you have to assume that the other people involved in making the decision are rational, and have reasons for what they're doing. So either you don't understand their reasons, or you disagree with them. So I'd talk to them and get a better idea for why they went with a different option. Why are they prioritizing those concerns over the things you value? I know that as an engineer, it can be very hard to balance technical correctness/best practices versus actually shipping a product.

For example, they think that moving logic from the backend to the frontend will make certain things easier to manage, and they want to allow people to make certain changes you think an admin should make, which again seems like it will minimize the amount of management you/the admin needs to do. You probably prioritize other characteristics, or disagree that those changes will minimize the amount of management time.

So one thing you could do, going forward, is at least think about changing your metrics for decision to match those of your other cofounders, and/or focus your energy on the areas that you think will maximize whatever characteristics you care about. And be prepared to not "win" all the discussions. Worst case, if everything goes horribly wrong, you can always say "I told you so."