Archive for the ‘pain’ Category

Part 3 – Sell Differently

I’m continuing this series of blogs here by looking at the techniques that software vendors can use to create the “illusion” of differentiation in markets where technical standards have led to little material product difference.

Perhaps the most obvious differentiator between organisations that have “broadly” similar technology, and an area that particularly hurts smaller or less well established software vendors, is the vendor’s approach to selling.

Which audience strata do you aim at and what do you say to them?

At its most crude this can be the difference between Vendor A talking to a technical audience about the features of Product A whilst Vendor B is talking to line of business managers within the same company about how their product will provide some business benefit or other. Two similar offerings, with similar capabilities being “sold” in very different ways to very different parts of the same organisations.

The benefit of selling at a business level is enormous.  Decisions get made at that level, budgets get signed off at that level and enterprise-wide relationships get built at that level.  However, the difficulty with this approach, especially for smaller or less well connected vendors, is that gaining access to senior management outside of the IT domain of their prospects’ organisations is very difficult.

It takes years of building credibility and demonstrating proof of delivering benefits (reducing risk, Increasing profit, saving time,removing cost, etc.) to buy a ticket to the business-benefits ball.  Unless you’ve paid your business benefit taxes, have documented how you’ve helped deliver benefits and have an army of references willing to stand up on your behalf you’re likely to not be taken seriously.

In addition, in my experience, the skills that a sales exec needs to credibly describe the features of a technical proposition are usually mutually exclusive from the ones they need to engage a senior C-level exec in a discussion about the business issues that keep them awake at night.

So where to start if you’re a technology-focused vendor looking to sell differently?

Well it’s a journey and will involve dramatically changing the way your organisation thinks, behaves and looks.  Many of your staff will have to undergo a dramatic transformation and many won’t make it (especially the sales team).  Then you need to look at developing marketing messages for IT Business and the Business audiences.  You’ll do this by talking less about specific product capabilities and instead aligning yourself with where the prospect wants to be AFTER they’ve done business with you.

What are their pains, what are they looking to achieve, how can you help them do this and what proof can you provide that you’ve done it before?

The marketing materials and programs that support such a business audience-focused sales approach are very different too.  And whilst this has a significant impact on the structure of the marketing organisation, perhaps the biggest challenge is that just because you’re now selling to a business audience doesn’t mean that you stop marketing to the technical audience.  We still have to convince these guys that we’re able to do the job. So now you’re waging a marketing battle on two fronts and this means significantly greater investment.

But before embarking on this approach you should ask yourself whether you’re committed to the journey.  I’ve worked for, and with many organisations that have seen “selling to the business” as the holy grail, the panacea to address their competitive losses and their inability to control the sale.  But embark on this journey without fully committing to the changes it WILL have on your organisation and it will lead to a bloody disaster.  I speak from bitter experience.

Well that’s about it for the “selling differently” approach to differentiation in a homogenised market.  The benefits of selling at the business level while your competitors are talking to “minions” in the technical side of the business are enormous, but as I’ve mentioned about it’s not an easy journey.

I’ll cover some more differentiation techniques in coming blog posts.

Danny Goodall

I’ve just had a conversation with a friend, an ex-colleague who was picking my brains (for free I might add!) about what he could do to make his sales year look better.

I asked him how his product was positioned and where his focus was on the market. He told me, and in doing so mentioned 3 industries, 3 market categories and 4 sub market segments, 4 or 5 target audiences and a similar number of problems they address in each of the 3 industries. I told him that this isn’t a focus. It’s a hedging of bets. It’s a baiting of many hooks in the vain hope of landing at least one fish. My mate was embarrassed. He knows this himself.

Focus, especially in these tough times is an absolute necessity. If you can’t focus to the point of one or two key problems you solve, you can’t expect your prospects to work out what you do and what you could do for them, and don’t expect to be in business come the economic recovery.

And my mate’s company isn’t a small, inexperienced company lacking real marketing talent. On the contrary they have really good people. So how did they get themselves into this situation? The answer is that sales management, worried about the lack of leads and general interest in the product in the market had put pressure on the marketing organisation to “aim wider”, to target some of the areas the competition and other vendors in adjacent market segments were targeting.

The result? They were “targeting” everyone.

So it was the sales departments fault then? Well despite being a paid up member of the Marketing Protection League, I’m not going to endorse the marketing=good, sales=bad stereotype here. The marketing team was at fault. Sure the sales team were acting without a plan and not working from common sense, but that’s understandable.  Just as we’re led to believe that waterboarding can make you say and do things that you don’t really mean, so come the end of the quarter when the members of the sales team has to put various bits of their collective anatomy on the line, they will happily advocate changing strategy 7 times a day, 5 days a week.

