The problem that returns under another name
A commercial proposal is approved, but operations later discovers that it cannot be delivered under the conditions that were offered. The case is corrected, the client is contacted and greater care is requested. Two weeks later it happens again. The salesperson, the service and the urgency are different. The structure of the problem remains.
The organisation can interpret each episode as a different error. It can also observe something more precise: the transition between offer prepared and commitment assumed does not close sufficiently. Sales checks one set of conditions; operations needs another; nobody verifies the whole before the company becomes bound.
That is structural friction. It is not just any tension or any error. It is the signal that a form is not reliably producing the subsequent state that the organisation declares it has reached.
Friction appears where the company has to add energy again and again to obtain a closure that its own form does not know how to produce.
Friction does not mean conflict
A company contains legitimate disagreements, human error, breaches and unforeseen events. E³ does not erase them by placing everything under a structural explanation.
It is useful to distinguish:
- Isolated error: execution fails within a sufficiently defined function.
- Legitimate conflict: two incompatible positions require a decision, negotiation or priority rule.
- Conscious breach: a person knows the applicable criterion, has the capacity to comply and decides not to do so.
- Structural friction: the same transition repeatedly produces reopenings, incompatible interpretations or recurring compensation because its form is insufficient.
The distinction matters. If the company treats as indiscipline what the system has not defined, it punishes the person carrying the ambiguity. If every breach is called a “design problem”, structure becomes an excuse. Structural review precedes attribution; it does not remove attribution when attribution is appropriate.
Signals that justify a review
A single incident may be enough when a serious risk is involved. In other cases, friction is usually recognised through accumulation:
- something declared closed reopens;
- the result depends on later clarifications;
- different areas use different criteria for the same state;
- one particular person always has to intervene at the end;
- parallel records appear “just in case”;
- exceptions stop being exceptional;
- technology accelerates the flow but does not reduce disputes;
- the result consumes more coordination each time it is repeated.
No single signal proves a cause. It activates a question: which function was trying to close, and what had to be true at the end?
From symptom to function
Review begins by delimiting, not explaining. “There are problems between sales and operations” is too broad. “Accept an offer that the company can deliver under the committed conditions” already names a transformation.
To begin the review, five questions are enough:
- Affected function. What specific transformation is the company trying to perform?
- Committed subsequent state. What is declared closed and later fails to remain closed?
- Evidence. Which reopenings, delays, corrections or dependencies show it?
- Scope. Which people, areas, systems or third parties receive the effects?
- Risk. What happens if the form remains unchanged?
The first sheet should not yet contain the solution. Its purpose is to prevent a quick interpretation from closing the investigation before the transition has been located.
Review the form before increasing control
The usual response to friction is to add supervision, approvals or reports. That may temporarily contain risk, but it may also hide the cause.
E³ proposes a different order:
- delimit the actually existing prior state;
- specify the subsequent state that is meant to be reached;
- identify who may declare closure and on the basis of what evidence;
- reconstruct the effective form, including what is absent from the formal procedure;
- listen to those who produce, receive or carry the transition;
- compare hypotheses: insufficient design, lack of capacity, conflict, exception or breach;
- intervene with the minimum sufficient modification;
- test and integrate the adjustment if it works.
The review does not require the company to stop operating. It can start with one function and a small number of cases. The unit of work is not the department or the whole organisation: it is the transition whose closure has lost sufficiency.
The activation sheet
| Field | Minimum content |
|---|---|
| Candidate function | Verb and transformation: “approve an executable offer” |
| Declared subsequent state | What the company says is already true |
| Observed friction | Reopening, compensation, contradiction, delay or risk |
| Evidence | Cases, records, communications or verifiable results |
| Affected systems | Who executes, receives, decides, controls or carries effects |
| Initial scope | Which specific part is reviewed and what remains outside |
| Decision | Review now, observe further or treat as an isolated incident |
The sheet does not look for culprits and does not certify a cause. It opens the problem correctly.
The limit of structural review
E³ does not promise that all friction can be eliminated. Some tensions belong to the activity itself, to uncertainty or to the simultaneous existence of legitimate interests. Nor does it assume that every transition should be formalised. Explicit structure is justified only where weight, repetition, risk or propagation capacity makes it worthwhile.
The next step is to understand what is being reviewed when a transition is reviewed. That requires abandoning a widespread reduction: form is not the organisation chart or the drawn process. It is the effective configuration that makes closure happen as it actually happens.