Modeling
A model is a simplified representation of something real. It captures the details that matter for a specific purpose and deliberately leaves out everything else.
Modeling is one of the most practical forms of abstraction. Every time you sketch a diagram, create a spreadsheet, or draw a floor plan, you are building a model. This chapter explores how modeling works, why simplification is a feature rather than a flaw, and how to build models that are genuinely useful.
What Makes Something a Model
A model has three defining characteristics:
- It represents something else. A model always stands in for a real thing, process, or system.
- It is simpler than the thing it represents. If it were not simpler, it would not be useful — you would just look at the real thing.
- It serves a specific purpose. A model is built to answer particular questions or support particular decisions. Different purposes call for different models of the same thing.
Everyday Models
A Map
A road map is a model of geography. It shows roads, intersections, and distances. It does not show every tree, building, or fire hydrant. That omission is the point — a map that included every detail of the physical world would be the size of the physical world and completely useless for navigation.
Different maps model the same geography for different purposes:
- A road map shows highways and routes for drivers.
- A topographic map shows elevation for hikers.
- A subway map shows stations and lines, often distorting physical distance to improve readability.
Each one is "wrong" in some way — they all leave things out — but each one is useful for its intended audience.
A Budget
A household budget is a model of your finances. It groups spending into categories like rent, groceries, and entertainment. It does not track every individual transaction at the penny level (unless you want it to). It simplifies your financial life into something you can reason about and make decisions with.
Monthly Budget Model
Income: $5,000
Rent: $1,500
Groceries: $400
Transport: $200
Savings: $800
Other: $2,100
This model answers the question "Where does my money go?" without requiring you to examine every receipt.
A Recipe
A recipe is a model of a cooking process. It captures ingredients, quantities, and steps. It does not capture the exact hand movements for chopping, the ambient humidity in your kitchen, or the precise age of your baking powder. Those details exist in reality but are left out of the model because they are not needed for most cooks to succeed.
Why Simplification Is a Feature
Beginners often worry that models are "inaccurate" because they leave things out. But that is exactly what makes them valuable.
Consider trying to plan a road trip. You could:
- Option A: Study satellite imagery of every mile of road, research current construction projects, check tire pressure recommendations for each road surface type, and calculate fuel consumption based on elevation changes.
- Option B: Open a map app, enter your destination, and follow the suggested route.
Option B uses a model. It is less detailed, but it lets you actually make a decision and start driving. The goal of a model is not to be complete — it is to be useful.
The statistician George Box put it well: "All models are wrong, but some are useful."
Modeling in Technology
Database Schemas
When a business builds software, one of the first steps is modeling the data. A database schema defines what information to store and how to organize it.
Consider an online bookstore. The real world has books — physical objects with covers, pages, smells, and memories. The database model captures only what the software needs:
Book
- title
- author
- isbn
- price
- publication_date
- category
- stock_count
This model leaves out the weight of the book, the font used on the cover, and the texture of the pages. Those details exist in reality, but the software does not need them.
Wireframes
A wireframe is a model of a user interface. It shows the layout, structure, and key elements of a page without colors, fonts, or final images.
+----------------------------------+
| Logo Navigation [?] |
+----------------------------------+
| |
| [ Search Bar ] |
| |
| +----------+ +----------+ |
| | Product | | Product | |
| | Image | | Image | |
| | Name | | Name | |
| | Price | | Price | |
| +----------+ +----------+ |
| |
+----------------------------------+
Designers use wireframes to discuss layout and user flow before anyone writes code or creates visual designs. The simplification is intentional — it keeps the conversation focused on structure rather than aesthetics.
UML Diagrams
UML (Unified Modeling Language) diagrams model the structure and behavior of software systems. They show relationships between components, data flow, or sequences of events.
A simple relationship model:
Customer --places--> Order --contains--> Item
|
+--ships-to--> Address
This tells you the key relationships without drowning you in implementation details like data types, error handling, or network protocols.
How to Build a Good Model
Start with the purpose
Before modeling anything, ask: "What question does this model need to answer?" A model built to answer the wrong question will be useless no matter how detailed or elegant it is.
Choose the right level of detail
Include details that affect the decisions the model supports. Leave out everything else. If you are modeling a restaurant for a reservation system, you need tables and seating capacity. You do not need the color of the tablecloths.
Validate against reality
A model should be checked against the real thing it represents. Does the budget actually reflect your spending? Does the database schema capture the information the business needs? Models drift from reality over time and need periodic updates.
Expect to iterate
Your first model will be wrong in some way. That is normal. Build it, use it, learn from it, and refine it. The best models evolve through use.
Common Pitfalls
Over-modeling
Including too much detail defeats the purpose. If your model is nearly as complex as the thing it represents, it is not helping you think more clearly.
Under-modeling
Leaving out critical details makes the model misleading. A budget that ignores taxes and insurance will give you a dangerously optimistic picture of your finances.
Confusing the model with reality
The model is not the thing. A map is not the territory. A database record of a customer is not the customer. When the model and reality diverge, reality wins.
Using one model for everything
Different questions require different models. A single "universal" model that tries to serve every purpose usually serves none of them well.
Failing to update the model
The real world changes. A model built six months ago may no longer reflect current reality. Stale models lead to bad decisions.
Key Takeaways
- A model is a simplified representation of something real, built for a specific purpose.
- All models leave things out — that is what makes them useful, not what makes them flawed.
- Everyday examples of models include maps, budgets, recipes, floor plans, and organizational charts.
- In technology, database schemas, wireframes, and UML diagrams are all models.
- Good models start with a clear purpose, include the right level of detail, and are validated against reality.
- Models need to evolve as the things they represent change.