Tags:
Permalink Reply by John Davey on February 10, 2009 at 7:19pm
Permalink Reply by David Locke on February 10, 2009 at 7:32pm
Permalink Reply by Greg Akins on February 11, 2009 at 12:17am The Pragmatic Marketing web site is a great resource for learning about product management.
Without knowing more about how your company defines releases and manages requirements, it's hard to give specific advice. You talk about focusing your team's development efforts - one place to start is with a product roadmap that lays out the major goals and features for the next few releases. If your company doesn't have one, or has several and doesn't exactly follow them, creating a roadmap and getting buy-in from the other leaders in the company will help get your team focused.
Permalink Reply by Greg Akins on February 11, 2009 at 12:18am I second the vote for Pragmatic Marketing. Start with their well-trusted framework and do a gap analysis. There's probably lots of areas you can move into without treading on toes and increase your product marketing role and ultimately become seen as the natural choice to take over other areas of the chart from your colleagues.
There's lots of great stuff available on the 'net...
- How to become a Product Manager
- The Top Product Management Blogs
Permalink Reply by Greg Akins on February 11, 2009 at 12:22am Why do a job that isn't all that important. Beware! Careers go off the rails when you move from core to pheriphery.
What you really have is a culture problem. You will have to change the culture of your organization. It has to be "product-manager ready." How reliable is your estimation process? What does your requirements processes look like? What do you think the product manager does? Who will the product manager report to? Do you have project managers? Program managers? A minimal marketable feature portfolilo? A customer portfolio? Does sales separate their hunters from their farmers? Does your company capture its increasing return? Some don't. Many don't. Do you have a VP of Marketing, or does Sales totally hate that idea? Are you in a market where professional services are relevant? I know you have professional services, but they are relevant to a particular market and not subsequent ones. Sales alone might work until late market, commoditization, or recession, then it gets bleak.
Do you have a replacement for yourself ready to take your job? Are you ready to give up that staff menality and move to a line job. Or, if you already see yourself as being in a line job, are you ready to give up authority and get things done without it. Hopefully, you already have influence, but how much of that influence with staff is just due to your job title? How reactive are you right now?
The way to become a product manager is like anything else, read everything, joing organizations, go out and meet other product managers, take a certification if you believe is such things, and then just do it. It will mean seeing things other than code as being important. Some product managers manage the bug list, the backlog, this, that, and the other, still, never grasping the scope of the job. Everything that touches the offer is part of your job. That includes the mundate shipping, AP, and AR. That includes marketing that doesn't generate sales leads. That includes all customer communications. It's a big job, and you have no power, execept the power you earn through enablement. You'll have to make decisions without running to the CEO, because the question needs to be answered now, not next week. If you've always asked permission, hopefully, that isn't the case, stop that. Get forgiveness, just get it done. I don't know what your organization is like. I don't know where the problems will arise for the product manager. They will arise. They probably already have, because if you've been out pushing for it, you're defining it, without knowing what it is. Fun.
Just dive in. Let go. Don't keep doing the same thing you've done.
Why on earth take a job that pays less and will be a commodity soon? There comes a point where you are overqualified to be a product manager. You are probably beyond that point right now. If by dev manager, you don't mean dev exec, then ok. Maybe you can do the work without taking on the job title, but the conflict between line, staff, authority, and influence will get blurred.
The product manager won't solve the problems inherent in the structure of your organization. a product manager is usually hired, because the CEO wants to shead that responsibility.
Permalink Reply by allan kelly on February 11, 2009 at 12:03pm
Permalink Reply by Michael House on February 11, 2009 at 6:47pm
Permalink Reply by Adriana Iordan on March 4, 2009 at 8:29am
Permalink Reply by Ben Johnson on September 3, 2009 at 12:48am
© 2012 Created by Neil Davidson.
Powered by
.