Process Maps as Schema: Drafting Your Data Model from Workflow Diagrams
Every data model encodes a story about how a business works. The tables, foreign keys, and constraints are the grammar; the process is the plot. Yet many teams begin modeling by listing nouns—Customer, Order, Product—without first asking how those nouns interact over time. The result is a schema that technically satisfies a spec but feels awkward when developers try to write queries against real workflows. This guide offers a different starting point: treat your process map as a rough draft of your data model. By translating lanes, steps, and decision diamonds directly into tables and relationships, you can produce a schema that mirrors how work actually happens—before you ever open a modeling tool. We will walk through the core idea, show a concrete example, discuss edge cases, and honestly assess the limits of the approach.