Article
Accountability Without Authority Is a Setup
If someone owns an outcome but cannot make the decisions, access the information, spend the budget, or escalate the exception, the business has assigned blame—not accountability.
DISC can affect how the mismatch appears:
- Stronger Drive may push past the boundary or repeatedly seek control
- Stronger Connect may negotiate informally through relationships
- Stronger Sustain may carry the problem quietly to protect service
- Stronger Verify may stop and request formal approval or evidence
None of those reactions fixes the design.
Define five parts of ownership
Outcome: What must be true?
Authority: What may the owner decide, change, access, or spend?
Standard: Which boundaries remain mandatory?
Escalation: Which condition transfers or raises the decision?
Evidence: How will the result be reviewed?
Example:
Outcome: Resolve standard customer credits within one business day. Authority: Service leads may approve up to $250 under the published reasons. Standard: Credits cannot bypass identity verification. Escalation: Suspected fraud or totals above $250 go to Finance. Evidence: Weekly sample review and exception log.
This lets different styles operate without guessing what ownership means.
The owner's bottleneck
Owners often retain authority because exceptions once went badly. The result is a queue in which capable people wait, customers wait, and the owner works inside every decision.
Move from universal approval to thresholds, sampling, and exceptions. Keep high-consequence decisions controlled while allowing compliant routine work to move.
BOS connection
This is primarily Control, supported by Information and Operations. The authority rule must be findable, the workflow must route exceptions, and Intelligence must show whether delegation works.
Try this: Choose one repeated approval. Define the amount, risk, or condition below which a named owner may decide without you.
Related terms: Accountability · Authority · Control · Delegation · Exception