Search This Blog

December 16, 2010

Importance of Social Media in Business

Here is an interesting piece on the importance of social media and the probable disconnect at senior levels in Fortune companies, with almost no CEO's being active in social media. This cuts them off from their customers but also the way their customers are thinking.

It has lessons for all PMM - we need to be engaging with our customers effectively and in many markets this means being active in the social networks. This will drive our brand recognition and our competitive positioning.


A 2009 study found that the CEO’s of top U.S. companies tend to avoid social media, according to UberCEO.com. The study found that most of the Fortune top 100 CEO’s were markedly absent from the social media community, including Facebook, Twitter, LinkedIn, and Wikipedia.

December 13, 2010

Does the Perfect Product exist?

So we all know that one of the hardest things about being a Product Manager is trying to get the product to the market - preferably with most of the required features and in the same decade as the target launch date.

Product timing is critical - often it is better to be in the market with a less than perfect product, getting customers involved and committed than still be in the labs working and missing the opportunity - although a poor offering can do incalculable damage to our product and our brand.

This inevitably forces us to make tough product decisions and compromises on what is in and what is out. We would all like the perfect product, but, in practice we try and define what is good enough. We need to review the product requirements and categorise (in reality recategorise) them into features that are key to the functionality, for example product differentiation and leadership, competitive positioning, key customer commitments (but see this post on balancing customer influence on a release) and usability. There will be many other features, that make sense for the overall product offering, but will not gain customers nor will they loose customers and so sometimes they will just have to wait for the next release.

These calls can be tough and it can take a brave PM to stare down the boss and the market. When Apple introduced the iPhone it was revolutionary (touch screen etc), but at the time it missed some of the key features of a phone that traditional phones already supported (network technology and speed.) Some poor PM in Apple had to make the call and say those features could wait. In this case it worked.

Sometimes, however, the choice is less successful and worse some minor features get delayed from release to release without a solution. So following on from my analysis of Nike getting some marketing issues wrong - here are some thoughts about a place were Google gets it wrong.

Briefly, when you build a website, two of the key stages in launching it are to submit the site to the major search engines together with its sitemap.

Now when we built this blog we built it on a Google platform, and naturally assumed that submission to Google would be automatic. Not so - a few weeks on and we realise that we seemingly need to submit and that the submission is from a different set of Google tools and not the blog control panel. Even more frustrating, building the site map probably isn't automatic and doesn't always work the way they say. Or maybe it is automatic - depends who you believe - the Google support guy on one of the forums or the official instructions. Worst of all - this saga seems to have a history judging by the support forums and QA pages.

So given that these tools are for the general public - the user experience could have been so much smoother. Maybe there is a very good reason why submission isn't automatic - but it is hard to see why this couldn't have been properly explained and a couple of items included in the blog set up wizard. True in this case they didn't loose me as a customer, but they almost did see me checkout a different blogging platform.

To wrap it up - we need to compromise on our dreams for our products, failure to do so can ruin our chances to get market share, but, we need to make sure that we don't compromise too much. We need to listen to our customers and fix the things that we missed or omitted the first time round, failure to do will also ruin our market share in the longer term.

December 6, 2010

The Importance of Documentation

As PM&M we spend a huge part of our working day communicating both internally and externally. Despite this, we often get far into a product process and discover that somehow we don't have documentation or that we have very poor documentation. It may not, therefore, come as a complete surprise that we have a poor product definition and a weak customer engagement.

Sure, our creative skills and leadership mission don't leave much time for hacking away producing long word documents, but, as we will discuss in this post good functional documentation is an essential part of our mission and the craft, that can help or hinder the overall business success.

We welcome a guest blogger - Larry Lester - A Sales & Marketing Documentation Guru to discuss

There’s a host of reasons why small, emerging companies (aka start ups) should take documentation seriously. The problem is that most of those that I have worked with – don’t.

First and foremost they should take it seriously for all the reasons that larger companies take it seriously – it is a way of keeping your marketing, development, operations, and sales efforts – and the also the customer – in alignment.

