Month: July 2010
I recently started reading LiteMind, and have been enjoying it very much. The focus of the site is personal development, productivity, freedom, and creativity … all topics that product managers can benefit from.
They have an offer today that you should check out: A free eBook just for making a comment on a post. I think it’s a draw, so it’s not a sure thing, but the list of books is worth perusing.
Check it out here: http://litemind.com/personal-development-giveaway/
There’s a lot of general discussion about traits and activities to help individual Product Managers excel, but not a lot is written about Product Management teams and departments. I wrote a pair of blog posts on this topic a couple of years ago, but not much since, so I thought it was time to revisit the topic.
A reality of Product Management teams is that they are usually relatively small, particularly when compared to larger departments such as Engineering, Marketing or Sales. And perhaps it is because these teams are small, that not much thought is given to how to best structure them. But in fact, given the critical cross-functional role Product Management plays, having a well structured, scalable and properly staffed team can make a huge impact on the top-line of a company’s balance sheet.
Here are the 5 steps to building a great organization.
1. Understand the full value of Product Management
Too often technology Product Management is viewed as the requirements collector, or keeper of the product roadmap, or an adjunct to Engineering. But all of these sell short the value and impact Product Management can have on a business.
What is the ultimate goal of Product Management?
To optimize the business at the product, product line or product portfolio level over the lifecycle of the products.
Or as Don Vendetti defined it in his guest post:
To deliver measurable business results through product solutions that meet both market needs and company goals.
Either way, the focus is on the business success.
And if you look back at the origins of Product Management it’s clear that’s how it was envisioned by James McElroy at Procter and Gamble almost 80 years ago.
2. Put formal Product Management in place very early in a company’s life
Understanding what should be built and for whom is a core task of Product Management. But even in very early stage companies, there are many other questions that Product Management must answer:
Questions such as:
- What high value problems does the product solve?
- Who faces these problems today?
- How much pain do these problems pose for these people?
- Who will be the main buyers of the product? (Note: buyers and users are not necessarily the same).
- Will the buyers pay to address the user pain (i.e. is the pain a high enough priority for the buyer to spend money to address it?)
- What are the current alternatives to using the product?
- What obstacles need to be overcome for people to adopt this product?
- What skillsets will the target users have?
- Do the skillsets of those users match with the required skillsets needed to use the product?
- How should the product be priced and licensed?
- How should the product be initially delivered into the market?
- What channels or partnerships are required to enter the market?
These are all fundamental questions that should be asked and answered in the earliest stages of a business, as they not only impact how a product is built, but also the activities and people needed to bring the product successfully to market.
For any startup, company success is tied directly to product success. Or as Bill Campbell said, “Great companies start with great products”. It is something a lot of companies seem to forget, as they release complex or unfocused products that require significant marketing and sales efforts to generate customer adoption. Put skilled Product Management in place early to accelerate market adoption, revenue and profits.
3. Product Management must be part of the Executive team
An experienced Product Management executive should be the first formal Product Management hire as she/he can not only help with overall product strategy and market alignment, but can set the stage for building a great team as the company expands. In short, Product Management needs a seat at the management table.
Many companies that hire early, make the mistake of hiring a less experienced person — a “hands on” individual contributor — to be “the Product Manager” for the fledgling product. This person typically reports into Engineering or Marketing and thus isn’t part of the Sr. Management team. While a good individual contributor can certainly help a company avoid common mistakes, an experienced executive can help drive the company forward and accelerate success.
4. Don’t starve Product Management as the company grows
Far too many companies have significant budgets to hire additional engineers, sales and marketing staff as growth occurs. But as they grow, they typically don’t increase the Product Management team to keep pace. This is a pattern repeated in many companies.
Over time, Product Management becomes a bottleneck for other groups in the company. This not only reduces the effectiveness of Product Management, but also impacts all the downstream teams and activities that depend on information and decisions coming from Product Management. This creates a drag on the company’s ability to execute effectively and to bring new successful products to market.
5. Create Product Management teams with differentiated roles
An often heard lament of companies looking for Product Managers is that it’s difficult to find really good Product Management candidates. I’m sure that’s true, but it’s also true when it comes to finding really great candidates for sales, marketing, software development, QA etc.
In general, good talent is hard to find. But what exacerbates the Product Management search even further is how companies define the job of individual Product Managers.
Product Management is a very broad function with a mix of technical and business responsibilities. Product Management needs to stay abreast of changing market conditions, competitors, and new technologies. Product Management also must create product and business plans to address market opportunities. Additionally Product Management must work across multiple groups and departments in a company to help ensure they are aligned.
A lot of companies make the mistake of rolling all of these responsibilities into a single role – the Product Manager – and then looking for the ideal candidate with all of the the technical and business experience, domain knowledge and leadership skills to fill that role.
And then when they need to scale – for example when looking to create a second product – the same companies look for yet another candidate with the same broad skill set. This process gets repeated over and over again across many companies. Of course, not only does this make it hard to find suitable candidates, but it makes it very difficult for those people, once hired, to be truly effective and successful.
Would any company hire software developers and ask them to design and write software, test it and also write the documentation for it? Or how about trying to hire a salesperson who can do their own lead generation and act as their own sales consultant. Not very likely.
Few if any companies would think that these are ways to build scalable and effective software development or sales teams. It should be evident then, that it is also no way to build a scalable and effective Product Management team.
Roles in Product Management should differentiate between technical and business focus; between short term tactical focus and longer term strategic focus; between internal (inbound) and external (outbound) responsibilities. These roles should be organized as small teams focused on specific products or product lines, with defined metrics to measure progress and success.
This is what is done with virtually every other department in a company. Why should it be different for Product Management?
NOTE: Shortlink for this article is: http://wp.me/pXBON-1Fv
Simple question :
What’s one thing you know now that you wish you had known when you became a Product Manager?
Think of it as advice you’d like to pass down to those new to or thinking about entering the field.
I wish I had really understood the value of ruthless prioritization. By that I mean prioritizing all the things that were (seemingly) expected of me, and being able to clearly define what was most important and focus on those.
I remember being completely overwhelmed in my first Product Management position by trying to do what I thought was expected of me by all the other teams.
It was a huge learning curve, and this was in a company that in hindsight, probably had one of the best grasps of Product Management of any company I’ve worked in.
OK, over to you. Please leave your answers in the comments section below.
NOTE: Shortlink for this article is: http://wp.me/pXBON-1Fl
For this post, the specific question asked was:
If you could change aspects of your job to make it a more effective role, what would those things be? (The UGLY)
NOTE: As in previous posts, I’ve categorized the responses into high level categories and tabulated those. I’ve tried to keep a bit of consistency (where possible) with the categories used in previous survey result posts.
And with that, here are the results:
Lack of Authority
This was by far the most common answer with a lot of consistency in the comments provided by people. Not surprisingly, lack of authority was a common answer in the BAD of Product Management results. Some of the comments:
- More decision making power
- More control over the development process (we’re an ASP)
- Ownership of the product in reality and not just on paper
- More “voice” over development priorities
- Resource management (control/greater influence over dev and /or marketing priorities)
- Give PM full ownership over the product – i.e. don’t promise anything without checking with her first, trust in her
- Management of complete portfolio
- Product Management participation in strategic planning
- P/L ownership
- Ownership of product roadmap; move it from the CEO to Product Management
Looking at these, I’m going to make an assumption that Product Management is being defined as a silo (along with other departmental silos) in companies. The last two points about P/L and roadmap ownership attest to that.
This was also a frequent response in the BAD results. I see a clear relationship between the Authority comments above and the Culture comments below. In some ways they are flip-sides of the same issue.
- A culture that believes in good product management
- Get people to understand the importance of product management
- Clear accountability of teams to each other
- Cooperation with R&D
- Eliminate the micromanagement by empower the Product Managers to own their business
- Having enough time to attempt to do things right from the start rather than always rushing through each process
- Product Management shouldn’t be defining product architecture; Engineering should!
- More accurate LOEs (level of effort) and schedules from engineering
- Be given clearer objectives from Management
I think most of us have heard these comments before, or probably lived them in companies we’ve worked at. The question to answer is HOW can we affect the change needed to address these issues. If they are so common, there must be common reasons why and certainly means to start addressing them, either bottom up or top down.
There was one comment that I want to pull out specifically as I think it’s a great one:
- Get resources and time to celebrate more. Too many project teams seem to see the reward of their hard work as more work in the next project. We should be taking the lead to celebrate wins and rewarding eh people that made it happen. this is especially important in the age of Agile when projects continue for long stretches
I really think every company should take this comment to heart and address it in whatever ways are appropriate.
When I worked in California – after a LONG effort on a major release — all of the PM and Engineering staff were treated to a 3 day trip: Hawaii for those in California and Thailand for those in India. It was a very nice way for the company to show their appreciation.
These kinds of celebration and rewards can do wonders for staff morale, productivity and loyalty. Hey, if the sales teams can go to Club for their efforts, why not the people who build the product that the Sales teams sell?
Another common issue in most Product Management teams is around staffing. I’ve never heard anyone say, “We have way too many Product Managers!”. And given the cross-functional nature of the job, as well as the general lack of clear definition of the PM roles, it’s not surprising the PMs feel overloaded.
- Have a staff of evangelists on hand to drive feature adoption
- Hire a Project Manager to run projects
- Have a project/program manager working with Product Management
- Have a dedicated team of developers and project managers
- Need more staff; business doesn’t comprehend the importance of activities, so understaffs
- Have more product experts in house, allowing me to be a market expert
Restricted Customer Contact
It was surprising how many times people indicated that they are blocked from direct customer contact.
I’ve listed this high because it is such a glaringly obvious issue that companies need to change. I think it also goes back to earlier comments about companies that don’t understand how to define and implement Product Management. It also ties into the next heading of Job Definition and Process. Some of the customer related comments were:
- Be allowed to interact with customers more often
- Have more time to spend speaking 1:1 with customers
- Getting to speak more openly with strategic customers
- More customer visits
- More time with customers/prospects outside the sales cycle
Poor Job Definition and Process
This category combines two related items that seemed intertwined in the comments. Anyone who has worked in Product Management for any length of time has encountered these problems in at least one company.
- Define the role more clearly
- The job requirements for the role are too broad
- Better definition around the scope of Product Management
- Real roadmap process
- Less day-to-day support of other functional areas
- Have a good process where Product Management can have sufficient influence
- Improve the organizations ability to handle changes coming in from the market
- Have bottom up strategy and budget planning
- Don’t be “too Agile” and change the concept of Agile
Inefficient Organizational Structure
Another common thread when talking about changes that need to be made. This is often related to the staffing issue described earlier.
- Hire pre-sales people in each region globally who are specific to my product
- Restructure the company to product-centric P&L teams
- Eliminate expectation for sales support
- Create a PM support later to handle day-to-day issues
There were a number of other comments that didn’t get a broad coverage in the responses. These included:
- Strategy – 5 responses – e.g. strategic planning, clear corporate goals
- Metrics – 5 responses – e.g. create clear measures of PM success
- Issues with Sales – 4 responses – e.g. hire better qualified sales people
- Budgets – 3 responses – e.g. larger travel. Let me experience the market directly
- Tools – 2 responses – e.g. need better tools for requirements tracking, customer summaries, sales data etc.
I’m quite surprised the Metrics didn’t get mentioned more often. It’s clear that few companies have well defined metrics for Product Management, and this causes problems in role definition and staffing.
Tools was another one that surprised me by how few mentions it received. Maybe people are actually using real tools, or may be most respondents have just given up, or maybe lack of tools isn’t one of the 3 biggest problems people face in their roles. 🙁
So there you have it, the final installment – What people want to see changed in their roles and companies.
Does you see issues that apply to you or your company?
Are there other issues that were missed by the survey respondents?
I want to hear from you.