Recently, I’ve done joint announcements with Oracle, SAP, HP, Tibco, Software AG and HP. As you can imagine, I’ve had varying relationships with each and I’m happy to report that the state of the A/R industry is good and that we can work together.
When I was in PR, it was cat fight supreme with territorial ism and turf wars. Most of the announcements I did with these companies when in Analyst Relations didn’t have that element. For the most part, the announcements were about standards, not products. So that went a long way towards working together. Still, if you include IBM, the companies I’ve named here aren’t known for being best buddies.
As and aside, I can say that the executives (who can be the source of most problems) all worked towards the cause of the best briefing possible.
Some things are given, like in a certain area (we just did SOA) the analysts know the exec’s by company and the exec’s know each other so I’m happy to report they acted like grown ups.
With the typical name calling (from the CEO’s)and because of t the belief in your own products, the first issue to overcome is that the announcement is usually about a jointly create product or standard, not us vs. them. That rule has to be set down first and if you don’t overcome that, you have no chance at building trust, the basis for working together.
DIVIDE THE DUTIES
One company can’t dominate the duties or or it is not a joint announcement. This also forces the companies to work together to approve what the others have created as their part of the announcement. There are analyst lists, invitations, charts, follow up issues and any number of duties that need to be attended to and dived up. Once that is done, you must rely on each other and the level of trust inherently rises.
It’s important that the analyst see this as equal amongst the companies. One company presenting more than another is a dead give away. You can’t help Q and A as the analysts will direct the question directly to a company.
You either put your differences aside and work together, or you’ll never get anything done. It’s tough to do when your day job is to hammer the company that you are working with other than on the announcement. These are the days of co-opetition though. You learn to get along or you’ll never make it to announcement day.
2 thoughts on “Doing a Joint Announcement With Your Competitors”
Pingback: [Guest post] Doing a Joint Announcement with Your Competitors « The IIAR Blog
Pingback: WORKING WITH THE COMPETITION ON A JOINT ANNOUNCEMENT – What went on behind the scenes with Microsoft/IBM/Intel « Delusions of Adequacy