Big Data. Big Decisions
InformationWeek
Special Coverage Series


5 Lessons For SMBs From Nokia's Marketing Mistake

Nokia is taking a beating for its misleading Lumia 920 marketing. Here's what startups and other small firms can learn from the company's foul up.

10 Tips For Tapping Consumer Sentiment On Social Networks
10 Tips For Tapping Consumer Sentiment On Social Networks
(click image for larger view and for slideshow)
It shouldn't come as much surprise that Nokia is taking heat for misrepresenting the camera capabilities of its new Lumia 920 smartphone. But we're not here to fan the flames. Rather, let's sort through what small and midsize businesses (SMBs) can learn from the much larger company's error.

The reason for doing so is simple: Nokia will likely weather this particular storm. SMBs often can't sidestep major public relations disasters, especially when self-inflicted. (If you missed the mishap, here's the recap to get you up to speed.)

"Con marketing is a fast path to SMB ruin," said Techaisle CEO Anurag Agrawal, in an email interview. Agrawal's market research firm focuses on SMBs. "SMBs, especially very small businesses, reply upon word-of-mouth and referrals to grow their business. They have to be extra careful to make sure that they deliver what they promise."

With that in mind, here are five lessons learned from Nokia's bad example.

1. You're not going to fool anyone.

One of the more head-scratching aspects of the Nokia story is that someone may have thought no one would notice the deception. Well then. The Verge gets credit for the catch, which was then picked up by dozens of other media outlets. The 24-7 news era isn't particularly forgiving, nor is the similarly incessant commentary on social media and other public forums.

[ Online controversy can drive big traffic to SMBs. See Engaging The Enemy On Social Media: 5 SMB Tips. ]

"Today, businesses use many different digital avenues to have a 360-degree [view] of their customer," Agrawal said. "Many forget that customers themselves track and verify the offerings and marketing messaging of businesses. Any misrepresentations are usually caught and widely reported within the same digital avenues."

2. Weigh risk against reward.

Set aside the morality of the Nokia case for a moment and just consider the risk-versus-reward picture: Whether it realized it or not, the company took a big risk without a particularly obvious reward. As InformationWeek's mobility reporter Eric Zeman asked: "Why do this?" Nokia was already in a precarious position and while this dust-up will eventually subside, it's certainly not going to help the company's cause.

For different reasons, startups and SMBs have a similarly narrow margin for error--they don't have the resources to withstand a major error in judgment. Entrepreneurs are willing to take big risks, but they do so with big rewards in sight--and hopefully without deceiving customers in the process.

"If an SMB is caught lying, especially on something high profile, it's going to take a lot of money and time to set the record straight," said Analysys Mason analyst Steve Hilton via email interview. "Just don't do it."

3. Clear communication is critical.

Hilton offers a general theory as to how Nokia found itself in this position: "I'm guessing a bunch of Nokia employees were working on these videos and pictures of the Lumia and for whatever reason there was a breakdown of communications," he said.

Make sure major customer-facing decisions--and this definitely qualifies in Nokia's case--are well-communicated and well-vetted within the company. "Oftentimes mistakes happen when that communication isn't as robust as it needs to be, when communications break down or when employees don't have a chance to provide input into decisions," Hilton noted.

Agrawal agrees, noting that clarity--let alone honesty--should not be sacrificed for convenience. "Some [companies] even post stock photos of people that do not even work at the business," Agrawal said. "It is a matter of convenience but does not provide any cohesive and constructive positioning of the company."

4. Don't market something that doesn't exist.

Nokia's initial apology points out its fundamental mistake: They were marketing a future promise rather than present reality. (Of course, they would have been OK if they had said so in the copy.) "We produced a video that simulates what we will be able to deliver with OIS," the apology reads. And later: "This was not shot with a Lumia 920. At least, not yet."

Pre-launch buzz can be a good thing, but not if you chase it at any cost. That's a big part of the problem, according to Agrawal: It's simpler and cheaper than ever to market an idea an online, even if that idea doesn't yet pay off.

"It is easy for SMBs to get carried away by promising what they are not capable of delivering either due to competitive pressures or internal directives," Agrawal said. He offers a better alternative: "If a customer comes along that wants something beyond [your] capability, take the customer into confidence, make the customer a partner and work together to develop capabilities and deliver to [everyone's] satisfaction," Agrawal said. "This is a surefire way to develop new business, new products, and new capabilities. Most successful startups and SMBs succeed because of the above method of operations."

5. You need a strategy for screw-ups.

People and organizations make mistakes. When they do, how they react and respond goes a long way to determining the scope of their second chance. Nokia's public apology seemed reasonable enough, if perhaps a bit on the light-and-airy side. But the company has since sent a slightly different message, telling Bloomberg that they'll open an internal investigation. A spokeswoman said the company is handling the fallout "quickly, fairly, and privately." That last adverb is a bit confusing--the cat is out of its cliched bag, so the private route seems ill-advised--but that's Nokia's call.

It's a reminder that you need at least a rough plan in place for handling public problems, even if they're someone else's fault. Giving some thought to the worst-case scenarios can help owners and executives better handle bad situations of all kinds, such as a lawsuit or a data breach.

Of course, there's at least one way to prevent screw-ups from happening in the first place. "Thou shalt not lie," Hilton said. "It's an oldie, but a goodie."

Even small IT shops can now afford thin provisioning, performance acceleration, replication, and other features to boost utilization and improve disaster recovery. Also in the new, all-digital Store More special issue of InformationWeek SMB: Don't be fooled by the Oracle's recent Xsigo buy. (Free registration required.)



Related Reading


More Insights




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.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.