Home
David Nour

David Nour

CEO, The Nour Group, Inc.
CEO, The Nour Group, Inc.

Why Soliciting LinkedIn Endorsements Is A Bad Idea

Comments | David Nour, InformationWeek | February 05, 2013 08:43 AM


Facebook's 2012 Highs And Lows
Facebook's 2012 Highs And Lows
(click image for larger view and for slideshow)
Have you noticed that every time you log into LinkedIn now it keeps pestering you to endorse the skills and knowledge of your network? It's another classic case of LinkedIn trying to abdicate the care and nurturing of your relationships to technology -- and it doesn't work.

I've been a LinkedIn Business Pro user for several years and have written extensively about all that's positive about the site's focus to become the prevailing professional social networking platform. But when you have a hammer, you begin to treat every challenge or an opportunity as a nail.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

LinkedIn launched Skills and Knowledge as a functionality that few knew about, much less paid attention to or used. After all, shouldn't you be able to ascertain my skills or knowledge from my bio, background, experiences, education and recommendations?

[ Have you adapted to LinkedIn's changes? Read 5 Ways To Improve Your New LinkedIn Profile .]

By asking you to endorse the skills and knowledge of your network, it is trying to bring this new functionality front and center. Here are three fundamental problems with that:

1. Contextual Irrelevance.

Let's say I worked with Steve on a social media strategy-consulting project and am aware of his specific skills or knowledge around an influencer campaign. But what LinkedIn keeps prompting me to endorse is his graphic design skills, which I wasn't privy to in our work together and not really relevant to the context of our relationship. Does that mean that I don't have a relationship with Steve or can't endorse a skill or knowledge of his? No. It simply means that LinkedIn is taking our relationship out of context. Can I keep scrolling for his other skills? Sure, but who has the time or patience?

2. Degrees Of Competency.

Let's further say that Steve did a decent job on the above consulting engagement, but there were some areas where I thought he should have been more knowledgeable or competent. There is no way to rate the degrees of his competency or recommend areas for Steve to grow professionally in this area. Any competency metric I've always seen or have found effective gives you a range, such as a 1 to 10 or 4 out of 5 stars.

3. Weighted Endorsements. Did I work with Steve only once and experience his skills or knowledge in a very limited scope, or have we worked together on multiple projects, allowing me to see him deliver results across a spectrum of challenging scenarios? Anyone who has ever endorsed someone else knows that not all endorsements are created equal. There is no way for me to comment on each endorsement or give it more credence or credibility as to the frequency of our interactions.


Are these the endorsements you really want?

I don't know about you, but here are two other problems that give me quid pro quo heartburn:

-- I feel guilty for all these people and their skills that pop up that I have no idea they were capable of (am I the only one who keeps asking "seriously?" to many of these skills or knowledge?) Does that mean I don't really know them that well or have a strong enough relationship with them to be connected on LinkedIn? Or that they've done a poor job in branding themselves for me to realize that particular knowledge or skill was a part of their repertoire?



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events