Tagged articles
Conway's Law
33 articles · Page 1 of 1
This article details practical implementation of evolutionary architecture, covering Conway's Law alignment, cross-functional team organization, culture and experimentation, budget considerations, fitness functions as experimental tools, enterprise governance with bounded contexts, adoption strategies, and when to avoid evolutionary architecture.
Conway's LawDevOpsarchitecture governance
0 likes · 72 min read

Anthropic argues that multi-subagent architectures often mirror organizational charts rather than technical needs, showing single-loop agents with progressive skill disclosure outperform complex pipelines in quality, latency, and cost, and provides a migration framework.
AI agentsAgent EvaluationAnthropic
0 likes · 22 min read

This article distinguishes architecture styles from patterns, explores three primitive patterns, compares technical vs domain partitioning, details the fallacies of distributed computing, and explains how Conway's Law and Team Topologies align team structure with architecture.
Conway's LawPartitioningarchitecture pattern
0 likes · 10 min read

This article explores microservices architecture beyond basic decomposition, covering decoupling principles, service boundary identification, governance pillars (observability, traffic control), distributed transaction patterns, data management strategies, API design best practices, infrastructure choices (Kubernetes, Service Mesh), organizational alignment via Conway's Law, and when to avoid microservices.
Conway's LawDecouplingKubernetes
0 likes · 12 min read

Google’s I/O 2026 talk warns that AI‑driven code generation can amplify output tenfold, but without solid fundamentals the resulting software ecology—code review, build times, testing, and dependency management—will collapse, making engineers the true bottleneck.
AICI/CDConway's Law
0 likes · 11 min read

The article explores how Conway's Law—"organizations design systems that mirror their structure"—extends to large‑model agent architectures, offering concrete examples, role‑alignment strategies, concise communication patterns, and cautions against over‑engineering to improve multi‑agent collaboration.
AI coordinationAgent System DesignConway's Law
0 likes · 9 min read

The article examines how engineering team structures—illustrated by Adobe's functional silos and Spotify's cross‑functional squads—shape information flow, decision‑making, and delivery speed, explains Conway's Law, outlines common organizational patterns and their traps, and offers a systematic approach to diagnosing and redesigning team topologies.
AdobeConway's LawR&D management
0 likes · 13 min read

A CTO recounts how a six‑year‑old e‑commerce core system was transformed through simultaneous technical and organizational restructuring, detailing the diagnostic findings, the shift to a domain‑driven microservices architecture on Kubernetes and Istio, the execution timeline, and the dramatic improvements in availability, latency, deployment frequency, and team health.
AIOpsConway's LawIstio
0 likes · 12 min read

The article argues that a CTO's true value lies in mastering organization design—aligning team structures, decision rights, culture, and talent density—to keep technical systems evolving and teams resilient during rapid growth, rather than relying solely on personal coding prowess.
CTOConway's LawOrganization Design
0 likes · 12 min read

The article explores structural thinking as the core mindset of software engineers, breaking it into three levels—conception, insight, and understanding—while emphasizing runtime and evolutionary structures for managing complexity, enabling collaboration, and sustaining long-term system health.
Conway's Lawcomplexity managementevolutionary architecture
0 likes · 8 min read

Splitting a monolith into microservices can shift complexity to inter‑service communication, causing data consistency issues and CAP trade‑offs, so you must evaluate motivations, apply single‑responsibility and team‑aligned boundaries, and follow practical guidelines to ensure a sound architecture.
CAP theoremConway's Lawbackend architecture
0 likes · 11 min read

The article traces the rise and fall of China’s mid‑platform craze, illustrating its promise through Supercell’s profit‑driven reuse model while warning that extensive integration costs, organizational misalignment, and latency can outweigh zero‑cost benefits, and concluding that such platforms succeed only in stable domains with deep domain expertise.
Conway's LawSupercellmid‑platform
0 likes · 10 min read

The article explores how organizational structure, Conway's Law and its inverse, and the management of team cognitive load influence software architecture stability and development efficiency, offering practical measures for team design, governance, and architectural practices to align teams with desired system outcomes.
Conway's LawR&D managementcognitive load
0 likes · 18 min read

The article argues that both business and personal health debts inevitably accumulate like entropy, but can be managed through structured thinking—identifying, categorizing, prioritizing, and continuously monitoring and feedback‑driven actions such as mindfulness, exercise, and disciplined system maintenance—to reduce complexity and sustain growth.
Conway's LawHealth Managemententropy
0 likes · 18 min read

This article reviews JD.com’s automation testing framework, explores how Conway’s Law and organizational culture affect software quality, presents a coupon‑system redesign case, and offers practical guidance on metrics, team cohesion, and probabilistic effort estimation for high‑quality delivery.
Conway's LawProcess ImprovementQA
0 likes · 18 min read


DevOpsAug 24, 2023 · R&D Management
This article summarizes the main concepts from the book “High‑Performance Team Patterns”, explaining why teams—not individuals—are the primary unit of software delivery, how Conway’s Law and the Dunbar number guide optimal team size, and presenting four basic team topologies with interaction models to enable end‑to‑end value‑stream delivery.
Conway's LawDunbar numberteam topologies
0 likes · 17 min read


