Concepts of our own: the vocabulary of the bridge

These are the terms with which the paradigm thinks and writes. They are not textbook definitions: they are operational senses, sharpened for the work. When a term has an academic owner, it is noted and referred to Authors and currents.

Naming well is not an academic luxury. On ground where business and technique misunderstand each other all the time —the same words for different things—, a precise vocabulary is already half the translation done. Each term below is a tool: it names something that, without the word, was overlooked.

If you read The four links, you already saw several of these terms in action at Distribuidora Norte —knowledge that did not circulate among salespeople, a “last purchase” field that each branch understood differently—. Here they are defined sharply for reference; in the case narrative they appear in context. The two readings complement each other: the story teaches the method, the vocabulary sharpens it.

Core terms

Sociotechnical bridge

The paradigm —and the practice that embodies it— that integrates the competence to read the human fabric of an organization with that of building its technical system, without delegating either of the two. It is not coordinating two specialists (that is project management): it is a single competence that embodies the translation instead of outsourcing it. → The thesis of the bridge

Translation in flesh and blood

The operational version of translation from actor-network theory.¹ In the theory, to translate is to align the interests of the actors so that an artifact stabilizes. “In flesh and blood” means that it is not done by a process nor by a requirements document passed from hand to hand, but by an integrated practice that preserves the meaning of the human problem all the way to the code. It stops being a step —which degrades at every handover— to become a continuous practice.

Translation gap

The structural hollow in the market between those who understand people but do not build, and those who build but do not read people. There the digital transformation projects die; that is the space the bridge occupies. → The thesis of the bridge

The loop of the four links

The method: sociology of organizations → software engineering → data engineering → AI architecture and governance → and back to the person. What is distinctive is not the four disciplines (they exist loose in the market) but that they form a closed cycle without handovers, so that the sociological hypothesis is not lost at the edges. → The four links

Sociotechnical diagnosis

The deliverable of the first link and the condition of everything else: a reading of the organization before touching the technology, which separates the declared problem from the real one, maps power, incentives and resistances, and rules on where AI pays off and where it only destroys value. → The diagnostic method

Integrated pre-sales

What the software industry calls pre-sales —the technical work that happens before a client signs: eliciting the problem, designing a credible solution, sizing it and proposing it— carried out by the same person who will later build it, not by a salesperson who scopes and promises only to hand the engagement off to a delivery team. The paradigm holds a precise thesis about that moment: committing scope and price is where the translation gap is paid for most dearly, because the mismatch does not surface in a minor requirement but in what was promised. When whoever sells is not whoever builds, the hypothesis about the organization is translated twice —from client to salesperson, from salesperson to engineer— and degrades exactly where what will be delivered is set. Integrated pre-sales is translation in flesh and blood applied to the commercial phase: its four moments —discovery, solution design, scoping and proposal— are not a sales funnel but the commercial face of the diagnosis, with the honesty of saying “not here” as part of the scope. → The diagnostic method

Sociotechnical maturity

The degree to which an organization is ready for AI to add to it instead of subtracting from it. It is not measured only by infrastructure: it is multidimensional —strategy, culture, talent, governance and data quality—, an idea anchored in the research on AI readiness,² whose categories the IMIA model adapts and expands to make them measurable —its definition lives in IMIA, the maturity instrument—. Measuring maturity first is rule number one of the method.

From silo to architecture

Most organizations do not reach AI from an excess of failed technology, but from scarcity: management in spreadsheets, data in silos with no interconnection, manual processes, decisions without evidence. The real and today attainable opportunity is a constructive arc: connect the silos, raise an information architecture, govern the data, and only then add agents and AI where the organization is ready. The counterintuitive nuance: starting from little or no digitization does not reduce the risk, it concentrates it, because it forces building the technical subsystem and the human one at the same time —exactly what the bridge knows how to do—. → The bridge applied to small businesses

The adoption ladder

If from silo to architecture says where an organization starts from, the ladder says toward where it climbs, and that one climbs one step at a time: from the everyday office work to the systems that order the operation, from there to the AI that anticipates instead of merely recording and, on today’s step, to the agents that no longer suggest but execute end to end. What matters is not the inventory of steps, but its slope: the higher one climbs, the dearer the cost of having skipped the human reading. At the bottom, a badly-understood system is avoided —people go back to their spreadsheet—; at the top, a process no one understood is not executed more slowly, it is executed on its own, at scale and with no witness. That is why the paradigm does not age with the technology: each new step makes it more necessary, not less. → IMIA, the maturity instrument

Analytical ladder

Parallel to the technology adoption ladder, data also climbs step by step. First comes the descriptive: what happened —how much we sold, how many orders. Then the diagnostic: why — which product fell, which branch diverged. Higher up the predictive: what will happen —which customer will leave, which stock will run out. At the top the prescriptive: what to do —replenish this, call that customer.

Many organizations believe they are at predictive because they bought an AI tool, but in practice they operate on poor descriptive: each area calculates “sales” differently and no one audits definitions. Buying predictive on broken descriptive only automates the error faster, with a prettier chart. The diagnosis must name the real analytical step before promising models. → Value metrics

Institutional memory

Before talking about data architecture you need something more basic: the organization must give consistent answers to questions that repeat every week. “How many active customers do we have?” should not return three different numbers depending on who asks. Spreadsheets that circulate by email, answers that “live in Juan’s head” and Excel versions no one knows which is current are not lack of technology: they are lack of reliable memory. Modeling on top of that —even in the most expensive cloud— only exports disorder to a more visible place.

Warning terms (what the thesis combats)

Automating the error faster

What happens when technology is mounted on a broken process or dirty data: the problem is not fixed, it is executed at greater speed and scale. It sums up why order matters: first understand, then automate.

The data that lies

A technically “correct” piece of data (well typed, no nulls) that nevertheless does not say what people believe it says, because its meaning depends on a human context that was lost —the “status” field that for one team means collections and for another, shipping—. It operationalizes Wang & Strong’s idea³: data quality is contextual and fitness-for-use, not an isolated technical attribute. Almost always, a data that lies is the mark of a badly-incentivized human process. → Authors and currents

Sociotechnical debt

By analogy with technical debt: the liability that accumulates each time technology is installed without resolving the social subsystem (resistances not worked through, processes not understood, users not involved). It does not appear in the code, but it is collected in null adoption, sabotage and rejection. It is invisible until the “perfect” system goes unused by everyone. And like all debt, it accrues interest: the later it is recognized, the more expensive it is to settle the human subsystem that had been skipped.

Erosion of the scaffold

The silent decay of the path by which an organization forms its own experts, when AI takes over the entry-level tasks —the “easy” ones— that were the novice’s practice ground. It is not automation unemployment, which is seen and debated: it is a loss of future capacity that no usage metric registers, because productivity improves while the scaffold falls. Academic owner: Beane, with the three C’s of craft learning —challenge, complexity, connection—. It is a design risk, not a destiny: the novice’s challenge can be deliberately preserved. → Psychology of adoption

Shadow AI (symptom, not crime)

The ungoverned use of generative AI tools outside any policy, often with internal data. Against the security framing —a risk to ban—, the paradigm reads it as a diagnostic symptom: the same old workaround, now with a language model instead of a parallel spreadsheet, and like any workaround it is latent demand made visible. The answer is not to ban but to read the need and govern it: inventory use cases, classify risk, channel toward governed alternatives. It turns shadow AI from a risk into an adoption roadmap. → Sociotechnical hygiene

The pre-sales handoff

The common pattern in consulting where whoever sells and sizes is not whoever builds: someone closes scope, price and promise, and only then passes the project to a delivery team that never listened to the client. It is the translation gap in its most expensive form, because the mismatch is fixed in the commitment —what was promised, on what budget and timeline—. The symptom repeats: in the first week, the team that builds discovers that what was sold is not what the organization needed, and the contract is already signed. The bridge’s answer is not to separate the promise from the construction. → integrated pre-sales

Technological solutionism

The belief that every social or organizational problem has a buyable solution in the form of a tool. The direct antithesis of the bridge: it confuses having the technology with solving the problem. (A term in wide use, adopted as a recurring target, not as an invention of our own.)

Vanity metric vs. value metric

The vanity metric measures what is easy to measure and what looks good on a dashboard (number of models, registered users, “AI usage”). The value metric measures what changes the day of the person in link 1: an hour freed, a better decision, a gap that closes. The bridge measures value.

Metric anarchy

When each area calculates the same magnitude differently and two dashboards officialize two different truths, there is no tool failure: there is absent governance of meaning. Sales for commercial is not the same as billing for administration, and if no one agrees, any new dashboard only adds a third version of the truth. The cure is not a prettier chart: it is naming an owner for each indicator, defining in one sentence what each number means, and retiring KPIs no one uses to decide. → Value metrics

Agile theatre

Rituals without increment or learning: the daily that changes nothing, the sprint that ends in a demo no one uses, the retrospective where everyone nods. That is agile in name only: the organization adopted the vocabulary without adopting the method. The antidote is not more meetings but three concrete things: a shared Definition of Done (finished = usable in operations), reviews where real operators participate —not only the technical team— and a Product Owner who can prioritize within forty-eight hours when needed. → The four links

Technological lock-in

Vendor dependence that makes exit costly —or impossible. Before signing, the verdict asks three simple questions: can we export our data if we leave? who owns the code that differentiates us? what happens if the vendor raises prices forty percent next year? If the answers are uncomfortable, the problem is not technical: it is negotiation and contract design.

Value terms (the promise)

