Morettini on Management

General Management and Marketing Advice for Software and Tech Companies

Tag: product management

How Important Is Ease-Of-Use In The Software Business?

In a phrase–it’s ABSOLUTELY CRITICAL.

To some, this statement might appear to be a big “DUH, of course it’s important”. While this appears obvious to anyone with software industry experience, in practice a really intuitive user interface is actually quite difficult to achieve in practice. It really doesn’t matter if you’re in B2B or B2C–building a traditionally licensed product, SaaS, mobile or Open Source–ease-of-use is often the difference between success and failure. Unfortunately in my years in the software business I’ve seen considerably more applications that I’d consider to be hard to use than I have easy-to-use products.

Why ease of use is so important and what superior ease of use does for you

  1. You only get one chance to make a great first impression–and your user interface in many cases is that first impression.
  2. New prospects and users won’t even get to try out all of your neat and useful features if they view using your application as too difficult and give up.
  3. Outstanding ease of use can dramatically reduce your support costs–either by just reducing the amount of support personnel required or even allowing you to go to a “self-service” support model, via support databases and communities in the case of low priced products. This frees up cash flow for additional marketing and product development
  4. An application that is viewed as easy-to-use is by far the most likely to be referred on to friends and colleagues, creating the potential for a lot of viral-driven sales.
  5. A well designed user interface with advanced features hidden by techniques such as a customizable UI setup or a progressive disclosure approach can bring the best of both worlds–easy enough for beginners and casual users and sophisticated enough for power users.
  6. Supreme ease-of-use allows you to more effectively use “low touch” marketing methods such as Freemium Business Models and trial downloads converting directly to sales with little or no sales personnel required.
  7. Above all,  ease of is critical to creating happy, long-term customers

How to ensure you fully optimize the ease of use of your applications

  • Resist the temptation to add every feature that a user has ever asked for–or might ever. Complexity and feature creep can sneak in quietly and insidiously and are the enemy of a user-friendly application.
  • If your application is SaaS-based, resist the temptation to constantly “improve” the interface–just because you can. Often this improvement occurs without the user’s knowledge or consent and can be disconcerting to them. I use some applications that if I don’t use for a few months, when I login I can barely recognize them (Google Adwords is a notable example). This can be frustrating for even your most experienced users.
  • If you must add features for advanced users, use a progressive disclosure, customizable UI setup or some other advanced technique to hide these important-but little used features from average users.
  • Keep interfaces as simple and clean as possible–make certain it’s necessary before you add that last button or drop-down list box.
  • Conversely, interfaces can’t be “blank sheets of paper”. Ensure that the most important features are accessible from where ever in the application the user might want use them–sometimes TOO MUCH simplicity can itself make an application harder to use.
  • Nearly every application is complicated to a brand new user. Consider adopting a “new user wizard” approach to walk new users through there first few times through the application.
  • Even though the complaint is that “no one will use them anyway”, provide as much easily accessible help within the application as possible. Link the searchable user manual, context sensitive help, tool tips, video tutorials for common or difficult tasks, FAQs, community support boards and direct technical support. All of these improve your ease-of-use incrementally. Add anything and everything you can afford to provide that makes the user more self-sufficient–it will save you money and increase your revenue in the long run.

I’m sure that I’m preaching to the choir among veteran software developers, product managers and CEOs on this topic. But in my experience, it’s all too easy for ease-of-use excellence to slip under the pressure of getting the application out, responding to feedback from major users and just the general fatigue and blindness that comes from looking at a software application too many times. It’s understandable that any of these things can trip you up during a long and difficult development cycle. But in my opinion it’s critical almost above all other things to not let these and other legitimate reasons keep you from ease-of-use optimization. It’s your product’s most important feature.

What’s your opinion on the role of ease-of-use in the software business?  Leave a comment below with your own views or best practices.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

Software Product Marketing: Horizontal vs. Vertical

An important discussion for most software companies–both in the product planning stage and in the downstream active marketing phase–is the manner in which it will be marketed. The decisions to be made in each phase are separate but closely related. This set of discussions need to happen regardless of whether you are marketing a traditionally licensed application, an open source application or a SaaS application.

One of the more important aspects to this is whether the product will be aimed tightly at one or several vertical segments, or marketed more broadly to the widest possible audience. This is the crux of the vertical vs. horizontal decision. Let’s examine a few topics which can be useful in framing this discussion.

How specific is the “language” of your application to a vertical audience?

This is very important because in some product categories the unique business processes of a vertical can be very important, while in other categories there is great commonality in process and language across industries. If you’ve written your application specifically to solve one market segment’s unique problem, it’s probably VERY specific. When this is the case it’s pretty obvious that you’ll start (and possibly end) with a highly vertical marketing effort. Sometimes as thing go along you may find that you’ve solved a problem for market A, but it’s also useful in market segment B and C–although there often needs to be at least some modification. If you’ve solved a more generic problem that applies to many markets, the decision to market the solution horizontally or vertically can be much less clear.

How big is your overall market?

A key consideration when you’re entering a new market with a new product. The larger the market the more likely it is you will need to take a vertical approach get initial traction. In many cases this means verticalizing the product in the product development phase. But even if there isn’t a strong set of vertical needs with respect to product features and “language”, in large markets a vertical promotional approach may be required to build market traction. It is often far easier to build a brand name and market traction in a tight vertical before you move on to the next segment, than by taking a more scatter-shot approach with no vertical focus.

What is the level of competition in the overall market?

This question is related to first question above as strong competition often goes hand in hand with large markets. They are separate issues, however, and should be evaluated individually. If the level of competition is high, regardless of market size, a new entrant is likely to have a better chance of success with a more vertical approach. It there isn’t significant competition in the segment, you may be able to have success with a horizontal approach, which can be a more efficient way to use both product development resources and marketing dollars.

Market maturity: has the overall market verticalized already?

Regardless of the level of competition and the market size if the larger market has already evolved into a number of vertical sub-markets, it may be too late to take a horizontal approach. It is usually very difficult to defeat entrenched verticalized competitors when entering a market with a horizontal application. The exception to this would be a new competitor with a product that provides a quantum leap forward in functionality (usually as a result of a technological paradigm shift).

What level of marketing resources are available to you?

