Issue No. 8 · September 30, 2026
TL;DR
Most stuck work isn't hard. It's just nobody's. Give one workflow one clear owner before Q4, and watch how fast "someone should really fix that" turns into "handled."
Hey there, Ops Connectors... how's everybody connecting the dots this week?
This month we've been diagnosing: your bottleneck, your handoffs. Here's the last diagnostic before we start fixing things in October, and it's the fastest one you can run.
Ask "who owns this?" about any workflow in your business and watch what happens. If you get one confident name, ownership is at least clear. If you get "well, it depends," or three people pointing at each other, you just found your next thing to fix.
the words “Who Owns This?”Several people can do the work. One person should own the outcome.
Why "everyone's job" is nobody's job
When a workflow has no single owner, it doesn't fail loudly. It fails quietly. Each person assumes someone else has the next step. Nothing is technically dropped, it's just always a little late, a little inconsistent, a little "wait, did anyone...?" Shared ownership feels collaborative. In practice it means no one is accountable when it slips.
An owner is not the person who does every step. An owner is the one person responsible for the whole thing working, start to finish. They can delegate the steps. They never delegate the outcome.
What an owner actually does
One name, attached to the result, who:
knows the workflow from start to finish
is the person you ask when you want status
has the authority to change it when it's broken
is accountable for correcting it when it slips
That's it. Not a committee, not "the team." One name.
Pick one workflow to fix before Q4
You don't need to assign owners to everything today. Pick one. The right one is usually the workflow that breaks or slips the most and touches the customer or the money. Onboarding a new client. Getting invoices out. Fulfilling an order. Following up on leads.
reads: “Ask one question: Who owns this? One clear name—or your next thing to fix.”If no one can name the owner, you’ve found a workflow to fix.
Choose the one where "who owns this?" gets the muddiest answer, and give it one clear owner before the quarter turns.
How to hand it over so it sticks
Assigning an owner only works if the handoff is real:
Name the owner out loud, to them and to everyone who touches the workflow. Ambiguity is the enemy.
Give them the authority, not just the task. An owner who can't change the process isn't an owner, they're a scapegoat.
Define what "working" means, one metric or one standard, so everyone agrees what good looks like.
Then get out of their way.
The Business Operating System Starter Kit includes delegation and process-mapping tools that can help you clarify responsibilities and document how the work should move.
Find your ownerless workflow (free)
Not sure where ownership is fuzziest? The free Business Operations Quick Check surfaces the parts of your business that depend on people remembering instead of someone owning, which is usually where the answer to "Who owns this?" falls apart.
Regina's Ops Lesson
Some of the most expensive operational problems aren't complicated. They're ownerless. A workflow can involve several people and still have no one accountable for whether the whole thing works. It limps along until something breaks, everyone scrambles, and then the cycle repeats.
The fix can be surprisingly simple: put one name on the outcome. That doesn't mean one person performs every step. It means one person watches the complete workflow, has the authority to improve it, and knows when it is slipping.
A surprising amount of what looks like a process problem is actually an ownership problem. Before redesigning the workflow, check whether accountability for the result is clear.
This week's AI prompt
The Ownership-Gap Prompt
"Here are the main workflows in my business: [LIST THEM]. For each one, ask me who owns the outcome start to finish. Then point out which ones have unclear or shared ownership, and which single workflow I should assign an owner to first based on how often it breaks and how close it is to the customer or revenue."
It's a quick way to see, in black and white, which parts of your business nobody is actually holding.
Your challenge this week
Pick one workflow and ask "who owns this?" If the answer isn't one clear name, assign one before Q4 starts. Reply and tell me the workflow and who now owns it.
Quick Hits
Shared execution is fine. Shared accountability still needs one clearly named lead.
An owner without the authority to change the process is just a name to blame.
"Who owns this?" is one of the fastest diagnostics in operations. Ask about everything.
Your takeaways
Work often stalls because no one clearly owns the outcome, not because the work itself is difficult.
An owner is one person accountable for the outcome, with the authority to change the process.
Pick the one ownerless workflow closest to the customer or the money, and assign it before Q4.
Name the owner out loud, give them authority, and define what "working" means.
Quick Answers
What does it mean to own a workflow? Owning a workflow means being the one person accountable for the whole thing working start to finish, with the authority to change it. The owner can delegate the steps but not the outcome.
Why do workflows fail without an owner? Because each person assumes someone else has the next step. Nothing is clearly dropped, so it fails quietly: late, inconsistent, and nobody accountable when it slips.
How do I decide which process to fix first? Pick the workflow that breaks the most and sits closest to your customer or your revenue, and where "who owns this?" gets the muddiest answer. Assign that one an owner first.
Know a business owner whose team keeps saying "I thought so-and-so had it"? Forward this. The fix might be one name.
Until next time, keep connecting the dots.
Regina Morgan
aka The Dot Connector™
Founder, Break Into Ops™
Founder, The Ops Connector™
Helping professionals and businesses connect the dots through better operations, smarter systems, and AI.
Next Wednesday: Stop Explaining It Twice: Write Your First SOP This Week. We move from finding the problems to fixing them, starting with the one document that saves you the most time.