So it’s up to the marketing team to lead the company through these crazy times. Understand your ideal client and what their problem is, understand the value you can provide them that will make them want to buy from you and understand why you’re different from the alternatives. Perhaps most importantly make every effort to gather intelligence that will tell you where your prospects are still spending money. Focus is what you need in these tough times.

Of course that is only half the story. Marketing can hand a map with clear directions to the rest of the organisation but it won’t stop them all heading off in different directions and ignoring the map. So that’s where the close relationship between sales management and the marketing team comes into its own. One plan executed with focus and passion by two teams acting as one.

Simple.  Well not really, but it’s not rocket science.

Danny Goodall

Pain, problem, need or desire

Continuing  the series of blogs looking at the elements of the positioning statement I’m going to look at the customer pain or problem section.

In this entry I will look at the pain, problem, need or desire that we believe that target customer is looking to resolve.  So just so we have a the context for the discussion, here is the positioning statement format that Lustratus uses.

FOR [the ideal customer] WHO [has this specific pain or problem] OUR [product name] IS A[product category] THAT PROVIDES [this main benefit and reason to buy] UNLIKE [the primary alternative or competitor] OUR PRODUCT [has this unique selling proposition].

In the last blog entry we had started to create the unique position in a prospect’s mind where our products and services uniquely sit.  We did this by first identifying the ideal client.  Now we’re going to expand on the ideal client segmentation by adding a specific pain, need or desire that the ideal customer can relate to or a situation that they find themselves in.  The “who” element describes the situation, nearly always negative, that the ideal customer finds themselves in and the implication is that we can positively alter the ideal customer’s situation.

The following questions often help to narrowing down the “who” element of the positioning statement:

• What is the ideal customer looking to do or achieve that they cannot do without help?
• What must the ideal customer do that they are struggling to do?
• What is the desired state that the ideal customer is looking to achieve?
• What is the problem that the ideal customer is wrestling with?
• What situation (needn’t be negative) does the ideal customer find themselves in?
• etc.

Some examples

In a previous blog entry on the positioning statement we looked at an example REPAMA reverse-engineered positioning statement for Microsoft ESB Guidance.  Here, we saw that Microsoft’s “who” section was was defined as:

WHO are building solutions that leverage the SOA pattern

For those readers who are not experts in SOA (service-oriented architecture) or the infrastructure software market in general, “SOA” here is an esoteric software architecture model that many organisations believe provides great benefits.  Microsoft, amongst other vendors, claims that its products help its users to implement SOA more effectively.

Microsoft is effectively saying that it believes that the situation its target customer (Microsoft BizTalk Developers) finds themselves in is that of ”building solutions that leverage the SOA pattern”.  Interestingly, in our attempt to reverse-engineer Microsoft’s positioning statement, we see that Microsoft has not aimed at an overtly negative pain for the ideal customer.  Rather it has chosen to simply focus on a situation the ideal customer finds themselves in.  Other vendors from the ESB REPAMA SAS report show a different approach to the pain.  Oracle with its Oracle Service Bus product chooses to identify the following area of pain in our reverse-engineered positioning statement:

WHO need to enforce quality of service, security and performance policies across an enterprise-wide network of multiple SOA domains

Progress with its Progress Sonic ESB product identifies this need

WHO need to connect many different IT resources using many different technologies in many physically different locations

So whilst Microsoft has chosen to simply state a situation, other vendors have chosen to highlight specific needs or deficiencies. Remember the positioning statement in its entirety should be used to make the ideal customer feel that you have designed and built the product (or service) specifically for them in response to their specific problems.  Other, more generic examples might include:

• WHO are struggling to implement the latest governmental regulation
• WHO need to remove costs from their IT operations
• WHO fail to bring new products to market ahead of their competition
• WHO are unable to ascertain their risk exposure in a timely manner
• WHO cannot currently meet their corporate governance requirements
• etc.

So that’s the main pain, need or desire section, I’ll tackle the “OUR [product name] section in a later blog entry.  <More information can be found in the Lustratus REPAMA Guide here>

Danny Goodall.

BTW
It should be borne in mind that Lustratus’ focus is on the high-tech software industry and whilst positioning as a concept will transfer to just about any business to business industry, many of the classifications we use assume that we’re dealing with a technical audience for infrastructure software.  So please bear that in mind for your own industry.