The level of marketing dollars available to you are quite important in formulating your approach to the vertical vs. horizontal question. As one example, let’s say you are entering a market that is large, quite competitive and you won’t have a lot of marketing budget available. In this case, it would be very important to develop the product upfront with the strongest vertical focus possible and market it accordingly. On the other extreme, you might be entering a market of modest overall size that hasn’t verticalized to a great degree to date and you are well funded, enabling a substantial marketing budget relative to the competition. It this case it might be an easy decision to take the ROI-efficient horizontal approach both from a product development and promotional perspective. There are many potential scenarios between these two extremes which unfortunately will lead to less obvious decision-making.

Is your software a “point” or “platform” application?

Most software applications are “point applications”, meaning they have little or no integration with the rest of the software infrastructure. In addition, any possible customization is generally intended to be done by the application vendor themselves or maybe their channel partners.

I define a software application as a “platform” when it utilizes an open API which enables BOTH channel partners and third party software vendors to write add-on applications which extends the platform software’s functionality in two key area:

1)      by adding “vertical” functionality not present in the platform software thereby enabling a complete solution for a specific vertical market.

2)      using the API to integrate the application with other parts of the software infrastructure

In this way a platform software application allows a software vendor to “have it’s cake and eat it too” with respect to the Horizontal vs. Vertical discussion. The platform software itself provides basic functionality which can be sold broadly across many markets, while the open APIs enable the product to be tightly customized for specific verticals as required, by both your channel partners and independent ISVs. The platform application can be a product manager’s dream and is the Holy Grail of software when it comes to efficiently serving as many market segments as possible by leveraging partner investments. But it’s not something that can be forced; there needs to be a natural reason for the platform to exist, or there will be no third parties willing to write the add-on applications so critical to the platform’s success. Without these add-on application a platform will more often than not die a quiet death in the marketplace.

In some cases, such as when you write an application which aimed at a problem specific to a single vertical market, the answer to this “vertical vs. horizontal” question is easy. In many other cases you’ve created a product which is useful across several market segments–but do you have the resources to attack multiple market segments simultaneously? How do you approach this common problem?  Leave a comment below with your take or shoot us an email with your questions.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

Musings on Software Market Segmentation and TV Morning Shows

I like to check out one of the morning TV shows on one of the major US-based networks for a few minutes, as I’m eating my breakfast cereal. There are 3 major programs on at the start of the day: NBC’s Today Show (the traditional market leader), ABC’s Good Morning America (the perennial runner-up) and the recently re-branded CBS This Morning in (last place for many years).

So what the heck does this have to do with software market segmentation, you ask?

I’ve been struck by how much the morning show race reminded me of the software industry has become more vertical over time. In particular, there are some strong parallels between the software business and the morning shows with respect to the product being “soft enough” to make relatively easy product changes as part of a new segmentation strategy.

Recent changes in strategy on the TV morning shows

The Today Show has been the “10,000 lb Gorilla” of the morning shows since the beginning of the category. They’ve had a large lead over their competitors across multiple changes in on-air personnel and even societal cultural changes over the years. The Today Show’s format has been aimed at a “horizontal” audience–a little bit of something for everyone. They start with hard news at the beginning of the show and it gradually becomes “lighter”, transitioning to Pop culture, celebrities and gossip as the show progresses through its marathon 4 hour time slot.

The other two major shows have taken a real beating at the hands of NBC in the ratings, with many tweaks to their formats and even more turnover in personnel over those many years. Fundamentally they have tried to compete by “building a better Today Show”, essentially competing head on with the market leader in a horizontal fashion. But over the last couple of years, ABC and more recently CBS have changed their strategy, utilizing a much sharper segmentation than at any point previously. ABC has essentially gone “younger and lighter” over the last couple of years. The show has the least serious tone and is the most “fun” of the three, focusing a lot of time on pop culture and other topics skewed toward younger viewers. It’s paid off. Good Morning America has taken a clear lead over the Today Show due primarily to this new segmentation and to a lesser extent some personnel missteps at NBC.

After many years in last place, CBS has segmented sharply in the other direction with a shorter 2 hour program focused almost entirely on hard news and staffed by serious, credible news people. It’s too early to say how successful this will ultimately be for CBS, but they have won over this writer and have picked up some market share overall-I’m watching consistently CBS in the morning for the first time. The Today Show has been struggling to remix it formula and regain its clear lead, looking much like a complacent large company that has grown fat, dumb and happy as a result of years of unchallenged success.

Software Market Equivalents

Ok, enough about TV morning shows! How does this relate to segmentation in the software market? A very similar situation albeit in a B2B rather than B2C market, is the ERP software market. The ERP market is also a very large, horizontal market–a mass B2B software market, if you will. Just about every company in the world needs some type of ERP software to run its business, from an entry-level, basic accounting application like Intuit’s Quickbooks all the way up to very expensive, complex enterprise suites such as offered by Oracle, Microsoft, SAP and Sage.

This of course is one form of verticalization–segmentation by target customer size and sophistication. Intuit and Oracle aren’t targeting the same segments. But the ERP market is so large that over time it has also segmented by industry; nearly every industry group of any significance now has ERP software vendors with specialized applications aimed at a narrow industrial segment.

Another similar example is Medical Practice Management Software. The last time I looked, there were over ONE THOUSAND software vendors with products targeting this very large market. You would think the software requirements of most medical practices would be pretty standard across the board. But because the market is so large and lucrative, nearly every market segment (Surgeons, Gynecologists, Dentists, Chiropractors, etc.) has it’s own sub-market of competitors, with applications that speak that particular medical practice’s lingo and strictly models its business processes.

I have a personal example from earlier in my career that illustrates how important segmentation can be as part of a software company’s overall strategy. I took over as CEO of an early stage mapping software company with excellent technology but an unsophisticated business strategy. While the company had a neat technical advantage over its larger competitors, the product otherwise was positioned directly against the market leaders in that space. The primary distribution channel for the mainstream mapping products of the time was computer and electronics retailers, a notoriously tough and expensive channel. I was able to make some headway in penetrating this channel. But even with our technical feature advantage it was already too late in the game and we lacked the resources to compete and win head-to-head with the larger market leaders of that time.

