The Forrester Blog For Technology Product Management & Marketing Professionals

July 09, 2009

Should Google be the next Microsoft?

Google's announcement about the Chrome OS raises a whole lotta questions about the future of the operating systems market, or what an operating system really is, or how the Chrome OS fits into Google's larger strategy. As interesting as these questions may be, we also have very little foundation on which to answer them.

I have a much longer post here about the reasons why we can't reach any conclusions yet. Here's the short version:

  • Netbooks, which play a significant role in the prospects for Chrome OS, can be both a blessing and a curse.

  • You could say the same thing about the degree to which the Chrome OS depends on the Chrome browser.

  • Users may not see the compelling reasons to use this new platform, or even understand it fully.

  • Governments may not be thrilled about the implications for competition and privacy.

  • There's still a lot of murkiness about cloud computing in general that this does nothing to dispel.

  • Serious technical challenges lie ahead.

July 07, 2009

The Heretech, episode 12: Saeed Khan on the PM role

Saeed Khan of the On Product Management blog identifies the dangers of defining product management the wrong way. Plus, a quick review of some inspirational material about the political aspects of a PM's life. Click here for the MP3 (hosted on The Heretech blog).

July 06, 2009

Product management and marketing mix it up

For people in product management and product marketing, organizational questions—for example, Where should we report? What specializations of the PM role seem to work?—are always high on the list of hot topics. That statement is true of this week's Heretech podcast, to be posted later today, in which Saeed Khan and I spend a good deal of the interview discussing these issues. It's also true of the research that I do, including a recent study that revealed some interesting results about the relationship between product management and product marketing.