Positioning

Happy 2009! I’ve been in debate with a number of correspondents about the layout and format of the positioning statement that we use in the Lustratus REPAMA-based research.  So I’m going to dedicate the next few blog entries to the positioning statement.  I hope to answer the following questions.

• What is the positioning statement?
• Why use a positioning statement?
• What is the value of a positioning statement?
• What is the format of a positioning statement?

The first thing to say is that over the years, having worked with some of the best product marketing people in the industry, I’ve seen many different approaches to positioning and equally many different formats for positioning statements. Each of them, to a greater or lesser extent has been valuable.  Most positioning statements that I’ve seen and used have had a very similar structure.  Although I have seen some that have been very different, in fact more like a what I would refer to as a value statement or a value proposition.  Perhaps I will revisit them in a future blog but here I’m going to focus on the classic positioning statement.  So as I’ve mentioned there is no single way to construct a positioning statement but Lustratus has settled on a specific format that captures and conveys the seven key product marketing elements and it is this format that I will concentrate on here.

What purpose does the positioning statement serve?

It’s probably best to start with a definition for positioning first.  And if positioning statements are contentious then the the broader subject of positioning is even more so.  Whilst there are many views on this, for me, positioning is about creating a unique, compelling and defensible space in the minds of your prospects where your product/service and only your product/service sits.  Your ideal prospect must feel that you created the product/service for them alone to answer their specific problems and very importantly they must understand exactly how you are different/better that the alternative/competition.  Most product marketing professionals understand this well but as mentioned above, the development of positioning strategies and the statements that captures those strategies can take many different forms.

In my experience most positioning statements are designed to be internal tools for the development and then internal communication of a unique and compelling market proposition.  The positioning statement seldom gets used externally (with customers or prospects) in its raw format.  External marketing communications strategies are typically developed using the internal positioning statement as a guide.

The positioning statement conveys the following seven product marketing elements:

1. The Ideal customer
2. The main pain that the ideal customer has or the negative situation they find themselves in
3. The name of the product
4. The name of the product category – the generic way to refer to the class of product (I often see this omitted)
5. The main benefit that the product provides and the key reason that the prospect should buy the product
6. The primary competition or alternative
7. The unique selling proposition (USP)

The format of a positioning statement

A positioning statement is natural language-based and should read fluidly and easily as a single sentence and yet should contain all seven of the marketing elements above.  This sounds like a complex task and to aid us in that development we use a specific structure for the statement.  This is shown below.

FOR [the ideal customer] WHO [has this specific pain or problem] OUR [product name] IS A [product category] THAT PROVIDES [this main benefit and reason to buy] UNLIKE [the primary alternative or competitor] OUR PRODUCT [has this unique selling proposition].

So the “for”, “who”, “our”, “is a”, “that provides”, “unlike” and “our product” elements give our positioning statement the structure it needs.

An example positioning statement

An example positioning statement is shown below. It is taken from the upcoming Lustratus REPAMA Segment Analysis Study into the Enterprise Service Bus (ESB) market segment. In the study we reverse-engineer the seven marketing strategy elements of positioning statement (as well as many others) used by a number of the vendors in the ESB space – in this case the products examined were Microsoft ESB Guidance, Oracle Service Bus, Progress Sonic ESB and TIBCO ActiveMatrix Service Bus.  In the example below we’ve attempted to capture Microsoft’s position and proposition in the ESB market.

FOR Microsoft BizTalk Developers WHO are building solutions that leverage the SOA pattern OUR Microsoft ESB Guidance IS A loosely-coupled messaging environment THAT PROVIDES an infrastructure for enabling a service-oriented architecture UNLIKE traditional ESBs OUR PRODUCT provides a superset of ESB functionality, extending the ESB pattern to include modelling and execution of business rules, workflow, and adapter integration

It’s notoriously difficult to be precise when reverse-engineering a vendor’s positioning statement and sections like the “that provides” and “our product” are especially difficult to define precisely.  But hopefully it shows how an organisation like Microsoft might set about defining its approach to a particular market segment.

In the next several blogs I’ll expand on the positioning statement and cover each of the seven elements in a bit more detail.  <More information can be found in the Lustratus REPAMA Guide here>

Other posts in this series

The Positioning Statement
FOR… positioning element
WHO…positioning element
OUR…positioning element
IS A…positioning element
THAT PROVIDES…positioning element
UNLIKE…positioning element
OUR PRODUCT…positioning element

Danny Goodall.