The four links: the four disciplines of the method

If The thesis of the bridge explains why the paradigm is needed, this chapter sets out how it operates. And it is worth saying from the outset what distinguishes it: it is not a professional who knows a little of each thing, but four disciplines exercised as the four stretches of a single journey, which begins in a person and returns to a person. The data is the medium; the beginning and the end are always human.

The loop, not the list

The mistake would be to read the four disciplines as a menu —a professional who “knows sociology, and also development, and also data, and also AI”. That is dispersion, the opposite of what the paradigm asserts. The four form a single closed journey:

        ┌──────────────────────────────────────────────────────┐
        │                                                      │
        ▼                                                      │
  [1] SOCIOLOGY ─▶ [2] SOFTWARE ENG. ─▶ [3] DATA ENG. ─▶ [4] AI GOVERNANCE
  reads the org    builds the           guarantees the     returns value to
  (human           system               reliable data      the human decision
   problem)        (the hypothesis                          under governance
                    becomes                                 (from data to
                    a tool)                                  the person)
        ▲                                                          │
        │                                                          │
        └──────────────────────────────────────────────────────────┘
              value returns to the person and reopens the cycle

The closing of the loop is what distinguishes the paradigm from an ordinary multidisciplinary team: in a team, information is lost at every handover between specialists who do not understand one another. In integrated practice there is no handover: the hypothesis that arises from reading the organization is the same one that models the data and governs the AI. It is not retranslated —and degraded— at every step; it is preserved.

The four disciplines, one by one

Link 1 — Sociology of organizations

What it does. It reads the organization before the technology. It maps power, culture, incentives, real processes (not those in the manual) and resistances to change. It distinguishes the declared problem from the real one.

What it produces. A sociotechnical diagnosis: where it truly hurts, what can be changed and what cannot, who gains and who loses, where AI pays off and where it only destroys value.

Why it matters. Without this reading, everything else optimizes the wrong thing.¹

Guiding question: What do these people do here, why this way, and what breaks if this changes?

Link 2 — Software engineering

What it does. It turns the sociological reading into real software: auditable, maintainable, that people use every day. The social hypotheses become concrete tools.

What it produces. Secure backends, versioned APIs, event-oriented systems, MCP servers — with the auditability discipline of a regulated environment.

Why it matters. It is where the idea materializes or stays in a presentation.²

Guiding question: How is this built so that the person in link 1 uses it without it getting in their way?

Link 3 — Data engineering

What it does. It guarantees that the data exists, is reliable, accessible and meaningful in its context. It builds the pipelines (CDC, streaming, governance) that feed everything else.

What it produces. Governed data platforms, measurable quality, lineage, data ready to decide on — not only to store.

Why it matters. Without quality data there is no AI: errors are merely automated faster. And data quality is contextual and social, not an isolated technical attribute.³

Guiding question: Does this piece of data say what people believe it says, and does it serve the decision that matters?

Link 4 — AI architecture and governance

What it does. It designs AI solutions that return real value to the person: they amplify their judgment, do not replace it, and do so under auditable rules. It closes the bridge from the data to the human decision.

What it produces. Auditable AI systems, with governance controls, measured by the value they deliver to the person and not by the metric in fashion.

Why it matters. It is where the loop closes or is betrayed: the AI either returns to the person as power, or leaves them out.⁴

Guiding question: Does this AI return decision-making power to the person in link 1, or take it away?

When AI stops suggesting and moves to executing on its own —the agentic step of the ladder—, this link does not put a person to review every case: it puts the judgment into the design and the audit of the rules with which the agent decides —what it resolves on its own, when it escalates to a person, what it leaves on the record—. Human control is not lost; it moves one step up, from the decision to the governance of the decision. The loop closes all the same, but the demand for governance rises with autonomy.

The loop in a case

A concrete example, of the kind that recurs in the field, shows the journey better than any diagram. A mid-sized distributor wants to “use AI to anticipate which customers it is about to lose”. The request arrives like that, already translated into a solution: a model that predicts churn. The temptation is to start from the model. The method starts earlier.

Link 1 — read the organization. Before touching a single piece of data one must understand what truly happens, and what appears is almost never what was asked for. The salespeople already know who is about to leave —they smell it in a call that cools, in an order that shrinks—, but that knowledge lives in their heads and in no system. And no one has an incentive to share it: here the customer belongs to the salesperson, and releasing the information is releasing power. The real problem was not predictive; it was that valuable knowledge did not circulate. A churn model that ignored that would have competed with the salespeople’s intuition instead of adding to it. And it would have lost.

Link 2 — build the system. From that reading comes the true requirement, which is not “a model” but a tool the salespeople find it worth their while to use: fast, that returns something to them on the spot —a customer about to leave and the probable reason— and that neither exposes nor replaces them. If recording a signal costs three clicks and returns nothing in exchange, no one records it, and everything above collapses. The system is designed, from day one, for the person in link 1.

Link 3 — make the data mean something. Only here does the data come in, and at once the usual problem appears: the field “last purchase” means different things at each branch —one subtracts returns, another does not; one counts the counter sales, another only the deliveries—. To model on top of that without correcting it is to train on sand. Getting the data to say what everyone believes it says is not a technical formality: it is to go back to link 1, because that mismatch is the mark of human processes that never agreed with one another.

Link 4 — return the decision to the person. The model, at last, flags the customers at risk. But the loop closes well only if that flag returns to the salesperson as power and not as surveillance: it reaches them with the why —“this customer lowered the ticket three months in a row”—, it is left to their judgment to act, and the system records what happened afterward in order to learn. Auditable, explainable, theirs. An AI that instead scored the salespeople by how they “manage” their alerts would have reopened, multiplied, the distrust of the beginning.

And there the cycle reopens: the salesperson’s decision —called, recovered, lost— is the new data that sharpens the next reading. The value did not end in a dashboard; it returned to the person, and from the person it begins again.

What is decisive is not that these four steps exist —they exist in any serious project—, but that the same practice runs through them, without dropping the hypothesis at any edge. The reading of link 1 —“the problem is that the knowledge does not circulate because the incentive blocks it”— is the one that keeps governing in link 4. In a chain of specialists that hypothesis would have been lost at the first handover, and the project would have delivered, with impeccable technical neatness, the model that deep down no one had asked for.

Why continuity is the product

Each discipline exists in the market on its own. What is scarce is continuity:

The differential is not mastering four disciplines separately. It is that knowledge does not degrade at the edges, because there are no edges: the chain is traveled as an integrated practice, not as a succession of specialists who pass the problem along.

That is why, in the end, the method is not judged by the four disciplines it brings together, but by a single thing: whether the person at the beginning —the salesperson, the small-business owner, the employee who enters the data— ends up with more decision-making power than they had. If the loop closes in them, it worked. If it closes in a dashboard no one looks at, it was, once again, technology without reading. The four disciplines are the path; the person is the point of departure and of arrival.

See also: The thesis of the bridge · Concepts of our own · The bridge applied to small businesses · Bibliography