I mean, shouldn’t the bugs be kept closer to what they’re concerned with? Why not JIRA, Azure DevOps, GitHub Issues, etc.? I assume the code repo has some supplementary bug tracking feature.
Their “swears by it” just sounds like laziness or perhaps a poor UX in the existing tool. Either way, working in an Excel just sounds like unnecessary decoupling and a higher barrier to work with.
But also, it could just be a garbage PM. I’ve met tons of product folk that are in it just for the money and can’t ACTUALLY manage a team or product.
Comments
I mean, shouldn’t the bugs be kept closer to what they’re concerned with? Why not JIRA, Azure DevOps, GitHub Issues, etc.? I assume the code repo has some supplementary bug tracking feature.
Their “swears by it” just sounds like laziness or perhaps a poor UX in the existing tool. Either way, working in an Excel just sounds like unnecessary decoupling and a higher barrier to work with.
But also, it could just be a garbage PM. I’ve met tons of product folk that are in it just for the money and can’t ACTUALLY manage a team or product.