Single-threaded Owner

Assigning an owner to an important initiative is not new. The problem was that the owner already had three or four other things. A name is written down, so ownership looks settled, and that person answers the questions in the review, so the work looks like it is progressing right up until the deadline.

What actually happens is that urgent work keeps pushing important work aside. An incident in production or a request from a large customer pulls the person over. So two of three quarterly goals slip, and asked why, the answer is always that the owner was tied up elsewhere. Planning harder doesn't change the outcome. What's missing isn't a plan but a person attached to only that one thing. Give someone three initiatives and they don't advance a third each — two stop and one moves, and which one moves is decided by whatever was loudest that week.

A single-threaded owner is how that person gets made. Instead of dividing involvement into a table of roles, one person is pulled out of everything else and attached to one initiative. Not holding another assignment is the core of the name, and removing that condition removes the point of the seat while keeping its title.

The day is filled with the progress and the blockers of one initiative. The surface is narrow, so the work goes deep.

1. Morning means looking at this initiative's blocked items only: what's waiting on another team's answer, what's stopped for lack of a decision, what's taking longer than expected. The state of other initiatives doesn't get looked at, because having nothing else to look at is the condition of the seat, and so the morning list fits on a single screen.
2. Decisions get made on the spot. Half the reason the seat exists is here. Send a decision upward and wait and a week goes by, so how far this person can decide alone gets written down when the seat is created: a spending limit, and a list of decisions that can't be undone. Anything off that list gets decided here and only what's on it goes up. Leave that boundary unwritten and you have freed up a person while the decisions still queue somewhere above them.
3. What's needed gets fetched directly. If another team's hours are required, negotiating with that team's lead is part of this job, rather than filing a request and waiting for a slot. Waiting is unusually expensive in a seat that has nothing else to work on meanwhile, which is why the negotiation happens in person.
4. Weekly, status gets reported as one number — not an internal figure like percent complete, but the outcome the initiative was meant to move. "Eight of twelve features built" is not this seat's language; "first-week return visits up four points" is. In an organization running OKRs, objectives paired with key results, one key result becomes exactly that number.
5. New work gets declined. Blocking requests to take on a second assignment is part of the job. That's hard to carry alone, so a route for sending those requests to the sponsor gets built at the same time — grounding a refusal in a rule rather than in a person costs less goodwill.

A dedicated team alongside is the best shape, and a squad — a small team owning one goal — is that shape. Where dedication isn't possible, people get borrowed from other teams for a fixed period, which collides with the lending team's priorities, so the period and the share go in writing. Half of one engineer for six weeks, with the numbers stated rather than implied, prevents most of the later argument.

Authority comes from the sponsor: the executive who decided the initiative should exist, who meets fortnightly and clears what's blocked. When the sponsor is absent or changes, this seat's authority blurs immediately, because that authority is the only basis it has for asking other teams for anything at all.

Alongside sit the owners of other initiatives. They compete for the same engineers and the same designer, so a separate forum for deciding who goes first is required. Without it, three owners each demand dedication and summon the same three people. Organizations that create several of these seats therefore cap the number of initiatives per quarter first.

Neither RACI, which divides involvement into a table, nor DACI, which divides the roles in a single decision, is mutually exclusive with this. Individual decisions inside an owned initiative still use those tables, with the owner's name sitting in the accountable box each time.

"Let's free somebody up and give this one an owner."

Someone has to be pulled off their other work for this to mean anything.

"The owner can decide that. No meeting needed."

Authority is already delegated, so the decision shouldn't travel upward at all.

"Calling someone an owner while they hold three other assignments is a label, not a change."

The condition that makes the seat work is missing.

Pagedeck created this seat for the first time while building enterprise permission management. For two quarters the initiative had appeared in the plan and slipped every time, always for the same reason: an owner was named, and that same person was also handling the customer requests that arrived every week.

In the third quarter Mia came off everything else and took only this. The customer requests moved to someone else, and Grace took the sponsor role with 30 minutes fortnightly. Decision authority was written down as feature scope plus spending under $15,000. The initiative shipped inside that same quarter. What changed wasn't anybody's ability but the number of things one person was holding.

The most common mistake is reading it as doing everything alone. Holding one thing sounds like holding it by yourself. But what the phrase describes is the owner's attention running in one thread, and having a dedicated team is the norm rather than the exception. Read as working alone, it leads to handing someone an initiative without staffing it at all, which removes the second assignment and the headcount in one move.

Believing seniority is required is the other one. Deciding things without asking makes it read that way. But this seat's authority doesn't come from a title — it comes from the sponsor's delegation. Write down how far the person can decide and someone early in their career can hold the seat; leave the delegation unwritten and even a senior person sends everything upward. What has to be specified when the seat is created is the scope of the authority rather than the rank of the person filling it.