Tag Archives: product manager skills

Book Review – Stealing the Corner Office

Had been busy for a while, but have managed to read a book in the downtime. The book is titled “Stealing the Corner Office“. I have posted a brief review in the resources section. It’s a little expensive to buy in India, but the lessons it imparts about the workplace are invaluable. In case you are a corporate citizen with access to an online library, do read this book. If you are building your own collection of useful books, then you must buy this one.

Advertisements

Kaggle for Analytics Competitions – Feedback?

Kaggle is a platform for data prediction competitions. As per their wikipedia entry “This crowdsourcing approach relies on the fact that there are countless strategies that can be applied to any predictive modelling task and it is impossible to know at the outset which technique or analyst will be most effective.”

I reviewed a few competitions on Kaggle, and they seem fairly complex and perhaps a good fit for advanced statisticians or data modelers. However, Kaggle is fairly popular and gets a decent amount of traffic for niche site.

  1. Does anyone have feedback on their personal experiences using Kaggle?
  2. Have you ever recruited or solicited candidates from Kaggle, for analytics roles in offshore development centers or for offshore analytics practices of IT/Analytics firms?
  3. Have you ever used it for networking?

Drop a comment on this post if you have tried any of the three.

Product Manager Maturity Model

Product Manager Maturity Model

There are several different career paths available for technology product managers, but in all of those, there are certain key skills that show how capable a person would be in any role. With job descriptions becoming more and more generic, it is up to you to understand what a role offers and what you might be able to deliver in that role. I will post more on this later.

Web Product Management and JavaScript

If you ask any product manager at a web firm if he does coding, he will respond with a firm “NO”. Then ask him what his work consists of, and he will explain about  use cases, features, experiments and other common responsibilities. At this point, you should ask him if he knows JavaScript and/or HTML and CSS. 90% of web product managers, whether in local market roles or offshore roles, will respond with a “YES”.

Today, it is almost mandatory for web product managers to have knowledge of web software development. And this knowledge is necessary not for software development, but for meaningful conversations about architecture, design and deliverables with the software team. [It helps a lot if you can speak their language!] One of the key components of this lingo is JavaScript, which is surprisingly easy to learn and fairly difficult to master.

In my opinion, JavaScript and Java and 2 programming paradigms similar to RISC and CISC microprocessor architectures. In earlier times, CISC dominated and it required a strong mastery over the instruction set, to construct good quality programs. Later, RISC (and parallel processing in multi-core microprocessors) made life easier for not-so-skilled programmers to churn out software. However, to build really good programs for RISC chips, you still need to learn a lot of “other” constructs apart from the chip’s instruction set. These other constructs are similar to the vast amount of libraries for JavaScript, which make life easier for a master programmer, but difficult for a product manager, if he wants to master coding. Even then, this is far simpler than the hundreds of patterns, libraries and classes that you will need to work on for many years to become a master at Java programming.

More formally, JavaScript is a client-side scripting language, which can be learnt quickly, and will definitely set you apart from the “non-techie” product managers. There are several tutorials that explain the syntax (Hello World!, decisions, loops etc) of JavaScript, and after that, it is just a matter of practising these learnings. Of course, you must have a basic knowledge of software development to fully “speak Javascript”.

So how does this help you as a product manager? As I mentioned before, it is useful in 3 scenarios:

1) Prototyping

No matter which prototyping tool you learn to use, a mockup will rarely be interactive unless you add JavaScript. HTML forms, pages and dialogs will become more clear than basic wireframes when you present the concept to the engineering team. This may even allow them to improve on your efforts during development.

2) Discussions

When your engineering team starts explaining  the benefits of designing “multi-threaded JavaScript objects” running parallelly versus a simple object pool, you should be very sceptical. And knowing JavaScript basics will allow you to research on the net why this could be a bad idea from a time, complexity and engineering resource point of view.

3) Career Development

While a JavaScript certification may never be a career changer, having JavaScript in your skill set, even with an MBA, will set you apart from the other product managers. It’s easy to learn, you can practice it on any laptop and use it practically when needed.

Apart from JavaScript, it is useful to learn HTML and CSS. And recently, there has been a lot of talk about “Big Data” technologies such as Hadoop, Hive, PIG etc. More on that in a later post.

