If you’re not rethinking how your business model and company could be disrupted and made better by software products, you’re not truly doing a product “transformation”.
Over the past 7 years I’ve worked with many large enterprises which are what I call “software enabled”. That means they don’t primarily sell software for revenue.
Banks, insurance companies, pharmaceutical companies, manufacturers, etc. /2
These companies typically were run on a traditional IT approach - the business tells tech what tools they need, and tech builds them. Tech is a Dev shop, a services org. Not strategic but reactive. /3
Flash forward 20 years and they usually have thousands of tools, no insights into how they have been used, and a massive amount of tech debt.
So they decide to “transform”. They start to adopt #agile teams, restructure, and create the product role. This is where I come in. /4
When I work with leadership to understand the outcomes of the product transformation I hear:
- streamline our products
- stop being reactive
- Lower cost of ownership
- better prioritization
Everything is cost related because IT is seen as a cost center. /5
So I ask them “if you really want to transform, how is this transformation going to disrupt your business?”
They’ll look confused. But we’re just making a new product portfolio? We’re streamlining. We are making things better for our business customers. /6
While that’s a fine way to optimize your tech teams, it’s not a true transformation.
The reason older enterprises get disrupted is because they don’t see software as a strategic lever to further or disrupt their business model. /7
They want to be more strategic with their software, but they are worried. “We can’t just stop serving our business needs to build something radically different!” No one said you had to, hence a portfolio approach to building horizon 1-3 products. /8
But usually the problem is no one in leadership saw this as a true transformation. They claim they want the product teams to be strategic but there is usually no clear strategy anywhere, not even at the business, that software could align to. /9
And the software leaders and teams are worried that no one in the org will get behind the idea of these teams changing into a strategic player because that means saying no to some requests from the business. /10
So here’s my advice, so you at least level set before you get into planning on how to build #prodmgmt teams.
Ask yourself if you are transforming or streamlining. Is our goal to lower costs or transform our business? /11
There’s a very different approach to each of those. And very different outcomes.
One will give you cost savings, the other will help defend against competitors and grow your business.
Knowing where we are all going is key to undertaking any big product transformation. /end
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Here’s my current saga with @HomeDepot and a story about their technology that is completely broken.
I returned $1000 worth of brick I bought online to the store. It said I could. The store accepted it but had to call homedepot.com to process the return. /1
This is an issue I run into all the time at @HomeDepot. They can never return the things I bought online without help but they still tell you to return to any store. So they accept the return, I leave. Here’s a pic of it sitting in the store. /2
I call to make sure it got processed when I leave, and they said yeah everything fine.
I get a call a week later from their shipping company trying to schedule to have it picked up. I tell them it’s at the store they can’t. They said they’ll cancel the pickup.
Calling your Product Managers something else may solve some issues in the short term, but it's just going to prevent you from hiring great people in the long term.
Anyone who says titles are not important is either trying to screw over someone or in a very privileged position.
Salary bands are determined by seniority. Salary bands are determined by job titles and positions.
This is from @BuiltInNewYork but I don't necessarily agree with these, just pointing out discrepancies in title.
Director of Product vs VP of Product salaries are HUGE differences.
If you do have a bit of experience in PM or someone to learn from there, I think startups are great. I had an opportunity to be employee 40ish at OpenSky or go to Amazon. I would have made a lot of money if I went to Amazon. My career would have never been the same.
Also I know there’s privilege in these choices, and I’ll say this- if you can negotiate a pay that’s comfortable, I’d recommend a startup. I had to do this to pass on Amazon (OS matched their base). I lost out on stock, but 10 years later my career has more than made up for it.
When things are broken, it gives companies an opportunity to solve the problem and exploit it for value. That's what Robinhood's doing. It's SMART. You find a problem, you solve it. Good business.
But we have to be careful not to exploit our customers as well. /2
When you specifically target unsavvy customers in a complex industry, the burden of education falls on you.
The risk to keep your customers safe falls on you.
I don't know of a single Chief Product Officer who has a PhD. What is this trash advice, Cleverism?
Also, make sure you brush up on those Microsoft PPT skills if you want to be a CPO! You know, because that's SUCH a good investment in your time, and it's not like you could hire someone to help there.
Let's go back to 2005 and break out the Fireworks, shall we? That will REALLY get the board to invest in our roadmap.