A perspective from the other side – Seema Joshi, Lead Product Manager – BMC Software, #PNHangout.

In this #PNHangout, Seema Joshi, Lead Product Manager – BMC Software, shared with us her insights about Product management and the challenges and scope on the road ahead for Women Product Managers.

Why did you choose to be a Product Manager?

There are two aspects to why I chose to be a Product Manager. The first is related to the evolution of the Indian IT industry and the second my personal journey.

The Indian IT industry, after its beginnings in the 1980s, saw good growth in the 90s with the economy opening up primarily due to high cost arbitrage. During this time the industry was dominated by the services sector. In the 2000s, the industry was maturing rapidly due to economic downturn pressures and consequently margins were eroding and cost arbitrage decreasing. The services industry still dominated the IT sector as the cost arbitrage play was becoming increasingly competitive. We also began to see larger R&D centers, mostly captive, setting-up base in India. Now, in this current decade, the focus is shifting to total product ownership. With increased expertise as well as domestic markets, startups and VC eco-system expanding, product management is becoming a critical part of success. It is more critical than it has ever been. While we do have a growing leadership presence across companies in India from a R&D product and project delivery stand-point, product management and product leadership focus needs to be stronger to deliver great products to local and global markets through entrepreneurship or intrapreneurship. Product management clearly has a large role to play in shaping the course of the Indian IT Industry.

I am a Bachelor of Civil Engineering and I began my career as a structural engineer after graduation. While I loved my work building peoples’ dream houses, factories, bridges, etc. I knew that I was more productive and happier working with people. So, I took up an opportunity with eGain Communications- a product company in Pune in a customer facing role where, after sometime in this role, I moved to the sales team as I thoroughly enjoyed working with in a customer oriented role. We were a small team targeting new territories which meant wearing various hats from lead-gen, pre-sales, solution consulting, account management all the way to acquiring business. It wasn’t always easy, but it was challenging and educating work. After a few years in this role, I was offered a position in the product management team and the decision to move wasn’t difficult. I think I always was and still am a sales person at heart. So the proximity of working with customers to find solutions for their problems was important to me. At the same time, I had seen typical enterprise sales cycles span anywhere from 6-12 months. I now had an opportunity to bring to the table my experience of working with customers, their needs and expectations from solutions, etc. and, with the outside-in perspective to help build the product, I could indirectly contribute to getting business from a greater number of customers beyond my sales territories! The product management role was like a win-win.

It was both the opportunity and the challenge to be a Product Manager that got me into the role nearly a decade ago and it still continues to be my passion!

Great, you’re a Product Manager. So what do you really do?

I’m often asked this question and I have begun enjoying answering it, so much so that I have two versions of answers. For the people interested in a short answer I tell them – “As a PM I do lots of conversations using a ton of post-its, a set of lenses and glue.”

For the ones still with me, I tell them: a PM is responsible for the success of the product to maximize business value through the product’s lifecycle depending on the business goals—be it driving market share, revenues, customer retention or whatever the focus for that product might be in its life-cycle at that point. This requires a PM to have good understanding of the unsolved problems in the market to identify market opportunity. To do this effectively they need to bring out the post-its and engage with customers to understand problems in their context and what their pain points are.

They then need to use their short-term and long-term lenses to review this vis-à-vis corporate strategy, internal strengths, risks, funding, competitive landscape, etc. to come up with a business strategy to address the market opportunity and product strategy to build a kickass product.

With the strategy in place, they need to communicate with the entire value chain to help deliver this—right from exec approvals, working with engineering to build the product and with marketing to convey the planned product value, sales tools and processes to ensure sales is able to effectively sell to the right buyer and with support to ensure customers understand how to use the product in the desired way, etc. They need to be the glue between cross-functional stake-holders to ensure right execution.

Though a PM might not be responsible for each of these areas, it is very important for every Product Manager to still have what I call the imbibed-CEO attitude. You may not call the final shots in each case, but if you do not align and orchestrate various aspects while driving your areas of responsibilities, you might reduce the odds of your product’s success. A Product Manager really must be passionate and enthusiastic about everything related to the product to make it truly successful!

Managing a product demands multiple sources of information and skill. How can a Product Manager prepare herself for this role?

A Product Manager needs lots of post-its, glue and conversations as they do their daily jobs. Conversations are typically of two kinds—one in the listening mode to gather insights and the other communicating what to do and not to do and conveying value and ways to get there. The PM does not need to be the encyclopedia, but needs to know different ways to get this information that can go into the encyclopedia. It is really a mix of art and science!

