What to do this week
Move one recurring decision before you ask for more ownership.
Do not redesign the org chart. Start with one call that came back twice and make its authority visible.
Open the last five returns.
Use the actual Slack tags, copied emails, meeting notes, spend requests, and client exceptions. Memory will make the pattern cleaner than it was.
Name the repeated decision.
Do not write “operations” or “customer service.” Write the actual call: approve a replacement, adjust a deadline, choose a vendor, or accept an exception.
Write the boundary.
Name what the person can decide, the standard they should use, and the specific change that requires escalation.
Let the next call stand.
If the decision stays inside the boundary, do not quietly take it back because you would have chosen differently. Improve the standard after the result.
Use the team-solve versus owner-escalation worksheet to write the authority, required evidence, exception, and decision owner. The matrix also includes a completed example.
Check the next comparable decisions.
Keep a short record beside the original requests: what needed deciding, whether it fell inside the agreed boundary, who acted, how long the work waited, and whether it was completed. Compare the same kind of decision before and after the transfer.
For example, imagine three delivery requests. The manager resolves two within the permitted slots and escalates one that would create a new promise to the client. That is two independent decisions and one appropriate escalation. The owner still being involved does not make the transfer a failure.
If messages stop but the work sits unfinished, the transfer is not proven. Check which information, authority, or standard is still missing. If the manager acts outside the agreed boundary, review the decision and its consequences before widening that authority. Keep the boundary that worked and change the part the actual requests exposed.