MODRRELATIONAL DISTANCE WORK
Language
PT-BREN-US

UNDERSTAND MODR

MODR, step by step.

Think of a service you received. What did you expect? How did you perceive what was delivered?

1 / WHO EVALUATES

The recipient evaluates the relationship.

One relationship, two judgments by the customer Service is directed to the customer. The customer forms expected and perceived judgments about the same experience. ONE RELATIONSHIP · TWO JUDGMENTS Service source · A Customer receives · B E Expected P Perceived Same referent · same experience

In the direction A → B, the customer forms both judgments about the service. Reversing the direction gives us another relationship and another point of view, which require their own observation.

MODR calls each participant in this configuration a pole. A pole may be a person, a team, an organization, or a non-human entity when evaluations can be associated with its relationships.

Expected is the expectation actually formed about that relationship. Perceived is the assessment of what was received or experienced. Both must address the same referent under compatible conditions.

Expecting something is different from wishing for an ideal. Evaluating a relationship is different from giving a general score to a person or an organization.

2 / EXPLORE THREE CONTEXTS

What the values let us observe.

Compare three hypothetical contexts. The values are normalized from 0 to 1; each relationship keeps its own expected and perceived assessments.

01 / CUSTOMER SERVICE

ORGANIZATION SERVICE

One experience,
from the customer's perspective.

What the customer expected to receive in this relationship.

How the customer perceived what was received.

WHAT THESE VALUES SHOW

Distance · Δ0.30|P − E| · magnitude of the gap
Coherence · C0.701 − Δ · agreement between values
Perceived quality · Q0.50P · perceived level
Compare illustrative configurations

HYPOTHETICAL GOVERNANCE CONTEXT

Ticket closed without a solution

The customer asks for an incorrect charge to be fixed before month-end. Support promises a reply within two days, then closes the ticket without correcting the charge; the customer perceives the message as brusque.

Qualification
The gap may deserve priority if the charge affects the customer or unresolved closures recur.
Contextual deepening
Check the promised deadline, ticket history, charge, and how the message was perceived.
Intervention
If the failure is confirmed, fix the charge, review ticket closure, and monitor new cases.

OTH7600 grounds the structural reading; MIT7625 (MIT I) proposes the governance phases. Situations, criteria, and proposed actions are hypothetical.

02 / ACROSS DEPARTMENTS

One employee evaluates a colleague in another department.

Sales assesses the handoff received from Operations for a specific order. This relationship and point of view differ from customer service.

CROSS-DEPARTMENT HANDOFF

A handoff between colleagues.

What the sales colleague expected from this handoff.

How she assessed the information received.

WHAT THESE VALUES SHOW

Distance · Δ0.30|P − E| · magnitude of the gap
Coherence · C0.701 − Δ · agreement between values
Perceived quality · Q0.50P · perceived level
Compare illustrative configurations

HYPOTHETICAL GOVERNANCE CONTEXT

The missing status update

A sales colleague expects Operations to confirm an order's dispatch before calling the customer. The update arrives late and omits a known delay, leaving Sales to make a promise it cannot keep.

Qualification
The gap may matter if missed handoffs affect customer commitments or recur across teams.
Contextual deepening
Check the agreed handoff, event timestamps, available information, and both colleagues' accounts.
Intervention
If the breakdown is confirmed, clarify who updates the order status, when, and how exceptions are flagged.

A hypothetical illustration of the governance phases proposed in MIT7625 (MIT I).

03 / DIGITAL ACQUISITION · LBD9755

A consumer evaluates an acquisition.

Purchase, delivery, and product are three relationships evaluated by the same consumer. Each retains its own expected and perceived values.

ONE ACQUIRED ITEM · THREE RELATIONSHIPS

Explore the acquisition profile.

RELATIONSHIP 01

Purchase

Distance · Δ 0.05 Coherence · C 0.95 Perceived quality · Q 0.85

RELATIONSHIP 02

Delivery

Distance · Δ 0.50 Coherence · C 0.50 Perceived quality · Q 0.35

RELATIONSHIP 03

Product

Distance · Δ 0.02 Coherence · C 0.98 Perceived quality · Q 0.82
Compare four hypothetical situations

HYPOTHETICAL GOVERNANCE CONTEXT

Delivery disrupts the experience

The consumer completes the purchase easily and likes the product, but the parcel arrives after the date on which it was needed as a gift.

Qualification
The gap is concentrated in delivery. Favorable purchase and product assessments do not erase what happened in transit.
Contextual deepening
Check the promised date, logistics events, and the importance of timing to the consumer; compare similar acquisitions.
Intervention
If similar delays are confirmed, review risk notices, delivery promises, and incident handling with the logistics operator.

LBD9755 structures the acquisition's three relationships; the governance phases follow MIT7625 (MIT I). Scenarios and actions are hypothetical.

In LBD9755, the profile preserves all three relationships. One acquisition illustrates the reading; detecting patterns requires comparable observations across events.

For each relationship, C = 1 − Δ reexpresses distance. Reading it with perceived quality separates alignment from level: E = P = 0.20 and E = P = 0.90 both have zero distance but different perceived values. In an acquisition, each of the three relationships keeps its own values. No isolated result determines a decision.

3 / SITUATE THE EXPERIENCE

One relationship, distinct observations.

A relationship may have successive records. A period or event defines the experience assessed in each observation.

BY PERIOD

Service over a month.

A customer assesses the relationship with an administrative office during September. A later observation may refer to October, provided the conditions for comparison are stated.

Septemberobservation 1Octoberobservation 2
BY EVENT

Service for one request.

The assessment refers to an identified request. Another request creates another observation even if the poles of the relationship are unchanged.

Request 01one eventRequest 02another event

Two records of the same relationship are two observations. They do not automatically become two distinct relationships in an aggregation.

4 / INTERPRET WITH CARE

What the numbers cannot decide alone.

Does MODR measure satisfaction?

Its object is the state of a directed relationship, represented by expectation, perception, and derived quantities. Satisfaction has its own concepts and instruments; relational distance is not a synonym for it.

Does a larger distance mean a larger problem?

Distance describes the magnitude of a gap. Its significance depends on the relationship, expected and perceived levels, purpose, and organizational context.

Does an average tell the whole story?

The same average may summarize very different relationships. MODR pairs average position with heterogeneity while retaining the relationships from which the aggregate came.

Is a value above expectations always better?

The direction of the difference is descriptive. Interpretation requires understanding what was expected, what was perceived, and what the delivery means in context.

Why use a network in the visual identity?

The model admits multiple poles and directed relationships. The network represents that multiplicity; each relationship retains its identity, components, and evaluative point of view.