Issue #18 November 16, 2026

Huang Out at Nvidia, the Outlook Outage, Anthropic's IPO Math, What Claude Fable 5.2 Can Do, and Two Org Briefings: the Flattened Middle and the AI-Enabled Fractional CFO

Editor's Take

Two headlines dominated last week, and neither was a product launch: Jensen Huang's abrupt exit from Nvidia, and a Microsoft outage that took Outlook down for most of a working day. I comment on both briefly below. Together with Anthropic's IPO filing, which puts $895.4B of compute commitments on the record, they make one point: the AI economy rests on very few people, platforms, and balance sheets.

Also this week: Claude Fable 5.2 is out, and I walk through what it can actually do. OpenAI gave its agents a wallet. And there are two Org briefings: the thinned middle-management layer that is carrying most AI rollouts, and a new look at org design for smaller companies, starting with how AI changes what a fractional CFO can deliver.

This Week's Briefings

The Flattened Middle Is Carrying Your AI Rollout

Two new surveys agree: companies are thinning the management layer that AI adoption depends on, and most cannot say whether the managers who remain are ready.

TL;DR

AI change is being delivered by middle managers, and almost nobody above them is checking whether they can deliver it. Korn Ferry's Talent Trends 2027 report found that only 6% of respondents believe their top executives are fully prepared to lead AI-driven transformation, and 66% expect managers to spend more of their time helping teams through change than overseeing daily work.

The managers are not ready either, and many firms do not know it. In a Paradigm survey of HR leaders at more than 650 companies, just 6% said their middle managers are ready to lead change companywide. Nearly one in five said managers are unprepared across the whole organization, and another 19% said they do not know.

Meanwhile the work itself has not been redesigned. Deloitte's AI Pulse Check (about 3,700 professionals) found 48% of organizations have introduced AI without redesigning the workflows or roles around it. Only 12% report redesign at scale with a new operating model behind it.

Two different 6% numbers, one problem

The coincidence is worth separating, because the two figures measure different things. Korn Ferry's 6% is about the top: how few people think senior executives are fully prepared to lead the transformation. Paradigm's 6% is about the middle: how few HR leaders think their managers are ready everywhere in the company. Put together, they describe a rollout where neither the layer setting the mandate nor the layer delivering it is judged ready, and the weight lands on the layer with less authority.

Korn Ferry's Cathi Rittelmann has the phrase for it: "Managers will become the shock absorbers of the organization." Her colleague Susan De La Vega describes the mechanism to Fortune: managers end up defending and communicating AI mandates they had no say in and little context for. That is the job most companies are now asking of a group they are simultaneously shrinking. HR Executive's reporting on the "Great Flattening" makes the same point from the other direction: the layer is being cut in the name of AI efficiency without preparing the managers who remain for wider spans and a change-leadership job.

Why this is the binding constraint

Deloitte's data explains why the middle matters more than the tooling. Nearly half of organizations have dropped AI into existing workflows and roles unchanged. Value shows up when the workflow is rebuilt, which Deloitte describes as redesigning the "work chart" (how work, decisions, and accountability are organized) ahead of the org chart. Workflow redesign is local, detailed work. It is done by the people who know how the work actually runs, which in most companies means the managers one or two levels above the front line. Remove them first and you have removed the people who would do the redesign.

The firms making progress follow a recognizable pattern. Among organizations that are changing how work is done, 37% start by fully owning one workflow, testing it, and then scaling.

What to do with this

  1. Measure manager readiness before you cut the layer. A fifth of HR leaders cannot say whether their managers are ready. Get a function-by-function read first; it is cheaper than discovering the gap after the reorg.
  2. Brief managers before their teams, with the reasoning. A manager who hears the AI mandate at the same time as their team cannot explain it, defend it, or adapt it. Give them the why, the metric, and the room to object a week early.
  3. Rewrite the manager job on paper. If two-thirds of the role is now leading change, something has to come off. Status reporting, routine approvals, and schedule coordination are the obvious candidates to hand to agents. Say so explicitly, in the role description and in how managers are measured.
  4. Redesign one workflow end to end, with a manager as its owner. Follow the 37%: pick one process, give one manager authority over it, rebuild it with AI inside, measure it, then scale the method.
  5. Sequence delayering after redesign. Wider spans are sustainable once the workflow carries less coordination overhead. Widening them before the redesign adds load to the people doing the redesign.
The strongest counterargument: flattening is the forcing function, and organizations never redesign work until the old structure is gone. That holds where senior leaders can run the redesign themselves. The Korn Ferry number says most cannot yet. Until they can, the middle layer is the only place the redesign capacity exists, and spending it on absorbing shocks is the expensive choice.

Second Briefing: Org Design for SMBs

The Fractional CFO, Rebuilt: What AI Changes for SMBs and the Lower Mid-Market

