Frederick Van Brabant argues for a return to opinionated architecture in enterprise design, criticizing the prevalent ambiguity in the field. He highlights a conversation with a reader who questioned the common architectural phrase “it depends,” which often serves as a way for architects to evade responsibility or commitment. This mindset leads to convoluted designs that prioritize backup plans over clarity. Van Brabant emphasizes that while it’s important to have options, excessive flexibility can result in increased costs and maintenance burdens without tangible benefits. Van Brabant draws from his experience as a developer, expressing a preference for frameworks that offer clear, supported pathways instead of multiple options that complicate understanding and implementation. He contrasts opinionated architecture with unopinionated setups, which can create a confusing array of choices. He warns that building in too many contingencies not only complicates development but can also lead to waste if those plans are never executed. Rather than preparing for every possible scenario, he advocates for focusing on what is currently needed and adapting later. He also critiques the notion that software can easily be swapped out or replaced, pointing out that while technology may allow for flexibility, organizations often struggle with the training and changes required to accommodate new systems. Van Brabant urges architects to select a clear path and stick to it, arguing that businesses primarily care about functionality and timely delivery, not elaborate contingency plans. By making decisive architectural choices, organizations can streamline their operations and reduce unnecessary complexities.