> Markdown version of [/videos/663-we-don-t-need-a-software-architect?t=662](https://www.wearedevelopers.com/videos/663-we-don-t-need-a-software-architect?t=662). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# We (don't) need a software architect!?!

Unplanned architecture leads to technical amnesia, not just messy code. Learn why your team desperately needs a hands-on architect to translate complex business requirements into sustainable software.

- **Speakers:** [Hendrik Lösch](https://www.wearedevelopers.com/@hendrik-losch)
- **Event:** World Congress 2023
- **Published:** September 21, 2023
- **Duration:** 24:52
- **URL:** https://www.wearedevelopers.com/videos/663-we-don-t-need-a-software-architect

## Summary

This presentation explores the critical role of software architects in bridging the communication gap between internal development teams and external stakeholders. Because software is inherently invisible, complex, and unconstrained by physical laws, external parties often misunderstand its changeability and constraints. The architect acts as a crucial translator, shaping requirements, designing initial structures, and ensuring implementations align with cross-functional goals. A significant insight shared is that effective architects must remain grounded in actual code—those who do not write or review code risk designing theoretical solutions that fail during real-world application.

A core theme of the discussion is the management of non-functional requirements using frameworks like the iso 25010 standard to define boundaries for functional suitability, security, and performance efficiency. For instance, in manufacturing environments involving cyber-physical systems without internet access, a monolithic architecture often outperforms cloud-based microservices by ensuring reliable, high-speed data processing. The speaker argues that unplanned architecture inevitably leads to technical debt, which is primarily caused by lost project context and forgotten requirements rather than poorly written code. To combat this amnesia, utilizing architecture decision records is highly recommended for capturing the context, choices, and consequences of long-term structural decisions.

Finally, the session delineates the lifecycle of software through phases of evolution, servicing, and phase-out, drawing a stark contrast between everyday refactoring and large-scale restructuring. While refactoring involves minor, continuous codebase improvements, restructuring acts as a major capital project requiring dedicated budgets, significant time, and strategic governance. Architecture is ultimately positioned as a multi-layered discipline encompassing business, data, application, and enterprise levels. Whether a team formally holds the title or not, someone must maintain overarching strategic oversight by blending the attributes of a lead developer, product owner, and test manager to keep the system sustainable.

**Keywords:** software architect role, stakeholder communication gap, non-functional requirements, iso 25010 standard, functional suitability, architecture decision records, technical debt root causes, software evolution lifecycle, legacy software restructuring, code refactoring limitations, cyber-physical systems, manufacturing software performance, monolithic vs microservices architecture, enterprise application architecture, technology stack homogeneity

## Chapters

1. **Bridging internal and external stakeholder perspectives** (00:04) — Aligning technical implementation details with business expectations prevents critical communication gaps in projects.
1. **Understanding the unique characteristics of software complexity** (02:13) — The invisible and highly changeable nature of software requires intentional architectural translation.
1. **Core responsibilities of a software architect in development** (04:24) — Defining requirements, designing solutions, and continuously validating implementations ensures software meets overarching business goals.
1. **Applying non-functional requirements using industry standards** (07:20) — Leveraging frameworks like iso 25010 helps define crucial constraints around performance, security, and suitability.
1. **Identifying the root causes of systemic technical debt** (11:02) — Unclear requirements and missing documentation drive deep architectural decay far beyond superficial code quality issues.
1. **Tracking choices through architecture decision records** (13:25) — Capturing context, decisions, and consequences in simple records preserves essential long-term project knowledge and team intent.
1. **Managing long-term software evolution and lifecycle phases** (14:06) — Planning for extended servicing and phase-out cycles prevents critical business failures in aging legacy models.
1. **Distinguishing between routine refactoring and structural overhauls** (17:46) — Large-scale application restructuring requires deliberate planning and significant resources compared to everyday code refactoring.
1. **Navigating the multiple layers of enterprise systems** (19:57) — Aligning business operations, applications, data strategies, and tooling creates a robust and scalable technical ecosystem.
1. **Balancing cross-functional roles to maintain project oversight** (22:37) — Effective technical leadership requires blending multiple disciplines to keep teams aligned on unified long-term strategies.

## Related Moments

- [Understanding the role of software architecture and quality](https://www.wearedevelopers.com/videos/1684-modern-software-architectures) (from "Modern software architectures")
- [Building engineering cultures that support long-term software architecture](https://www.wearedevelopers.com/videos/1998-from-code-to-culture-why-leadership-determines-software-quality) (from "From Code to Culture: Why Leadership Determines Software Quality")
- [Navigating the software architect role and daily team responsibilities](https://www.wearedevelopers.com/videos/206-move-fast-with-software-architecture) (from "Move fast with Software Architecture")
- [Improving software architecture skills through consistent writing habits](https://www.wearedevelopers.com/videos/925-i-will-remember-that-and-other-lies-why-documentation-matters-and-it-makes-your-apps-better) (from ""I will remember that" and other lies - Why documentation matters and it makes your apps better")
- [Preventing software architecture deterioration over product lifespans](https://www.wearedevelopers.com/videos/68-model-based-systems-engineering-in-an-agile-product-development-process) (from "Model Based Systems Engineering in an Agile Product Development Process")
- [Architectural planning to avoid crippling requirements debt](https://www.wearedevelopers.com/videos/1438-why-most-software-projects-fail-silently) (from "Why (most) software projects fail silently...")

## Related Articles

- [Why You Shouldn’t Build a Microservice Architecture](https://www.wearedevelopers.com/magazine/118-why-you-shouldn-t-build-a-microservice-architecture)
- [How to Avoid Over-Engineering](https://www.wearedevelopers.com/magazine/546-how-to-avoid-over-engineering)
- [Why Event-Driven Architecture Isn’t About Speed (and When You Actually Need It)](https://www.wearedevelopers.com/magazine/745-why-event-driven-architecture-isn-t-about-speed-and-when-you-actually-need-it)
- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)

## Related Jobs

- [Senior Architect Realtime Bare-Metal Software](https://www.wearedevelopers.com/jobs/ext/381559-senior-architect-realtime-bare-metal-software) at **ZEISS Group**
- [Enterprise Architect - Integration / Connectivity](https://www.wearedevelopers.com/jobs/ext/1540882-enterprise-architect-integration-connectivity) at **ZEISS Group**
- [Enterprise Architect - ERP](https://www.wearedevelopers.com/jobs/ext/1965168-enterprise-architect-erp) at **ZEISS Group**
- [Senior Cloud Software Architect (all genders welcome) for our Intelligent Service Operations Hub](https://www.wearedevelopers.com/jobs/ext/1284556-senior-cloud-software-architect-all-genders-welcome-for-our-intelligent-service-operations-hub) at **Rosenxt Group**
- [Senior Cloud Software Architect (all genders welcome) for our Intelligent Service Operations Hub](https://www.wearedevelopers.com/jobs/ext/1693682-senior-cloud-software-architect-all-genders-welcome-for-our-intelligent-service-operations-hub) at **Rosenxt Group**
- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**