One of the questions I often encounter as a delivery manager is how to balance speed and stability, especially when we’re under pressure from tight deadlines. However, I would argue that there’s a fundamental issue with the premise of this question: why are we under such tight deadlines in the first place? More often than not, these deadlines exist because stakeholders lack confidence in our ability to meet them. This is the absurdity of deadlines.
Let’s consider the nature of deadlines. Some deadlines are imposed by external factors, such as regulatory requirements. For instance, if a government introduces a new regulation that our software must comply with, we might face a deadline that seems absolute. However, even in these situations, we have options. We can choose to pay the fines for non-compliance rather than rush to deliver a feature that may not be ready.
Here are a few key points to consider:
-
Assess the Real Cost: What is the cost of building a feature quickly? What are the implications of pushing for speed? If we rush, we risk tripping over ourselves, leading to a product that could damage our brand and erode customer trust.
-
Quality Over Speed: It’s crucial to deliver features with the right capabilities and quality. Shipping a poor-quality product can have long-term repercussions that far outweigh any short-term gains from meeting a deadline.
-
The Fine Dilemma: While paying fines may seem undesirable, it’s often a more viable option than delivering a subpar product. The fines are typically much smaller than the potential costs associated with a failed product launch.
Reflecting on my experiences, I recall the case of Zoom during the pandemic. As their user base skyrocketed, they faced a critical decision: cap the number of users or scale up their infrastructure. They opted for the latter, prioritising user growth over quality. This led to significant compromises, including the disabling of encryption features, which had been a key selling point.
This decision had dire consequences. Many organisations still block Zoom due to concerns over security and trust. It’s a stark reminder that reducing quality to ship features faster can backfire spectacularly.
So, how do we strike a balance between speed and stability?
-
Prioritise Stability: Stability is paramount. It’s far more important than speed. If you find yourself in a situation where you must choose, always opt for stability and quality.
-
Make Ethical Choices: Avoid the temptation to cut corners. The easier, cheaper path may lead to ethical dilemmas that can tarnish your brand and reputation.
-
Communicate with Stakeholders: Educate your stakeholders about the implications of rushing projects. Help them understand that quality work takes time and that the long-term benefits of a stable product far outweigh the short-term gains of speed.
In conclusion, while the pressure to deliver quickly can be overwhelming, we must remember that the foundation of a successful product is built on stability and quality. If it means paying a fine or missing a deadline, so be it. Let’s commit to doing things well and properly, ensuring that we maintain the trust of our customers and the integrity of our brand.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Navigating the Unpredictability of Software Development: Embrace Agile for Success
Explores how Agile principles, technical leadership, and engineering excellence help teams manage unpredictability, adapt to change, and …
Navigating Technical Debt: How to Transform Challenges into Opportunities for Quality and Efficiency
Explains how managing technical debt and distinguishing it from poor quality can boost product efficiency, reduce costs, and support …
Maximising Deployment Frequency: The Key to Faster Time to Market and Business Success
Explores how increasing deployment frequency, stable environments, and fast feedback loops improve software delivery, reduce time to market, …
Transforming Agility: How Azure DevOps Went from Two-Year Releases to 880,000 Deployments
Explores how Azure DevOps shifted from slow, two-year releases to rapid, continuous delivery, highlighting the benefits of fast feedback, …
The Power of Technical Excellence in Agile Development
Explores how technical excellence in Agile development reduces risk, prevents technical debt, and boosts product quality and delivery speed …
Why compromising on software quality is a leadership decision
Compromising software quality is a leadership choice, not a team one. Lowering standards carries business risks that should be openly …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Detecting agile theatre with real delivery signals
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …