Inverse Conway maneuver

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

The inverse Conway maneuver is an organizational design practice that structures teams to reflect the desired architecture.

The inverse Conway maneuver organizes teams around a desired target architecture. During modernization, it connects organizational design with technical boundaries rather than treating change as purely technical. section 17.4

Apply it as an adaptive transition:

• Reorganize teams toward the target architecture, while acknowledging that the existing system may still impose old boundaries. section 17.4
• Plan for intensified collaboration when teams share technical artifacts or cross-boundary components. section 17.4
• Prioritize modularization and collaboration before attempting costly physical separation. section 17.4

CloudSuite’s phased reorganization

CloudSuite reorganized teams first, although they remained aligned with the old architecture during the initial phase. Because the backend API crossed team boundaries, the organization accepted extra collaboration and focused first on modularizing that component. section 17.4

Figure 17.5 In phase 1 of the inverse Conway maneuver, teams were reorganized first.

Use the phase diagram to inspect how team reorganization precedes architectural realignment. section 17.4

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

How deep it goes

Explains phased reorganization, transitional compromises, and collaboration needs around shared technical artifacts.

Examples

Uses CloudSuite’s phased team reorganization and cross-boundary backend API as concrete examples.

What it assumes

Assumes a desired target architecture and acknowledges constraints imposed by the system that cannot yet be changed.

What you can do after

Apply it via phased team reorganization while managing shared components and transitional collaboration.

How it connects

Connects modernization with software architecture, team organization, collaboration, and modularization.

liveBookmanning.com

Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

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.