So we quickly came up with a segmentation strategy that proved quite helpful. Initially we took out some features away from our primary product and created an entry level product priced far below the mainstream mapping products. This allowed us to occupy the price leader position targeting the most price-sensitive consumers, and distribute through both consumer/gaming software stores of the time as well as mass market retailers such as drug and grocery stores. The mainstream mapping software players had almost no presence in these channels due to their higher price points. This entry level product, created with minimal development costs, allowed us to generate cash flow to fund our longer term segmentation strategy which was to target the B2B market. The mainstream mapping products were fairly generic and used by business people as well as consumers, but really designed for any consumer with no business-oriented features to speak of. We were able to create a premium, business-focused version of our product which we positioned as the mapping products for mobile workers/road warriors such as sales reps and service technicians. We included important business-specific features, such as integration with the popular CRM systems of the day, which weren’t found in any of the other mainstream mapping products of the day.

Important considerations in segmentation strategy

Hopefully we’ve established that segmentation of your software market can be a very powerful tool to compete with and outflank strong competitors and ultimately maximize the value of your business. So what are the important things to consider in formulating your segmentation strategy? Let’s look at a few:

Horizontal vs. Vertical – The first thing to consider is how horizontal your segment currently is and how vertical you think you need to be to compete effectively. There is a fine line here; the more horizontal you can remain (targeting multiple segments with the same product) the higher your product’s ultimate profit potential. But you must be realistic about your market position–go as “vertical” as you need to win–or your profit potential is likely zero!

Market Maturity – The more mature the market is when you enter, the more likely it will be important to segment smartly and attack a vertical niche. Of course this or any single factor shouldn’t be used in a vacuum to create a strategy–many factors need to be considered in your segmentation decision.

Market Size – The larger the market size, the more likely it is that it’s ALREADY segmented and will likely force you to do the same. There are several prominent potential exceptions here, listed in the bullet points below.

Market experience of the company - Do you know the market well, and just as important, are you known by the market? In cases where you’re known and understand your market well, it raises your odds of success even entering with a more horizontal approach.

Levels of funding – Big companies with massive resources or heavily funded startups may be able to successfully  use a horizontal approach, although many confident late entrants of this type have failed in a variety of software market categories.

IP/Technology & other strategic advantages – A true innovator with market changing IP may also be able to attack and win in an established market using a horizontal approach, as they are effectively changing the ground rules of the market. But again, I’ve witnessed many companies very confident in their technical advantage that have ended up with their hats handed to them when competing head on in an established market.

Important upfront decision–but never too late to change

Like any important business consideration, it’s far better to optimally segment the market for your products up front then to wait until you are FORCED to do so. But just like a morning TV show, in the software business it’s relatively easy–at least compared to other technology categories such as computer hardware or semiconductors– and almost never too late to modify your target segments.

What’s your feeling on how best to approach segmentation in the software business? Post a comment so we can all benefit from your experiences.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

Separating Technology Wheat from the Chaff

In software and hardware businesses new ideas, technologies and products come down the pike at a rapid-fire pace. Many fail immediately and some muddle along before finally fizzling out. Some meet with modest success. Only a very select few turn into long run big hits. How can you tell which products will become hits, out of a sea of mediocrity?

Not many people can differentiate between these new ideas, technologies and products at an early enough stage to profit massively from it. Keep in mind I’m not talking about small successes, but the really big ones. The ability pick the big winners out early is a rare skill set, yet one that is applicable across a wide swath of functions including general management, product planning/management, inventors, venture investing, stock analysis/selection and many more.

Short of having a brilliant mind, multidisciplinary worldview and the ability to see the future—how do you go about maximizing bets on what will hit it big and what won’t? Here are some questions that may be useful to ask when making your evaluation:

Does it solve a fundamental problem, bend a cost curve or create a new playing field?

Not every new product is based upon a fundamental technical breakthrough—but it sure helps! After all, innovation is still the basis of the technology business. This is where you look first when seeking big ideas you can profit from, something that fundamentally changes the game in a particular marketplace. One of the most spectacular examples of a breakthrough that met all three of these criteria is the personal computer. It solved some fundamental problems of the time associated with mainframe computing, certainly bent the cost curve of computing downward (and continues to due so even today) and created an entirely new ecosystem with broad societal implications. Meeting all three of these criteria is a very tall order that you won’t see often, but passing one of these three tests is almost essential for a big-time winner with staying power.

Where does it fit in the marketplace?

There are certainly many great stories of fundamental research breakthroughs without immediate, obvious market applications that ultimately found a market and became a great hit. The problem occurs when the second step—finding a market—is given short shrift, or skipped completely. This can happen when there is pure excitement and the folks funding the project have a purely technical viewpoint. The number of big successes without expert market vetting is actually pretty rare although there have been some spectacular exceptions.

We’ve all heard of the invention of super glue by accident. And Thomas Watson Senior, Chairman of the IBM Corporation in 1943 was quoted as saying: “I think there is a world market for about five computers.” Five units do not make a commercial market, but IBM made the investment anyway—and look how that turned out. But in reality the number of fundamental breakthroughs in the research lab dwarfs the number of truly successful, innovative new commercial products. So it’s important to not get too excited about these breakthroughs until a commercial application becomes obvious and realistic. Avoid at all costs the proverbial “Cure looking for a disease”, regardless of the almost mythical stories of a few massive winners borne from purely technical circumstances.

How does it compare to alternative solutions, both current and forecasted?

After deciding the breakthrough isn’t a cure looking for a disease and which market segment it fits in, it’s also very important to evaluate how it stacks up vs. rival technologies and products. And not just with respect to a current market snapshot, but looking forward as well. Forecasting really comes into play here; which technical platform has the longest runway? An example is satellite TV vs. Cable TV. When Satellite TV came into play it took a lot of market share quickly by providing innovative new services which the utility-like Cable TV companies were slow to match. But in the long run the wired infrastructure of the CableCos may provide a strategic technical advantage in that long running battle that may enable a more advanced and diverse product set.

Do the owners have what it takes to bring it to market?

This question applies not only when evaluating someone else’s product or technology—but also your own. Realistic self-reflection is important here. There have been some great new innovations that have been wasted due to bad marketing, lack of financial resources or just plain ignorance and incompetence. These weaknesses often lead to the “ arrows in the back of the pioneer”, where the folks that initially bring out the “next big thing” fail or are quickly overtaken by a more tactically skilled competitor, who improves on the idea and/or out-executes them in the market. The software spreadsheet market is instructive here, conjuring up images of several bigger fish progressively swallowing smaller ones. Visicalc was the original spreadsheet innovator overtaken by Lotus who was then in turn overtaken by MS Excel. The resources and capabilities of the innovation’s owner matters a great deal in the long run.