However, for a start up the lack of good technical and marketing documentation – with the emphasis on good, or not having something basic at least – makes survival more perilous than usual. My phone usually starts ringing when these guys are about to crash land. If they have had the good fortune to make a sale, the customer is being nasty and delaying a milestone payment because a full set of technical documentation was supposed to be delivered and has not even been written. Or, if they have only got their foot in the door, discussions are about to collapse as the only marketing material they have to give to potential customers are a few pages of incomprehensible gibberish and a dreadful PowerPoint presentation! “We thought we could pull it off”.

The situation is, in fact, more serious than that. A company that does not maintain product requirement documentation is openly toying with suicide. There are two aspects to this assertion.

  1. Poorly documented development is bound to result in a bug-ridden product. If you don’t write about it (requirements) then you don’t talk about it, and if you don’t talk about it, you brush aside the problems. Lack of a standard process and workflow causes product decisions to be made in an ad hoc way. At best, it is inefficient. At worst, it will kill your efforts to make a sale.
  2. A good product requirement or a spec can serve as the basis for installation, operation and maintenance documentation. The saving in time, energy and money can be substantial. Somewhere down the road, you will need a technical writer, whether you like it or not. The more solid information you have to provide, the easier your lives will be.

The bottom line: give both technical and marketing documentation the same priority you give to development and sales. All of these processes are fully entwined - together the product should succeed; without any one of them it will be a struggle and potentially a product failure.

November 24, 2010

Cloud Computing - should it / will it impact our product?

I recently attended a conference on cloud computing, held by The Virtual Computing Environment Coalition (VCE), a coalition of three of the leading vendors in the industry: EMC2, Cisco and Vmware. Virtualization and cloud computing are two of the newer technological trends and gaining momentum every day. Gartner EXP Worldwide Survey of Nearly 1,600 CIOs indicates that in 2010 the first technological priority of the CIOs is virtualization and second is cloud computing. This is a major change in the IT industry; in the same survey in Jan 2009 neither of these were in the top ten technologies.

New technologies always represent a challenge to the Product Mangers. Should we invest and adapt the technology or is it only a “buzz” that will disappear? In some cases it introduces a disruptive force to the industry which actually changes the rules of the game, creates an opportunity for new players and might be a threat to the existing players in the market. So, the stakes are high, misjudgment of the affect of the new technology might cause a large impact on our business. We will discuss the importance of and ways to track technological trends in a future post.

In the case of cloud computing the potential affect might be more than only on the product. It might change the way we do business. Should the business be “product centric” or should it change to a xAAS model?

As we discussed in the post “the Craft of PM&M”, one of the main challenges is to make a decision in a world of uncertainty. The impact of Cloud Computing will be different between industries and between domains within a specific industry. There is no one answer that fits all. Each PM in his/her own domain should consider the wide view of the industry and take into account the users and usage habits, the competitors, possible new competition due to the change, the customers (if the users and customers are different), and the maturity of the technology related to the specific industry. Our task is to correctly position the product.

The decision to be made is not between ignoring the change and fully embracing it. There are several alternatives to implement or approach a change. We need to determine the correct product requirements in the light of the possible changes.

We can choose not to do anything and wait. The simplest approach, before making substantial investments, is to change the “marketing language” that is used to describe the offering and start using the newer, trendier, terms when describing the product and the offering. The next step is to create a demo which is more convincing than the marketing pitch. Moving up in the investment and the complexity, we can build a “Proof-of-Concept” which is not only a demo but still not a product that can be delivered to customers. Finally, if there is a decision to adapt the technology, only then we should implement it in the product.

Whether we choose to ignore the change for now, or choose any of the other alternatives we must decide on parameters or events that we should track. These parameters and events should signal us if a decision should be changed. They should indicate changes in the market that point to either the direction of adaptation of the technology by the market or that the market abandon this trend. Any change that indicates a deeper commitment and implementation in the market should cause us to reconsider our strategy and move to the next level of investments in our offering.

Cloud Computing is an interesting topic in its own right and it serves as a good case study for the wider discussion of technological change and product positioning. Constantly, there are technological trends to follow, but not all trends are relevant to all domains and products. However, it is crucial for a Product Manager to keep track and to be informed so that those trends that are relevant will not be overlooked. Missing on a relevant market trend might not have an immediate impact but can prove to be critical in the mid and long terms. It is also important to make the correct call on the required response.

November 23, 2010

A New Way to Present

