Product Managers & Innovation

This content is syndicated from Tyner Blain by Scott Sehlhorst. To view the original post in full, click here.

Thanks everyone for the great conversation in the most recent #prodmgmttalk chat session!  This week, Roger Cauvin inspired us to think about product managers as innovators – or enablers of innovation.  Each week, I find myself thinking about at least one of the #prodmgmttalk questions long after the hour is over.  This week’s thought – organizations prevent product managers from innovating.

Innovation and Product Management

What a great topic.  I’ve never met a product manager with a goal of solving valuable problems who didn’t aspire to creating innovative products.  Maybe you’re out there – say howdy if you are.  Roger’s topics, Cindy and Adrienne’s moderation, and the great community that is forming around the weekly #prodmgmttalk chats created a great hour of thought provoking discussion (brainmates’ summary;  full transcript).

Before diving into how organizations prevent product managers from innovating, I want to frame the discussion around a particular definition of innovation.

While there were several different definitions of innovation proposed during the session, I’m partial to one that I articulated during an  Accept 360 webinar last year on Innovation and Transparency (videoslides).

From the presentation on Innovation and Transparency:

Innovation = Valuable Invention

Putting it visually:

For a product manager – the focus is on discovering the value.

Roger has a great perspective on this product-management-centric view of innovation:

True innovation comes from understanding the problem in solution-neutral terms. So Product Management first attempts to understand the problem thoroughly & communicate it to designers. By framing the problem clearly, Product Management enables designers to unleash their creativity & skills. Peter Drucker speaks of “purposeful”, systematic innovation. Product Management is a big part of systematising innovation.

Roger Cauvin via Brainmates

However, innovation is not just about solving valuable problems (that’s just good product management) – and does not have to start “market first.”  Innovation can also come from discovering applications of novel technology – invention.

A researcher discovers an adhesive that is not strong enough for tape – but can be used over and over – and we have sticky-notes.  Another scientist accidentally leaves a chemical mixture in a beaker overnight and tada! – bullet-proof glass.  This is the view of innovation that seems most pervasive in the collective consciousness – someone invents some awesome thing and then finds a good use for it.

You can have a sequence that works either way – discovering market applications for a new technology, or inventing solutions that address market problems.  Innovation is what you get when you do both.

Another fun example to think about – the light bulb.  Did Mr. Edison start with a market problem (candles are not a good solution to “see stuff at night”) and end up with a light bulb?  Or did he start with an invention (distributable electricity as a service), and try and “invent” a market use?  I never met the guy :), but my hunch is the latter.

The problem is that product managers aren’t inventors looking for market opportunities.  We don’t create hammers and run around looking for nails (or things to hang up).  We engage our market, discover that bare walls are a problem (and people are willing to pay to solve it); then we work with our teams to find ways to hang pictures.

Common Organizational Approach to Innovation

I’ve worked both for and with several companies – large and small – that take this inside-out approach to developing innovative products.  Google is famously known for their “twenty percent time” – which gave us GMail and Google News.  Microsoft now has a policy where employees get to keep the intellectual property (and a share of the revenue) from their side projects.  Inventor-inspired (or developer-driven) projects are more likely to create something novel, and less likely to create something valuable.

As a related anecdotal data point – what percentage of start-ups actually succeed in the market?  I bet there are hundreds or thousands of failed start-ups for every winner.  Most small businesses close their doors in less than five years.  However, that stat includes all businesses, as this great discussion on Quora highlights.  Still – even those statistics reflect business failures, not product failures.  Most businesses have a failed product or two (or two hundred) in their past.  Even Facebook’s first “product” failed, before Mr. Zuckerberg created The Facebook.

Back to organizations.

In the crazy stream of conversation, the following caught my eye:

Whether Product Managers are innovators or innovation enablers depends on the organisation & size of your group. Additionally some orgs have a Product Planning role which precedes Product Managers, moving them to an innovation enabler role.

Rich Velazquez via Brainmates

Yup. Seen that a lot. Don’t care for it.  I think it is dysfunctional to decide what products to create / problems to solve without product management.

That neuters your product managers – making them order takers – and they lose the ability to birth innovative products, left to only participate as midwives in the process.

Bill Bliss wrote an article with great visuals describing the product planning process, (check it out) where he shows how the flow from “vision and mission” breaks down before it gets to products.  He highlights that responsibility shifts from one group to another, and that the process typically breaks during that translation of goals into products (he says ‘projects’).  He references a great article from the Silicon Valley Product Group on establishing a product council that assures product management participation (among other things) in that key “decide where to invest” step.

When product managers don’t participate in the planning process, we don’t have strategic relevance, and we aren’t innovators – we’re order takers.

Call to Action

If you’re in an order taker role with a product manager title, your goal should be to inject yourself into the decision making process.  The specific steps you need to take depend on your specific circumstances.  The skills you need are the ones you already have – story-telling, inspiration, leadership-without-authority, stakeholder management, executive communication.

OK.  So – go do it.

ps: If you weren’t here (at Tyner Blain) in 2006, go read these Top Ten Tips for Preventing Innovation.  Another tip would now be “prevent product managers from deciding where to innovate.”

Post to Twitter Post to Facebook

Leave a Reply

What is 2 + 7 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”