The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Merging Product Management and Marketing into a Single Function

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
Merging Product Management and Marketing into a Single Function Posted: May 25, 2007 8:05 PM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: Merging Product Management and Marketing into a Single Function
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Advertisement

James Morehead heads up Product management and Marketing at SupportSoft. he's giving this talk in terms of where he works.

So - traditionally, Product Management and Product Marketing are separately organized, although often with the same management. He's advocating having a single marketing organization for all of that. Where he works, the organization is one centrally located and managed group. Responsibilities?

  • Customer interaction (supporting sales)
  • Outbound - web content, collateral, press/analyst, speaking, etc
  • Inbound - market research/planning, roadmap/release planning, pricing, training

Metrics for the merged organization:

  • Quarterly MBO process - aligned with corporate objectives and quarterly bonuses
  • Pipeline per product
  • Release completeness - aligned with engineering, focuses each PM on shepherding reqs to delivery

By combining the two pieces, you get aligned communications. To ensure this, they set up a system of "gates" to ensure that products get to where they need to go - miss a gate, slip a release.

  • Market Opportunity
  • Use Case Definition
  • Functional and Usability Reqs
  • Engineering Development Timeline
  • Functional Completeness
  • Release Readiness
  • 6 Month Assessment

These gates have various people who are notified of progress, and who have approval/decline power.

Benefits:

  • Credibility with customers as you have one group in charge of all messaging - roadmap and communication
  • Reqs tied tightly to customer interaction
  • No communication gaps between PM and PMM
  • Efficient Staffing Model

Challenges:

  • Constantly being stretched between sales, engineering, and corp. marketing
  • Hiring is more difficult - staff needs to be articulate and detail oriented
  • Both sales and engineering can end up feeling under-served

One caveat: James is not sure that this would scale up to a larger firm (his has 220 or so people). In the summary, he figures that the roles will eventually split to some extent - probably around industry verticals, followed by field marketing.

Technorati Tags: ,

Read: Merging Product Management and Marketing into a Single Function

Topic: Layman's Manifesto Previous Topic   Next Topic Topic: New BottomFeeder Dev Builds Up

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use