In a recent post I discussed some of the common mistakes that we all make from time to time when presenting. I described the experiences of Jim who spoke at a recent meeting. I recommended that when preparing and delivering presentations we need to focus on some core techniques - clarity of messages, good graphics, effective time management and speaking to your audience.

In this post I want to introduce you to a presentation concept known as Pecha Kucha - here you limit yourself to 20 slides - each slide can only be shown for 20 seconds - & here is the key - you are not in charge of the slides - either you put it on auto pilot or hand the control to somebody else.

I am grateful to my good friend Larry Lester for drawing my attention to this concept. Larry writes in his blog

"I discovered an interesting method for the delivery of presentations, totally different from anything that I have previously encountered. It is called Pecha Kucha - within 400 seconds you must make your point. This is very intriguing stuff. Just think how different it is from the prevailing norms of presentations. And Pecha Kucha has real added value – it is an excellent way to start discussions and business relationships."

I am personally fascinated by this technique & plan to try it out. I think that there is a real challenge here - remember that one of the hardest things to do when speaking is to PAUSE - people need time to absorb what you have to say - so in just over 6 minutes you have to get the audience's attention, develop your ideas and communicate your message and allow the listeners to understand your message.

Write in with your comments on the idea and if you try it out for yourself let us know how you get on.

Larry Lester is a highly-experienced marketing writer who has been involved in the sales support process in Israeli high-tech companies for many years, participating in the development of customer-directed documents and responses to RFPs. You can read the full blog article here


November 22, 2010

Be A Good Speaker

Recently, I attended a sales conference trying to promote interest in a relatively new technology trend. This was a large production – I am guessing over 1000 technologists enjoying the hospitality of 3 of the very largest international technology companies (together their market cap is just short of $200B.) –The companies flew in some of their best sales stars from abroad, so we assumed that we were in for a real treat. Unfortunately one of my main take away messages was that the skills of being an effective presenter are in short supply.

I want to focus on one unfortunate presenter let’s call him Jim (not his real name) who had flown through 10 time zones to be given the middle slot in a 3 person breakout session – just before a late lunch. So Jim has my every sympathy – he got a really rotten deal – I just hope that he was really in country for some excellent one on one meetings, to at least justify the time it took him to get here and return home.

However, Jim made pretty much every possible presentation error known to the PMM world – no small feat in only around 15-20 minutes. Let me state at the outset that I and at least several others only managed to figure out what the presentation was about in the last slide or so. It was very informative seeing Jim up there - here are a few of his mistakes – I hope it gets you cringing with shared embarrassment, find some sympathy for Jim who sacrificed himself for the greater good, and please firmly resolve not to make these mistakes next time you are up there.

Know your Audience & Speak to Them – Jim assumed that everybody in the room knew about his company, its product and the reasons why it had just been acquired by one of these huge companies hosting our lunch. WRONG – most of us had never heard of them; and were either passively learning or intrigued by title on the agenda. This is a really common problem that happens in webinars, at sales meetings and at internal briefings. Unless the session is very clearly understood to be at an advanced level you probably need to assume a much less savvy audience than you would like or intuitively expect – you need to find a way of getting them interested without insulting the people who have the background.

Never, never start a presentation with the Competition – Its negative, very negative and completely pointless until I understand who you are – tell me what you do, why you are good and why you are what I need – at the end maybe tell me about the other guys – but generally why give them free advertising?

Get me Interested at the Beginning– Jim’s last slide was a case study & it was wow! If only that had been the first slide he would have captured our attention & to be honest he would have got 90% of his message over whilst people were still in the room and still listening.

Timings – So we all do it – we need to share our knowledge and passion and give a complete picture. We need to share everything right now. I don’t know what Jim expected and what he really got in terms of timings, but he was literally panting from slide one, in a desperate rush to get through the slides. He wanted to get through the slides – what he should have been doing is focusing on his message. In any meeting like this you need to be ruthless in trimming the presentation and ideally you should have an emergency plan in mind about how to cut it even further if you are left racing the clock. Less is really more in these situations.

