Trjtdtk

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.

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".

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.

  
  

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."

Much of it is about the mindset you enter the meeting with. If you want them to pick your solution and they don't, that's a defeat. And it sucks extra hard because as a co-equal co-founder you now need to slave away for those who defeated you.

Try these to avoid the feeling of defeat:

1. Chose your battles, early.




2. Learn how to convince people.




3. Invest in partial victories.

Chose your battles

Emotional investment, as the word says, is an investment. Invest wisely. You see their approach, it's good enough, and arguing about it costs more than the benefits of your approach? Spend the time improving their approach instead. Oftentimes keeping momentum and focus is far more important than getting things perfect, especially in a startup. But sometimes it isn't. Try to tell the 2 apart, and learn to see benefits where you haven't seen them before.

Learn how to convince people

This is way too long for this format, so to keep it brief: there are management courses for exactly that. It includes not just how to talk, but also how you dress, your body language, and how you listen to people.

Invest in partial victories

You mustn't want people to pick your solution. When you go into strategy meetings, the ideal outcome is that together you come up with a solution that has the potential to be better than the one you had. The minimal outcome must be that they hear and acknowledge your concerns. Your solution isn't what's important. Your concerns about the chosen solution are what's important.

Just talking generally, I think there's two basic things to consider here:

1. The responsibility of the leader/manager/boss/person with authority. It is, at least partially, the job of a leader to make sure their employees are in a good mental condition and stay motivated; if you repeatedly feel slighted, I suggest you try to communicate. This shouldn't affect the end decisions, but it may affect your ability to accept them; it might also cause change in the behavior of your colleagues, maybe change the way they present their ideas, or the way they respond to yours.


2. The responsibility of you as a professional. You should realize (not just consciously, but on an emotional level) that sometimes you might not be right, or you may not have all the information; it is entirely possible your idea was wrong, maybe not for you personally, but for the project/team/company as a whole. Of course, it's also possible you were right; in that case, keep in mind that you presented your idea and got it rejected; at that point, the responsibility doesn't lie with you. If your colleagues keep making decisions that turn out to be wrong, that might be a sign you might want someone else (potentially you) calling the shots, at least in certain fields; but if that's not the case, then maybe you're just wrong sometimes.

Having recently encountered this myself, I would highlight you're a team of 3 co-founders, you've been outvoted; and you'd be equally annoyed if it was the other way around where someone was demanding something but had been outvoted.

Ultimately, you've made your case, and presented the pro's and con's; but if they don't want to listen to your experience then you must walk away with the knowledge that people need to learn from their mistakes. The first is on whatever you were discussing, and the second is to ignore the experience which is why I assume you were brought onto the team... just don't say "I told you so".

Lastly, your mistake is to get overly stressed by this. The decision has been made, and unless you can bring new evidence or reasoning; then you're unlikely to convince the others to change.

I would like to add to the existing answers, that the very excellent book "The Five Dysfunctions of a Team" by Patrick Lencioni has a whole chapter about this, and is a very relaxed read.

In summary, what the book says is that team dysfunction often happens as a pyramid, which starts as lack of trust between team members (in the sense that they can be trusted that they all share a common goal first and are able to put personal benefits second). Without trust, you can't get creative and constructive 'conflict', and instead you avoid trouble by going quiet, which leads to 'artificial harmony'.

The next step up in the dysfunctional pyramid is where you're at. If it becomes impossible for you to create constructive 'conflict' and have your ideas discussed on their merit, whatever decision is chosen will leave you feel 'wronged', and like you didn't have a stake in it. In other words, there will be no 'buy-in'. This in turn leads to the next dysfunction, which is, you will not care to keep either yourself or others accountable when things don't go according to plan; you will simply shrug and say "well it was never my idea in the first place".

So, it appears, you are in a somewhat dysfunctional team, despite presumably best intentions. And, the 'blame' lies with both you and your team (as led by your manager). You, because you failed to conflict creatively to make your points, and instead accepted the resolution without having your concerns adequately addressed, and your manager because they didn't pick up on this.

In an ideal team, there doesn't have to be a consensus of decision, there only has to be buy-in. In other words, I feel that what you feel is wrong here isn't that people chose the wrong decision per se, but the fact they chose it without listening to your concerns and discussing why they felt they were an appropriate risk etc.

Going past this point, however, if your views have been discussed adequately and your points addressed and dismissed in a professionally appropriate context of a functional team, then you should accept the outcome, and hold yourself accountable to it as if it was your idea. If you feel the context was not appropriate, raise it with your manager, and state your concerns. Who knows, maybe they'll discuss your concerns with you and either have another meeting with the 'good' points you raised, or manage to convince you that your ideas were heard, and that there were valid reasons to take a different route (which may have been less technical and more business in nature, etc).

I would not care about psychological aspects. Use the competence you have to figure out which of the following four happened:

• Your proposal is not good and the alternative was better. Nothing horrible.


• Unable to find good enough arguments, they finally took the opinion of someone maybe slightly senior to you. This difference in seniority may be tiny and not worth to worry about.


• It was something primarily opinion based, like Python vs C#. It may be completely different view in another workplace.


• Not less probable than others - they have made the wrong decision. They will pay the price and probably will listen more carefully for you next time.

This question has already generated some excellent answers, but i feel one aspect has not been covered yet.

When choosing between two possible directions, it is not the pros- and cons but the weights you have assigned them, you are comparing. You colleagues feel the pros of their approach outweight the cons, when compared to your approach. Maybe they are not entirely wrong?

Years ago we needed to get a daily data-dump from one db to another. My manager wanted me to implement this by transferring an excel file and reading it into the db.
I was livid! This would unnecessarily complicate things, i would be writing code just to deal with excel.

His stance was that we needed to be able to check what was transferred in case the numbers didnt look right, or 'if we just needed to check'. I tried to explain there were other other ways, and anyway, running software is like a car: you test it before you take in on the road, you don't open the hood while driving on the highway 'just to check'.
He won and i was very very angry.

Years later I am much milder. I've seen cases where users found the numbers didn't add up, and being able to have them check intermediate steps is helpful. (still, csv would have been easier)