Friday Accountability: If No One Can Stop It, Own It, and Close It, It Is Not Accountability

Friday, October 23, 2026 | Operations & Leadership Perspectives

This week we moved through the operating system.

• Monday: Where execution bottlenecks are forming.
• Tuesday: Who remains accountable as AI takes on more work.
• Wednesday: Which external assumptions should be reopened.
• Thursday: Why resilience increasingly belongs in capital-allocation decisions.

Today we close the loop.

Because identifying a risk is not accountability.

Approving a budget is not accountability.

Assigning five functions to an initiative is not accountability.

Putting an item on a dashboard is not accountability.

Accountability exists when someone can see the deviation, owns the outcome, has authority to act, and is expected to close the loop.

Three current signals make that especially important.

Finance leaders are discovering that they can approve AI spending faster than they can stop it.

Boards are placing enterprise risk management higher on the agenda while oversight complexity increases.

And cross-functional work continues to create situations where many people contribute but nobody clearly owns the final result.

Different problems.

Same weakness.

Ownership becomes fuzzy exactly where execution becomes important.

---

1. If You Cannot Stop the Spend, You Do Not Control It

Deloitte’s third-quarter 2026 CFO Signals survey offers a useful example.

The survey included 200 CFOs from North American organizations with annual revenues of at least $1 billion.

As AI usage expands, finance organizations are facing a very different cost model from traditional software.

Seat-based software was relatively predictable.

AI consumption can vary with model choice, token volume, data processing, context length, workflow design, cloud infrastructure, agent activity, and usage intensity.

The result is a new cost-control problem.

Deloitte found that 53% of surveyed CFOs said their organizations primarily review AI usage costs retrospectively, through bills, reports, dashboards, or manual analysis.

Only 47% monitor AI costs in or close to real time and actively manage deviations. Deloitte

That alone should get a CFO’s attention.

But the response-time data are even more revealing.

When AI costs exceed approved limits, 74% of respondents said their organizations typically need several business days to several weeks to pause or shut down the related usage.

Only 19% can respond the same business day.

Just 7% can respond automatically or near real time.

Think about what that means.

The budget may exist.

The threshold may exist.

Management may know the spend is outside the plan.

Yet the operating system cannot stop it quickly.

That is not cost control. That is delayed observation.

The Principle Applies Far Beyond AI

AI makes the issue visible because consumption can move quickly.

But the same accountability gap appears across operations.

Consider premium freight, overtime, scrap, temporary labor, expedited purchases, emergency maintenance, consultants, cloud infrastructure, inventory obsolescence, customer credits, spot-market materials, and special freight.

A company may have monthly limits for all of them.

But what happens when the limit is exceeded?

Who sees it? How quickly? Who has authority to intervene? Who decides whether the spend is justified? Who changes the underlying operating condition? And who verifies that the cost actually comes back down?

If the answer is: “We will review it next month,” the organization may have a financial reporting system.

It does not necessarily have an accountability system.

Every Material Cost Needs a Control Loop

For material variable spending, define five things.

1. The target

What should normal spending look like?

Not simply the annual budget.

What should the cost look like per unit, per order, per customer, per shift, per transaction, per AI workload, or per production hour?

The closer the metric is to the activity creating the cost, the faster the organization can understand what changed.

2. The threshold

At what point does normal variation become an exception?

A 1% deviation may not deserve executive attention.

A 30% increase probably does.

Define the trigger before the problem occurs.

3. The owner

One person owns the outcome.

Not Finance and IT. Not Operations and Procurement. Not Supply Chain and Sales.

One accountable leader.

Other functions contribute.

The owner remains clear.

4. The response time

How quickly must somebody act?

Same hour? Same shift? Same day? 48 hours?

The appropriate answer depends on the risk.

But there should be an answer.

5. The closure rule

What constitutes closure?

Spend below threshold? Root cause eliminated? Contract renegotiated? Workflow changed? Supplier corrected? Policy updated? Automation installed?

A problem is not closed because somebody explained it.

It is closed when the agreed condition has been restored or leadership consciously accepts a new condition.

Use a Cost-Control SLA

Earlier this week we discussed decision SLAs.

The same concept applies to material spending exceptions.

• Premium freight: above agreed weekly limit — Supply Chain Director — same day.
• Overtime: above approved hours — Operations Manager — next shift.
• Scrap: above threshold for two shifts — Quality/Operations owner — immediate containment.
• AI consumption: above workload budget — Business process owner — same day.
• Temporary labor: above approved level — Plant Manager — 24 hours.

The exact rules will differ.

The concept should not.

A financial threshold without an operational response standard is incomplete governance.

---

2. A Risk Register Is Not Accountability

The second issue sits at a higher level.