A Picture is Worth a Thousand Words – So we all know this one too – but for most of us it is so much easier to throw down 1000’s of words. The problem that Jim had was that it was a large room, a huge projection and he had a small font so for most of the room it was like trying to read the newspaper of the guy 20 rows in front of you on the plane – it was just not happening. We all like having the info on the slides – it reminds us and lets the audience read and learn for themselves. WRONG – you need to know your message and the audience should be listening to you – that’s why you travelled half way around the world! For further information on this I recommend http://www.presentationzen.com that has many interesting tips and refreshing ideas on skills and approaches to presentation. Explore the ideas of the naked presenter. Guy Kawaski (http://blog.guykawasaki.com/2005/12/the_102030_rule.html#axzz1637iAUyr) who has a rule that the smallest font should be no smaller than half the age of oldest person in the room (and ideally 30 points).

Bob spoke after Jim – he was the session that should have been lunch and he was a techie and clearly also not a gifted public speaker, but, he was really engaging – he had some pictures, in the first couple of slides we understood the main messages and he used humour – not the stand-up variety, not vulgar, but just basically dumb engineer jokes. But most of the audience were there in their capacity as engineers and so he vey successfully connected with the audience, he got their attention and made an impact.

So Jim – thanks for being such a good sport (if it is any consolation you were not the only lousy presenter) and for giving us this opportunity to remember the principles of good presentations – it’s all about clarity of messages, good graphics, effective time management and speaking to your audience.

November 14, 2010

Product Management - The Longest Race - Part 2

In a recent blog (here) I discussed the product management and marketing lessons that could be learnt from the recent Nike 10K night race in Tel Aviv. I discussed the event planning (impressive and complex) and the event objectives (which were probably significantly more than just a fun run).

In this blog I will discuss some of the results of the event.

As a runner I can say I had an amazing time, and that on the whole this was an impressively run event.

However, the main question is what did Nike think? What KPI's did they set in advance for the event (number of runners? low number of problems? set up/clean up time? News minutes? Facebook group members?) Were their targets met? More importantly were the targets the correct ones or were they chasing the wrong things - were they were focused on their own issues and not on being customer centric?

During the course of the race itself there were other aspects of product management in action. Every once in a while there were music and water stations, we can consider them to be product features, helping the customers to enjoy the experience more, to engage with them - what will make them happy customers that will come back next year and recommend to their friends?

On the assumption that they plan to run a similar event next year, how, are they acquiring data and how are they planning to review and improve?

On the subject of next year we can consider product extension; will they feel the need to enhance the offering - perhaps by offering a shorter or longer version or by diversifying into a cycle race or triathlon? Perhaps there is a market for more than one event a year?

There were strict rules, we were all supposed to wear the official race shirt and run the course in an orderly manner. There were a few people who ran but I guess hadn't registered, and so ran in their own shirts and there were a few who wanted to stand-out and so ran in other shirts (last year's race etc) - on the whole this caused no problems to the runners. However, we can certainly view them in the context that the product was excellent, but, that it wasn't perfect - it was fit for purpose. Of course, since we mostly followed the rules, then we were complying with a certain standard, specification or protocol.

The race had a strict delivery schedule - it had to be ready on time and it had to work adequately well on the night. So part of the secret here is in team work and execution. The PM&M can have designed the perfect race, but if his project team didn't get the water in the runner's hands or publish the results then the product experience would have been irrevocably tarnished in the eyes of many of the customers.

So in conclusion I had a good run that evening and I believe that the experience was shared by the vast majority of the runners; I suspect that Nike felt that it was a success, but, that they have some points to improve or change in the next year. Overall this was a fine example of the craft of product management and marketing.

More importantly, I hope that by looking at an event that is outside of our day to day we can see the implications of strong product management leadership on all aspects of product design, management and marketing in general.

November 12, 2010

Creating a Product Road Map

“Follow the yellow brick road” - this is the instruction that Dorothy got in order to get to Emerald City.

Product managers are responsible for building the product’s yellow brick road – the Product Road Map.

The road map generally should normally be planned for a 3 year period at a high level and for 18 months in a more detailed manner.

Probably the most important starting point for the road map process is the outcome of the strategic business process of the company. This is a critically important process performed periodically (often annually) by the senior management of the company together with the marketing team and actually drives the entire company. When we start to create or update the road map the last version of the strategic process is a major input.

