Introducing Banking Customer Segmentation Commons
A community focused on customer segmentation in small and regional banks
Read articleFrom fundamentals of data modelling to contractual abilities, and how they uphold the constantly evolving semantics between data producers and data consumers
In the realm of Data, a model would usually refer to a data model: a collection of data entities (e.g., “customers”, “accounts”, “orders”) and how they are related to each other. But we are taking a step back here to the broader and more fundamental understanding of “Model”:
A model represents a concept, system, or process structurally. The purpose of the simplified structure is to help in navigating, understanding, and interacting with complex realities. Like a map in a new city. It is the simplified abstraction that captures important details while bypassing unnecessary complexity so users comprehend a larger reality through the model’s lens.
A model is an informative representation of an object, person, or system.
Models can be divided into physical models (e.g. a ship model and abstract models (e.g. a set of mathematical equations describing the workings of the atmosphere for the purpose of weather forecasting). [refer]
Etymology is one of the most foundational fields of study when it comes to data.
It is the study of the origin of words. And as we know, a single word could change the meaning of data. Which is why Semantics is such a major area of innovation and discussion in the data space.
This leads us to go back to the origin of “Model” to understand the perception of the word in the broader subconscious. Or the deeply embedded root sentiment the word evokes. We’ll find out in a minute why this is so critical.
The word “model” comes from Latin root modulus, which means “a small measure”or “a standard”. This is a diminutive form of modus, which means “measure,” “manner,” or “way.”
Ergo, the connection between model as a structured representation and measure as a unit of quantification is almost intuitive when we break it down:
Originally, modulus (small measure) referred to a standard unit: a way to quantify and compare things. Over time, this idea expanded: instead of just measuring physical dimensions, models became ways to measure conceptual coherence, relationships, and expected behaviours.
Thus, a model is a measure of how well a system holds together: it captures the essence of something in a structured way.
A measure tells us how much of something exists, while a model tells us what is relevant in the first place.
In other words, a model is a higher-order measure, not just a number, but a structured way of defining what should be measured and what relationships exist.
When we say Model-First Data Products, we are embedding measurement inside the model:
The SQL (acting as models or blueprints for tables/views) defines what data is valid, how it’s structured, and how it can be used, setting measurable expectations.
The model itself contains tests, ensuring that data conforms to predefined constraints (e.g., uniqueness, integrity, quality thresholds).
Instead of an after-the-fact measurement of data quality, the model encodes the measurement criteria upfront.
Defensive programming is a coding philosophy where developers anticipate and guard against potential failures, edge cases, and unexpected inputs. Instead of assuming all inputs and conditions will be correct, a defensive program is built to handle errors gracefully, prevent failures, and maintain stability under uncertain conditions.
When we combine the model as a structured representation and the model as a measure of reality, what emerges is the idea of a contract.
A contract exists to create alignment: between parties, across contexts, and over time. It defines what is valid, what is expected, and what will not be tolerated. That’s exactly what a model does in the data space.
Thus, a Model-First Data Product is, at its core, a contract-first system. The model is the contract that binds intent with execution, semantics with measurement, and structure with reliability.
And just like legal contracts in society, the strength of the data ecosystem depends on the strength of these contracts: clear, enforceable, and universally interpretable.

Thanks for reading Modern Data 101! Subscribe for free to receive new posts and support our work.
If you have any queries about the piece, feel free to connect with the author(s). Or feel free to connect with the MD101 team directly at community@moderndata101.com 🧡

Find me on LinkedIn 🙌🏻 | Find more about Animesh on our Expert Directory 📒
From MD101 team 🧡
With our latest 10,000 subscribers milestone, we opened up The Modern Data Masterclass for all to tune in and find countless insights from top data experts in the field. We are extremely appreciative of the time and effort they’ve dedicatedly shared with us to make this happen for the data community.

A no-cost session with a practitioner who's been where you are.
Modern Data 101 is a global movement redefining how the world thinks about data. Built by the team behind The Modern Data Company, the company pioneering DataOS, the data operating system, Modern Data 101 brings together a global community of practitioners, architects, and leaders across 150+ countries at the intersection of data, product thinking, and AI.
While DataOS advances the technology and infrastructure on-ground to help enterprises operationalize data as products, Modern Data 101 advances the ideas, practices, and conversations that shape how the industry approaches data and AI. Together, they connect technological innovation with the broader movement to rethink how organizations build, govern, and activate data.
At its core, Modern Data 101 exists to simplify the journey from raw data to tangible, measurable impact. It champions data product thinking and next-generation architectures that unify and activate insights and automation across analytics, applications, and operational workflows.
In a world shifting from data stacks to AI ecosystems, Modern Data 101 helps the industry rethink what's possible.
A 9-dimension self-assessment used by 100+ data teams to benchmark strategy, ownership, and platform readiness.


Modern Data 101 is where the data community thinks out loud. When you're ready to move from articles to architecture, data products, governed AI pipelines, or a full Data Operating System; the team behind this community can help you build it.