Is it defensible?

This is what often separates the “flash in the pan” from a true long term winner. Defensibility can be defined by the traditional technology means of patents, copyrights and trade secrets. But there are more subtle ways of defense that can be very successful in the long run: branding, entrenched distribution channels, strategic partnerships and cost advantages.

Especially in the software and hardware businesses there are tons of fast followers, who are lying in wait for an emerging trend or new market segment, where they can apply deep resources and tactical skill to out-execute the pioneers. In hardware markets the major Japanese manufacturers long ago mastered this model by taking US inventions and productizing them cheaper and better. The large Korean manufacturers then found success with this same model and most recently it’s been replicated by the Chinese. In the software business Microsoft and other large software companies have grown by either mimicking or buying up technology leaders who have pioneered a new market segment. However it’s done–make sure the next big thing is defensible before betting on it becoming a big-time, long term winner.

Does it pass muster from every angle?

As stated earlier, it really helps to be a “renaissance man” man with a multidisciplinary worldview. But people meeting that description are in very short supply, so it’s really important to employ experts across several key disciplines such as technology, finance, manufacturing and marketing, to evaluate market potential and possible weaknesses. In the technology business marketing and technology are usually the key differentiating factors, so at a minimum make sure that expertise is brought to bear in those areas during your evaluation.

There you have my view—how to do separate the winners from the losers. Post a comment with your own view of this very debatable topic.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

Is Your Tech Business Marketing or Sales Driven?

Software and hardware business are often segmented by the vertical or horizontal market they’re targeting, their technology platform, small vs. large companies and so on. One of the important ways to segment tech businesses, which isn’t often discussed, is by whether the company is sales-driven or marketing-driven in their customer acquisition strategies.

A balanced approach

Now some reading this article may ask “why wouldn’t you take a balanced approach”? Indeed, I don’t mean to suggest that either sales or marketing should be absent in the customer acquisition efforts of tech companies. There are a few scenarios that could be drawn up to support such a singular approach—but very few for sure. There are also some situations where the customer acquisition circumstances are “in between” in price, complexity, market size, etc. and you end up with a fairly balanced approach between marketing and sales. But in my experience the sales or marketing function will rise to the lead, more often than not.

Key criteria in choosing customer acquisition techniques

There are several considerations that often drive whether marketing or sales will dominate:

  • Product Complexity – This often decides whether or not a product can be truly driven to purchase by marketing or whether significant sales rep intervention will be required to close a deal. It should be noted that when product complexity is high, marketing support in the form of sales tools (examples: case studies, road map presentations by product management) will still be very important in the sales cycle. But this will generally be a sale that is driven by the sales force with marketing in a supporting role.
  • Product Price/ Typical Sale Size – The smaller the product price and typical sales size, the more likely you’ll be able to acquire customers exclusively through marketing, or in conjunction with inside sales that is largely “taking orders”. Conversely, products that cost a lot may require the extra interaction provided by an outside sales force (and the deal size also justifies the cost of the sales force).
  • Market Size – Very large markets with lots of customers are more easily and cost-effectively reached with effective marketing. A tight market with a small number of total prospects (think nuclear power plants) will usually be served almost exclusively by an outside sales force with minimal marketing intervention.
  • Use of Channels – While companies selling heavily through channels often need reps to call on the channel partners, far fewer channel reps are required than if the reps are dedicated to direct selling. Generally the heavier the use of third party channels in the customer acquisition approach, the more heavily the mix will lean toward investment in marketing.

Marketing driven keys to success

  • Adequate marketing funds – If you’re going to be marketing-driven in your customer acquisition approach, you better dedicate enough money to fund marketing programs with superior performance. To do otherwise will cripple your business.
  • An objective, data driven culture – The beauty of a marketing-driven approach is that it can take much subjectivity out the management of optimizing your customer acquisition activities. Especially in this era of highly measurable online marketing, decisions should be made on what the data says—not on the whims of the CEO or some other senior executive.
  • Excellent inside sales in support – Except for very simple, low cost products where marketing can truly drive the sale all the way to completion—these days that often means a software download, SaaS signup or physical product order—it’s still important to have an efficient (but low cost) inside sales operation supporting your marketing machine.

Sales driven keys to success

  • Great sales people – Hiring good people is so very important in every area, but when your relying on an expensive outside sales force to drive revenue—you better hire the best reps you can afford and attract.
  • Success driven comp plan – If your success depends upon them, make sure your sales reps become really happy only when the company is happy as well.
  • Good marketing support in the form of lead generation programs and sales tools – Unless you have a tiny market with obvious, easily identifiable prospects, it’s still very important to have a marketing function which generates leads as well as supplies good sales tools.

The best approach isn’t always chosen

Unfortunately, logic and situation analysis doesn’t always win out when designing a customer acquisition strategy. Usually by the time a company grows to be large, their approach is in line with what’s best for the business. Of course, your chances of growing to be a big company are reduced if you make serious errors in sales and marketing strategy. But in any event, by the time a company is big they are usually utilizing both sales and marketing heavily and in the proper balance.

Startups and early stage companies are another matter. Often the emphasis on either sales or marketing is based on the experience of the founders and senior executives. If they’ve been successful in the past and their new company has a similar focus, maybe it’s fine and their approach works again. But a problem occurs when these executives start up a very different type of company than they’ve had success with in the past. It’s human nature to fall back on what I refer to as your “common business sense”, which is formed by your personal background and past experiences. This is when you can get a misalignment between what a company needs and the approach taken in the sales & marketing mix.

Even worse still is when the customer acquisition approach develops more or less haphazardly. This can happen when the founders of a company really don’t have much functional experience in sales or marketing. This occurs somewhat frequently in software and hardware companies, as many startups are created by technical types. In these cases there may be a fairly unsophisticated approach to both sales and marketing—and whatever works early may end up dominate. For example, a sales rep is hired who has some success, so the model becomes hire a lot more reps and turn them loose without much (or any) support on the marketing side. Or an early direct email campaign or online advertising generates some sales, so money is poured into that method. Unfortunately, these may not be the best approaches strategically for the business in the long run.

That’s what I think about Sales vs. Marketing driven orientations in software and hardware companies. What do you think? Post a comment with your own opinions or stories about what drives customer acquisition in high tech companies.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