Often this will be replaced or supplemented by a product strategic process where we systematically look at all aspects of the product and the market and set key business objectives within the overall corporate strategic framework.

The road map process starts with information collection which should include the following:

  • Market trends
  • Regulatory trends
  • Technology directions
  • Competitive analysis
  • Customer requirements and suggestions

In the next step we need to analyze what is the likely impact of each item on the product and what we can or should be do in order to give the best response to the probable impact. The best way is to create a product requirements matrix with all the needed activities, new features, platform changes, etc. and then to prioritize this list.

Having done that, we need to figure out what is required in the development of each element in the matrix. We must get the rough effort estimation and / or the budget needed. Now we have the information needed in order to make decisions and to create a road map release plan, if possible for a 3 year period, but not less than 18 months.

Needless to mention that during all the process described here we need to drive internal collaboration and buy in by involving and getting the opinions of many other groups from within the organization for example marketing, R&D, sales, operations and so on.

This is a cyclic process, since we need to do it again at least once or twice a year and adjust the road map if needed.

The decision whether to let our customers be involved in the road map or more precisely to what extent they should be involved is not an easy one. See this article for some of our thoughts in this area. Generally we need to make the product ready for market, but at the same time, we need to be careful not to let the road map drift in the direction of one or two (big) customers, but, is not in line with the general market direction.

We should be very careful when externalize the road map document since it is has some legal status as a kind of contract and as such we need to enter all the needed legal and financial disclosures.

Hopefully this road map will lead us to Emerald City.

In subsequent blogs we will look at ways to share the roadmap internally and externally, getting internal buy in and some of the methods available to do competitive analysis and technology reviews.

November 11, 2010

The Craft of Product Management & Marketing

The Product Management & Marketing (PM&M) profession presents significant challenges to its practitioners. The main challenge of our profession is: making good product decisions in an environment of uncertainty to drive long term sales, profitability and competitive positioning.

There are many methods and best practices that one can learn and use in the challenging world of PM&M, in order to to help. Occasionally there might be some fortunate PM&Ms facing projects where all the parameters are available, obvious and accurate, for most of us most of the time this is not the case.

Once we are over the decision making challenge, we have to face the organization and manage the “internal marketing” of the decisions within the various functions in the company. The PM&M has to coordinate and collaborate with almost all internal organizations – Sales, Marketing, Operations, Delivery, Support, Legal and R&D. To be able to do all this cooperation the PM&M has to build matrix management skills, but more than this relay on excellent human relationship capabilities.

Finally… after we have managed to make the decision and get buy in within the company, then we reach the critical stage (& our original objective) – going to the market and meeting our customers. In my view, the PM&M must face the customers. This is the way to “feel” and learn the market, find out what the customers are looking for, what are the advantages and disadvantages for our product and how to make it a winner with clear differentiation. Close engagement with the customers is essential to enable the right decision making. However, meeting customers successfully isn’t always an easy task, and the PM&M needs to have the human and technical capabilities to interact with the customers, to present the product and to face the challenges the customers present.

The Customer is King – But are they Always Right?

The customer is the king – they buy our product. We also know that the customer is always right. However, sadly they are not always right or at least not completely right; especially if (fortunately) there are many different customers with different needs. After we have engaged with the customer we will often be left with a conflict – do we meet the customer’s requirements or do we take them into account yet specify other product goals? Generally we are time limited and resource restricted and so our decisions will be (to a large extent) between mutually exclusive options.

As in many situations in life, there is the “easy way out”. When making decisions the PM&M can rely on what the customers demand. It will make everybody happy; internally in the organization no one can argue with the logic of satisfying the requirements coming from customers and the sales people will be delighted to go to the customers and tell them that all their requests are fulfilled. The customers will be delighted to get their exact requirements and to have their views influence the product. But, the “easy way” is not necessarily the “right way”, the popular decision will give the PM&M a friendlier environment in the short run, but will it be justified by the business performance in the long run? Did we sacrifice the future of the product for the comfort of making easy decisions? One of the classic PM&M dilemmas or minefields is letting one or a few key customers dictate the product design. Our responsibility is to make the best product decision in an environment of uncertainty and we need our customers to buy our product, but, we also need to ensure that one or two key accounts do not set the product back in terms of its wider market acceptability.

