10y
Thank you for posting about the positives you’ve experienced at GoDaddy and for calling out the need to balance launching new features while investing in the underlying architecture and infrastructure to be able maintain and improve those products over time.
As a senior leader in our product organization, I ask the engineering teams to plan out investments in the platform, e.g., set aside sprints to move to the latest version of Ruby, build a service that can be reused by others instead of a quick fix, and to work with their product management peers to build roadmaps that include both new features and code base health. That balance is hard to achieve and needs constant attention to stay centered.
A great example of that balanced roadmap would be Workspace email where the team has worked almost exclusively the past three years on the underlying code, networking, database and storage capabilities to improve reliability and performance for our millions of customers. We also have been shutting down older products and migrating customers to newer versions to lessen the load of legacy products and improve the customer experience.
I’d ask that if you see decisions that don't balance current and future needs well to please ping me (steven@godaddy.com) so we can talk about it and decide what to do differently.