DevOpsJun 30, 2023 · R&D Management
This article explains how team topology and Conway's Law shape communication structures, describes the concepts of flow, enabler, and complicated‑subtle teams, and offers practical guidance on aligning team cognition, applying cognitive load theory, and building value‑stream teams to improve DevOps efficiency.
Conway's LawValue Streamcognitive load
0 likes · 24 min read

This article explains the challenges introduced by breaking a monolithic application into microservices, discusses CAP and BASE theories, Conway's law, and provides concrete strategies such as single‑responsibility splitting and team‑aligned architecture to help engineers design well‑structured distributed systems.
CAP theoremConway's Lawbackend architecture
0 likes · 11 min read

This case study details how Qunar’s hotel pricing platform was reorganized in 2021 using Domain‑Driven Design and explicit architecture principles to streamline cross‑team collaboration, reduce data‑flow complexity, and improve response time by 25%, while aligning system structure with Conway’s Law.
Conway's LawDDDHotel Pricing
0 likes · 14 min read

The article explains how breaking a monolith into microservices can introduce data consistency challenges, discusses the CAP theorem and Conway's law, and provides practical guidelines—such as single‑responsibility division, team‑aligned service boundaries, and appropriate use of BASE and distributed transactions—to split services responsibly.
CAP theoremConway's LawSingle Responsibility
0 likes · 11 min read

The article explores how Conway’s Law and the entropy increase principle explain the dynamic nature of organizational structures in tech companies, highlighting the impact of communication patterns on system design, resource allocation, and team efficiency.
Conway's Lawentropyorganizational structure
0 likes · 6 min read

This article explains how micro‑frontends reflect Conway’s Law, discusses the entropy problem of large codebases, and outlines clear scenarios where adopting or avoiding micro‑frontends makes architectural sense for modern frontend teams.
Conway's LawFrontend ArchitectureMicro Frontends
0 likes · 7 min read

The article argues that merging microservices back into a monolith can be justified when service boundaries no longer align with team structures, emphasizing that microservices address both technical load and people‑organization problems, and that the right size of a service depends on context rather than the misleading notion of "micro".
Conway's Lawmonolithscalability
0 likes · 11 min read

The article compares large‑scale, highly regimented development teams with small, autonomous squads, explaining how the latter achieve faster delivery, higher innovation, and better resource efficiency while still handling complex projects, and discusses Conway's Law and practical implications for modern software organizations.
Conway's Lawlarge teamsproject management
0 likes · 12 min read

The article explains how designing autonomous, end‑to‑end responsible teams—by minimizing inter‑team collaboration, adopting full‑process or cross‑functional squads, and leveraging automation tools—leads to better software architecture, aligns with Conway’s law, and improves efficiency in modern DevOps environments.
AgileConway's LawDevOps
0 likes · 6 min read

This article explains Conway’s Law and its four principles, showing how an organization’s communication patterns dictate system design, affect microservice adoption, agile practices, and the need for political navigation in large‑scale software architecture.
Conway's Lawagile developmentmicroservices
0 likes · 7 min read

The article explains Conway’s Law and its four derived principles, showing how communication structures shape system design, why small teams reduce complexity, how agile and micro‑service approaches address time and scalability constraints, and why architecture decisions are inherently political.
Conway's Lawagile developmentmicroservices
0 likes · 9 min read


DevOpsAug 10, 2018 · Operations
This article examines how enterprises can adopt DevOps with minimal risk and cost by leveraging agile management, continuous delivery frameworks like the 100‑to‑100 model, Conway’s Law, automation, scripting, and containerization with Docker, while also presenting a recruitment call for DevOps engineers.
Continuous DeliveryConway's LawDevOps
0 likes · 9 min read

The article examines how adopting microservice architecture reshapes companies into flat, small-team clusters, arguing that microservices function more as an organizational design than a pure technical pattern, and outlines principles for aligning teams with business, embracing uncertainty, and simplifying inter‑team integration.
Conway's LawR&D managementteam organization
0 likes · 13 min read

The article explains how Conway's Law—stating that system designs mirror organizational communication structures—provides a theoretical foundation for microservices, highlighting communication costs, team size limits, resilience, and practical guidelines for building autonomous, business‑oriented service teams.
Conway's Lawteam communication
0 likes · 12 min read

Based on Gene Kim’s 2017 DevOpsDays Seattle keynote, this article explains how DevOps transforms IT performance through higher deployment frequency, reduced lead time, lower failure rates, Conway’s Law implications, and real‑world case studies from Etsy to Barclays, illustrating why the practice is essential for both startups and legacy enterprises.
Conway's LawDevOpsIT performance
0 likes · 14 min read

At SpringOne, Credera engineers Jason Goth, Micah Blalock, and Patricia Anderson explained how they leveraged Conway’s Law to redesign a client’s technical architecture and processes, overcoming productivity decline by restructuring teams, applying the open/closed principle, and introducing new communication roles, ultimately accelerating high‑quality code delivery.
AgileConway's LawOpen/Closed Principle
0 likes · 6 min read


21CTOJan 16, 2016 · R&D Management
The article examines Digg’s former software development workflow, detailing its team structure, Git‑Gerrit code review, Jenkins testing, Puppet deployments, evolving practices, and how Conway’s Law shaped its architecture, offering lessons for modern engineering teams.
Continuous IntegrationConway's LawDeployment Automation
0 likes · 8 min read