Optimal Levels of Formal Process in High Tech Companies

The level of process in an organization is a pretty esoteric topic that I haven’t seen discussed very often, or in very much depth. Yet I believe it is critically important to any CEO looking to grow a company, particularly a software or hardware technology based company.

The reason I believe it is so important is that, in aggregate, how process-oriented your company culture is effects every nook and cranny of company operations. Oftentimes, however, senior management doesn’t even explicitly think about how much process they want governing company operations. More often than not, this part of the culture grows in a random and haphazard manner, driven by unforeseen key events that shape the level of process. Sometimes the level of structure varies dramatically by department. In these cases, managers below the senior executive level usually are driving department cultures that may or may not be process-oriented, depending upon their own operating styles. The key takeaway here is that process levels often aren’t being driven strategically, but occurring tactically or even haphazardly. This is usually a mistake–here’s why I think so.

In technology companies, in particular, the level of processes can make or destroy your business. There are three reasons that I feel there is much more sensitivity in high tech companies to process levels:

  1. The rapid evolution of technology and technology markets
  2. The need to innovate if you want to thrive in technology businesses
  3. The necessity and difficulty of constantly ‘taming” new technology

I’ll use as an example a recent experience with a client to illustrate my point. The client is a small but growing software company. They have in their culture a high level of chaos, as is common with many growing, young software businesses. The company was bootstrapped and grown out of what started as a service business, and possesses very little in the way of corporate controls or processes.

On the positive side they are very responsive, fast-moving and innovative, able to capitalize on changes in technology and inefficiencies in the market. These are very important qualities in a software startup, particularly one of the thinly capitalized variety. These attributes are the very reason they’ve been able to crack through the very early stage that kills many startups, and has allowed them to grow and thrive.

But there’s a flip-side to this type of unstructured corporate environment, however. This company lacks the discipline that is required to “stick to the plan”. Indeed, there is very little planning going on to begin with! This operating style fits great in the segments of the business where innovation is critical, such as conceiving new products. But in other areas where a more disciplined, structured approach is important, performance is much lower and is a drag on company results. While excellent at conceiving and quickly prototyping new products, follow-on releases often come out much later than planned. QA is not a formal function and the initial new releases and documentation are lower quality than they could and indeed should be. The website has very little oversight and is littered with a lack of consistency, broken links, old content and grammar & spelling errors. We’ve  worked on correcting these problems — carefully — without killing the very environment that is enabling success. It’s tricky to fix without “throwing the baby out with the bathwater”.

This is just one example, and of course the level of process needed to run IBM optimally is fundamentally different from that of an early stage software startup. In your particular company, it may be very important to have a high level of formal process in one department–and just as important to minimize the level of process in another. This may be quite different altogether in other companies.

So how do you know that you need to adjust your level of process in a strategic sense? Here are a few guidelines to get you thinking about where your process level stacks up vs. what may be optimal:

Your competitors are beating you to the punch

This is a sure sign that you are bureaucratic and process-oriented relative to your market. While there may be good reasons for the processes you have installed, being consistently behind in responding to market needs can have a very negative effect on your growth prospects.

You are constantly releasing “flawed” products into the market

This is the converse to the first point above. It usually indicates you moving too fast, with too little process and structure in product development, QA and release. In truth, the end results of this approach is usually worse that being beaten to market.

Employees are complaining about so much process

I always listen to what employees are saying; they are the “canary in coal mine”, often a leading indicator of issues that later show up in your financial statements. The caveat here is that these types of complaints can also indicate a hiring problem. Make sure you’re not hiring people who’s operating style aren’t a good fit with the way the company needs to operate.

Employees are complaining about the lack of process controls

The converse to the point directly above is when employees are complaining about how much chaos exists in the company. While the point above about watch for hiring mismatches rings true here as well, this is often the time you need to take a hard look at adding some structure to how you operate.

There’s absolutely no “chaos” in your organization–and little or no innovation as well

I have a rule of thumb when it comes to pricing new products: if no one is complaining about price, you probably are leaving money on the table. My “chaos corollary” is similar: if there is no chaos in your operations that folks are complaining about, you probably have created an environment so process-oriented it will limit your innovation and resulting revenue.

Generally speaking, I have a bias towards a little less process and a bit more chaos in software and hardware companies. Often excessive process is just a bad band-aid covering up poor hiring practices. Nothing allows you to minimize process like a strong, responsible, empowered group of employees. Creating the environment to hire and retain highly responsible people generally leads to a company getting done everything it needs to, with a good level of innovation to boot–while keeping formal process to a minimum.

I recommend holding off adding new processes until you absolutely have to, because going the other direction is much more difficult. But in fact, it’s important to have the proper balance if you want your company to function optimally. Analyze what the proper level of structure and process is not just for your company overall, but in each discrete operating segment of your business.

There you have it–my view on how to analyze and instill the proper amount of formal process for your company. What’s your view on this topic? Post a comment to expand the discussion.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

Starting Software Product Businesses Within Service Companies

The focus of my consulting practice is on commercial software product businesses, whether traditionally licensed, mobile, open source, SaaS–or some combination of all. While many software product businesses are originally organized with that purpose in mind, a remarkably large number of others started in another business. Let’s take a look at a few service-oriented scenarios which tend to grow into or spin off software product businesses:

Software (consulting) services

It’s very common for a product to be developed out of a software services company, which can mean a range of services such as consulting or outsourcing. These companies are being asked to design/create full applications, either for internal use by end user customers or as actual commercial software products. As a result, these service companies are in good position to recognize software product opportunities; sometimes these products are created by a funded service contract (if the service company is savvy enough to retain code rights!).

Government contracting

This is a very similar situation to the Software Services example above, with a couple of important differences. Government contractors are often not pure software development organizations; they may create hardware or provide other services as their government customers dictate. So they may not have a culture which emphasizes software development. Even more importantly, it can be tricky to retain rights to code developed with government funding–contracting expertise and an upfront emphasis on rights retention are critical in these circumstances.

Hardware/Systems

Another common scenario is software developed within a hardware or systems-oriented company. While not strictly fitting into the service category, I’ve included this example because it’s another common way software product companies are started that doesn’t fit the traditional methodology. The fact is that even in hardware companies these days, most of the innovation and IP is software-based. So it’s not at all unusual to see software developed as part of a systems approach that is later seen as having a market as a standalone application, apart from the hardware. Many successful software companies have started as spin-offs from hardware or systems-oriented companies.

