Tensions in Practice: Local methods and shared commitments¶
A network of local service teams
Imagine local teams that jointly promise a service to users. The network can set both the promise and the method, each team can set both for itself, or authority can be split by decision type. These arrangements change who governs the work. Giving teams freedom over methods does not give them authority to change the shared promise.
Use local judgment
Let teams govern decisions for which local knowledge and local ownership matter.
Keep joint commitments coherent
Let the network make and uphold promises that depend on more than one team.
Why these aims pull against each other
A decision cannot simultaneously belong entirely to a local team and entirely to the network. Moving its boundary changes what the other level is allowed to decide.
Choose an arrangement to see what changes and what remains difficult.
Arrows show the stated work, authority, or access paths. Position, length, and color do not measure time, risk, cost, or performance.
What this choice protects
What it costs
When it fits
Compare the arrangements
Network sets both
The network sets a shared service promise and directs the method teams must use.
- What it protects
- The network can align implementation when a common method is necessary for the joint commitment.
- What it costs
- Teams cannot change the method on their own even when local circumstances suggest a better fit.
- When it fits
- Plausible where interdependence requires common methods and the network has enough local information to specify them well.
Illustration note: This service-network arrangement applies the source boundary concepts. It does not claim central direction is generally more effective.
Teams set both
Each team chooses its local service promise and how to deliver it. The network has no authority to impose a common promise in this arrangement.
- What it protects
- Teams can adapt both ends and means to their own users and circumstances.
- What it costs
- A user crossing team boundaries cannot assume a shared commitment; one team cannot bind another to its choice.
- When it fits
- Plausible when work is sufficiently separable and local differences are acceptable to users.
Illustration note: The two-team diagram is an editorial contrast that removes the shared decision right. Different promises are possible, not inevitable.
Split the rights
The network owns the shared promise. Each team owns its method within that promise; a method change cannot silently redefine the promised service.
- What it protects
- The common commitment can coexist with local choice over how to deliver it.
- What it costs
- Teams still cannot change the ends unilaterally. Boundary disputes remain when a purported method change alters the promise.
- When it fits
- Plausible when ends and means can be separated clearly enough to assign decision rights and resolve disputed boundaries.
Illustration note: This is scoped discretion over how, not complete local self-government. It applies Autonomy T2 and does not eliminate the conflict in T1.
What this illustration does—and does not—establish
Autonomy: Local versus Global Autonomy (Scalar Nesting) and Autonomy: Scope versus Depth (Decomposition Axis) supply the nested-authority conflict and the scope/depth distinction. The service promise is an invented concrete decision boundary.
- The arrows show authority, not the flow of service work or evidence of successful performance.
- Freedom over methods can coexist with shallow autonomy over goals. The split arrangement does not grant total self-government.
- The diagram does not establish which level has the best information, whose values should prevail, or whether a boundary will survive a change in leadership.
Source entries
Autonomy
Autonomy: Local versus Global Autonomy (Scalar Nesting) explains conflicts across nested levels. Autonomy: Scope versus Depth (Decomposition Axis) separates the scope of a decision from how deeply a unit controls it.
T1
T1 — Local versus Global Autonomy (Scalar Nesting). A unit's autonomy always bounds the autonomy of its parts and its superordinate; granting a region self-government constrains both the towns inside it and the federation around it. The tension is that autonomy does not aggregate freely up or down the hierarchy. The failure mode is *single-level advocacy*: maximizing one tier's self-government while silently expropriating the level above or below, producing incoherence the local frame cannot see. Diagnostic: trace the same decision class up and down the nesting; if expanding this unit's scope removes a decision another unit was relying on governing, the boundaries conflict and the trade-off must be made explicit rather than resolved by default in favor of the salient level.
T2
T2 — Scope versus Depth (Decomposition Axis). Autonomy varies on two independent axes — which class of decisions falls inside (scope) and which kinds within that class (depth) — and collapsing them produces design error. The failure mode is *all-or-nothing delegation*: "give them autonomy" read as total self-government, when the workable design is deep discretion over *how* paired with central control over *what*. Diagnostic: before granting or removing autonomy, specify scope and depth separately; if a request or grant names only "autonomy" without saying over which decisions and to what depth, it is underspecified and will be filled in arbitrarily, usually too broadly or too narrowly.