Software Architect's Handbook

Knowing when to compromise

As a software architect, you will find yourself in discussions with others over a variety of topics. You may be negotiating something, or in conflict with someone, or you could be making a request for something. Whatever the reason, when it becomes apparent that you may not get what you want, be willing to compromise and know when to do so.

One reason to compromise is when you are simply lacking leverage, and if you fail to compromise, you may not accomplish any part of your request or goal. A compromise can make sense in that situation because you may still get something suitable out of the exchange. A compromise also makes sense if you think it will be beneficial in the long run. Giving up something now may pay ...