Deciding on controversial features for products

I’ve just discovered that leaving your account logged on Facebook allows CNN.com to somehow connect to it and see who of your friends have linked to CNN stories. To say the least, I was a little surprised to see a friend’s name with a link to a CNN.COM article, since I wasn’t logged into CNN and they didn’t ask for permission to connect to my Facebook account. My first instinct was to see behind my shoulder to see if the illuminati were behind me.

I did a little experimenting, logging out of Facebook and reloading the CNN page got me blank box with the caption that friends’ links would be shown there. Logging to Facebook again reintroduced the news about my friend’s link. Somehow they were getting access to my friend lists.

From the Product Management perspective, how do you decide on this type of features? I can think of several people who will love it, and a many more that will hate it. Obviously you want your product to remain competitive and offer features that go the extra mile for your customers. At the same time, if it takes a PhD to customize your preferences that would be a turn off.

To address this type of features, the steps I would follow would be:

• Prototype the hell out of it.

• Use customer’s panels and demo it in front of large groups

• Announce it and highlight it when it is shown for the first time.

• Build a “quick kill” or “shut down” button into the feature.

• Prepare for fallout in case it goes the wrong way.

Obviously I am simplifying the situation but the approach may help your company avoid Facebook-like privacy problems.

Why not a short term strategy?

If you, as management, are not clear on the strategy and do not communicate it; How can your employees deliver? I am surprised how many companies ask their employees to read management's mind, find the right intentions in there and execute to specifications. It makes no sense. Is like having a neurotic spouse with the power to fire you. You want to succeed in business? You have to be clear as to your objectives. If those are not clear, nothing will please you and your company will sink (unless you are really lucky).

It is OK to have temporary strategies. We have them for emergencies, why not for times when life is not clear (is it ever?). Why do we feel that is not OK to have shorter looking strategies? Square was in the brink of collapse with their games. They set out to build their last game (after that they were expecting to close). They put all their effort into the game but with a pessimistic feeling, they called it: Final Fantasy. They wanted to bow out with a last great hurray. Guess what? The game was a huge success. As well as FF2, 3, 4,... They are now one of the most powerful and well recognized game development companies in the world (it is now called Square-Enix) and they are working among other things in: Final Fantasy XIV.  What worked? Having a finite narrow strategy: Make their last game great!

In the middle of a M&A or bankruptcy debacle? Come up with a short term strategy and communicate it to all employees. They'll appreciate the honesty and the direction. They may very well build you a Final Fantasy.

Stopping the launch of weak products

A weak Product Management function can result in features that are not introduced in response to customer needs but in response to internal wish lists (that may be out of touch with the market), or in cost structures that are not being revised strategically to enhance profit margins (like outsourcing vs. internal development). To change a Product Management function takes making an assessment, mapping out where we are today, where we want to go be and what are the best practices in what we need.

After the initial assessment and once you understand where you are and where you want to be. Choosing the right framework will be one key to your success. There are several frameworks about what Product Management should be, for example: the PDMA model has one, author Steven Haines documents another, and author Marty Cagan shows us yet another one. All frameworks list a set of skills and functions that every organization should have. But just using any of these frameworks will not work for a company, as with everything in life, each situation is unique and your framework should be tailored to your needs. Best product management practices will come from a consultant (you are hiring one, right?), current literature and studies on the matter.

Another big factor is if your company wants to change its culture – for example, is the organization willing to let a Product Manager team define and control the product? Or are they convinced that it is a function of the Marketing department? Whatever the answer to the culture question, it will mean a lot of changes to marketing, product development, service desk, platform development, etc. If your company is not willing to change the culture, the best way is to look for a framework that will reinforce current weaknesses and strengthen what is being done today.

Product Management & its strategic implications

Product management is a market-driven approach to develop and manage products or services:

• Defines what the product should be – is accountable to users for feature sets, navigation, quality, and overall experience

• Is a cross-functional discipline: involves strategy, product development and marketing

• Is accountable for overall product direction, key decisions, including in some cases full P&L control or at least budget control
  

• Ensures that the final product meets specifications

• Evangelizes product to internal and external stakeholders

The strategic implications of a robust Product Management function are many: from increasing the value of the company, understanding the customer today and in the future, ensuring that all possible revenue is being captured, guiding future product investments and controlling the current cost structure of the products, to name a few. For any organization, it is imperative that these and other issues are being taking care of in the Product Management function.