VARs

Here’s another slightly different flavor of the Software Consulting Services example we began with. VARs are solutions providers for end user customers and are frequently asked to extend existing applications which are lacking in some way, integrate these solutions with other applications, or even write a standalone custom application. They are therefore well-positioned to get an early view of (and sometimes a customer-funded head-start developing) products needed to satisfy unfilled end users needs.

End user

End users often have in-house development capabilities and develop their own applications. In this case, the “service” organization is the internal IT department. These applications are often developed because of a “hole” in the existing commercial product offerings available in the marketplace. Forward thinking organizations may further develop and then spin-off these internal applications into commercial products.

So that’s a look at how organizations which aren’t-software product-oriented end up with a software product business. It can be a really great way for a software business to start–but there are many things that can prevent the successful transition into a going concern software product business. Here’s a list of a few:

Issues Which Can Prevent Success:

Culture

This is a frequent culprit in the failure of product businesses which are developed in the various service environments as discussed above. Depending upon the parent’s business, a mismatch in culture can come from a lack of understanding of either the software or product aspects of the resulting new business. For example, the management team of and “end-user” company that has developed a product may not be sufficiently software-savvy to make the right decisions to put the new business on a solid footing. A business executive in a software services company may not understand what it takes to develop a product to commercial product standards, or successfully market it. One of the biggest mismatches in culture often occurs within a government contractor. The “common business sense” required to be successful in the contracting business is shockingly different than that of a commercial software product business. The cultures are nearly polar opposites–It’s like English vs. French.

Capitalization

Often the cultural differences listed above or low overall capitalization of the parent company leads to the most common problem of these software product spin-offs: lack of proper initial capitalization. One of the attractive aspects of the software business is that it requires much less investment capital that a manufactured goods business–but it’s still a product business. Product businesses require more capital than service businesses. So even if you’ve created a great mousetrap, if you don’t have the money required to continue to develop it as well as market it–at least until you’re cash-flow positive–failure is quite likely.

Not productized

Maybe the most common problem of all is the lack of “productization” of the software application prior to launch as a commercial product. The level of usability, functionality and reliability required in the commercial product marketplace far exceeds the standards of the custom software application market. When you are supporting a single company directly with a custom app, you can afford a level of support which can overcome minor deficiencies in the areas listed. Once rolled out to a mass market of users in the software product marketplace, these deficiencies can kill a promising new product very quickly.

Me-too Products

One of the areas of expertise lacking in a service-oriented company (almost by definition) is Product Marketing/Management/Planning. The lack of this functional expertise can lead to a number of mistakes. One of the elementary mistakes that I see surprisingly often is not ensuring that you are making a novel “contribution to the market”. A software product startup with the 19th product to enter an existing market, with no discernable competitive advantage, is a great way to lose money.

Lack of software product industry experience

If you add up the potential mistakes listed above, most of them can be mitigated by the addition of software-product company operating experience. Sadly, in many instances the parent service company senior management is too proud or simply ignorant and unable to acknowledge this weakness. This potential weakness can be alleviated by hiring an experienced operating executive, or retaining a software product industry management consultant such as PJM Consulting.

The bottom line to all of this is that there are alternatives to the more conventional approaches of creating a traditional investor-funded or founder-bootstrapped software product company. Whether created intentionally from the beginning or a “happy accident”, companies started this way can provide an advantage of significantly reduced capital-requirement-to-profitability compared to traditional startup methods. But there are potholes and roadblocks that must be avoided to prevent crib death of embryonic software startups born this way.

So that’s some of the lessons I’ve learned with regards to creating product businesses from service companies. Is this something you’ve done or witnessed others attempt?–what were your results? Pitch in with your two cents — post a comment to expand the discussion.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

Is Outbound Marketing Dead?

The craze in the marketing world these days is “Inbound Marketing”–otherwise know as “content marketing”, “permission marketing”, “new marketing” “modern marketing” and a few other buzz-terms. The definitions may vary slightly, but they’re essentially variations on the same theme:

Potential customers find you, rather than you (the marketer) approaching them.

The current commentary on marketing methods goes like this:

People are insanely busy these days, and constantly inundated with marketing offers of all kinds, causing them to tune them out. Traditional outbound methods such as direct mail/email, advertising, etc. no longer work as a result. The answer is to use inbound marketing methods, defined as to driving traffic to your website via search engines, content (such as blogs and videos) and social media. Since these users have found you, they are by definition more attentive and better qualified targets.

Of course, although this discussion is very hot in the marketing world today, it isn’t really a new topic. It’s an argument about Push vs. Pull marketing, concepts which have been around nearly since the beginning of marketing as a science. At any rate, the preceding paragraph makes a lot of sense, does it not? No denying that getting boatloads of prospects finding you is a good thing.

The problem I see is that like most “trends”, the inbound marketing case is being grossly overstated. There is no doubt that the Internet has enabled pull/inbound methods grow to a degree not previously possible. If you’re a software or tech company marketer, in almost every market/product situation you should be leveraging online inbound methods to the max. But is that all you should be doing?

Of course not. Some companies may be able to fill their pipelines using only inbound methods. But this shouldn’t be an either/or discussion. In almost every situation, both inbound (pull) and outbound (push) should be used. They are not competitive methods; they each serve a different purpose, and are actually very complementary. Let’s take a look why:

Different psychographic profile of prospects

Prospects are not a homogeneous group in any market. They come in all shapes and sizes–early adopters, mainstream buyers, late adopters, etc. As a result, they respond to different stimuli, and have different buying styles. Many want to be totally in control and never have any “invasive” marketing targeted at them. But for every person that is offended by any offer directed at them, there are others who are happy to receive a timely, targeted offer which saves them money–as well as time– in searching out a software or hardware product they need. This is especially true for some very busy folks, and others that absolutely hate the shopping process. Outbound marketing can be a real advantage with these prospect profiles.

Different stage in the buying process

