How to you handle the end of life (EOL) of libraries?
1 Answer
Twilio Staff Product Manager, SDKs and Libraries • February 11
In the past I've worked on new library launches, major upgrades, and I'm actually in the process of an end of life (EOL) effort right now. While these types of efforts have their own nuances, the core principles remain the same.
- Transparency - When working on developer tools you have to maintain the highest level of transparency possible. Systems, developer workflows, and customer data can all be dependent on these tools and their interfaces.
- Communication - The way and the cadence that you distribute information about changes to libraries or tools goes hand in hand with transparency. You need to ensure that you are giving your end users enough time to adjust/migrate, test, and be confident in using the next version or tool in a production environment.
- Cross Functional Teamwork - Assembling a group of team members from across the organization will ensure that you are considering the customer/developer experience as well as any edge cases. Working with a team like this enables you to be really thoughtful about what to communicate (transparency), and when and where to share it (communication). I like to keep a group like this going even after a launch or major change for a little while so that you can hear feedback and areas to improve.
1216 Views
Top Product Management Mentors
Tanguy Crusson
Atlassian Head of Product, Jira Product Discovery
Laurent Gibert
Unity Director of Product Management
Farheen Noorie
Grammarly Monetization Lead, Product
Deepak Mukunthu
Salesforce Senior Director of Product, Generative AI Platform (Einstein GPT)
Mike Flouton
GitLab VP, Product
Paresh Vakhariya
Atlassian Director of Product Management (Confluence)
Tara Wellington
BILL Senior Director of Product Management
JJ Miclat
Zendesk Director of Product Management
Natalia Baryshnikova
Atlassian Head of Product, Enterprise Strategy and Planning
Reid Butler
Cisco Director of Product Management
Related Questions
One thing we've always struggled with ongoing communication about the success of previous launches. Do you have a framework for revisiting and communicating out things like "hey here's how that thing we launched 3, 6, 12 months ago is performing"?What do you report on to build early internal confidence with the product strategy? And how often do you report on this?How do you coordinate and work cross functionally with the product marketing team to create commonly shared KPIs?How do you think about shared KPI’s with your engineering team? And what are ones that product teams often miss?Have you leveraged Gen AI to communicate and report on things internally to stakeholders? What has been the most valuable artifact that AI has helped you create?How do you define and set SLAs with engineers?