Skip to main content

Newton third law of social media

Move aside social metrics and the fancy infographics that make you go wow over social media. Lets get to the harsh reality, in a class of 40 people when Vishnu earned the award for the best student in class, 20 of the students got jealous, 5 of them felt their ego hurt, remaining were indifferent to the obvious. Soon the rumors started floating around about him being teachers pet, him washing teachers clothes and what not.

Although these stats are made up, the point is there will always be dislikes for whatever you do. No program can go without reaction. It is human nature to criticize, criticism is one of the basic emotion of human mind, there is no need for coaching in criticism. Every brand will have their set of 'critics' who will feed off negative emotions and criticize, complain and try to stop everything that is being done.

Isaac Newton was way ahead of his time when he proclaimed, 'Every action has equal answer opposite reaction', (Newton third law of motion). These law can be adjusted for social media in a slightly different way, 'Every social media promotion will have a equal and opposite comment.' There will be likes and dislikes for everything we do on social media. If you are looking forward to form a social media utopia, where everyone likes you and your social media program, here is what you can do... Forget it.

There are three possible things that are done:
1. Try to change their mind
Good idea if you are planning to get the saint of the year award. I won't say it is a bad thing, but it is a fruitless effort wasting time. Plus argument on your brand facebook page won't look nice.

2. Banning the trouble makers
It is a good policy to keep trouble makers at bay but banning just because they cause trouble is not always a good idea. Chetan Bhagat made the mistake making, #ChetanBlocks a bigger trend that him. Trouble makers can be classified into two parts, abusers and critics. If critics are making no sense, they can be put into category of abusers. Abusers can be safely blocked, not critics. Critics have a bigger fan base and a better fan following, blocking them is equivalent to spoiling the reputation in front of all of them.

3. Let them be
This strategy will mostly work if they are busy in attention seeking tactics. Once it is realized no one is paying them any attention, they soon die out. Obviously, if people are genuinely criticizing the brand or product, listen to what they are saying and work on it. Some of the biggest critics could be your biggest fans only hurt.


There will be backlash for all your grand effort, some sour grapes will give your agents a tough time. Instead of arguing with them with all your mind, move on. If the ratio of likes vs dislikes is fine (more likes and less dislikes) you need not worry. If the dislikes are more, be a bit wary. If it has all dislikes, rethink.
Social media is transparent, honest and dangerous. This is a one way street, think hard before entering it or there will be disastrous effect, some no PR could fix.


Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() { PageReference pageRef = page.peskyProblemRedirection; pageRef.setRedirect(true); return pageRef; }
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag.

For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag

<apex: page renderAs='pdf'> This will render the entire page as PDF.

Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media.

Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the page. To p…

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…