The fractional CFO used to be strategy without the weeds. A capable CFO with capable AI can now work from the raw data up, and that changes the org design of a small company's finance function.

TL;DR

The old problem: most fractional CFOs are strategic and stay at the top of the stack. They polish what the books already say. Few get into how data actually flows into the financial system, because on a part-time engagement that work needed either a team of analysts or the full cooperation of the existing controller.

What AI changes: a CFO who can use AI well can go into the messy source data personally. AI can map how the systems should connect, reconcile them, and clean the data, in days instead of a staffing plan.

The new regime: a small company can now get someone who has been there and seen that, whose advice rests on its real operating data. That combination used to require a full-time CFO plus a finance team.

Why the fractional CFO was hard to make work

The pitch has always been attractive: senior judgment at a fraction of the cost. The delivery has often disappointed, for a structural reason. Good decisions depend on trustworthy numbers, and in most small and mid-sized companies the numbers are the problem. Revenue lives in one system, billing in another, payroll in a third, and the general ledger is stitched together with spreadsheets and habit.

A part-time CFO facing that had three options, all poor:

  1. Stay on top. Take the books as given and add a layer: a board deck, a forecast, a KPI page. This is top polishing. It looks strategic and inherits every error underneath it.
  2. Bring an army. Staff the cleanup with analysts or an outsourced accounting team. It works, and it turns a fractional engagement into a consulting project with a consulting budget.
  3. Depend on the controller. Ask the existing controller or bookkeeper to pull, explain, and restructure the data. Some help generously. Many have little incentive to make it convenient for a part-time executive to inspect their work.

The standard advice in the fractional market reflects this. Practitioner guides tell owners to keep the CFO out of the books and fix the close first, on the reasoning that otherwise the retainer gets spent on bookkeeping at CFO rates. That advice was sensible under the old economics. It also guaranteed that the most experienced person in the finance function was the furthest from the data.

What AI changes

The constraint was labor: tracing a number from the P&L back to its source transactions across three or four systems took days of someone's time. That is now work an AI model does well and quickly, under supervision. A capable CFO can connect read-only to the ledger, the bank feeds, billing, and payroll, and have AI:

  1. Map the plumbing. Document how data moves between systems today, where it is rekeyed by hand, and where the definitions disagree (what counts as a customer, a booking, a margin).
  2. Reconcile and clean. Match records across systems, surface the breaks, and propose corrections for a human to approve.
  3. Rebuild the reporting on top. Once the data ties out, the forecast and the KPI page rest on something real.

This week's Claude Fable 5.2 release shows where the capability stands. Box reports the model flagging a mismatch between salary deposits and a bank statement balance in a loan file. Oracle reports that in one test, two other models generated SQL that ran cleanly and overstated totals five to eight times by summing summary rows. The first example is why this works. The second is why the CFO still matters: the output has to be checked by someone who knows what the number should roughly be.

Traditional fractional CFOAI-enabled fractional CFO
Starts fromThe books as reportedSource systems and transactions
Data cleanupSomeone else's job, or a separate projectDone in the engagement, with AI doing the volume
Depends onController cooperation or added headcountRead-only system access and their own judgment
First deliverableA deck or a modelA data map and a list of what does not tie
Strategic advice rests onNumbers nobody has tracedNumbers traced to source

The org design that follows

For a company between roughly $5M and $100M in revenue, the finance function changes shape:

  1. The CFO seat can be fractional and still be deep. The test for the hire changes. Ask a candidate to show, in your systems, how they would trace one number from the P&L to source using AI in their first 30 days. A candidate who answers with a deck is the old model.
  2. The controller's job moves from gatekeeper to owner of controls. The controller no longer decides what the CFO gets to see. They own the close, the approvals, and the accuracy of what AI proposes. That is a better job, and it should be offered that way.
  3. The analyst layer shrinks or never gets hired. The work a first finance analyst did (pulling, matching, formatting) is the work AI absorbs first.
  4. Guardrails are part of the design. Read-only access first. AI proposes entries and a person posts them. Reconcile to the bank every period as the independent check. Use enterprise AI tools with clear data terms for payroll and customer data. And document the pipelines, so the function does not depend on one fractional executive's laptop. This week's headlines are a reminder of what single points of failure cost.
The strongest counterargument: AI cleans data; it does not fix the process that produces bad data. If orders are entered wrong at the source, the cleanup repeats every month until someone changes the process, and that is operating work a part-time executive may not have the hours for. The combination is also scarce. CFO Dive, citing BTG's 2026 talent report, has interim-CFO demand up 14% year over year, with "financial controls, accounting and audit" the most requested skills and digital and AI work touching a quarter of requests. Experienced CFOs who are also fluent with AI are a small pool, and for now they can choose their clients.

Standalone articles from this issue

Written by .

Get the newsletter in your inbox

A weekly, curated digest on AI and organizational design.