Perspective

Last reviewed November 10, 2026

I was in a shop that looked like a lot of shops I know. Trades. Field service. A leadership team that could run the week if the owner would let go of a few seats.

Someone said, "Can you handle the vehicles?" Heads nodded. The title moved on a chart. The assets never did. Keys, vendors, insurance, who signed for repairs. Still sitting with the old seat. Every ops meeting reopened the same pile. I kept hearing the same word: accountability. The structure never finished the promise.

That pattern is why owners stay in the room. Unfinished promises do not wait politely. They keep billing attention until someone closes them.

Ask a leadership team where work gets stuck and you will hear the same words. Communication. Accountability. Culture. People.

Look closer and the pattern is more boring, and more useful. Someone asked for help. Someone nodded. The file moved. Then the week ended and nobody could say whether the thing was finished, accepted, or still half alive in a Slack thread.

We are talking about the commitments inside every handoff between teammates. Until those commitments are clear, the company keeps paying for work that never quite ends. That is owner dependency wearing a friendly face.

A request is not a promise yet

Inside a company, almost every useful move starts as a request or an offer.

A request says: I want a specific promise from you, and I am willing to deal with the consequences if you say yes or no.

An offer says: here is the promise I am willing to make, and here is what I need from you in return.

Neither one is complete when it is vague. "Can you handle the vehicles?" is not a promise. "I'll take a look" is not acceptance. "Sent" is not delivery. "Looks good" is not declare complete.

A real promise has two structures. First, a picture of done: what done looks like, in criteria you could show a stranger. (Some people call that the conditions of satisfaction.) Second, time: by when that picture will be true. Without both, action is a fantasy. People fill the blanks with their own stories, and those stories are rarely generous.

Without a picture of done and a by-when, the team is not coordinating. It is guessing in public.

The five commitments inside every handoff

Treat an internal handoff the way you would treat a small deal. There are five commitments. They apply when the requester and the doer are both on your payroll.

The person doing the work promises three things:

1. Produce the outcome that matches the picture of done.
2. Transfer ownership of that outcome.
3. Deliver it.

The person receiving the work promises two things:

4. Accept delivery.
5. Return something real: priority, budget, cover, or credit.

All of it by a specified time, or as agreed.

That fifth commitment is where companies get soft. We ask people to deliver, then we skip the return. No budget move. No priority clear. No public credit. No cover when the work gets contested. The doer learns that yes is expensive and no is safer.

Read the strip left to right. Delivery without acceptance leaves the work in limbo. Acceptance without a return trains people to stop volunteering. Declare complete ends the reason for further action and further cost. The satisfaction check is separate: are we open to the next ask from each other at lower trust cost?

Meeting expectations once is not the same as satisfaction. Someone can get exactly what they asked for and still not want the next request from you. That is useful information. It means the relationship cost is still high.

Where corporate handoffs usually break

These are patterns we see often. They are illustrations, not client cases.

Drive-by request. "Can you handle this?" lands in a hallway. No picture of done. No date. No owner of acceptance. The doer invents a version. The requester invents another. Both are sincere. Both are wrong.

Assumed acceptance. The request was heard as a FYI. A week later: "I thought you had it." Nobody ever said yes. There was no promise, only proximity.

Scope ghost. The deliverable changes after the yes, with no re-promise. The original picture of done dies quietly. The new one was never born.

Ownership never transfers. The work is "done" but still sits with the doer. The fleet still reports to someone else. The warehouse still belongs to another seat. A title without transfer of ownership is just a title.

Delivery without acceptance. The file hits email or Slack. Nobody says "accepted." The doer thinks they are free. The requester thinks they are waiting. Cost keeps accruing for both.

No declare complete. The project stays half alive. Every meeting reopens it. Time, energy, money, and lost opportunity keep charging to a job that should have ended.

Two more show up so often they deserve names.

Fake pay. The doer delivered. The requester never returned priority, budget, cover, or credit. Next time the best people are suddenly "at capacity."

Satisfaction skipped. Expectations were met once. Nobody checked whether the next ask would be welcome. The next request costs more trust than it should.

Incomplete work does not sit still. It keeps billing the company in attention.

Why this feels personal when it is structural

When a handoff fails, people reach for character. He does not care. She drops balls. They are not accountable.

Sometimes that is true. Often the structure failed first. The request had no picture of done. The acceptance was assumed. Ownership never moved. Nobody declared complete. Moods follow the structure: distrust, skepticism, quiet resentment, resignation. Those moods then make the next handoff harder, which confirms the story that "people are the problem."

Owners who want better accountability usually need better promises, not louder speeches.

That includes the owner. If you ask for something with no by-when, you taught the standard. If you accept work with a nod and reopen it on Friday, you taught that declare complete does not count. If you rename a seat and leave the assets with someone else, you taught that titles are theater.

Unfinished promises are how owner dependency hides in plain sight. The company looks staffed. The scoreboard looks fine. The owner is still the only person who can say what done meant, so every sticky handoff climbs back to their calendar.

We see this in shops, plants, and professional firms the same way. The meeting is not really about vehicles or a warehouse aisle. It is about a promise that never closed, so the owner keeps holding both sides of it.

What to do this week

Pick three open requests on your team. Rewrite each one before you escalate anyone.

For each request, write four lines:

1. Picture of done: what done looks like, in language a new hire could check.
2. By when.
3. Who accepts delivery, by name.
4. How we declare complete, and what return the doer gets (priority, budget, cover, or credit).

Then run the conversation out loud. Ask for an explicit yes or no. If the answer is no, that is useful. An honest no beats a fake yes that keeps accruing cost.

If you cannot name the handoffs and dates, you are not ready for the talk. Wait until you can. A seat without transfer of ownership will land as a title, because that is what it is.

Clarity is not softness. It is how adults coordinate without wasting each other's week.

The point

Coordination inside a company is not a vibe. It is a sequence of commitments that either close or keep charging.

Put a picture of done on the promise. Put a time on it. Deliver. Accept. Return something real: priority, budget, cover, or credit. Declare complete. Check satisfaction before you ask again.

Do that and fewer balls get dropped, fewer meetings reopen the same work, and more of your team's attention comes back available for the next real move. The owner can leave the room a little longer. That is structural resilience, one closed promise at a time.