A leader can be accountable for an outcome and still be unable to improve it.

That happens when the organization assigns responsibility for the result while leaving the decisions that shape it with several other functions. One person carries the number. Product controls the roadmap. Finance controls the budget. Operations controls capacity. Legal or security controls the risk boundary. The work moves through a chain, while the accountability line points to one person.

That is not a motivation problem. It is an operating design problem.

Accountability becomes useful when the person carrying the outcome can influence the conditions producing it. The Lumaire Lens names those conditions through four questions: What outcome matters? What drivers are creating it? Which levers can the business move? What impact should follow?

A reorganization changes the chart first

HubSpot’s October 6, 2026 communication is a useful illustration of the question.

HubSpot said it would organize product teams around customer outcomes instead of Hubs, reduce management layers, move decisions closer to the people doing the work, and create teams with clearer ownership and authority. Its SEC Form 8-K says the plan affects approximately 7% of the workforce and estimates $65 million to $75 million in restructuring charges.

Those sources establish what HubSpot announced and what the company intends to change. They do not establish that customer outcomes, decision speed, or profitability have improved. The filing identifies the plan’s benefits as forward-looking and notes that the change could fail to deliver its intended benefits or disrupt operations and customer relationships.

That distinction matters. A reorganization is a hypothesis about how work will move. The evidence comes later, in the decisions made, the handoffs changed, the customer experience, and the economics of delivery.

The broader question for any organization changing its structure is this:

What has to move underneath the chart for accountability to become actionable?

The work does not follow the org chart automatically

An organization chart can show where accountability sits. It cannot show where a customer request waits, where a decision gets escalated, or which team approves an exception.

Most meaningful outcomes cross functional boundaries. A new customer may need a commercial promise, a product capability, an implementation path, and an operating process that keeps the result intact after launch. If one team owns the outcome while each dependency remains controlled elsewhere, the new owner inherits coordination work.

The organization has renamed the destination without changing the route.

This is why a flatter structure can still feel slow. Fewer layers do not automatically mean fewer decisions. Clearer ownership does not automatically resolve competing priorities. A team can be told to move faster while waiting for data, budget, specialist capacity, or approval from a function that does not share the same measure.

Before changing the chart, trace one outcome through the work. Look for the points where the result depends on a decision, handoff, resource, or definition that sits outside the named owner’s control.

Accountability needs four operating conditions

The person accountable for an outcome needs more than a title.

Decision rights

The organization must specify which decisions the outcome owner can make, which decisions require consultation, and which decisions remain outside the role.

“Own the outcome” is incomplete until the decision boundary is clear. If every material choice still requires escalation, responsibility may have moved down the organization while authority has not.

Information

The owner needs timely access to the evidence that explains the outcome.

A team cannot manage customer friction, implementation time, retention, or cost to serve from a report that arrives after the decision window has closed. Data access is not the same as decision-useful information. The owner needs the right definition, the right level of detail, and enough timing to act.

Resources

Authority without people, budget, technical capacity, or specialist support is a mandate without means.

A team does not become empowered because it has been given a target. It needs enough capacity to pursue the priority and a clear path to resolve constraints it cannot remove on its own. Otherwise the team spends its time escalating the gap rather than improving the outcome.

Measures

The scorecard has to show the outcome and the drivers underneath it.

A team can hit a local activity target while the customer waits longer, the work requires more rework, or the cost of delivery rises. The measure needs to follow the result through the full workflow, including the effects that may appear in another function.

These conditions reinforce one another. Decision rights without information create poor decisions. Information without authority creates analysis that waits. Authority without resources creates escalation. Measures without ownership create reporting without movement.

Independent evidence points to design, not motivation

MIT CISR describes decision rights as one of the hardest changes in a digital transformation. In its survey, nearly two-thirds of the companies represented were rated no more than moderately effective at changing decision rights.

The research compared companies classified as empowered with companies that were not classified that way. The empowered group reported higher industry-adjusted net profit margins, revenue growth, and revenue from newer offerings. Those findings are useful direction, not a guarantee: the performance measures were self-reported, and the comparison does not prove that empowerment caused the difference.

The disciplined conclusion is structural. Organizations that combine accountability with authority, data, guardrails, and resources are better positioned to act than organizations that leave decisions concentrated at the top while distributing responsibility below.

A U.S. Government Accountability Office review of cross-functional teams reaches a similar practical conclusion. Its leading practices include autonomy, clear goals and structure, senior support, committed members, and an empowered team leader. The review also found that a strategy without specific implementation steps made progress harder to assess.

An operating design is not complete when the future state is described. It is complete when people know how decisions will be made in the work.

Test the design through one outcome

You do not need to redraw every box to find the gap. Choose one outcome that matters economically and trace it end to end.

Ask:

  • Where does the work begin, and where does the customer experience the result?
  • Which decisions change the outcome most directly?
  • Who can make those decisions today?
  • What information arrives too late or remains trapped in another function?
  • Which resource constraint creates the longest delay?
  • Where do exceptions leave the standard process and become rework?
  • What measure would show that the outcome improved without shifting cost or risk somewhere else?
  • How are unresolved dependencies surfaced and resolved?

The answers reveal the operating model more accurately than the organization chart. They also show whether the proposed change is a real redesign or a new layer of language around the same work.

A useful decision-rights map can be simple:

  • Name the outcome and its economic importance.
  • List the decisions that materially influence it.
  • Assign a decision owner for each one.
  • Define the information, resources, and guardrails required.
  • Set an escalation path for decisions outside the boundary.
  • Review the expected impact at a defined cadence.

This is the difference between asking someone to be accountable and giving them a workable control surface.

The economic effect is in the gap

Accountability without authority creates economic drag through mechanisms leaders can observe.

Decisions wait. Work is repeated. Customer friction increases. Exceptions accumulate. Capacity is consumed by coordination instead of delivery. Managers spend time escalating issues that the operating model could have resolved closer to the work.

These effects should not be assumed from a title change or a restructuring announcement. They need to be measured in the business being changed.

A practical scorecard might track:

  • Decision age: How long material decisions remain open.
  • Dependency age: How long teams wait on another function.
  • Rework: How often work returns to an earlier stage.
  • Customer friction: Where the journey slows or breaks.
  • Cost to deliver: What the outcome requires in people and time.

These are not proof that a new structure worked. They are signals that the operating conditions underneath it are changing—or that the old constraints remain.

This is also why a shared metric is not enough. As Your Dashboards Agree. Your Executives Don’t. argues, leaders can see the same number and still leave with different conclusions about cause, ownership, and next action. The operating review has to connect the outcome to its drivers, levers, and expected impact.

Clarity creates momentum when authority can reach the work

Accountability is not a personality trait that some leaders have and others lack. It is a relationship between an outcome, the conditions that shape it, and the authority available to change those conditions.

HubSpot’s announcement makes that relationship visible without proving the result. The company described customer outcomes, fewer layers, clearer ownership, and authority as part of the same operating change. The implementation—and its effects—remain to be seen.

That is the useful lesson for any leadership team: do not evaluate the chart before checking the work.

Can the person carrying the outcome make the decisions that shape it? Can they access the information in time? Can they move the resources required? Can the business see whether the full outcome improved without shifting cost or risk somewhere else?

If the answer is no, the next conversation belongs in operating design.

Clarify the decision rights. Move the information. Resource the team. Set the measure. Create a cadence for dependencies. Then watch what changes in the work.

Clarity creates momentum when accountability is matched with the authority to act.

References