Who should decide what, and when should a decision escalate?

Assign each recurring decision to an accountable role and specify when consultation or escalation is required. Define triggers around authority, consequence, and cross-functional conflict so routine uncertainty does not send every choice to the CEO. Rehearse actual exceptions before relying on the table.

Decision authority is the agreed power of a role to make or approve a specific work choice. This practical definition does not determine legal rights. A relevant behavioral foundation is Emerson’s 1962 analysis, which discusses authority as legitimized power vested in roles. Formal powers and obligations must be checked against the applicable arrangements with qualified counsel.

Find the decisions that share the same queue

Composite scene: You answer routine approval messages from the sofa while an important customer exception waits among them. Managers have learned to ask you whenever an answer could be challenged later. You remain involved in ordinary choices, but cannot readily see which request exceeds an approved limit or creates a new obligation.

Start by separating the decision types. A routine adjustment inside an authorized scope differs from a proposed contractual change or a safety concern. A single instruction to escalate anything important does not explain the difference.

Ask managers why they escalate. They may lack authority, lack information, face conflicting instructions, or want protection from later criticism. Do not interpret all requests as unwillingness to decide. Identify which operating arrangement is missing.

Distinguish ownership, consultation, and approval

Ownership identifies who is accountable for bringing the decision to a usable conclusion and carrying its implementation responsibility. Consultation supplies relevant input. Approval authorizes a choice where a separate authority is required. Define these terms for your operating context rather than assuming everyone uses them alike.

A manager may own preparation of a proposal while another role approves a commitment. A technical specialist may advise without deciding the commercial tradeoff. Copying the CEO into a message should not silently transfer either responsibility.

Where formal governance, contractual, employment, or regulatory powers are involved, ask qualified counsel and relevant specialists to establish the actual limits. An internal table cannot override a binding duty or grant authority management does not possess.

The owner-and-escalation table method

1. List recurring decisions from actual work

Choose decisions that repeatedly create delay or confusion. Use a customer exception, capacity allocation, supplier change, or internal priority conflict as appropriate to your business. Record the decision itself rather than a broad department label.

Describe the ordinary case and a meaningful exception. Ask what managers currently do and which instruction they rely on. If different functions use different rules for the same shared decision, preserve that discrepancy for resolution instead of selecting the answer most convenient to the CEO.

2. Name an accountable operating owner

Assign the role that can obtain the needed information and make or route the choice within its authority. Confirm that the person occupying the role understands the responsibility and has access to the required work inputs.

Avoid joint ownership that leaves the final choice undefined. Several roles may contribute. If a decision needs a committee or board approval, specify who prepares the matter and which forum authorizes it. Do not invent a single-person approval where the governing arrangement requires something else.

3. Specify consultation and its limits

Name the input needed and who supplies it. Explain which facts the consulted role is responsible for confirming. Use realistic timing based on the work and any relevant duties, not a generic instruction to respond immediately.

State what happens if input is unavailable. The owner may need to defer, use an authorized interim instruction, or escalate. They should not assume silence means consent where explicit approval is required. Qualified owners must establish the actual arrangement.

4. Define observable escalation conditions

Use conditions managers can identify. Examples include a proposed commitment outside approved scope, a conflict between authorized priorities that the ordinary owner cannot resolve, or a matter requiring a different formal authority.

Keep urgent protective routes visible. Safety, security, legal, and other immediate concerns may require specialist or emergency handling rather than waiting in a routine approval queue. Have the appropriate qualified owners define those routes and any reporting duties.

5. Rehearse exceptions and revise the table

Give managers comparable hypothetical cases and ask what they would do, whom they would consult, and what instruction applies while the issue is unresolved. Compare the answers with the intended rule.

If the answers differ, inspect the wording and authority rather than immediately blaming judgment. A useful table should tell managers where a real conflict goes. Revise it through the proper owner and communicate which prior instruction it replaces.

Use a compact table with distinct questions

The following is a hypothetical format. Replace the examples with verified authority and requirements for your organization.

