[JamesBarney]

Most negotiation experts disagree with this advice. The first person who gives a number anchors the conversation to that number. When you name a number you certainly do set a max on negotiation, but you also get to set the starting number. And many negotiation experts think the latter is more valuable than the former.

So they can start off trying to negotiate you down from your max, or up you can spend your time trying to negotiate them up from their min.

[erdevs]

If you're doing something like selling your startup, you want to set the anchor price, yes. There is such a huge range of outcomes, it's best for you to shoot high (as long as you're comfortable with the risk of scaring the buyer off) as the seller. (Or to start and shoot low as the buyer; with the walkaway risk reversed.)

For something like salary negotiation where results are more well-bounded and there is a lot more commoditization (ie replacements are relatively easy to find, or are perceived to be relatively easy to find), you generally don't want to anchor. An anchor that's way out of whack is easy to shoot down (show comp data). Anchoring slightly high/low doesn't buy you much as there is no real anchor... you're just in the established/known range... and so it's more valuable to see where the counterparty starts off an dplay from there.

There are unique situations / exceptions of course. For example, you might have uniquely valuable skills for a given company (or be able to convince them you do) and therefore move into a less-bounded zone of negotiation, in which making the ask/establishing the anchor would again be a good idea. But for a normal, well-established position, there is literally no benefit in "anchoring" as the bounded range is already fairly well established and that is the anchor.

[gozur88]

Still, coming up with that first number is very tricky. A application of mine once reached the salary negotiation phase, and the company asked me what I was expecting. I didn't want to go so high they were insulted, so I took what I thought was a reasonable number and bumped it by 40%.

They said "okay". No negotiation, no fireworks, nothing. I've always wondered what I could have gotten out of them.

[rogerdpack]

I guess the fear is that you'll anchor it "lower" than they would have. Example if they are intending to pay 120, and you say "I'm hoping to make 110" they might just come down to 110. But I suppose if you start at your high range that might be in your favor. Some of us (myself included) just don't know what we're worth so it's hard to know how to start the deal...

[JamesBarney]

Also if your problem is every time you look for a job people keep on wanting to throw more money at you than you could ask for with a straight face. Well then dang I wish I had that problem :)

This problem is usually because people just set their starting price too low, or aren't firm enough on it. One tactic(I haven't used yet, but I'll try the next time I apply to a job) is ask the hiring manager how selective they are. Many time they'll brag about how hard it is to join their company. They'll say things like "We only accept 1 in 10 developers". Boom now they just admitted that if they were paying fair market value their offer should be about $153k :). [0] This is a great place to start a salary negotiation. Also glassdoor is a good place to find information for where to start a salary negotiation as well.

[0] 80% of devs get paid between $57k(10th %) and $153k(90th %).

[pc86]

Your citation needs a citation.

[JamesBarney]

Whoops, here you go. http://www.bls.gov/oes/current/oes151132.htm

[dopamean]

That sounds similar to the idea the Overton window[0]. I've thought for a while that I hope I get to say what I want before they say what they're offering. The hope is that if I say a high number then we will be negotiating based on that high number rather than some unknown, possibly lower one.

[0] https://en.wikipedia.org/wiki/Overton_window