This is a key point which someone relatively new to marketing may not understand. If you have a prospect in the active buying stage, inbound marketing works great. Since they are out searching for your product or service, if you’ve done a good job on inbound marketing activities, there is a good chance they will “find” you. But what about those target prospects that aren’t yet in active buying mode? Should you just be ignoring them? I think not. First of all, you absolutely want to get a leg up on your competition and get your message to them as early as possible. By doing this, you’ll be on their short list of vendors to check out when they are ready to buy. But the right offer can also turn that future prospect into an active buyer–without so much as a look at the competition. What happens to your odds if yours is the only marketing message they see? Outbound marketing is much more effective than inbound in this scenario.

Timing vs. budget

From a marketer’s perspective, outbound and inbound marketing may fulfill different needs. Inbound marketing may provide a solid, day-in-and-day-out flow of leads and revenue. Outbound marketing can provide a more instantaneous bump to your numbers. Think PPC advertising vs. SEO. An inbound marketing technique like SEO is probably the more powerful activity in the long run, but and outbound method like PPC advertising can start creating business almost instantly. This outbound marketing bump can be very useful during slow periods where you’d like to “smooth out” your numbers, when you’re just getting started, during a busy (but competitive) holiday buying season or to give extra emphasis to a new product introduction.

Targeted Offers

Since you have greater control with respect to when a prospect will be exposed to an offer, it’s much easier to provide urgency and that critical timeliness component via outbound marketing. In addition, targeting can also be easier with outbound methods.  Direct outbound marketing, in particular, can be highly targeted if good lists are available.

Push and pull on the same prospect

Lastly and very importantly, this really isn’t an either/or argument–as I stated earlier. When discussing inbound and outbound marketing, we’re really still just talking about push and pull by other names. As any good marketer knows, push and pull work together. The number of total marketing impressions matters–more impressions increase your odds. This is fundamental brand-building. As an example, it’s well documented that PPC ads and organic results on the SERP converts better than either alone. So don’t choose between inbound and outbound marketing–use best practices in both methodologies to optimize your marketing results.

So what do you think? Will all your investments going forward be toward inbound Marketing activities, or is there still room in your budget for outbound methods? I’d love to hear your plans and opinions–post a comment to weigh in on this discussion.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

Will SaaS Lead to the Death of Software Product Management?

There is a lot of talk in the software business these days about changing business models, particularly the trend toward SaaS (Software as a Service).

Will SaaS business models dominate the software business?

Many consultants, pundits and other industry figures are proclaiming that SaaS will very soon take over the world; saying if you’re not on the bus soon, you’re going to be out of business. I believe this is a bit overstated, but the strong trend toward the SaaS business model can’t be denied.

My opinion on SaaS adoption: When bandwidth is unlimited and close to free, all IT systems are totally secure, the Internet is as reliable as old AT&T; and every customer in the world decides they want to rent everything and own nothing–then I’ll agree that SaaS is heading toward 100% market share. As I said above there’s a strong trend in this direction, but we’re a long way from there.

Is software product management dead?

I’ve written about SaaS a number of times before, and since it has become very important in the software business I’ll continue to do so frequently. What I want to address today is another opinion some “experts” are also espousing: that the trend toward SaaS means the end of the Product Management function in the software business.

I find this statement to be downright silly.

When following this debate, it’s important to take notice that many of the folks proselytizing these opinions have businesses whose success is based upon these predictions actually coming true. It’s always important to consider conflicts of interest among the debaters.

In one recent webinar they trotted out a SaaS software company that was growing briskly every year with no product managers in the company. What wasn’t said is that it was always possible to find software companies (of the traditional sort) who didn’t have a product management function. Software companies are often founded by programmers, and they haven’t always seen the need for Product Management. There are very successful companies where the developers talk directly to the customers, with no product managers at all. However, the facts are that a very small percentage of companies that do business this way are successful, and its usually based upon special circumstances: the rare developer who understands markets and customers as well as he does coding, markets where the developers themselves are perfect customer proxies, etc.

So while software companies without Product Managers have always been out there, it just hasn’t been a broad formula for success. Trotting out one SaaS company successfully doing business this way (incidentally, I saw some big holes in their model long-term) doesn’t impress me much.

I’m not defending the status quo–I’ll say it once again, there is a huge move to SaaS in the software biz. Many (and maybe most) will be doing business this way in the near future. However, like most over-hyped trends, this are some pretty big overstatements being thrown around.

SKILLED product management will always be important

The argument being made is that many of the functions Product Managers currently perform are obsolete under the SaaS model. With continuous development more practical using SaaS, there may be fewer (or no) new version introductions. So the old waterfall chart with MRDs being created for the new version may go away along with new product introductions. I’m sure you get the picture. SaaS is a pretty fundamental change to the software business model, so you wouldn’t expect a product manager’s job to be stagnant under such change.

But those predicting the death of product management are focusing on the more mundane aspects of Product Management. The essence of this critical function is the ability to understand markets and match widespread, aggregate customer needs to the technical skills and IP of your company–creating a PRODUCT which can be sold to these many people. It doesn’t matter whether you deliver this PRODUCT over the Internet in a hosted manner using monthly subscriptions, or in the more traditional on-customer premises, licensed model. Product Management is about creating a profitable PRODUCT well-matched for a market segment. It matters not whether you are engaged in customer facing marketing/promotional activities, or upfront product planning–the product manager’s understanding of market needs and how your company can fulfill those needs is crucial in a product business. Otherwise, you’re just selling custom software–one-off’s for every customer. That’s a different business–not a bad one–and one you which doesn’t require product managers.

Can Social Media replace Product Management?

Another thing being bandied about by my favorite pundits is the impact of communities and other social media for its potential impact on product development. The thinking goes that there will be much more direct interaction with the end customer, leading to tremendous amounts of data available to ISVs. While SaaS is very well suited to communities (although not exclusive–they can be well utilized by traditional licensed software vendors), the ability to more easily obtain direct customer comments, and maybe take votes on potential new features doesn’t eliminate the need for product management. To the contrary. While communities and other forms of social media are very powerful tools, don’t mistake more data and customer access with actionable market intelligence. Data needs to be interpreted, and skilled marketers are best positioned to discern who’s telling you what and why–the underlying motivations behind any customer feedback. So all of this added customer access and resulting data will only put a premium on good product management, to use these powerful new tools and data for quicker action and to allow better product planning decisions. Remember, SaaS competitor down the road will have access to the same tools and data that you do.

