Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
I had the opportunity to talk to Aurelio Garcia-Ribeyro, Senior Director of Product Management at Oracle.
Two years ago I wrote an article about the concerns with Java. These included: quality, release cadence and fatigue, taking security seriously, Oracle's role as a steward of Java, and progress relative to other languages. I began the conversation by asking Aurelio about these issues.
The video for the talk I gave at the 2018 API Conference is now available.
I have talked about this a bit before, as well as shared the slides, but one of my main takeaways is that we are all (mostly) in the business of building products on a daily basis, whether we are coding or writing docs, tests, change requests, specifications, or designs. There is almost always an end product of our work, and the product decisions we make while building it has a direct impact on the end-users (people will have to read/amend your code, read your specifications, translate your designs, consume your APIs, etc.). With that in mind, it seems sensible that we look at what lessons we can take from the discipline of Product Management to help us make smart decisions in our day-to-day lives.
In the last blog, we talked about working in the model where you are a product manager working on a single product that has multiple teams. Now, it's time to up the ante and look at the case where you are a single product leader who is responsible for many products being worked on by many teams.
First off, congratulations! You have officially made it to the big time. You are a product line manager, a VP of Product Management, or maybe even the Chief Product Officer (CPO) for your company. Once you finish the bottle of champagne celebrating your promotion, buckle your seatbelt because some stuff is about to get real.