Enterprise risk is moving up the board agenda.

The fifth edition of the Audit Committee Practices Report, produced by Deloitte’s Center for Board Effectiveness and the Center for Audit Quality, found that enterprise risk management became the number-one priority for audit committees with responsibility for ERM.

39% ranked ERM as their number-one priority and 77% included it among their top three.

Cybersecurity appeared among the top three priorities of 87% of respondents. Deloitte

The report also shows how quickly AI governance has moved onto the oversight agenda.

Deloitte reports that 75% of respondents identified AI governance as a top-three priority, up from 35% the year before, while only 56% said they were confident in their audit committee’s ability to oversee AI governance effectively.

That gap matters.

Boards can identify risk faster than organizations necessarily build the capability to manage it.

And a growing list of risks can create a false sense of control.

Cybersecurity. Supply-chain concentration. Trade policy. AI. Talent. Energy. Customer concentration. Regulation. Liquidity. Geopolitics. Climate. Operational continuity.

The risk register gets longer.

The presentation becomes more sophisticated.

Colors show green, yellow, red.

But one question remains.

Who owns the action?

Risks Do Not Manage Themselves

A risk statement might say:

Critical supplier concentration creates exposure to extended production disruption.

Useful.

Now what?

Who owns supplier diversification? What event triggers escalation? What is the acceptable concentration level? What mitigation is underway? What deadline exists? What capital is required? What residual risk has leadership accepted? When will it be reviewed again?

Without those answers, the risk register is descriptive.

It tells leadership what could happen without establishing who must make something happen.

Give Every Material Risk Seven Fields

1. Accountable owner: One person. The risk may cross five functions. Ownership still needs one name.
2. Risk threshold: Define the signal that tells you exposure has materially changed.
3. Mitigation action: Specify what is being done now—not simply “monitor closely.”
4. Due date: Risk programs with no dates become permanent intentions.
5. Escalation path: Define what happens when mitigation fails or the risk accelerates.
6. Review cadence: Weekly, monthly, or quarterly depending on how quickly the risk can change.
7. Residual-risk decision: After mitigation, what risk remains, and who accepted it?

Not all risk should be eliminated. But material residual risk should be consciously accepted—not accidentally inherited.

One Risk. One Accountable Owner. Many Contributors.

That rule is simple.

It is also frequently violated.

Consider supply-chain resilience from yesterday’s post.

Procurement may manage suppliers. Finance may quantify exposure. Operations may manage capacity. Engineering may qualify tooling. Legal may manage contracts. IT may manage digital risk. The board may oversee enterprise exposure.

Everyone has a role.

But who owns the outcome?

If the answer is “Everyone,” accountability may actually belong to no one.

---

3. Cross-Functional Work Is Where Accountability Gets Fuzzy

Many of the most valuable outcomes in an enterprise cannot be delivered inside one function.

SIOP. Customer recovery. New-product introduction. ERP transformation. AI implementation. CapEx projects. Plant launches. Supplier transitions. M&A integration. Cost-reduction programs. Working-capital improvement. Footprint changes.

Each requires collaboration.

That creates a structural challenge.

A leader can directly assign work to their own team.

It becomes harder when success depends on peers.

Harvard Business Review’s October 22 delegation guidance makes this point directly: as leaders become more senior, they increasingly need to get work done through peers rather than only through direct reports.

Its guidance for lateral delegation emphasizes establishing clear roles, timelines, check-ins, and explicit agreement on ownership rather than assuming cooperation will automatically translate into accountability. Harvard Business Review

That distinction is fundamental.

Collaboration describes how people work together. Accountability identifies who answers for the result.

You need both.

“Operations and Finance Own It” Is Not an Ownership Model

Consider a working-capital initiative.

Operations manages production. Supply Chain manages inventory. Finance tracks cash. Sales influences customer commitments. Procurement influences supplier terms.

Who owns working-capital improvement?

If the answer is “All of them,” what happens when inventory rises?

Operations blames demand volatility. Supply Chain blames forecast accuracy. Sales blames service requirements. Finance reports the miss.

Everyone participated.

Nobody owned closure.

The better model might be:

• Outcome: Reduce inventory by $12 million while maintaining service.
• Executive owner: COO.
• Finance: validates cash impact.
• Supply Chain: owns inventory actions.
• Operations: changes production behavior.
• Sales: resolves demand and customer exceptions.
• Review: weekly.
• Escalation: CEO/CFO if service or cash thresholds are missed.

One outcome.

Many contributors.

One accountable owner.

Gallup: Accountability Remains Leadership’s Weakest Competency

This problem is not simply procedural.

It is also behavioral.