It is rare to find a developer who has truly exceptional product management skills. That’s not a knock on developers; as a whole they are an extremely sharp bunch. But specialization in life happens for a reason–very seldom is someone the best at everything. Developers are trained to write code and build applications, not understand markets or extract the “truth” from customers. Different types of people’s brain’s work differently, and a good developer and good product manager are an example of this.

I find that it’s when a talented, open-minded development manager teams with a market-savvy product manager, that most great software applications are made. So no, I don’t believe that the Product Management function is going away anytime soon in the software business. There are many important changes going on in the business, the SaaS business model not the least of these. With any change in business model, functional roles will evolve and change. But I believe strongly that Product Management is a fundamental, important role that will remain critical in software businesses far into the future.

That’s what I think about SaaS and product management–what do you think? Post a comment to start the discussion! Follow Phil Morettini and Morettini on Management via Twitter, Facebook, RSS, or the PJM Consulting Quarterly Newsletter.

Integrating Sales and Marketing at Software and Technology Companies

In some but not all tech companies the Sales and Marketing functions are managed separately. They are separate but closely related functions that some people without a strong background in either function have a tendency to confuse. Normally, there is a VP or Director heading up the Marketing department, and another VP or Director leading the Sales staff. But it is also not unusual to see a VP or Director of Sales & Marketing who leads both functions.

This all seems benign enough, so what’s the issue? The issue comes when actual revenue fails to meet the forecast–that’s when the finger-pointing usually begins. Unfortunately not meeting forecasts is a common event in technology businesses, where forecasting of new software and tech products can be particularly challenging. When that finger-pointing starts, it often breaks out first between the Marketing and Sales departments–here’s how the ensuing “discussion” might go:

SALES: “You haven’t planned products that our customers want to by. You’ve priced them too high. And those leads that you’ve spent SO MUCH money on that you are giving us aren’t qualified and are essentially worthless to us.”

MARKETING: “You’re not selling the right products as we directed, or presenting the positioning of our product line properly. All you do is try to sell on price, constantly discounting and hurting our margins. If you’d follow up on all the leads we gave you, get off of the golf course and work more than 4 hours a day, you’d be well over quota and the company would be doing fine.”

Sales folks and Marketers are different types of people, and tend to view the world differently and from their own selfish perspectives. This often nasty “discussion” as simulated above is far from uncommon, and can get pretty ugly–which can really hurt a company in trying to reach its goals. So what’s the right way to get the Sales and Marketing departments to work together as a team, avoiding all of this counter-productive ugliness?

SOLUTIONS TO REDUCE POTENTIAL CONFLICT

The VP of Sales & Marketing
One way to greatly reduce this conflict is to have a common leadership for the Sales and Marketing functions. This usually means having a VP-Sales & Marketing in your organization. If you can find the right person to fill this role, this can actually be an excellent solution. Having a single leader can go a long way toward eliminating or at least greatly reducing this conflict, assuming he has a balanced background and perspective and is fair, not favoring one department over the other.

Good people to fill this role are out there–but are very rare in my opinion. There are far more managers who have been put in the position of VP-Sales & Marketing than there are those who are well suited for the role. Most of the time you end up with a manager that understands one function well and gives short shrift to or completely screws up the other function.  You will often find this combined VP position in companies that are not “marketing-intensive”, where the sales function is the dominant aspect of the job. If the Marketing function is truly less important, a company can get by with this structure, although it usually isn’t ideal. You can read more about the issues with a VP-Sales & Marketing role in a previous article that I’ve written entitled “Big S, little m“.

CEO Demands Communication and Cooperation
If care isn’t taken, the very different personality types in sales and marketing can lead to some pretty intense conflicts. I’ve been a soldier, captain and general on both sides in this war–and let me tell you, it isn’t pretty. I’ve also (effectively) filled the role of VP-Sales & Marketing, which is a story for another day. Much like the battles between Marketing and Engineering that I’ve previously written about, I have seen this battle play out regularly in the companies that I have worked for as an employee as well as at many of my clients in eight years as a consultant at PJM Consulting. Things can get out of hand very quickly, and paralyze a company.

In many cases, the key is how the CEO handles the situation. He must go well out of his way to be a fair arbitrator in these discussions. Even the most benign comment can appear to show favor to one side in the eyes of the other.  A CEO can’t ignore or deny the problem or assume it will be handled at the VP level. It is the CEO’s responsibility to prevent, recognize and fix this problem. As a CEO you must also be careful to avoid inadvertently making decisions or setting up policies that reward or tolerate company politics.

Departmental Social Integration
Not everything can be avoided or corrected through traditional management techniques. In this situation relationships are really the key.   I recommend planning social activities which allow sales and marketing department counterparts to get to know each other as “people” outside of their project activities. Since a successful sales/marketing interface relies heavily on relationships, it’s very important to closely monitor the personal relationship between VP-Marketing and VP-Sales. Also, make sure that the VPs are monitoring the counterpart relationships below them. Ensure both VPs are open and honest with about the relationship between departments. Also watch for arrogance (especially from “experienced veterans”) when screening potential new hires for either department that will interface with the other –arrogance often is the trigger which starts the battle between departments.

Integration of Departmental Functions
Encourage the sales department to get marketers in front of their customers. Hire marketing people that have had some sales or business development experience,  who understand dealing directly with customers–and know what’s it like when your living depends upon making your quota. Insist that the marketing department include the sales folks in determining what a “qualified lead” looks like. If you can get agreement on this up front on this important issue, much of the finger pointing goes away when things don’t go as planned.

Joint Goals and Compensation Structure
It currently isn’t common to design department or individual goals which cross marketing and sales functions, but if you can find a way to do this you are structurally setting up the desire and need for close cooperation. Design goals or MBOs to reward the two departments for working together. It’s crucial that you don’t ever allow one department to “get ahead” by blaming the other–tie them together as much as possible in your goal setting.

SUMMARY
To limit issues between sales and marketing functions and ensure that they “sing from the same sheet’, pay close attention to the specific individual departmental activities which can greatly effect the perceived performance of the other department. Optimizing the cooperation between sales and marketing demands an upfront look at things such as the corporate structure at the highest levels, the social fabric of the company, compensation structure and use of targets/goals, as well as formal cross-departmental reviews so each department can influence the other department’s approaches. All too often I see these things aren’t taken into consideration until after the fact–when things have already blown up and there is a mess to clean up.

That’s my view on this all too common–but not often discussed–conflict. What has been your experience in this area? Post a comment and begin a discussion.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com