Reasonable decisions. A difficult collective outcome.
Competent people can work within functioning departments, follow established procedures and make reasonable decisions while the organisation struggles to deliver.
An industrial organisational setting brought this tension into focus. Looking at individual performance offered only part of the picture. The architectural question concerned the arrangement connecting responsibilities, capabilities, dependencies and authority: did it preserve the conditions required for the collective outcome?
Responsibility must remain connected to capability
Responsibility for an outcome and the capability to deliver it can sit on different sides of an organisational boundary. An accountable function may depend on expertise, capacity or information controlled elsewhere. Each function can act reasonably within its mandate while the dependency remains unresolved.
Communication can make the dependency known. It cannot, by itself, give anyone authority to resolve competing priorities or commit the necessary capability. Accountability becomes difficult to exercise when it reaches further than the decision rights attached to it.
Meaning can also weaken at the boundary. A request may arrive without the assumptions, uncertainty or consequences that made it important. The receiving function then makes a locally sensible decision using a narrower view of the situation.
Coordination, integration and coherence
Coordination asks who needs to communicate with whom.
Integration asks what capabilities, responsibilities, information and dependencies must remain connected across boundaries.
Coherence asks whether the resulting arrangement still supports the organisation’s intended outcome.
These questions explain why more coordination may leave the underlying difficulty intact. People can exchange updates frequently while the authority to allocate capacity, resolve a conflict or reconsider a boundary remains elsewhere. Functional performance indicators may confirm that assigned activities are complete without showing whether the whole still has what it needs to succeed.
The function can succeed while the conditions fail
A function can perform its assigned work correctly while the organisation loses the conditions required for collective success.
Escalation can temporarily bridge the gap. Someone obtains an exception, negotiates a priority or carries context across a handoff. Under operational pressure, that effort may keep work moving while leaving the same dependency for the next case.
The architectural distinction is between completing an action and preserving the conditions that make its intended consequence achievable. It directs attention to where responsibility, capability and authority need to meet.
What decision-makers can reconsider
Before demanding better communication, stronger individual performance or another leadership intervention, ask whether the organisational arrangement makes the desired outcome achievable.
Which capability does the outcome depend on? Who can commit it? What context must survive the handoff? Who can resolve incompatible priorities? When repeated escalation reveals the same gap, who has legitimate authority to reopen the arrangement itself?
These questions give decision-makers a clearer basis for reconsidering responsibilities, dependencies and decision boundaries. They also distinguish a problem within a function from a problem produced by the way functions are connected.