- The Product in Public Newsletter
- Posts
- The Product in Public movement
The Product in Public movement
Get a real-time, inside look at how top founders and product managers build products.
A lot of product managers come to the profession in an almost accidental way. I’ve heard story after story of people in different roles who became product managers. Some come from a business analyst or developer background to product management. However, plenty of people end up in product management because they showed the aptitude for the role or they fell into it because no one else on the team could do the job. Others come from completely, seemingly unrelated industries.
I’m one of those who fell into product management from a completely different profession.
I had spent 20+ years in the banking industry, climbing the corporate ladder as high as Chief Lending Officer. I was even told I had a shot at being a bank CEO. But, I decided to change career tracks and went to work doing strategy at a software company that provides banks and credit unions with the solutions they need to run their businesses. Eight months into that role, I was asked to put my lending experience to use as a product manager.
I didn’t even know what a product manager was. The closest thing to being a product manager that I had been was as the founder of three different startups. But I had never heard the term before. Fast forward to today, with about seven years of product experience, and I lead the product team that is managing the largest product build in our company’s 45+ year history.
My product management career has been a wild ride full of ups and downs and plenty of lessons learned. I’m learning new things every week. Sometimes daily. Plenty of those lessons have been about what not to do. Some have been what you should do in a given situation. For example, having one person that can demo a new product. That was a miss on my part. On the flip side, I’ve had success with the early phases of the Product Development Life Cycle (PDLC). Particularly with the ideation and validation phases of new product development.
Why Product in Public?
The newsletter's name mirrors the “Build in Public” software development movement. That concept involves sharing stories about products and services while they are being developed to inspire others. It has been fascinating to follow the growth of freelance developers as they build out new products. Many build-in-public developers are transparent enough to share their struggles and successes. You can find them on social media sites such as Twitter using the #buildinpublic hashtag. I often find myself rooting for them.
Being public about what the product management profession is all about is exactly why I started this newsletter. Because I know the power in learning from each other and how that will lead to better products for us all.
Many product management professionals start sharing their experiences after being in the industry for some time. They usually speak from influential roles such as Head of Product or as someone who worked in product management at a high-profile company (think Airbnb, Facebook, Google, etc.) and is now a product management consultant.
Without a doubt, their experience comes in handy when advising newer product managers on how to work through a certain challenge.
Still, I’ve always felt it would be more helpful to hear how other product managers do their jobs. To follow along as they make decisions in real-time. What processes do they use, or what tools do they leverage? Not hearing about it all years later, when victory has been declared.
I wanted to give other product managers, whether they are newer to product management than me or more experienced than I am, the chance to learn from my experiences while I am going through them.
What to expect?
The world doesn’t need yet another newsletter with a self-proclaimed expert telling you how to get where they are today. I don’t know about you, but the content I enjoy the most is content from people who are close to my experience level but have something interesting to share.
Not only will I share my experiences along the way, but I also plan to pull in other founders and product managers that can share the things they are learning or even big questions they have that we can all ideate on.
I plan to drop new content at least once a week. I’m going to start by publishing on Mondays.
I write often and once pumped out a 46,000-word book in under 90 days. But I don’t have any preconceived requirements about the length of each edition. My goal is to write however much it takes to make reading the information worth your time. If that means it takes 200 words or 2,000 words, so be it.
Wrapping up
Thanks for taking a moment to drop in. I truly hope that the information shared here is different and worth your time as a reader.
I’m always open to your feedback and suggestions and connecting with new people. So stop in over at Twitter and say hello.
Also, I’d be honored if you subscribed to this newsletter. Just click the button below to get started.