OBSERVATIONS
ROLES & CONSTRAINTS
When responsibility is assigned but control is missing
Assigning responsibility can reduce ambiguity.
But responsibility only works when the role has enough control over the conditions required to produce the outcome.
5 MIN READ
01. The instinct to assign responsibility
When something is not moving, assigning responsibility often feels like the right response.
- If a project is unclear → name an owner.
- If work is falling through the cracks → define who is accountable.
- If decisions are delayed → make someone responsible for driving them.
- If execution is inconsistent → clarify who should follow up.
The instinct makes sense.
A system with no clear responsibility creates confusion. People wait, duplicate work, avoid decisions, or assume someone else is handling the issue.
Naming a responsible person can reduce ambiguity.
It gives the system a point of reference: someone can coordinate, follow up, track progress, and be asked what is happening.
In many cases, that helps.
But responsibility does not work simply because it has been assigned.
It works when the role has enough access, authority, information, and room to influence the conditions behind the outcome.
That distinction matters.
A person can be responsible for an outcome while lacking control over the conditions required to produce it.
- They may own the project, but not the budget.
- They may own the process, but not the people involved.
- They may own the timeline, but not the decisions that keep delaying it.
- They may own the metric, but not the system that generates it.
At that point, responsibility exists formally.
But structurally, the role may not have enough control to make ownership operational.
02. When control is missing
Control does not mean absolute authority over everything.
It means the role has enough influence over the conditions required to affect the outcome.
That may include:
- access to information
- authority to make decisions
- control over sequencing
- influence over priorities
- or the ability to resolve exceptions when the normal path breaks.
When those conditions are missing, responsibility becomes difficult to use.
The person can follow up, ask for updates, coordinate conversations, report status, escalate when something is blocked.
But they may not be able to change the conditions that keep producing the blockage.
From the outside, this can look like an execution problem.
The owner is not pushing hard enough.
The manager is not coordinating clearly enough.
The team is not taking accountability seriously enough.
Sometimes that may be true.
But in other cases, the role is being asked to carry an outcome whose causes sit outside its reach.
The delay may depend on a decision the role cannot make.
The result may depend on priorities the role cannot change.
The metric may depend on behavior the role cannot influence.
The process may depend on constraints the role can only work around.
In that situation, adding more responsibility does not necessarily create more movement, it may only increase pressure on the place where the system has made the problem visible.
The issue is not that responsibility was assigned.
The issue is that the responsibility was assigned without enough control to make it operational.
03. What the role starts carrying
When responsibility is assigned without enough control, the system may still appear active. That is part of what makes the problem difficult to see.
The responsible person keeps following up. Meetings keep happening. Updates keep circulating. Issues keep being escalated. People keep asking for alignment.
The system does not stop.
It moves through the role.
Over time, the role may begin to carry more than the outcome itself. It becomes the place where unresolved parts of the system accumulate: reminders the process does not hold, ambiguity the decision structure has not resolved, and translation between groups that do not share the same criteria.
It may also carry the pressure of a result shaped by conditions outside its reach.
This can look like ownership. It can also look like dedication, leadership, or commitment.
But it may be something else.
A role may be absorbing unresolved structure so the system can keep moving.
That is not always sustainable. The person may become more reactive, the team may become more dependent on escalation, and the process may become harder to operate without informal intervention.
The organization may begin to confuse effort with control.
At that point, the issue is not only whether the person is responsible.
The issue is what the role is being forced to carry because the system has not made responsibility usable.
04. The diagnostic implication
The diagnostic question is not whether responsibility should be assigned.
It often should be.
The question is whether the responsibility has been made usable.
A role may be responsible for an outcome, but the system around that role may not give it a real path to influence the result. In that case, adding more accountability may increase pressure without changing the conditions that produce the problem.
The answer is not always to give the role more authority.
Sometimes the scope needs to be narrower.
Sometimes the decision rights need to be clearer.
Sometimes the constraint sits somewhere else.
Sometimes the metric is asking the role to carry an outcome it cannot structurally affect.
Sometimes the system has assigned responsibility to one place while leaving the real levers distributed across another.
This is where diagnosis matters.
Diagnosis does not replace leadership judgment, role design, or management.
It gives those decisions a clearer object.
Before asking for more ownership, more accountability, or more execution pressure, the system may need to reconstruct what the role is actually being asked to carry.
A Diagnostic Memo is designed for this kind of situation.
It does not prescribe a new org chart or implementation plan.
It reconstructs the system, identifies where responsibility and control are misaligned, clarifies the constraints shaping the role, and frames what should be understood before more accountability, process, tooling, or execution pressure is added.
The goal is not to decide whether someone is responsible.
The goal is to understand whether the system gives that responsibility a real path to operate.
Make responsibility usable before adding more pressure.
If this resembles a system you are trying to understand, System Diagnosis may help clarify where responsibility, control, and constraints are misaligned.