- ERE.net - http://www.ere.net -

LinkedIn Lemons to Lemonade

Posted By Maureen Sharib On July 5, 2012 @ 5:58 am In Opinion | 7 Comments

Age is a very high price to pay for maturity. – Tom Stoppard

I recently did a search for managers and senior managers in Tax out of second- and third-tier accounting companies on the East Coast.

The customer had sent me a list of names he already had — informing me they’d be a nice addition to my “database.”

The problem with that is 90% of his names were on LinkedIn [1].

I’m just not that interested.

Furthermore, several of his names were not only on LinkedIn – they were no longer at the respective companies he had them listed under or their titles had changed – senior managers having moved on to principle/partner, which were of no interest because they were too high on the totem pole.

Once again, I don’t have time to chase phantoms.

I started calling in to the respective companies, pulling the senior managers and managers in Tax.

That’s how I know some of his listed names were not there (or that their titles had changed).

I ended up matching his names by about 150%.

In other words, if he had five names at a company, I pulled eight more, most of whom were not on LinkedIn [2]!

Not only did I pull them, I pulled them knowing all of them were there in real time and that their titles were current.

What was helpful to me was that his assembled names helped me collect the others.

“Oh, Tom McKee’s no longer there? Has someone replaced him?” usually brings forth another name and sometimes that name brings forth others.

“While I’m asking, is there anyone else new there at your firm?” asked in a straight-forward and matter-of-fact way to a receptive Gatekeeper who has begun to give you information holds the possibility of a tumble of names coming forward.

I feel better these days about the fact that I never did keep a database; basically I’ve always felt the Internet was a good enough “database” to start any search.

I very rarely (if ever — I can’t recall any!) have searches that resemble each other within close timeframes, so information in a database would have likely “aged” and face the same dilemmas that names off (the database) LinkedIn are encountering.

I only see this problem (aged data) increasing as these online “social” databases age.

What do you think?


Article printed from ERE.net: http://www.ere.net

URL to article: http://www.ere.net/2012/07/05/linkedin-lemons-to-lemonade/

URLs in this post:

[1] LinkedIn: http://www.ere.net/2012/07/02/linkedins-week/

[2] most of whom were not on LinkedIn: http://www.ere.net/2011/12/15/fishing-in-a-small-pond/

Copyright © 2008 ERE Media. All rights reserved.