Gallup surveyed more than 23,000 U.S. workers and found that creating accountability was the lowest-rated of seven core leadership competencies among both leaders evaluating themselves and managers evaluating their leaders. Gallup

Gallup defines creating accountability as holding people responsible for exceptional performance.

The weakness appears repeatedly because good accountability requires leaders to do several uncomfortable things consistently:

• Set explicit expectations.
• Clarify ownership.
• Discuss missed commitments.
• Differentiate explanation from correction.
• Recognize performance.
• Escalate when necessary.
• Follow through.

Accountability is not aggressive management.

It is disciplined clarity.

The Three Problems Are the Same Problem

Now connect this Friday’s three topics.

An AI workload exceeds budget.

Finance notices it after the invoice.

Nobody can shut it down quickly.

That is a control problem.

A supply-chain dependency is marked red on the risk register.

Five functions are involved.

Nobody clearly owns mitigation.

That is a risk-ownership problem.

A transformation project misses its milestone.

Operations, IT, Finance, and the vendor all contributed.

Nobody is sure who had final accountability.

That is a cross-functional problem.

But underneath all three sits the same operating-system weakness:

The organization has responsibility without enough ownership.

That distinction matters.

Responsibility asks: “What work are you supposed to perform?”

Accountability asks:

“What result are you expected to ensure happens?”

Build the Accountability Chain

For every material outcome, establish this chain:

Signal → Threshold → Owner → Authority → Action → Due Date → Verification → Closure

If any link is missing, execution weakens.

Signal

How will we know something changed?

Threshold

At what point does it require action?

Owner

Who answers for the outcome?

One person.

Authority

Can that person actually make the necessary decision?

An owner without authority is a coordinator.

Action

What happens next?

Due Date

By when?

Verification

How will leadership know the action produced the expected result?

Closure

When does the issue leave the agenda?

That last step matters.

Organizations often accumulate open items because no one defines what “done” means.

Create an Accountability Ledger

A useful leadership tool can be extremely simple.

For the ten most important enterprise commitments, keep one ledger:

• Outcome
• Owner
• Target
• Due
• Current Status
• Next Action
• Escalation

Review it every week.

Not every activity.

Not every project task.

Only the commitments material enough that leadership needs certainty.

Examples:

• Recover $8 million in working capital.
• Qualify the second source.
• Reduce premium freight.
• Complete the automation launch.
• Close the cybersecurity exposure.
• Achieve customer recovery.
• Deliver the CapEx benefit.
• Reduce inventory days.
• Stabilize the new plant.
• Integrate the acquisition.

The purpose is not another dashboard.

The purpose is to make promises visible until the result exists.

Give the Owner Real Authority

One of the most common accountability failures is assigning ownership without granting authority.

A leader is told: “You own the result.”

But cannot change the schedule, stop spending, escalate the supplier, reallocate resources, challenge another function, approve corrective action, change the process, or access the necessary data.

Then leadership asks why the owner failed.

Accountability without authority creates frustration.

Authority without accountability creates risk.

The operating system needs both.

Stop Measuring Explanations as Progress

This is another Friday discipline.

A missed commitment enters the review.

The owner explains:

• The supplier was late.
• The system failed.
• Demand changed.
• The employee left.
• The customer changed the requirement.
• The forecast was wrong.
• The AI cost increased.

Some of those explanations may be completely accurate.

But an accurate explanation is not automatically corrective action.

After hearing the explanation, ask:

“What changes now?”

Then: Who owns it? By when? What result will demonstrate recovery?

That is where accountability begins again.

The Friday Close

The end of the week is an ideal time to close the operating loop.

1. What did we commit to? Not what did we work on. What did we promise?
2. What actually happened? Use evidence. Not confidence.
3. What remains open? No hiding inside percentages.
4. Who owns the next action? One name.
5. When will we know it is closed? Specific date. Specific result.

This can take 30 minutes.

But repeated weekly, it changes behavior.

A 30-Day Accountability Reset

Week 1 — Identify Fuzzy Ownership

Take your ten most important risks, projects, cost categories, and strategic commitments.

For each, ask:

Can we name one accountable owner?

If not, assign one.

Week 2 — Define Thresholds and Authority

For each item, specify trigger, decision authority, escalation level, and response time.

Remove the phrase: “Leadership will review as needed.”

Define what “needed” means.

Week 3 — Start the Accountability Ledger

Review material commitments weekly.

Owner. Outcome. Due date. Current state. Next action. Escalation.

Do not let items disappear because another meeting happened.

Week 4 — Close or Escalate

Every overdue commitment receives one of four decisions:

• Close. The agreed result exists.
• Recover. A corrective plan has a new date.
• Escalate. Authority or resources must change.
• Stop. The commitment no longer creates enough value to continue.

What is not acceptable:

Remain open indefinitely.

Questions for Your Leadership Team This Friday

1. Which cost category can exceed its approved limit today without anyone being able to stop it quickly?
2. How many days typically pass between detecting a material cost deviation and taking corrective action?
3. For each of our top ten enterprise risks, can we name one accountable executive?
4. Which risks currently have mitigation plans but no explicit due date?
5. Which material initiatives are described as jointly owned by several functions?
6. Where have we assigned accountability without granting decision authority?
7. Which open commitment has appeared in our leadership review for more than 30 days?
8. What explanation are we repeatedly accepting without changing the underlying condition?
9. Which financial metric tells us something went wrong only after it is already too late to intervene?
10. What would we have to change so that every material signal produces a named owner, a response, and closure?

That final question describes the real accountability system.

What CEOs Should Take From This

The CEO should look for ambiguity.

Not because every decision belongs at the top.

Quite the opposite.

The CEO should ensure that material outcomes have clear owners, appropriate authority, visible thresholds, defined escalation, and closure.

The CEO should not become the owner of everything.

The CEO should build an organization where ownership is unmistakable before escalation reaches the CEO.

What CFOs Should Take From This

Financial control should become increasingly operational.

Do not wait only for monthly close, vendor invoice, budget variance report, or quarterly review.

For volatile spending, finance needs visibility close enough to the activity to influence the outcome.

AI costs are one current example.

The same logic applies to freight, labor, inventory, scrap, external services, and emergency purchasing.

The faster the cost can move, the faster the control loop must operate.

What COOs Should Take From This

The COO should examine the space between functions.

That is where accountability often disappears.

Every critical cross-functional process should have one outcome, one executive owner, defined contributors, explicit decision rights, a cadence, and a closure rule.

SIOP cannot belong to “the SIOP team.”

Working capital cannot belong to “Finance and Operations.”

Customer recovery cannot belong to “Sales and Quality.”

Transformation cannot belong to “the project office.”

Processes can cross functions. Accountability cannot dissolve between them.

The ENLOSA Perspective

At ENLOSA: Global Business Solutions, we call the connection between strategy and execution Stratactic™.

Strategy establishes the investment, the risk appetite, the budget, the priorities, and the initiatives.

Execution determines whether somebody actually delivers the result.

That requires more than responsibility.

It requires an accountability architecture.

• Signal. Know when reality changed.
• Threshold. Know when leadership intervention is required.
• Owner. One person answers for the result.
• Authority. Give the owner enough power to act.
• Action. Change the condition.
• Verification. Confirm the action worked.
• Closure. Remove the issue only when the result exists or leadership consciously changes the commitment.

That is accountability.

Not blame.

Not bureaucracy.

Not another dashboard.

A management system that refuses to let important commitments disappear between meetings.

This week began by asking where execution gets stuck.

We end by asking who closes the loop.

Because organizations rarely fail from lack of activity.

They fail when important outcomes become everybody’s responsibility and nobody’s accountability.

One outcome. One accountable owner. Clear authority. Visible action. Closed loop.

That is how accountability becomes execution.

And execution becomes value.

References

• Deloitte — North American CFOs Cite AI Cost-Governance Gaps in Third-Quarter 2026 Survey, October 21, 2026. Deloitte found that 53% of surveyed organizations primarily review AI costs retrospectively, while 74% typically need several business days to several weeks to pause usage after costs exceed approved limits. Source
• Deloitte Center for Board Effectiveness / Center for Audit Quality — Audit Committee Practices Report, Fifth Edition, 2026. Enterprise risk management ranked first among committees responsible for ERM oversight, cybersecurity remained a pervasive priority, and AI governance rose sharply on audit committee agendas. Source
• Gallup — “Accountability Is Leadership’s Greatest Weakness,” March 19, 2026. Gallup found that creating accountability was the lowest-rated of seven core leadership competencies among both leaders and managers evaluating leadership performance. Source
• Harvard Business Review — “Our Favorite Management Tips on Delegating Effectively,” October 22, 2026. HBR emphasizes explicit roles, timelines, shared agreement, and follow-up when work must be delegated across peers rather than simply down the hierarchy. Source

ENLOSA: Global Business Solutions
Strategy. Leadership. Execution.
enlosa@enlosa.com | +1 (877) 246-1109

#FridayAccountability #Accountability #Ownership #Execution #EnterpriseRisk #RiskManagement #CostControl #FinancialDiscipline #CrossFunctionalLeadership #Delegation #AI #AIGovernance #BoardGovernance #AuditCommittee #CFO #COO #CEO #Leadership #PerformanceManagement #OperationalExcellence #OperationalRisk #WorkingCapital #ValueCreation #Stratactic #EGBS