A small chapter in a bigger story
Unfortunately, this latest research about these organizational questions puts me in a bit of a bind, since I'd like to share more of the results than I can.  Forrester always requires you to be a client to access our research, with minor exceptions. In the case of the just-finished study, "Best Practices For Product Management And Product Marketing Leaders," I'm really constrained. Members of the Forrester Leadership Board (FLB) for PMs asked us to do this study, which gets circulated among the FLB members, but not all Forrester clients. (It's one of the perks of FLB membership.) If there's a curtain between the general public and the typical Forrester research, there's yet another one between you, Dear Reader, and the FLB research.

Fortunately, we can always share a little bit of information from our research, even if we can't share everything. In this case, I'll share what we learned about one important organizational question: Should product managers and product marketers be part of the same department? Looking at successful PM teams, the answer is, Generally, yes.

What makes a successful team?
For this research, we deliberately picked successful PM leaders for our interviews. The adjective successful could mean a lot of things, and in our case, it meant...

  • Tenure. The PM department heads whom we interviewed have been doing the job for at least a few years.

  • Authority. These PM leaders handle important deliverables and activities, such as go-to-market strategy and product portfolio management.

  • Accountability.  Along with real decision-making power over matters like product strategy, these PM groups bear responsibility for the business outcomes of these decisions.

In other words, you know you're successful when the company entrusts you with important things.

One group or two?
Since I started doing research on product management and product marketing, I've seen a lot of different organizational formulas. Sometimes, these two groups are separate. At other times, they're two sides of the same group. I've also seen these job functions broken down further, with the pieces scattered even more widely around the organization. We've also spoken with groups that have introduced new roles, such as solutions manager and community manager, that overlap with the product management and product marketing functions.

Therefore, when we reviewed our interviews for "Best Practices For Product Management And Product Marketing Leaders," we were genuinely surprised to discover that approximately 80% of our interviewees ran departments that combined product management and product marketing. That's a result worth italicizing.

These arrangements made sense, since product people look to the same information about business problems, use cases, personas, competitors, and other aspects of the market. This knowledge guides everything from broad-brush messaging to nitpicky feature/function priorities.

Of course, separating product managers and product marketers also makes sense. However, the habits of these highly successful PM leaders strongly imply that the unified department not only makes sense, but also works. There are lots of reasons why, including both external and internal ones. For example, if you're going to produce different content for different audiences—requirements for Development, demos for Marketing and Sales—that's ultimately based on the same customer and product knowledge, that process goes a lot more smoothly when you don't have two separate groups trying to stay in sync.

Two jobs, but what do you call the one department?
The success of the unified product management/product marketing model makes me wonder if there's a a good umbrella term for both of them. "Product professionals" doesn't quite do it for me, and we definitely don't want to confuse the two distinct functions, even if they wind up under the same management. I'm certainly open to suggestions.

[Cross-posted at The Heretech.]

The unbearable lightness of Bing

Competition breeds innovation. Usually.

So far, Microsoft's launch of Bing hasn't inspired big new ideas in the world of search, but it's still pretty early. You never know. Read more at The Heretech.

June 30, 2009

Of designers and developers

In today's post at The Heretech, I come out of the closet. Yes, I am a bigger history geek than you can possibly imagine. Hello, my name is Tom, and I play wargames.

However, by playing a lot of games designed to simulate historical events, I've learned a couple of things that apply to designing products in the technology industry. Specifically, how do you create a design teeam that can overcome some of the common pitfalls, such as unnecessary complexity? To read more, follow this link.

[P.S. Thanks for pointing out the problem with the link. Typepad is intermittently eating the hyperlinks I enter. From now on, I'll just have to test them before I publish.]

June 25, 2009

Why use cases should drive technology design

During a briefing from Microsoft's xRM team, the question of how to integrate structured and unstructured data arose. If xRM (the Dynamics platform) is good at the structured stuff, and SharePoint is good at unstructured content, what's the right way to bridge the two?

Back in my Oracle days, we faced exactly the same question. At a technology level, there's no obvious answer. Bring together two development teams (the structured and unstructured specialists), and you'll first get a lot of technical-level discussions. How should security work? What API changes might be needed? How will metadata span the two kinds of information?

Unfortunately, there's no immediately obvious answer to these questions. In fact, the options are so broad, and the risk of technological quagmires so great, that the endeavor might easily grind to a halt. People ponder the options, argue over which one is best, go back and ponder some more...

At Microsoft, a clear use case accelerated this discussion. The Public Sector group developed a constituent services application for local governments that combines both SharePoint and xRM. Notice how specific the application, the Citizen Service Platform, is. Not all government, but local government. Not several government functions, but constituent services. 

Undoubtedly, the Citizen Service Platform team made it clear which kinds of integrations were important, and which weren't. It's not too hard to generalize the use case to other situations. After all, we're talking about the same CRM platform that property managers and church pastors use, for different but similar purposes.

For people who are already sold on use cases as the right foundation for designing products, this might seem like a "Well, duh!" sort of observation. However, many product teams go full speed ahead with only the haziest use case, or to be honest, none at all. If their product decision-making process is too slow, or too error-prone, they might reconsider the value of a very specific use case.

[Cross-posted at The Heretech.]

Podcast: My interview with the Cranky Product Manager

Stepping out of the shadows, the Cranky Product Manager and I talked about the sources of crankiness in the technology industry in this week's Heretech podcast. The conversation also ranges from the reasons why product management is a "wretchedly awesome" job, to how overzealous Agile advocates hurt their cause.

To maintain anonymity, I masked the CPM's voice. A couple of listeners have already compared the effect to the Cylon voice effect in the old Battlestar Galactica series. I'm not sure if the CPM would be flattered or mortified by that comparison.

In the same podcast, I also review a movie that you've never heard of, but which has a lot of relevance for a recent hot topic in the PM blogs.

June 18, 2009

Agile Executive post on "regime change"

Many thanks to Israel Gat at The Agile Executive for posting my thoughts on how Agile is following the same path that many revolutions take. After you've had some initial successes, and take your new programme seriously, what now?

June 16, 2009

Making a SaaS of yourself

I've worked on both SaaS products and on-premise ones. While the challenges may be different, I was never at a loss for things to do in product management and product marketing. In fact, some of these tasks became more challenging, not less so, in a SaaS world.

Which makes me wonder, why on earth would someone who purports to be an expert on SaaS say that PM is not necessary in SaaS applications? To get my complete reaction to this recent post on SaaS University's house blog, click here.

New PM podcast, with Adam Bullied

This week, I interview Adam Bullied of Write That Down. Among other topics, we discuss why PMs shouldn't try to be mini-CEOs. (Or just tiny.) For the actual podcast, click here.

Enter your email address:

Delivered by FeedBurner

Search this blog

Client Choice. Vote Now. Technorati Profile