The Four Causes, in Plain Terms

This is Unit Two of The M-CaReM-AI Method, on the four causes, in plain terms. Unit One ended with a diagnostic that kept pointing at the same gap: nobody had agreed what the system is made of. This unit gives that gap its name, and the three explanations it usually hides behind. Carry one question through this unit: why can a team describe its system's purpose, process and design fluently, and still be unable to say what it is made of? The answer arrives with the Incident Report taken through all four causes. By the end you will be able to state Aristotle's four causes. To explain why material cause is neglected. To take a system or a thing through all four. And to find where a definition is fuzzy by watching where people hesitate.

Nine entries on what Aristotle meant by cause, his four causes in his own words, and the method's plain-language versions.

A team that cannot say what its system is.

MCM 026 Four Answers About One Loan

The method's chapter on the four causes opens with a lending team that can describe its system's purpose, process and design, but not its substance. In the book's example, a compliance officer asks which record would show a regulator why an applicant was declined, and nobody knows.

What Aristotle meant by cause.

MCM 027 Cause, in the Older Sense

Today cause usually means what made something happen. Aristotle used the word more broadly, for the ways a thing can be explained. In the Physics he says people do not think they know a thing until they have grasped its why, and he finds four kinds of why.

The four, in his own words.

MCM 028 Aristotle's Four, in His Words

In the Physics, Aristotle names four causes: that out of which a thing comes to be; its form; the primary source of its change; and that for the sake of which it exists. His examples are the bronze of a statue, the father of a child, and health as the reason for walking about.

The first cause in modern terms.

MCM 029 Final Cause

Final cause answers why: the purpose a thing exists to serve, such as safer care, less fraud or faster processing. Purpose aligns people well, but a beautiful purpose statement does not settle what any record contains.

The second cause.

MCM 030 Efficient Cause

Efficient cause answers who and how: the teams, pipelines, sprints and tickets that bring a system about. The method calls this motion, and material cause substance; flawless delivery can still build the wrong conceptual model.

The third cause.

MCM 031 Formal Cause

Formal cause answers what shape: domain models, architecture, workflows and diagrams. The book warns that good models fail when they never become shared contracts, staying in slide decks while developers design from stories and code.

The fourth cause.

MCM 032 Material Cause

Material cause answers what it is made of: the cases, applications, decisions, logs and documents that exist inside a system. The method calls it the neglected basement: everyone has opinions about the living room, but a crooked foundation is paid for later.

Why the four belong together.

MCM 033 Several Causes at Once

Aristotle adds that one thing has several causes at once: the sculptor's art and the bronze both cause the statue, one as the source of change, the other as its material. The four are not rivals; an explanation that leaves one out is incomplete, which is the method's argument for material cause.

Two everyday examples from the book.

MCM 034 A Chair and a Contract

The book shows all four causes in a wooden chair and a legal contract. The chair exists for sitting, is made by a carpenter, follows a design, and is made of wood. The contract defines an agreement, is drafted by lawyers, follows a structure, and is made of clauses. The material is always the most concrete answer.

Four entries on why material cause is the one organizations neglect, what it really covers, and how AI sees it.

The cause nobody talks about.

MCM 035 The Cause Nobody Talks About

The method observes that organizations lavish attention on purpose, process and architecture, and treat material cause as merely the data. Asked what a Loan Application is made of, a team hesitates or gives several incompatible answers. The book's rule of thumb: the cause nobody talks about is usually the one that fails.

More than data modeling.

MCM 036 Not Just Data Modeling

Material cause covers a thing's business idea, fields, lifecycle, relationships and obligations such as audit, retention and privacy. A data model can be fast and normalized yet never record the policy version a decision was made under. That model fails materially, because an obligation was never represented as a field.

Material cause as an agreement.

MCM 037 A Shared Contract

In the method, material cause becomes a shared contract: an agreed short description of a thing's purpose, properties, lifecycle, relationships and obligations. Business, technology and compliance staff each say: yes, that is a Case. A definition only works once its users, governors and builders agree to it.

How AI sees material cause.

MCM 038 Statistical and Generic

