Over the past months, I’ve created a growing collection of Medium publications that explore the world of data modeling, metadata, architecture, and automation from two complementary perspectives — the technical and the human.
This article explains how these publications connect, why the naming evolved, and how they now form a consistent ecosystem for readers and practitioners.
🔍 Why organize publications this way?
Data architecture has many audiences. Some want to understand how models, metadata, and platforms work. Others need to see why these structures matter to business outcomes.
When I started writing, some of my publications had overlapping names — for example Business-Friendly Data Architecture and Model-Driven Data Architecture. Over time, it became clear that these two phrases represented different lenses on the same problem:
- Model-Driven — focuses on structure, automation, and the technical craft of architecture.
- Business-Friendly — focuses on communication, understanding, and bridging the business-technology gap.
By grouping my work into these two families, I could make it easier for readers to find the perspective they value most, while maintaining coherence across all themes.
🏢 The Three Families of Publications
To bring order and clarity, I structured all publications into three main families:
1. Model-Driven Family
Focus: technical design, automation, and metadata-driven engineering.
- Model-Driven Data Engineering — building scalable, metadata-driven data platforms
- Model-Driven Data Architecture — bridging models, metadata, and meaning across the enterprise
- Model-Driven Data Delivery — where models meet delivery
- Model-Driven Data Quality — automating data quality checks using patterns and metadata
- Model-Driven Migrations — evolving data platforms and sources through metadata and automation
These publications reflect the architectural and engineering backbone of modern data platforms.
2. Business-Friendly Family
Focus: translating complexity into clarity, and helping non-technical audiences grasp data architecture concepts.
- Business-Friendly Data Modeling — making data models clear and valuable for the business
- Business-Friendly Data Mapping — bridging technical models and business understanding
- Business-Friendly Metadata — explaining metadata, lineage, and data contracts clearly
- Business-Friendly Data Lineage — making lineage actionable for decision makers
- Business-Friendly Diagramming — creating clear, consistent, metadata-driven diagrams
These publications aim to humanize data architecture, promoting better collaboration and understanding across disciplines.
3. Universal & Conceptual Family
Focus: reusable patterns, sustainability, and future-ready design.
- Universal Data Models — reusable patterns for clear, scalable data models
- Universal Metadata Models — a universal structure for metadata and mappings
- Next-Gen Data Modeling — how AI and generative tools reshape modeling practices
- Cost-Friendly (Sustainable) Data Architecture — designing efficient, transparent, and sustainable platforms
This family explores the reusable and forward-looking principles that underpin both the model-driven and business-friendly perspectives.
🔄 From Confusion to Coherence
Early on, having both Business-Friendly and Model-Driven publications on similar topics created overlap — especially with titles like Business-Friendly Data Architecture.
After reviewing the audience and content, I renamed that series to Model-Driven Data Architecture, aligning it with the rest of the technical family.
This clarified the narrative: architecture is designed to serve the business, but it is inherently model-driven.
📊 The Visual Taxonomy
To make this ecosystem tangible, I designed a visual taxonomy that maps the three families.
The goal was to keep it as clean and minimalist as my publication icons — flat, modern, and concept-driven.
The taxonomy now looks like this:
Model-Driven | Business-Friendly | Universal & Conceptual
Each column represents one family, with shared colors and iconography (blue for technical depth, teal for connection, orange for emphasis). Together, they create a unified visual and conceptual identity.
💡 The Unifying Theme
Exploring how model-driven design and business-friendly communication make enterprise data platforms scalable, understandable, and governed by design.
This single statement unites everything I write — from conceptual data modeling and metadata-driven automation to visualization and governance.
It also sets the tone for future topics: how design and language shape the way organizations build and understand data systems.
📚 Looking Ahead
This ecosystem will continue to evolve as I explore:
- How AI and generative tools can assist in data modeling and documentation.
- How metadata ecosystems can bridge design, delivery, and governance.
- How visual languages can make architecture approachable without losing rigor.
If you’re following along, you’ll see a gradual integration of these themes into both families — always with the same mission: making data architecture both intelligent and human.