Do you agree with my definition of Business Development (BD)?
This is a question I asked at LinkedIn last week. And I've had very good responses from top BD people around the globe! Their answers ranged from the theoretically thought provoking to the practically blunt. It was extremely difficult to choose the best answer as all of the respondents brought something insightful, elucidating and practical to the table.
Here are some key insights I distilled from the answers:
- A lot of respondents agreed that the Ansoff Matrix is a classic. A classic is good for understanding and elucidating concepts (like what is done in school) but may not always be practical.
- BD is an evolving role. While the "What's" and "How's" will evolve, but the "Why's" will remain pretty much the same in whatever context. In my mind, the question, why does BD exist is this: BD exists and will exists as long as companies are concerned with their future sustainable growth - which is pretty much forever in my opinion.
- BD is all about identifying, cultivating and managing business mutualisms! (as opposed to biological mutualisms... I encountered the term "business mutualism" before but could not remember where or when)
- BD is a by-product of the "dejobbing" phenomenon (Dessler)(slide 35)
- BD more strategically inclined - FUTURE oriented - sustainability oriented. As opposed so Sales people who, bluntly put, are more oriented towards getting a "quick buck". Kevin Haskins mentioned that, "Business Development is salesmen that can't close", maybe Kevin was trying to be funny, but I think his answer highlights the future-orientedness of BD. So, BD people may not be able to close now, BUT they enable salesmen in the future to close. Salesmen closing now may very well owe their sales to a BD professionals who did their work in the past. Right Kevin? :)
- In fairness to "purely" Sales people, they bring in the revenues now so that BD people have something to finance their expenditures.
- Given the inherent strategic inclination of BD, is the term "Strategic Business Development" redundant? As in "Food Chef" redundant?
- Given this BD's KRAs and hence remuneration structure should be also aligned to being future or strategically oriented. This was pointed out by Anjali Sinha.
One answer that really got me thinking was
Dave Wolpert's. Here's are key excerpts from his answer:
The Ansoff Matrix was not intended to define a particular job function, but rather to broadly characterize strategic options for growth. As such, I don’t know if it makes sense to define BD in terms of this matrix. Yes, business developers may be involved to varying degrees in some or all of the squares of the matrix, but “being involved in” doesn’t help clarify a business developer’s primary role...
...I think business developers tend to be more strategically-inclined than traditional salespeople because the nature of the selling process when third parties are involved becomes more intricate. Also, as one person noted, business developers tend to always be on the lookout for new markets to tap that salespeople may miss simply because they’re more focused on meeting their short-term sales quotas.
Click
here to see Dave's full answer.
I have some clarifications with Dave:
- Isn't the BD's role centered around the company's "growth"? Therefore a BD professional, being, as you mentioned, "more strategically-inclined" would need to be aligned with the company's strategic options for growth, at least at a broad sense. Doesn't that make sense?
- I believe that that primary and specific role of a business developer would depend solely on the specific organization he is working for. A general definition such as mine, just serves as a framework (by defining possible "involvements") wherein organizations would base the primary and specific job description of the business developer.
- While I agree that the Ansoff Matrix was not intended to define a particular job function, using it to define a job function (a purpose it was not intended for) is, at least to me, innovative. A lot of things that are pervasive and indispensable now, were originally intended for other uses.
Dave, I think we are creating a
good opportunity by starting an online debate on this. Please comment on this post to reply.
Dave by the way is the author of "Sales and Marketing Careers in the Tech Sector" Tim Gilbert offers perhaps the most practical and concise take on my question:
Folks, I sense there's a lot of electrons being expended here on the theory side. Pragmatically speaking, the most important definition of BD is what your boss' boss says it is.
BD is often a situational job function within the company, and if you're contemplating a career in BD, ensure there is: (a) a clear job description of no fewer than two full pages having very concise, if not painfully tactical objectives and requirements; (b) senior-level assurances that these responsibilities are or will be clearly communicated to other executives and middle managers; and, (c) that governance of resources and internal authority are clear--rolled out to the corners and squared away. If not, don't take the job.
I have seen very fine professionals have their careers eaten alive by BD roles that were something else in disguise--either sales, having no authority other than personal charm to get things to happen, or general management or product management capacities demanding a personal quote (two jobs in one).
If you're contemplating a new path in "Business Development," ask about those three points above and angle to have them are written down and published to the stakeholders with whom you will be working. Just my two cents.
But the best answer in my opinion, based on a balanced mix of insightfulness, practicality and clarity of thought comes from none other than
Matthew Lockwood:
Mike,
The distinction between business development and sales is a fuzzy one, as I believe the core function of a “Business Development” executive is to sell the company’s new and existing products and services to new markets/new clients, and therefore create valuable new revenue streams, which is in line with both the Matrix across all areas and Bryan's comments.
However, the business development role requires the executive to possess a more strategic view of the market, target clients and product/services and being able to engage early within the sales life-cycle with senior level prospects i.e CXX , with a specific and relevant value proposition.
In my experience the sales lifecycle correlates with the Rodgers’ technology lifecycle adoption curve, with the business development executive focussed on the early adopters in the main.
http://en.wikipedia.org/wiki/Image:DiffusionOfInnovation.png
This provides a clue to the difference between "sales" & "business development", which lies in their inherent ability and skillset.
In my experience, the majority of salespeople lack the confidence and ability to approach the right level of contact with the right message at the right time, i.e. business development sells the vision and then the product, sales sell the product.
On the classification of Business Development as a "Sales and Marketing" function, I am broadly in agreement with Linkedin's position, as it sits in-between both camps in my mind.
Hope this helps.
Matthew