LinkedIn asked, "You're facing a software crisis. How do you decide between fixing critical bugs and developing new features?"

The answer is - It depends!

While new features drive innovation and revenue, critical bugs can erode trust and operational stability.

Striking the right balance is key and I try to do that by setting clear prioritisation criteria UPFRONT and agreeing it as part of the process going forwards, so decisions are easy, consistent, and only edge cases need escalation.

Our approach:

1. User & Business Impact First – If a bug affects core functionality, security, or revenue-generating processes, fixing it is non-negotiable. Otherwise, weigh it against new features based on overall impact.  

2. Strategic Alignment – Does the feature unlock growth, efficiency, or a competitive edge? If so, it may take priority - provided no high-severity issues are in play. Some companies value this more than resource constraints, so weighting must adjust accordingly.

3. Resource & Timeline Constraints – Sometimes, it's about feasibility. If fixing a critical issue takes two weeks but a feature delivers more value at the same time, I might opt for a phased approach: mitigate the bug immediately while progressing the feature.  

4. Customer & Team Balance – Listening to both customers and internal teams helps navigate trade-offs. A well-communicated roadmap ensures prioritization decisions make sense to all stakeholders.  

5. Make it Visual & Actionable – A RAG (Red-Amber-Green) system helps with quick triage, but I adjust weighting based on key factors like external dependencies, compliance risks, or revenue impact.  

6. Minimize Stakeholder Fatigue – Most stakeholders don’t want to be pulled into every decision. A transparent system keeps things moving while ensuring alignment.  

The main thing to remember - this is not a rigid formula. It’s a framework that evolves with the business. What matters most today may not tomorrow. And no, "because the boss wants it" isn’t a valid weighting factor!

At the end of the day, stability enables innovation, but innovation drives growth - and having the right framework makes the right choice obvious, balancing stability and innovation without it being onerous and contentious!