liveBook · Manning

Organizational structure

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Organizational structure is the arrangement of roles, responsibilities, teams, reporting relationships, and decision authority within an organization.

Organizational structure shapes software architecture through communication patterns, reporting relationships, team boundaries, and decision authority. Conway’s law makes this relationship explicit: systems tend to reflect how organizations communicate. section 11.1.6

Effective design jointly optimizes the organization and software around compatible domain boundaries. Misalignment forces teams into shared codebases, repeated coordination, and friction that slows independent value streams. section 11.1.6

Travel organization

A customer-facing team owned customer capabilities and reported to marketing, while another group operated internal API platforms. The differing organizational responsibilities exposed the need to examine how team structure shaped software architecture. section 11.1.6

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Connects communication patterns, reporting alignment, and domain boundaries to architecture, but stops short of prescribing a reorganization.
Examples
Uses a travel organization’s customer-facing team, marketing reporting line, and internal API platform group.
What you can do after
Evaluate whether team boundaries and software boundaries align, then identify coordination friction caused by mismatches.
How it connects
Links Conway’s law to software architecture, Team Topologies, domain boundaries, communication patterns, and independent value streams.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.