A language model's sense of material cause is statistical and generic: it knows typical things, not your institution's definitions. Asked about a case, it describes a typical organization's case, with plausible fields that may not exist in yours. The danger is invented fields, missing required ones, and two of your things merged into one.

Five entries on using the four causes on a system, on a single thing, and in a meeting. The opening question is answered here.

A lending system, cause by cause.

MCM 039 The Loan System, Cause by Cause

The book works an online lending system through all four causes in order. Final: customers apply online, decisions come faster, and lending rules are met. Efficient: a product team, two-week sprints and a deployment pipeline. Formal: services for applications, credit checks, decisions and notifications. Material: the Loan Application, Applicant, Credit Report, Risk Score, Loan Offer, Decision Record and Audit Log Entry. Most teams answer the first three fluently; the fourth is where hesitation shows, and hesitation marks undefined material.

Giving a tool your definition.

MCM 040 Teaching the Tool Your Definition

The method's rule is to tell a tool what your Case is, not ask it. Write the thing's definition and key fields, even roughly. Give the tool that definition with the request. Give it the method's template, so the output must name the thing, change and fields. Tell it to use only the fields given and list anything missing as a question. Then read the result against the definition. Ask in the other order and you get a typical Case back, presented as yours.

An Incident Report through all four causes.

MCM 041 The Incident Report's Four Causes

The book takes a hospital's Incident Report through the causes. Final: safety events are recorded, investigated, trended and reported. Efficient: staff create it on reporting screens. Formal: it links to a patient, a location and an action plan, and moves from new to closed. Material: its fields, including date, location, type, severity, harm level and a patient-involved flag. That answers this unit's question: teams can describe the first three fluently because they are talked about constantly, while the fourth must be written down deliberately. Without it, a tool may omit harm level; with it, the same tool can draft cards inside those fields.

The exercise to run with a group.

MCM 042 The Four-Causes Exercise

The book's exercise takes one important thing through the four causes with a small group. Pick the thing. Ask why it exists and what would be missing without it. Ask who creates and updates it. Sketch what it connects to. Ask which fields, states and relationships it must have to be valid. Throughout, watch where people hesitate or disagree, and write those points down. The hesitations are the result: they show exactly where material cause is fuzzy today.

Four questions for any meeting.

MCM 043 Four Questions for Any Meeting

The book turns the four causes into four questions that can steady a confused meeting. In its example, three groups argue over three changes until someone asks: what thing is this decision recorded in? How is it shaped in our data? Who and what act on it? What is it actually for? Nobody can answer the last one the same way, and the meeting ends by writing the purpose down. The questions work without anyone mentioning Aristotle.

Two constructed examples that take the library's Loan through the four causes and turn its hesitations into decisions.

A library Loan's four causes.

MCM 044 A Library Loan's Four Causes

A worked example, constructed for this course, takes the library's Loan through the causes. Final: fair borrowing, knowing where items are, getting overdue items back, and, to the room's surprise, figures for the funding council. Efficient: the desk, kiosks, online renewals and a nightly notice job. Formal: one Member, one Item, a Branch and possibly a Fine. Material comes last and slowest: is a renewal a new Loan, which date counts for the council, and is a lost item still an open Loan? Three causes took ten minutes; the fourth took an hour.

Turning hesitations into decisions.

MCM 045 Where the Group Hesitated

A second constructed example lists the four points where the library group paused and gives each an owner. The team then tries an AI tool twice. Without a definition, it counts renewals as new loans, assumes daily fines, and invents a category field. Given the rough definition and the open questions, it lists the questions as unresolved instead. The tool did not become smarter; the team became more precise, and had they accepted the first answer, invented details would have entered their requirements looking like research.

Look at what you can now do. You can state Aristotle's four causes in his words, the bronze, the father, the form and the end, and in the method's: why, who and how, shape, and made of. You can explain why material cause is the neglected basement, and why it is more than data modeling. You can take a system or a single thing through all four causes, and give a tool your definition before your request. And you can find where a definition is fuzzy by watching where people hesitate. Unit Three sets out the five phases.