TLDR
Software architect competence measured across three dimensions: Duties (what architects do—creating, evaluating, documenting architecture), Skills (how they work—communication, leadership, systems thinking), and Knowledge (what they know—patterns, technology landscape, domain). Architects need breadth in knowledge, depth in communication skills, with duties distributed across organization.
Core Idea
Software architect competence cannot be measured by a single dimension. Instead, it integrates three interdependent areas: the Duties an architect performs, the Skills they employ, and the Knowledge they possess.
The Three Dimensions
Dimension 1: Duties (What Architects Do)
The specific responsibilities architects own across the full architecture lifecycle:
- Architecting: Design or select an architecture; partition systems into components; identify patterns and tactics; evaluate prototypes
- Evaluating: Assess architecture against quality attributes (performance, security, availability); identify risks; lead architecture reviews
- Documenting: Create ADRs and architecture views; communicate decisions to different stakeholder audiences
- Managing: Coordinate architecture definition and review processes; work across teams and with project management
- Advising: Mentor developers in architectural thinking; guide technology choices and design discussions
Duties expand with seniority — from contributing to specific decisions early in a career to setting technical direction organization-wide at the principal level.
Dimension 2: Skills (How Architects Work)
The competencies architects employ to execute their duties effectively:
- Communication: Oral, written, and visual — the single highest-ROI skill for architects
- Leadership: Influence without authority, decision-making, conflict resolution
- Systems thinking: Big-picture perspective, trade-off analysis, translating between technical and business language
- Facilitation and negotiation: Building consensus across competing requirements and stakeholders
- Business awareness: Understanding cost implications, time-to-market pressures, and organizational structure
Depth vs breadth in skills: Communication demands deep mastery; leadership and collaboration require breadth across many contexts.
Dimension 3: Knowledge (What Architects Know)
The information architects must command to make sound decisions:
- Architecture patterns and styles: Monolithic, microservices, event-driven, and their trade-offs
- Quality attributes and tactics: How to achieve performance, security, availability at the design level
- Technology landscape: Breadth across languages, frameworks, cloud platforms, data technologies, and DevOps approaches
- Domain knowledge: Industry context, business processes, regulatory constraints, user needs
- Organizational knowledge: How decisions get made, historical context, team capabilities
Breadth vs depth in knowledge: Breadth is critical across the technology landscape; selective depth (2-3 areas) reflects organizational priorities.
How the Dimensions Relate
The three dimensions are interdependent — strength in one can partially compensate for gaps in another, but sustained excellence requires all three:
- High knowledge with weak communication skills: Brilliant ideas that cannot land
- Strong communication with shallow technical knowledge: Influence without sound judgment
- Broad duties with skills gaps: Ownership without execution quality
The most common high-ROI investment for architects is communication skills — it is the lever that makes knowledge and duties visible and persuasive.
Related Concepts
- Technical Breadth vs Depth - Knowledge breadth and selective depth
- T-Shaped Skills - Deep skills + broad knowledge model
- Learning Agility - Fluid and crystallized intelligence types
- Architect as Facilitator - Skills application in practice
Sources
Primary References:
-
Bass, Len, Paul Clements, and Rick Kazman (2021). Software Architecture in Practice (4th Edition). Addison-Wesley.
- Chapter 25: “Architecture Competence”
- Duties, skills, and knowledge framework
- Competence assessment models
- ISBN: 978-0136886099
- Available: https://www.oreilly.com/library/view/software-architecture-in/9780136885979/
-
Software Engineering Institute (SEI), Carnegie Mellon University (2014). “A Competency Model for Software Architects.”
- CMU/SEI technical report
- Formal competence evaluation framework
- Duties-Skills-Knowledge taxonomy
- Available: https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=9337
Architecture Skills:
-
Richards, Mark and Neal Ford (2020). Fundamentals of Software Architecture: An Engineering Approach. O’Reilly Media.
- Chapter 2: “Architectural Thinking”
- Chapter 22: “Making Teams Effective”
- Chapter 23: “Negotiation and Leadership Skills”
- ISBN: 978-1-492-04345-4
-
Ford, Neal, Rebecca Parsons, Patrick Kua, and Pramod Sadalage (2021). Building Evolutionary Architectures (2nd Edition). O’Reilly Media.
- Architect roles and responsibilities
- Skills for evolutionary thinking
- ISBN: 978-1492097549
Communication and Leadership:
-
Patterson, Kerry, Joseph Grenny, Ron McMillan, and Al Switzler (2011). Crucial Conversations: Tools for Talking When Stakes Are High (2nd Edition). McGraw-Hill.
- Communication skills for architects
- Handling difficult conversations
- ISBN: 978-0071771320
-
Maxwell, John C. (2007). The 21 Irrefutable Laws of Leadership. Thomas Nelson.
- Leadership principles applicable to architects
- Influence without authority
- ISBN: 978-0785288374
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.