There are recommended practices for the entire productizing process that can be used to source and communicate information effectively. Individually a PM can focus on some of the following to do this well:

  • Be a good listener: It is never about what the product can do. It is always about what the product can do for the customer. Engaging with customers and the market to understand problems in their context is critical. This involves being able to ask the right questions, understanding customers and their business and what their key pain points are as means is to identify pervasive problems.
  • Good domain understanding: It isn’t a pre-requisite for a PM to be a domain expert right from the beginning. However, to engage effectively with customers requires being able to do it in the context of their domain. So a PM needs to quickly get a good handle on how things work. Regular interaction with customers and prospects is definitely a great way to do this as well as following analysts and thought-leaders in the industry, tracking competition, attending industry events, etc.
  • Build an analytical approach to problem solving with a business-centric mindset: It is not about picking the first or the easiest solution or solving the problem of the noisiest customer. To derive the next set of outcomes, having understood the unsolved problems in proper context, requires being able to quickly analyze scenarios, potential opportunities, dependencies, financial implications, impact and mitigation plans. PMs need not be experts in each aspect but he needs to be able to evaluate options and work with the value-chain towards achieving business goals for which time and cost is critical!
  • Communicate effectively: Effective communication is the hallmark of a good PM. A PM is required to constantly communicate with various stakeholders to achieve a common objective i.e. to build a product that delivers value. For instance, a PM needs to communicate
    • Business opportunity and solution recommendations to execs for strategy and funding approvals
    • Product requirements to engineering to build the right product
    • With marketing to articulate solutions and convey the right value messaging
    • With analysts or customers to convey the solution and its value

If you fail to sufficiently communicate any of these, it could affect success!

  • Leadership and self-leadership: It is important for a PM to bring in the right vision, energize teams, influence, and be good at decision making for many a time it is about right prioritization and timely decisions. This cannot be done without passion for your product and its success. While good processes help reduce risk, even at an individual level, a PM needs to take charge and align and inspire teams towards their goals.
  • Belief, patience and perseverance: There are no two ways about it. In product management you’re in for the long haul. It is about a product’s journey towards success. If you want things to happen overnight, or view it just as a set of tasks from one release to another, you might end up taking the wrong paths. Keep the focus!

Women Product Managers – there are a few of them. Is it a disadvantage to be a woman?

Overall the gender diversity ratio in the Indian IT industry is approximately 25 % women, which is better than others. However, most women are still in traditional roles like HR and Marketing and to some extent engineering, technical-writing and delivery-centric leadership roles. The presence in product management and product leadership is still really small. In fact, in my 8 years of being a PM, both at my current and previous company, I have been the only woman PM in India. Of course it is a little different when it comes to global teams.

In India I have been on many forums and meetings where I am the only woman. Being a woman PM tends to have a two-fold challenge. For companies, organizationally, product management as a function is still not mainstream; it is getting better but it still isn’t there. This is further compounded by the lower women ratios overall and within the function.

One of the common challenges most Product Managers need to overcome is related to change—recommend change in strategy, change in practices to address opportunities, culture of organization, etc. If you’re the only woman in the room driving this, be ready with all kinds of data-driven reasons, proof-points and if-else conversations to make the change management smooth and effective to avoid “but, this is not how we’ve done it in the past” objections.

Beyond that, at a larger level, the challenge is a common one irrespective of roles—to have better diversity across hierarchies in an organization. If companies want to make a notable difference in diversity, it is crucial for them to cultivate a culture where women not only end-up taking more traditional roles like HR, Marketing, etc. but also actively encourage women to take up roles along technology leadership (as architects) or product leadership (product management and innovation) as we take the Indian IT industry to the next level AND if we don’t want women to be left behind once more time to only catch-up later!

I would also like to give a shout out to women in the industry to gear up for this and be prepared to play your part. Remember that what got you here won’t get you there and these days “lean is in”, so sharpen your skills to make a difference. For a better outcome tomorrow, it is a choice we have to make today—as individuals and corporates!

Is there a bright side for Women as Product Managers?

One of the key things for a Product Manager is to empathize with users and to care for the overall experience. Women tend to be naturally more attuned to this. They also come across as effective communicators and influencers. A PM needs to do a lot of communication as there are various stakeholders to be managed across ranks and a Product Manager has to be able to influence by bringing out the reason and value of why things need to be done the way they need to.

Being great at multitasking is a benefit as well. Recent studies are converging with the hypothesis that women are found to be better at multitasking than men. A Product Manager is always juggling between different things and different people and yet needs to keep all tracks aligned. It helps to be able to prioritize tasks, organize time and most importantly keep calm under pressure as they rapidly switch between activities.

Lastly, their leadership styles help too. PMs not only need to nurture a product from conception through its life-cycle but also drive larger teams towards a common objective without having any authority over them! This is corroborated by the increasing number of women taking up significant roles in corporations. Women Product Managers are definitely making a mark. Marissa Mayer’s growth from a great Product Manager to being the CEO of Yahoo is a testimonial to it. So there definitely is a bright side for women as Product Managers.

#PNHANGOUT is an ongoing series where we talk to Product Managers from various companies to understand what drives them, the products they work on and the role they play in defining the products success.

How to get to 1000 startups in India ever year

I will be on a panel with several others at the IAMAI conference next week for the India Digital Summit and the discussion is about how to make 1000 digital startups happen annually in India.

I thought I’d put some thoughts together and get some opinions before I present at the panel.

Currently there are less than half that number of product companies being started each year.

There are various issues across the funnel, but I’ll focus on the #1 issue, which I believe is at the top of the funnel.

Great product entrepreneurs starting great companies.

