Ch 15 - People and Organizations: Data Modeling is a Full-Contact Sport

2026-04-20 · Source: Practical Data Modeling · Field: Technology & Digital — Data Science & Analytics, Software Development & Engineering · Depth: Intermediate, long

Summary

Chapter 15 of an upcoming book on Physical Data Modeling (PDM) emphasizes that organizational dynamics, rather than technical acumen, are the primary drivers of success or failure in data initiatives. Drawing parallels to "gym politics" and citing Tom DeMarco and Timothy Lister's "Peopleware," the chapter argues that data modeling is a sociological phenomenon often overlooked in technical resources. It illustrates this with the $7 billion failure of Target Canada's expansion, where misaligned incentives and organizational structures led to systemic data defects, and a "Customer 360" project that stalled due to departmental disagreements over customer definitions. The content highlights that data models are political artifacts reflecting influence and priorities, and that real-world constraints often necessitate compromises over theoretical ideals. It also introduces Conway's Law, explaining how organizational communication structures directly influence system and data model design, leading to "silo taxes" that hinder agility.

Key takeaway

For CTOs overseeing data initiatives, recognize that organizational alignment and communication structures are paramount. Your data architecture will inevitably reflect your organizational chart, so proactively design team structures (Inverse Conway Maneuver) to foster desired system outcomes. Prioritize securing executive consensus on core data definitions and assigning clear data ownership before embarking on complex technical modeling, as neglecting these "sociological" aspects will likely lead to project failure and wasted resources.

Key insights

Organizational dynamics and human interaction are more critical to data modeling success than technical expertise.

Principles

• Data models are political artifacts.
• Conway's Law dictates system design mirrors communication structure.
• People and organizational issues sink more IT projects than technical ones.

Method

Design the "social contract" around the data model by enforcing canonical units, setting explicit quality bars, and assigning named business owners with accountability for data quality.

In practice

• Secure executive alignment on definitions before technical work.
• Time-box discovery work in hierarchical organizations.
• Use data models to bridge organizational silos.

Topics

• Data Modeling
• Organizational Dynamics
• Conway's Law
• Data Silos
• Project Failure Analysis

Best for: CTO, Director of AI/ML, VP of Engineering/Data, Data Scientist

Related on AIssential

• The Organizational Dynamics and Politics of Data Modeling — Organizational and political dynamics are paramount to data modeling success, often outweighing technical expertise.
• Organizing productive platform teams — Organizational structure dictates platform design; align teams to desired architecture, not existing complexity.
• Beyond Dashboards: How Data Teams Earn a Seat at the Table — Data teams must integrate technical reliability with business perspective and actionable insights to become strategic partners.
• April 2026 PDC State of Data Modeling Survey Results Are In! — Effective data modeling hinges on training, clear requirements, dedicated ownership, and sufficient time, not primarily on new tools.
• From Risk to Asset: Designing a Practical Data Strategy That Actually Works — Effective data strategy links organizational vision to daily implementation, ensuring data becomes an asset, not a risk.
• Conway’s Law: Your Operating Model Matters More Than The AI Model — Conway's Law dictates that AI systems mirror organizational structures; redesigning operating models is crucial for agentic AI success.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Practical Data Modeling.