grandvoye
My narrow advice would be to make a list of 20 questions you’d like to ask someone. Then reach out to people on LinkedIn you think could give you good answers and ask them if you could pick their brain for 30 minutes. Then ask those questions and say thank you a lot.
The one time we were top post it was 30k visits that day. Thousands the next. Then hundreds the following. Almost 500 points.
It’s a great feeling when it happens. Community comments are super insightful and thought provoking as well.
SEC Chief Warns ‘Clock Is Ticking’ on Delisting Chinese Stocks
America Failed in Afghanistan
The New York Times Doubles Down on Subscription Newsletters
Inflation Is Here – These 35 Metrics Tell You How Much to Worry
I think that there's sometimes a tendency to overthink management topics - there's no need to overthink this one.
My co-author and I use Markdown and Git as the author suggests, and one of the best things is that between simple CI/CD pipelines and effortless scaling of a static site, we don't need to do any technical work so there's no friction on my lifestyle. We've been writing for almost a year now, 4+ posts a month, and 99% of that "work" has just been writing.
Writing with a partner helps a ton as well.
(sorry for being somewhat vague but I try to keep this account anonymous!)
It's simply too much for our engineers to spend time deeply understanding every nuance of our business ("how should we make this product tradeoff between the needs of SMBs in Asia vs. the needs of our largest 10 customers across all countries? How will this then impact our pricing strategy?"). But PMs have more context here, because in exchange they don't (for example) know every nuance of how our data pipeline works.
In terms of how we make it work, we 1. try really, really hard to align incentives between Eng/PM so that they win together, 2. make sure that teams work together closely and have time to bond, and 3. write things down in planning docs as much as possible, as that's one of the best ways to reduce conflict and also fully leverage non-overlapping expertise.
"the PM's business expertise has usually been strictly less than the most experienced engineer on the team, leading to a typically never-ending, and eventually abandoned game of catch-up."
That's rough... those don't sound like good PMs to me fwiw.
What I have seen are cases where very senior engineers have a better grasp of the overall product vision than some PMs, due to experience and tenure. But they usually don't have more expertise in all of the business questions simply due to relative lack of time spent in that domain.
***
All of this isn't to say that engineers don't need to know about the business, or that it isn't a huge advantage if they do (it is). Just that there are so many hours in the day and eventually you've gotta get some division of labor.
I agree that PMs are largely overhead in the early days of a company, provided that you have strong product-minded engineers/designers.
(Also just my 2c from heading a PM department / being a former engineer)
- You are thought of as a leader - You get to invest in better companies because they know/want you - The better companies outperform, because they were better - You are increasingly thought of as a leader - You get to invest in better companies... etc.
The marketing angle is increasingly a way to get onto (and sustain your place on) this carousel.
I feel for the teams that will need to compete against them as they enter new markets, although I expect that their forays will fail at a fairly high rate (as most product line expansions do).
The standard trend in enterprise software is towards oligopoly, with a few strong incumbents that struggle to actually kill one another as their products converge over time. Most enterprise businesses focus primarily on sales/marketing as they grow, rather than doubling down on a product that can kill incumbents. The fact that Figma has done both is really impressive and as an enterprise product head definitely something that I admire.