BvBPL
Pour Decision Maker
I never negotiate based on only salary, you can nearly always get the company to make the first offer, with details about non-salary compensation. Then you can negotiate based on total compensation, hashing out salary/benefit details afterwards.
Yeah, non-salary compensation is a bit tricky. Most companies will not negotiate it. The company offers 80 hours of vacation a year and that's it. However, if you have a company that is willing to negotiate those terms then it opens up a lateral means of negotiation. Which can be helpful in closing gaps.
Even companies that say they aren't willing to negotiate non-salary compensation can sometimes negotiate it. For example, the company may offer initially 40 hours of vacation for new hires, increasing to 80 hours after a year. If you have experience in the industry, you may be able to negotiate coming in at the 80 hour a year mark as a new hire.
I like holding non-salary compensation in my back pocket as an option because I am know I am already getting some baseline benefits. That way I can pull it out if the negotiation slows down. Zelig's philosophy is also valid. It's a personal preference.
Concrete examples are good, but don't make stuff up like "500 lines of code" if you're not absolutely positive that it's actually a good thing. (LoC has no useful correlation to productivity - over the past two years at my job, I've arguably been the most productive dev, and have averaged negative 400 lines of code per day.)
You should make your examples measurable and relevant to the job. I don't know if 500 lines of code is good or bad b/c I don't work in that field. I just used it as an example of a measurable justification.
If your justifications are not directly relevant to your job you may need to provide some context. For example, if I said I tried one hundred cases last year while maintaining an average of a dozen cases on my desk at once, that wouldn't necessarily be directly relevant to putting in for a job writing appellate briefs (and thus would not be my strongest argument). However, I can place that in context my saying that my workload exceeded the expected standards for my position and that I was in the top quintile of the lawyers in the office.
Exposing your minimum is only a problem if you have a weak position. Essentially, the minimum compensation you'll take should be equivalent to your BATNA from Getting to Yes. Worth reading as a primer, you can read it in an afternoon if you're quick.
Personally, I think that exposing your minimum inherently weakens you position. Or, at the least, exposing your minimum does nothing to improve your position and therefore isn't useful. Generally.
Your BANTA (best alternative to a negotiated agreement) is what you can expect if negotiations break down. It is what you have if you walk away. If you already have a firm offer at a baseline rate than that's your BANTA, but it might also be staying at your current job or staying unemployed. Your minimum should reflect your BANTA, but it isn't necessarily your BANTA exactly. For example, if you are advancing to management or a position with additional responsibilities, you will want your minimum to be significantly higher than your BANTA to reflect the additional duties you will have to take on.
I totally agree with the rest of Zelig's advice, particularly about reading about negotiations and Getting to Yes.
Post script: if possible, consider to whom you are making your pitch. Is it to another skilled worker, a managerial professional without skills in your field, or an HR rep? You may want to adjust the technical specificity of your arguments to reflect the technical skills of the other party. This is particularly true if you are applying for a specialized position that is outside of the general field of the company, like an IT or in house counsel position for a, I don't know, a marketing company or something. If the negotiating manager does not share your skill set you may want to expand on how your examples of your skills would benefit the company.