The PM&M is usually at the eye of the storm. The customers have their requests and crisis, the sales people demand that we satisfy our customers and also give the sales people some new exciting things to sell and to meet their quotas, the operations and support are complaining on the product capabilities and R&D is always short on resources. There are methods and tools that help sort things out in this chaos, but often there are no easy or even obviously right answers. The “craft of PM&M” is to be able to observe the surroundings, analyze the conflicting information, to assess the situation and in the end make the right product decisions that will maximize long term sales, profitability and competitive positioning.

November 7, 2010

Social Justice

An interesting piece on social justice - not a topic that most PM&M people normally deal with directly. But we should remember that everything we do impacts real people and we should try to bring them benefit.

November 5, 2010

Welcome to the JET Blog

Welcome to JET - The Craft of Product Management & Marketing.

Our motivation for writing the blog is simple, we want to share our experience and the fun that we have in leading the development and deployment of technology systems.

We have had the privilege of doing some mega product management tasks, both with real bleeding edge technology and also on the scale of the product development. As you can see from our profile we are very experienced in the field and can and do walk the walk and not just talk the talk. Our recent experience is in the Telecom space, but, most of our insights work across the technology domain and indeed in many other product spaces.

We are very hands on in our products and have spent face time and energy with customers, sales guys and the development and operational teams that are key to getting a product to market on time with the right functionality, at the right time and at the right price.

Over the years we have had many successes, but, along the way we have made many mistakes ourselves and we have seen many mistakes being made. It is really true that mistakes are part of the secret of future success, but, then again it is far more fun to learn from success than to learn from failure.

We believe that if we have to learn from mistakes then we should learn from new ones - it is so 90's to repeat old ones.

So our KVP on this blog and the purpose of sharing our experience is to inform and entertain whilst helping you to avoid some of the pitfalls and to advance the Craft of Product Management & Marketing.

We hope that you will find our posts informative and fun. We invite you to share your thoughts in the comments section and so to join JET - The Craft of Product Management & Marketing.

November 4, 2010

Product Management & Marketing - The Longest Race

A few weeks ago, I was fortunate enough to run the 4th Annual Nike Tel Aviv 10K night run. Now 10K isn't the longest distance in the world, but it is long enough to enjoy the atmosphere (amazing) and to reflect on many different things whilst running.

Sad to say perhaps, but, whilst pounding the streets I managed a few thoughts on product management.

Organising a run with over 15K runners is a real task - coordination with the city, the police, bands, official running shirts, refreshments, web site for registration and results - clearly a massive project & clearly some top class organisers were behind this event.

However, there were many product lessons to be learnt. The race organisers claimed that the other Nike night runs in Europe have been abandoned this year and that our race was the sole survivor. So clearly we see that there was some effective market segmentation and strong brand/product recognition in the local market.

On the subject of brand recognition Nike (not normally slow in these areas) let the competition steal a trick on them - guess which company managed to get its posters on lots of billboards along the route? (So a clue then - Adidas) - so some poor promotion & competitive positioning here.

One of the main questions that we should consider is what is the product and what is the Key Value Proposition that they were promoting? Trivially, this was a race, but probably that isn't really the intention of the organisers; it was probably more along the lines of



to produce a mass street happening in an important city; promoting an active good time to sporty people who are likely to identify with our brand. The aim is also to attract people who previously would not have taken part in an event like this to participate.

This emphasis makes for a completely different plan driving them towards providing bands and music along the route, promotion on Facebook even the choice of the date - 10.10.10.

The local product management obviously worked hard at getting buy in from stakeholders - both in house (Nike management) and outbound keeping the city interested despite this was no longer a global effort. Not to mention trying to maintain product momentum in keeping the customers (we runners) very happy.

I guess we will never know, but it would be interesting to find out - if with all the cross branding (water, yogurts and granola bars) & other cross product promotion (Nike stores) what were the financial objectives of the event? Did the race actually make a profit - not that this is necessarily the objective. It would be acceptable to under-take a loss making activity in the right context. It would also be interesting to know (given this was a unique event this year) whether there was a process of strategic review of alternatives.

So much for the planning and product development, in the next post I will discuss some of the results (product, not my personal time) and suggest some possible conclusions.