The Cost of Being Too Correct
Stijn Vannieuwenhuyse explores how contesting requirements can lead not only to simpler, cheaper, and more maintainable software, but also better business outcomes.
In software development, we spend a lot of time making sure business rules are implemented correctly. But do we spend enough time questioning whether those rules really need to be enforced so strictly in the first place?
Every additional business rule, edge case, or hard constraint potentially increases the complexity and cost of building, testing, and maintaining software. And stricter rules don’t necessarily lead to better outcomes for the business.
Mandatory fields don’t guarantee better data quality, rigid processes encourage workarounds and shadow IT, and rare edge cases are sometimes fully automated when a human could handle them much more easily.
We all too often introduce unnecessary complexity into software by trying to control every aspect of the business. A pragmatic solution that covers 90% of situations might require only a fraction of the effort. The remaining cases could be handled differently, left to human judgment, or simply accepted as occasional exceptions.
This also connects strongly to Domain-Driven Design. Developers shouldn’t just translate detailed requirements into code. They need to understand the underlying business intent. When developers understand what the business is actually trying to achieve, they can make better trade-offs between complexity, cost, risk, and business value.
As those responsible for designing business software, we should be less prescriptive about exactly how software should behave, and collaborate more closely on what we’re trying to achieve. Not every business rule needs to become a hard invariant, and not every edge case deserves an automated solution.
In this session, I’ll illustrate this with relatable, real-world examples, based on my experiences as a trainer and coach at Aardling. Together we will explore how contesting requirements can lead not only to simpler, cheaper, and more maintainable software, but also better business outcomes.
Key takeaways:
Why stricter business rules don’t automatically lead to better data, processes, or business outcomes
How to recognise when a requirement adds more complexity and cost than value
When a pragmatic solution for the 90% case beats full automation, and how to handle the rest through human judgment or accepted exceptions
How understanding the business intent behind a requirement helps developers make better trade-offs between complexity, cost, risk, and value
How to tell which rules really need to be hard invariants and which can be softer
Practical ways to challenge requirements together with stakeholders, so you get simpler, cheaper, and more maintainable software
When and How?
December 8, 12.30 - 13.30 CET