Book Review: The Strategy and Tactics of Pricing

Strategy and Tactics of PricingThe Strategy and Tactics of Pricing is actually a management textbook, typically prescribed as a required reading or a reference text in a course on pricing for undergraduates or MBA students. However, the book is very well written and is a must read for all product managers. The book has also received glowing reviews on Amazon.com.

If you wish to understand how pricing is done, or take part in pricing discussions with senior leadership, or price a new product or service, read this book.

About the Book

The book talks about the 3 core principles of strategic pricing, that strategic pricing should be value-based, proactive (where you anticipate large deals, competition response and develop models to account for those) and profit driven (focus on your targeted profit). It then shows the limitations of cost-plus pricing, customer driven pricing and pricing for market share. A Wikipedia article has a detailed description of the different pricing strategies.

The other chapters in the book cover

  • value creation and what it means to the firm and its customers
  • pricing structures
  • pricing communication with stakeholders
  • pricing policy and pricing levels
  • pricing over the product life-cycle
  • driving implementation of the pricing strategy
  • understanding costs and basic financial analysis
  • competition and pricing sensitivity analysis
  • Following the ethics and laws on pricing

Overall, a complete reading of this book 2 or 3 times should make one confident to take up a pricing task and drive a pricing strategy. This information is of great value to a product manager in any role (on-site or offshore) for all types of product sales models (subscription, licensing, freemium, cost+maintenance and others). The challenge will be to keep these learnings since pricing decisions come around very rarely, and are normally taken up by the Director/VP of product management.

For Product Managers

Product pricing is a very important dimension of product management. And it is a sensitive and critical issue in most organizations. In many cases, pricing approval is actually done by the CEO or Executive Management. In the pricing exercise, there are multiple stakeholders and everyone wants the “best price”. However, the definition of best price is different for all. Sales wants the upfront price lower than competitors, finance wants to look at the cost/price variance and the best ROI possible and marketing wants to dictate the price. So it is the product manager’s role to build a valid structure for pricing the product/service or the deal and then come up with a logical product price (which could actually be higher than the competition’s price) for different situations.

This book explains pricing very well, and you should definitely keep a copy on your desk as a reference. It is as useful for pricing SAAS products as it is for pricing consumer or enterprise packaged products.

Note: In case you have a traditional software engineering->product management career path, you may want to pick up a few courses on corporate finance and management accounting. They will help you a lot if you are ever involved in pricing decisions. A part time MBA could also be useful.

7 Tips for Fresh MBAs working as Offshore Product Managers

[Caution: long post]

Today, most business schools prefer candidates with some work experience, which is also useful during lateral placements. Hence you see an increasing number of candidates with exposure to IT services or software engineering joining these schools and completing their MBA. Post-MBA, it is inevitable that some of them will head towards product management during campus placements or shortly afterwards. This post is about the 7 things to focus on in your first year on the job, apart from working on PRDs or MRDs.

1. Build a rapport with program managers

In most offshore R&D centers, program managers play a key role in organizing projects, resources and schedules. Hence they know the resource costs and availability for any ongoing or upcoming project. And since engineering dominates decision-making in ODCs (offshore development centers), the program managers help to balance the engineering dominance.

2. Get customer exposure on a sales call

An enterprise sale is a complex process, involving dozens of people from different departments, and it typically has a long completion cycle. You must gain a first hand exposure to how this works, as this is the main source of revenue for the firm and for your product line. However, it can be difficult to gain a sales person’s attention, as he is always looking outwards for opportunities. As an incentive to sales folks to get them to talk to you, arrange a product demo or a feature presentation. If the demo is interesting enough, they will make sure that you get in front of the customer.

3. Gain the trust of engineering and service delivery managers

I have written previously about key stakeholders for offshore product managers. If you cannot get these people to trust you, you will never be able to drive product decisions, even with your supervisor’s help. And you cannot keep going to him all the time. One good technique to gain the engineering trust is the show them that you can deliver on the product requirements and are not simply there because of your MBA. Essentially, you need to prove yourself with every engineering resource, right from the VP to the intern.

4. Train yourself

If you are just coming out of b-school, with a few years of pre-MBA IT experience, you have NO relevant skills whatsoever. The people in the ODC do not care that you can prepare kick-ass powerpoint. Neither are they interested in the font, color or direction of arrows in you block diagram. You must focus on gaining survival skills, which today include, UI design using HTML, CSS and Javascript, UML and MS Visio usage, basic analytics, and programming skills in at least C++, Java or PHP. There is a lot more to gaining skills in multiple dimensions, and I will cover this in a future post.

Do not bother to go for a formal product management training yet. Without relevant experience, it will have very little value and you will forget most of it very soon.

5. Prepare for a change to your role/product within 12 months

In today’s connected, global economy, it is almost guaranteed that your first role will last no more than 12 months. The change could be due to external forces or internal restructuring (ODCs are very prone to this), but it will definitely happen. In the worst case, you might feel stagnating in your role, and you will yourself ask for or start looking out for a change. The best way to survive this is to shine in front of senior management, build a rapport with the US teams and network with HR and other support staff.

6. Connect with Solution Sales, Analytics, Customer Service Teams

This is probably the most important task that you can perform outside of self-training. To understand how the product is built, you need to sit with engineering teams. To understand how the product is sold, you need to work with sales teams. And if you really want to understand how the product is used, you need to work with solution sales, analytics and operations and customer service teams, who cover all real use cases that the product was designed for. And remember, you need to proactively seek them out and learn from them. As a fresher, it is expected that you will be learning all the time.

7. Network outside the firm

There are a lot of opportunities for networking in Bangalore, Hyderabad and all the other major tech. centers in India. You must go to these get-togethers (a few of them are listed in the resources section of the blog). It can be a lonely job, working as a product manager, with no outbound teams near you. Connecting with other people in similar situations is a good way to understand the challenges of an offshore product management role, and the different ways in which people are coping.

Summing Up

A product management role, even offshore, can be incredibly rewarding, but only if you take care of your first few years on the job. It is not for everyone, and you should make sure that you are still interested in it at the end of your first year. Else, as an MBA, it will be easy to find something else.

Book Review: High-Tech High-Touch Customer Service

Hightech HightouchHigh-Tech, High-Touch Customer Service is a book by Micah Solomon, a writer and business strategist. He is well-known in the field of customer service, particularly on B2C customer service. However, the book is about customer service in general and is of some relevance to people in the B2B world too. If you are the product manager of a consumer facing product, or are looking to understand how customer service impacts your product sales, its lifecycle or its quality, you should read this book. Additionally, you could also recommend your HR team to buy this book for the customer service team in your organization.

About the Book

The book is divided into 3 parts, part 1 covers Timeliness and Timelessness in customer service, with several examples. Part 2 is called High-Tech, High-Touch Anticipatory Customer Service and it talks about your company culture, its customer service, the importance of autonomy in the service team and the ability to anticipate customer needs and it has several examples on these themes. Part 3 talks about customer self-service, social media and the principles to assimilate with these new paradigms.

There are 13 chapters in the book, and you can read through it in a couple of days, or browse through it a few chapters at a time. It also has examples of customer service within many organizations, such as Zappos, SouthWest Airlines and Apple.

For Product Managers

Fundamentally, there is no ground breaking insight in the book, but there are a lot of common sense principles discussed here, which we occasionally lose sight of, in the rush to design the product and get it out of the door. Today, a significant part of enterprise product management activities is about defining incremental releases and tracking the existing deployments and the client satisfaction with the product. This is actually as important as defining features and benefits for the new release, to sell to new clients and accounts.

Additionally, in the B2B world, a very important metric for retaining and growing accounts is CSAT or Customer Satisfaction. This is usually a numeric value, which determines the success of failure of your product in a vertical, geography or customer segment. To ensure customer satisfaction purely from brilliant features of a product is a really tough ask, and so customer support also has a very important role to play in improving and maintaining CSAT.

Of course, as a consumer market product manager, you must remain on top of all customer issues surfacing after the product release. And CSAT is also measured reliably if you are closely tracking the social media outlets.

This book gives several ideas for bringing together the strategy to retain existing users and gain more users. It would be a great exercise for any product manager to identify how they can integrate these ideas into product features and follow through with customer support trainings for the same.

Note: In case you manage a high technology product, I strongly recommend that you spend time with your customer service team. Understanding the product deployments and troubleshooting problem scenarios is a great exercise to gain insights into product usage.