I wanted to pick a specific example from our accelerator: two of the most amazing hackers and geeks I have worked with – Melchi and Aditya co-founded Cloud Infra after 6 years at Google here in India, building high quality products.

I would fund them just given their background and the quality of hackers they are. Regardless of what they are developing.

Anyplace else (Valley) they would have been funded first and then they would have been asked questions. I worked with them for 4 months.They are amazing.

India needs more of them to increase the number of startups from 500 to 1000.

Unfortunately that’s not happening and is not going to happen.

I may get a lot of brickbats for this statement, but:

I believe the best product entrepreneurs should have built & shipped a world-class product before they start a company.

If you have worked in a services company it does not count. Period.

There are very few software product companies in India – in fact fewer than 20 are really good. Of those 20, many, including Google, are cutting back on hiring and investing in India.

That’s just awful.

Yahoo, Zoho & InMobi in particular have contributed a LOT to the product startup ecosystem in India, given how many good developers they have helped groom.

If you worked at any of these product software companies a few years ago, then you are a candidate for a high quality product startup in India.

Granted, a small number of these folks are actually starting companies, but that can be fixed.

The trouble is there are not too many of them in the first place.

And the bigger issue is that the Google’s and Facebook’s of the world are preferring to hire more folks in the valley.

In fact many of the top IIT graduates who get jobs at Google and Facebook are moving to the valley. 2 years ago they’d be working here in India.

To get 1000+ digital startups each year in India, we have to work on making sure world-class digital software companies hire more of our top people here in India.

I dont think tax breaks will provide them any more incentive to hire here.

I also believe there are enough quality folks here in India they can hire.

I’d love some ideas on what will make them hire more people of high caliber in India and keep them here. I’d love to see them not cut back on hiring in India.

What are your ideas on how we can get these companies to hire great engineering talent in India?

Is Software Innovation an Art or a Science? It’s Artful Science or Scientific Art!

When we think of Software Product Innovation, we imagine getting “Eureka!” moments 3 am in the morning, getting up and writing down inspired thoughts and coding them the next morning!

Reality is much more mundane and is more of evolution rather than sudden insprirations from the sky!

Yahoo started because Jerry Yang and Filo just wanted to create a searchable directory of information first at Stanford University and then San Francisco in general!

facebook started as a teenage testorone-fueled comparion site for Harvard students to post pictures of fellow girl students and rate who’s hot and who’s not! From there it evolved into directories of students in universities to find each other for dating more than anythingelse. For a long time, facebook signed up university by university and not the general public-oriented thing it is now!

This stands for enterprise software products also – Oracle Relational Databases were less expensive, clumsy knock-offs and replacements for Digital Equipment Corporation’s RDB/VMS relational database system.

Before Microsoft Word and Excel spreadsheets, there were Lotus Ami Pro and Lotus 123!

Before Google search, there were DEC Alta Vista search engine and Yahoo!

What made all the successful ones innovations in their own right were not just technical superiority but they took useful innovations and products before them and fixed annoying problems with their usages or expanded the concept of who can use them additionally or fixed usability problems with them.

Or they took an older concept and applied it to a new platform!

Or took an older concept and applied it to a newer market!

So if you want to innovate, you don’t necessarily to invent something new. You can innovate by doing one of these:

—- Is there something useful but not so easy to use? Can I fix it by making it easier to use? (Google’s single search box in the middle is a great example – Alta Vista got lost in boolean searches and requiring ANDs and ORs when specifying search. Google said – don’t worry about all of that stuff. We will take care of it. Just type in what you want into that box!)

— Can I take something useful and apply it to a new market? eBay India was another company before it became eBay bought it and made it eBay India. Flipkart is India’s Amazon. Cleartrip is India’s Expedia! Make no mistake. They are not just copies. Flipkart uses courier delivery. Cleartrip is useful for buying train tickets less painfully than when going to the IRCTC website. They all add some value and difference!

— Can I take something in one platform and make it suitable and applicable to another platform? Mobiile versions of applications may need to be differently designed and executed than an online, browser version of something.

— Can I build a family of products around one idea with more features? Personal, Professional, Enterprise versions of software is a fairly standardized way of adding additional features but orienting them towards different markets.

— Can I build a family of products that are related to each other but different from each other in functionality? Word, Powerpoint, Visio, Excel are all examples of slightly related products but providing different kinds of functionality.

Many times, we think that innovation is coming up with something completely new,. Successful innovations have all fixed or fine-tuned something useful but had some problems that were preventing widespread adoption.

Sometimes it is as simple as figuring out what these are and fixing them. And also thinking about related things so that you are thinking about a “family of products” rather than a single “one hit wonder”.

Wikipedia provides a clear definition of Innovation:

Innovation is the development of new customer value through solutions that meet new needs, unarticulated needs, or old customer and market needs in new ways. This is accomplished through different or more effective productsprocessesservices,technologies, or ideas that are readily available to marketsgovernments, and society. Innovation differs from invention in that innovation refers to the use of a better and, as a result, novel idea or method, whereas invention refers more directly to the creation of the idea or method itself. Innovation differs from improvement in that innovation refers to the notion of doing something different (Lat. innovare: “to change”) rather than doing the same thing better.