Decision type	Ordinary owner	Required input	Escalation trigger	Interim instruction
Customer request within approved scope	Authorized account role	Delivery feasibility	Scope or obligation would change	Follow the existing authorized commitment
Shared resource conflict	Designated operating owner	Affected work commitments	Two approved priorities cannot coexist	Preserve the current instruction pending authorized resolution
Proposed supplier term change	Authorized commercial owner	Relevant technical and legal review	Approval exceeds the role’s authority	Make no unapproved commitment

The table is an aid to a conversation, not a source of authority in itself. Add the actual escalation destination and record owner. Keep sensitive or specialist procedures in the proper controlled reference rather than compressing them into an unsafe shortcut.

Distinguish uncertainty from an authority exception

A manager can face uncertainty within a decision they are authorized to make. If every uncertain choice escalates, ownership disappears. Ask what evidence the role is expected to obtain and which judgment remains theirs after consultation.

An authority exception is different. The manager may know exactly what they recommend while lacking permission to commit the company. They should use the proper approval route rather than treating confidence as authorization.

In the customer example, uncertainty about delivery feasibility may require an operating assessment. A change to the customer’s contractual commitment may require a separate commercial and legal review. Give the manager a way to recognize both without asking them to provide legal advice.

Make the CEO’s private instruction obey the same route

A decision table fails if you routinely create exceptions through informal messages. When a colleague asks you to override an owner, identify the decision type and the applicable escalation condition. If you authorize a legitimate change, tell the affected owner and record the new instruction appropriately.

Do not require managers to defend a decision publicly while reversing it privately. That creates ambiguity about who decides and which record matters. Review your own bypasses alongside other exceptions.

Colquitt’s 2001 organizational-justice research distinguishes process fairness from outcomes, treatment, and explanations. As an application, ask whether similar requests use a comparable rule and receive an understandable reason. The study does not validate a particular ownership matrix.

Keep escalation safe enough to use

Edmondson’s 1999 research concerns interpersonal risk within teams. A relevant question is whether a manager can identify an actual authority gap without being criticized for escalating. That differs from requiring the CEO to decide every difficult matter.

Use proposed wording:

You own [decision type] within [verified authority]. Consult [role] for [input]. Escalate when [specific condition] applies. If you see a gap in the table, describe the decision and what makes the current instruction unusable. We will resolve the gap without pretending the table already answered it.

Do not promise that this wording guarantees psychological safety or better decision speed. Inspect how actual exceptions are treated and whether managers retain authority over the ordinary choices assigned to them.

Review a wrong turn without rewriting the rule afterward

Suppose a manager escalates a customer request that appeared routine. The review reveals that it created a commitment outside the role’s authority. Clarify the example and update the reference. Do not punish the person merely because the headline request sounded small.

Suppose a manager escalates an ordinary allocation because you previously reversed similar decisions without explanation. Examine your own practice before asking for greater ownership. The table may be clear while the operating signal is inconsistent.

Suppose a manager acts beyond authority despite a clear instruction and appropriate support. Use the relevant management process, with HR and counsel where employment consequences arise. Keep that conduct question separate from improving the table for everyone else.

Include an absence arrangement for a decision owner who is unavailable. Confirm who can act, which limits apply, and how the original owner receives the record. A manager should not have to choose between waiting indefinitely and assuming that any available senior person can authorize the exception.

Maintain ownership as roles change

Assign someone to keep the table current. A change in reporting, a new contract type, or a different approval arrangement may make an earlier entry inaccurate. Ask the proper authority to review the relevant change and tell affected managers what replaces the old rule.

Industrial/organizational psychology, the psychology of work and organizations, helps examine role expectations and group responses. The table remains an operating tool. It is not a psychological test or a complete governance document.

At an appropriate review, inspect ordinary decisions that stayed with their owners and exceptions that escalated. Ask whether the required input arrived and whether the final instruction reached the people doing the work. The useful outcome is authority that remains clear when the case becomes inconvenient, with a credible route for the exception the table did not foresee.