Prioritization - How to measure the value of technical improvements?
Evaluate technical refactoring to assess them fairly against product features.
It all starts with the company's product maturity. We'll use the company's size as a proxy.
Small Companies are looking for Product Market Fit. It's just not the right time. Focus on solving a valuable user problem as quickly as possible.
Medium to Large Companies want to avoid code freeze. They'll aim to spend a constant % of their time on platform stability.
Evaluate severity - Is it noticeable? Will it get worse if we don't do it now? And is it illegal?
Never stop delivery of impact. Try to deliver in small chunks and disperse them through time as much as possible. It’ll help to evaluate the impact of solutions more granularly.
Align with the company's goals - The company often dictates the percentage of time each team should spend on platform stability. Keep in mind the strategic priorities of the company when evaluating a bug.
🧠 A good framework to get this done: The Strangler Pattern dictates rewriting small parts of your codebase until you have strangled all your old codebase, and the team can remove it. This contrasts with rewriting a large, complex codebase with many different interactions resulting in a planning nightmare.
This question was answered on Coachgroup.co
Coachgroup.co is a community of Product Managers where members are matched in groups of 6 and meet monthly to discuss their challenges, share their learnings, and help each other evolve in their respective roles.