Accountability Requires Authority to Shape Outcomes

In a recent LinkedIn post, Dr. Rachna Jain discusses how organizations can undermine accountability when they assign responsibility for results without giving people meaningful influence over them. This article examines Jain’s argument in that post; it is not written by Jain.

“A project owner cannot change its budget, deadline, or staffing.”

Jain uses that scenario to highlight a gap between being answerable for an outcome and having the authority to affect it. A project owner may be expected to deliver, yet lack control over core conditions such as funding, timing, or staffing. As Jain notes, that mismatch can shape how a role-holder responds to problems.

Responsibility needs practical decision rights

According to Jain, hesitation, escalation, and frustration in these situations can be misread as a lack of ownership. Her post suggests another explanation: the assignment may leave unclear which decisions the person can make, which resources they can direct, and which choices require approval.

“A credible assignment specifies which decisions a person can make, which resources they can direct, and where they need approval.”

That distinction makes role design central to accountability. Jain does not argue that authority must be unlimited. Rather, she points to the need for boundaries that people can use in practice. If those boundaries are vague or overly restrictive, a person may be held responsible for decisions that remain outside their control.

When approval boundaries matter

Jain’s framing draws attention to the everyday mechanics of authority: who can approve changes, redirect resources, or respond when a project encounters difficulty. Clear answers can help distinguish decisions that belong to the project owner from those that must be escalated. The post does not offer a detailed framework for setting those limits, but it identifies their usability as a condition of credible responsibility.

Accountability and influence must align

“When someone is evaluated on an outcome they cannot meaningfully influence, the organization has created a predictable conflict.”

In Jain’s view, that conflict is built into the arrangement rather than being a surprise revealed by an individual’s performance. Evaluating people on results they cannot shape may create pressure without providing a workable route to change those results. Jain therefore shifts attention from demands for stronger ownership to the design of the role itself.

Her conclusion is concise: “Better accountability begins with better role design, not louder demands for ownership.” The point is not that responsibility disappears when authority is limited, but that organizations should define the path a person has to influence the outcome they are accountable for. Jain closes by connecting the issue to a larger question she identifies with Interaction, inviting readers to consider how accountability is structured across organizational relationships.