MODRRELATIONAL DISTANCE
APPLIED TO ORGANIZATIONS · MANAGEMENT READING
Targets, deadlines, and satisfaction indicators show situated results. MODR helps examine the relationships in which expectations and deliveries meet, diverge, and recur.
By the end of this reading: you will be able to recognize different configurations, choose an observation boundary, and distinguish relational description from a management decision.
1 / QUESTIONS THAT DASHBOARDS LEAVE OPEN
A target may be met while expectations and experiences diverge in particular relationships.
Outcome measures and local indicators help managers, but may reveal little about the relationships that produced them.
A unit delivers on time, yet recipients consider its output insufficient. Another has a good average satisfaction score, while experiences vary greatly between teams. Indicators separated by department make it hard to see whether similar configurations recur across the organization.
It may also be difficult to locate where tensions concentrate: in a few relationships, across several interfaces, or in recurring experiences within the same relationship. MODR offers a common structure for observing those configurations and choosing questions for further inquiry.
Relational data can complement outcome and contextual measures. Their interpretation helps investigate causes, effects, and priorities, which depend on each organization's circumstances.
The examples on this page are constructed to explain analytical possibilities. They do not report observed organizational results.
2 / THREE WAYS TO EXPAND THE VIEW
These capacities work together while retaining each relationship's identity and the conditions under which its data were produced.
Expected and perceived values and their derived quantities describe relationships through a shared formal structure. This helps distinguish alignment from perceived level, even when distances are similar.
A possible question: do two equally aligned relationships also have similar perceived levels?
A common scale does not make distinct experiences substantively equivalent.
The structure can be used for academic, administrative, commercial, or inter-team relationships. An observation boundary can span several fronts while retaining each referent's meaning.
A possible question: which configurations recur across relationships in different areas?
A descriptive recurrence raises questions; it does not establish a shared cause.
Mean position shows where values lie; heterogeneity shows how much they differ. The boundary may encompass sets of poles while preserving source relationships and incoming or outgoing direction.
A possible question: does a team's average reflect similar experiences or conceal important differences?
Calculations begin with source relationships. Internal relationships are not external incoming or outgoing ties; group means do not automatically replace aggregation over source relationships.
Foundation: OTH7600, sections 7.5 and 7.8–7.12. The following examples show how these properties support diagnostic readings.
3 / SIX DIAGNOSTIC EXAMPLES
Open each example to see the situation, what the data distinguish, and a question for further inquiry. All values are fictional and normalized from 0 to 1.
Two relationships both have zero distance and coherence of 1. In one, expected and perceived values are both 0.20; in the other, both are 0.90.
| Configuration | Expected | Perceived | Coherence |
|---|---|---|---|
| A | 0.20 | 0.20 | 1.00 |
| B | 0.90 | 0.90 | 1.00 |
What this distinguishes: the agreement is the same, but perceived levels differ. High coherence alone does not describe a favorable condition.
Question to explore: what does alignment mean at this perceived level, given the relationship's purpose?
Consider two directed sets, each with four distinct relationships and compatible comparison conditions. Mean distance is the same, but distributions differ.
| Set | Four relationship distances | Mean M | Heterogeneity H |
|---|---|---|---|
| A | 0.30; 0.30; 0.30; 0.30 | 0.30 | 0.00 |
| B | 0.00; 0.00; 0.60; 0.60 | 0.30 | 0.60 |
What this distinguishes: all distances match in set A; set B contains aligned relationships and others with larger gaps. A mean alone hides this difference.
Question to explore: would one response suit the whole set, or should particular relationships be examined?
A university could observe Professor → Student, Administration → Student, and Coordination → Professor, specifying referents and measurement conditions for each direction.
What this distinguishes: a common representation permits checking whether configurations of agreement and perception recur across different functions while retaining the particulars of teaching, service, and coordination.
Question to explore: do similar configurations reflect similar experiences or circumstances specific to each area?
Comparison does not automatically rank areas or establish one common cause.
In Manager → Employee, the employee assesses what they receive from the manager. In Employee → Manager, the manager assesses what they receive from the employee. Each direction has its own expected and perceived values.
What this distinguishes: the two directions may have different configurations. One assessment cannot be inferred from the other or merged into a single score.
Question to explore: what expectations and experiences might clarify the difference between these perspectives?
Across successive observations of the same relationship, with comparable referents and procedures, distance may stay constant even when expected and perceived values change.
| Observation | Expected | Perceived | Distance |
|---|---|---|---|
| Time 1 | 0.80 | 0.50 | 0.30 |
| Time 2 | 0.50 | 0.20 | 0.30 |
What this distinguishes: the gap has the same magnitude, but both components have shifted. In this example, perceived level declined.
Question to explore: what changed in the experience and expectation over time?
The trajectory describes change; on its own, it does not demonstrate an intervention's effect.
Administration → Student can be observed for distinct requests. Each event retains its identifier, assessed referent, and expected and perceived values.
What this distinguishes: observations of the same relationship may vary by type of request or time. Event-based boundaries reveal such experiences without losing their origin.
Question to explore: in which experiences do the differences appear, and what conditions should be examined?
Event count and relationship count differ. Canonical relationship aggregation requires an explicit selected or synthesized state for each relationship; more records do not implicitly add weight.
4 / FROM READING TO ACTION
Relational description shows what was observed. Significance, priority, and action require organizational criteria, other evidence, and defined responsibilities.
Establish states and aggregates, retaining components, direction, and source relationships.
Examine the configuration's significance for organizational objectives and conditions.
Investigate cases that need clarification before deciding on action.
Choose compatible action and return to observation with explicit comparison conditions.
MIT9750 distinguishes compatibility assessment from operational preparation. First examine relationship identity and direction, the recipient's evaluative capacity, referent correspondence, how components are obtained, observational boundaries, and conformity of operations. Then specify purpose, instruments, state selection or synthesis, aggregation, protection, and traceability.
These artifacts support decisions before implementation. Governance assessment belongs to MIT7625 and is distinct from this preparation.
AET9760 proposes selective AI-assisted contextual inquiry for cases already referred by governance. LBD9755 proposes incremental recognition of patterns in multi-relational event profiles. These architectures may expand inquiry and analysis, but their reliability and organizational usefulness still require evaluation.
END OF THIS READING
You explored MODR's properties, six diagnostic examples, and the distinction between observation, assessment, and decisions.
References for this page: OTH7600; MIT7625; MIT9750; AET9760; LBD9755. Constructed examples for teaching. All papers appear under Published Papers in the main menu.
Back to the home page