In B2B #prodmgmt, you're going to come across industry/subject-matter experts. These are people with deep industry knowledge and sometimes get a bad rap from PMs but they can be super helpful, especially in complex industries. Let's dive in
1/6
1. The Potential Disruptor
They have product chops and maybe built a product in this industry before, so they know where the pitfalls are, broadly what can & can't be done, and are the most likely to help the product team build something disruptive and new. 2/6
2. The Essential Informer
They know the industry inside and out, but they've never built a product to speak of. They are the closest equivalent of your customers, but they aren't your customers. They can be super-insightful partners but beware of status quo bias. 3/6
3. The Customer Enquirer
The good old-fashioned generalist PM, who believes that good (hopefully continuous) discovery and a solid vision & strategy will see them through. Likely to have little status quo bias, but limited industry credibility & need help with the acronyms. 4/6
4. The Helpful Observer
Ones to watch - maybe they'll develop industry or product expertise. Meanwhile, they can help sense check you & make sure you're not doing anything quite obviously stupid. It's also true that good insight can come from anywhere. Don't ignore them. 5/6
I'm planning to write a more detailed blog post about industry experts with some hints & tips on how to best harness their wealth of experience and insight without becoming a project manager for their desires. Coming soon! 6/6
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I interviewed for VP Product at a place once & they asked me for my 30/60/90 day plan. I did my best "The First 90 Days" impression & talked it through. They were OK with it but said it sounded "a bit slower than they expected". And I started thinking about Lean Onboarding
1/7
My suspicion here is that 90 days is an incredibly long time in frantic startups and that spending e.g. 30 days getting to know your colleagues & reading documentation seems like a luxury that no one will be particularly keen to afford you
2/7
So then I start to think that this starts to sound a little like the dreaded waterfall. And, if we're being lean, we should consider some kind of a build/measure/learn cycle. We start with imperfect information and we get better as we go
3/7
I while ago I read the Phoenix Project by @RealGeneKim, which talks about the IT ops transformation of a failing traditional company. It was excellent.
I finally picked up the sequel, the Unicorn Project, about the developer side. It's also excellent!
Here are a few highlights:
1. Over time, organisations tend towards process control and compliance
This is desirable when you have a repeatable core business to defend, but can kill innovation & make it hard to keep up with the competition. When compliance is more important than results, you're in trouble
2. Technical debt is a choice but you have to pay some off
All systems tend towards tech debt as a sum of the compromises you make along the way. Some level of tech debt is OK but if you don't pay off the worst of it you'll spend all your time shovelling & no time innovating
Product leaders looked at the careers of failing product managers, where they spent their time, and tried to work out what the pattern was.
Where should they put more training budget?
What was missing?
The answer shocked them all (🧵)
One thought leader said they should invest more time in tech skills. Another said they needed to spend more time with users. Yet another said they needed better business acumen.
One brave junior thought leader dared to think different.. "there are no failed ones in the middle!"
Those who over-indexed on tech spent all their time focused inwards, talking to engineers, pretending to be competent analysts or that they understood how AI works. The engineers liked the attention but felt like they were just writing code for a frustrated former engineer
Chris Mason (@CM_IntelPeople) has been a product leadership recruiter for over 20 years & has seen some things in his time.
I chatted to him recently to see what's going on in hiring these days.
Here are 6 things people should know about the product job market:
1. The job market is weird right now. Economic factors & lay offs are part of it, but there's also been a stampede of people off on holiday for the first time in a couple of years.
The good news is that there are still plenty of opportunities out there!
2. Product has mainly moved from being an IT cost centre to a key strategic enabler for the business, with people hiring senior leaders to manage product. However, product practitioners sometimes still miss out due to the difference between being a practitioner & an executive
I was asked if I had a thread of my best product book recommendations. There are too many books to mention them all but here are some that I would recommend to anyone in & around product management. These will be obvious to many, but hopefully a helpful reference for some (🧵)
For those starting out, look no further than "Cracking the PM Interview" by @jackiebo and @gayle. A lot of focus on Big Tech interviews but also lots of actionable advice for how to prepare for that big job interview
If you want a general guide to product management principles from top to bottom, of course look no further than "Inspired" by @cagan - the White Album of product management books (make sure you get the 2nd edition!)