Records, Tables, Documents, and Relationships
Records represent individual facts, tables or collections group them, documents package related fields, and relationships connect business entities. Model stable business identities and relationships before optimising for the first screen's convenient data shape.
What You Will Be Able to Decide
- Explain records, tables, documents, and relationships in product and business terms.
- Apply this decision: Model stable business identities and relationships before optimising for the first screen's convenient data shape.
- Recognise this material risk: duplicated facts disagree and the team cannot determine which copy is correct.
- Ask a consultant for evidence rather than reassurance.
A founder is deciding how the product should remember information and preserve its meaning over time.
Records represent individual facts, tables or collections group them, documents package related fields, and relationships connect business entities.
A consultant can recommend and implement the technical approach. The founder still needs to decide which outcome matters, which risk is acceptable, and what evidence is sufficient.
Why This Decision Appears
A founder is deciding how the product should remember information and preserve its meaning over time.
The immediate question is records, tables, documents, and relationships. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.
Technical term
Records, Tables, Documents, and Relationships
Records represent individual facts, tables or collections group them, documents package related fields, and relationships connect business entities.
Treat it like a clause in a commercial agreement: its value comes from making expectations and consequences clear, not from sounding formal.
The Working Principles
Start with the product consequence, then choose the simplest technical treatment that protects it. A longer tool list is not a stronger plan.
For this decision, the useful standard is that the data model can represent the real business rules without ambiguity or silent corruption.
- Make the decision explicit: Model stable business identities and relationships before optimising for the first screen's convenient data shape.
- Ask what evidence would show that the chosen approach works.
- Name the person or provider responsible when the approach fails.
- Record the result in the data model and recovery plan.
How to Choose Without Overbuilding
Model stable business identities and relationships before optimising for the first screen's convenient data shape.
The principal risk is that duplicated facts disagree and the team cannot determine which copy is correct. This does not require the most expensive possible solution. It requires the consequence to be understood and the control to match it.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
A Useful Proposal and an Impressive-sounding One
Warning Signs
- Nobody can explain how records, tables, documents, and relationships changes a user or business outcome.
- The proposal does not address this risk: duplicated facts disagree and the team cannot determine which copy is correct.
- The only evidence is a successful demonstration of the easiest path.
- The decision has no named owner, boundary, or review point.
- A provider-specific feature is being mistaken for a permanent product requirement.
Questions to Ask a Consultant
- What decision are we making about records, tables, documents, and relationships?
- Which user or business outcome does the recommendation protect?
- How have we reduced or accepted this risk: duplicated facts disagree and the team cannot determine which copy is correct.
- What evidence can I review without relying on the original implementer?
- What is deliberately deferred, and when will it be reconsidered?
- Who owns the accounts, data, documentation, and recovery process?
Key takeaway
Key Takeaway
Records represent individual facts, tables or collections group them, documents package related fields, and relationships connect business entities. The founder's job is to make the consequence explicit; the consultant's job is to recommend and demonstrate a proportionate implementation.