Core Idea
The Covering Your Assets anti-pattern occurs when architects make architecture decisions without documenting clear justification or rationale, preserving plausible deniability to deflect blame if decisions fail later.
What This Is
Definition: A defensive, risk-averse approach where architects prioritize personal protection over institutional knowledge — avoiding commitment so they can later claim “I never said that would work.”
How It Manifests:
- Presenting multiple options without recommending one, forcing stakeholders to choose
- Using vague language that can be interpreted multiple ways later
- Avoiding written decisions entirely, relying on verbal discussions that leave no trail
- Hedging every decision with disclaimers signalling they expect failure
Underlying Psychology: In organizations that punish failed decisions or where blame culture dominates, architects rationally protect themselves by avoiding definitive positions. The cost is steep: teams can’t learn from outcomes, new members can’t understand why systems are structured as they are, and decisions get repeatedly re-litigated.
Why It’s Insidious: Listing risks and alternatives seems responsible. But when done to avoid commitment rather than inform decisions, it paralyzes progress.
The Antidote: Architecture-Decision-Records (ADRs) that explicitly document the why:
- What problem the decision solved
- What alternatives were rejected and why
- What trade-offs were accepted
ADRs create accountability and institutional memory that prevents Groundhog Day scenarios.
Why This Matters
Without documented decision rationale, organizations lose institutional memory — new team members inherit systems they don’t understand, and the same architectural debates recur endlessly. The pattern also signals a deeper cultural problem: when architects feel they must avoid accountability rather than embrace learning from both successes and failures, the organization lacks psychological safety. Effective architecture requires making clear recommendations, documenting reasoning, and accepting that trade-offs mean no choice is perfect.
Related Concepts
- Architecture-Decision-Records — The primary mechanism for preventing this anti-pattern
- ADR-Format-and-Structure — How to properly document decision rationale
- Architecturally-Significant-Decisions — Which decisions require formal documentation
- Architecture-Decision-Anti-Patterns — Related dysfunctional decision-making patterns
- Groundhog-Day-Anti-Pattern — The consequence of undocumented decisions
- Email-Driven-Architecture-Anti-Pattern — Another decision documentation failure mode
- Architectural-Governance — How to enforce decision documentation practices
Sources
- Richards, Mark and Neal Ford (2020). Fundamentals of Software Architecture: An Engineering Approach. O’Reilly Media. ISBN: 978-1-492-04345-4.
- Chapter 19: Architecture Decisions
- Discussion of anti-patterns in architecture decision-making
- Available: https://www.oreilly.com/library/view/fundamentals-of-software/9781492043447/
Note
This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.