Value in the person, not in the model

The measurement principle of the fourth link: the deliverable is never a model, it is a better human decision. An impeccable model that changes no decision is worth zero; a modest system that returns an hour a day to a team is worth a great deal.

AI as an extension of judgment (not as a substitute)

The position on the role of AI, above all in the State: it does not replace the worker (the public servant, the small business), it amplifies their judgment. Good AI returns decision-making power to the person; bad AI takes it away and leaves them out. Basis: human-centered AI.⁴ → The bridge applied to the public sector

Judgment in the design, not in every transaction

How AI as an extension of judgment survives when the software stops suggesting and moves to executing on its own. If an agent approves a refund, routes a complaint or prioritizes a case file without anyone looking at each case, the old “human in the loop” —a person reviewing one decision at a time— stops being possible, and at scale stops being desirable. Judgment does not disappear: it moves elsewhere. It goes from filtering decisions to defining, auditing and being able to revoke the rules with which the agent decides —what it does on its own, where it has to escalate to a person, what it leaves on the record for review—. The extension of judgment becomes the governance of judgment. It is the answer to whoever fears that agentic AI will make the human reading obsolete: it makes it more necessary, because without auditable rules autonomy is not extended judgment, it is delegation in the dark.

Context as an organizational asset

The context an AI agent needs to operate with judgment is not a technical artifact manufactured at the end: it is the institutional memory and the bilingual glossary the method builds from the first link. Hence a proposition with diagnostic bite: the organization that cannot explain its process to a person cannot package it as context for an agent either. Organizational illegibility, once paid for in zero adoption, is now also paid for in the impossibility of delegating. It inverts the usual order: one does not start with the agent and then “give it context”; one first builds the legibility of the organization —the bridge’s work— and that legibility is the context. → The agentic extension

Closing the gap (not just delivering profit)

The definition of economic value used for small businesses and the State: the result is not only one client’s gain, it is shortening the distance between the few who already use AI and the rest of the productive fabric. In Latin America, with AI penetration below 4%,⁵ that gap is the opportunity and the mission at once. → The bridge applied to small businesses

AI as a multiplier with a sign

The synthesis that reconciles two assertions that seem to clash: the mission is to close the gap, but the evidence shows that badly-applied AI widens it. They do not contradict each other. AI is a multiplier of what it finds: on order and judgment, it multiplies value; on disorder and without a judgment to filter it, it multiplies the harm —in the Kenya experiment it helped those already doing well and sank those doing badly—.⁶ What decides the sign is not the power of the model, but the human reading that orients it. That is why the bridge is not an ethical add-on: it is, literally, what sets the sign.

Process terms (SME context)

Maturity measured by IMIA and the adoption ladder give direction and a snapshot in time. In SMEs, real configuration is often reversible without sociotechnical hygiene: alignment between technical and social subsystems is not a one-time destination but windows that open and close. Amanollahnejad et al. (2026), in a qualitative study of 27 UK SMEs grounded in STST, call this episodic alignment: bursts of progress when there is sponsorship, reliable data and a pilot that worked; rollback when management changes, the key person leaves or patches stop holding. Geographic caveat: UK 2023–2024; the mechanism helps thinking, not automatic prediction for Latin America.

Operational terms the diagnosis uses:

• Productive misalignment. Friction is not always to be eliminated: it sometimes exposes ambiguous roles or unreliable data —distinct from toxic misalignment (automating error, ignoring valid resistance).
• Culture-strategy misalignment. Incoherence between what strategy declares and what culture rewards in practice —punishing error, ritual compliance—. Distinct from productive misalignment (friction that teaches). Technology advances in demo and dies in operations (Gupta et al., 2020; Shokrollahi Yancheshmeh, 2026).
• Sociotechnical bricolage. Improvised integration —exporting a spreadsheet, re-keying data by hand, patching two systems together— as how resource-constrained firms keep operating. Not shame: a signal of how far to automate before connecting properly.
• Organized epistemic uncertainty. Beyond the data that lies: the organization has no agreement on which evidence to use when a decision is irreversible. If three people would give three different numbers for the same question, it is not yet time to model.
• Champion dependency. All digital momentum tied to one person, with no backup or documentation that survives if they leave.
• Scale misfit. Copying a large-firm solution or generic guide and worsening your own operations because the context is not the same.
• Coffee economy. Legitimate decisions made in relationship —at the counter, on the call, over coffee with the supplier—; standardizing everything for an algorithm can feel like losing what makes the SME valuable.

None of these terms is a theoretical ornament. They are the way not to lose sight, amid the jargon, of what is being done and for whom. They all return, sooner or later, to the same question: does this serve the person on the other side? A vocabulary that did not answer that would be, itself, another way of automating the error faster.

See also: The thesis of the bridge · The four links · The diagnostic method · Bibliography