A tool from Chris Courneen · SHRM Visionaries 2026

The Orchestration Test

Turn your AI productivity gain into enterprise value — instead of a reflexive layoff. This coach helps you find the blind spots, put numbers on what's easy to miss, and build the case to orchestrate the freed capacity rather than cut it.

How to use it

Name the decision you're weighing.
Work the four questions — open “Go deeper” on each to pressure-test your thinking and capture it.
Read your verdict, then hit Build my argument to turn it into a case you can send.

"The team got faster, so we can run it with fewer people."

The gain is immediate and countable. The cost of cutting is deferred and invisible. So you weigh a number against a feeling, and the number wins by default. That's not a tradeoff. It's a measurement failure wearing a tradeoff's clothes.

The decision you're pressure-testing

Example — replace it

The stated reason for the cut

Question 01 · Name both numbers

Can you state the gain and the cost of cutting with equal specificity?

A savings figure to the decimal against "some morale risk" is half a spreadsheet, not a tradeoff.

Yes — I can put a real number on both sidesThe savings and the cost of cutting: lost capacity, knowledge, rework, trust. Honestly, only the savings is a numberThe cost side is a feeling, a hunch, or "we'll manage."

The gain — be specific The cost of cutting — same specificity

Go deeper — put a number on the invisible side +

Questions to sit with

If this role vanished tomorrow, what's the first thing that would quietly stop getting done — and who'd notice, three months later?
What did it actually cost — time and money — the last time you cut a role and then had to rebuild it?
When demand comes back (cheaper work invites more of it), how fast could you rebuild this capacity, and at what premium?
What knowledge lives only in these people's heads and isn't written down anywhere?

Cost buckets most people forget — tap to add to your notes

Your working estimate of the true cost of cutting (a range beats a feeling)

Question 02 · Test the link

Is your evidence a task-level speedup, or a real role-level drop in demand?

Productivity shows up at the task level. Layoffs happen at the role level. You can't subtract a task from a headcount line.

The actual volume of work has fallenDemand for the role's output is structurally lower, not just faster to produce. A tool made a step fastere.g. "56% faster on this task" — a task-level gain, not a demand drop.

Go deeper — separate the task from the role +

Questions to sit with

Name the exact task the AI sped up. Now name the role you're cutting. Are they the same thing?
If this task is now 10× cheaper, will the business genuinely want less of it — or more?
What did the productivity number actually measure: a clean benchmark, or your real, messy workflow?
Who checks, edits, and stands behind the AI's output now — and did that work disappear, or just move?

Where "freed" demand tends to go — tap to add

In one line: has demand for this work actually fallen, or just the time per unit?

Question 03 · Search for the other door

Where else could the freed capacity go — and why was that rejected?

If no one can describe that conversation, it didn't happen. Usually the other door is standing wide open.

We searched, and there's genuinely no higher-value useRedeployment was considered on the record and ruled out for a real reason. We searched — and a viable redeployment existsThere's a real place the capacity could create value. We didn't really have that conversationThe cut was the first and only option on the table.

The other door — where the capacity could go

Go deeper — find the door that's standing open +

Questions to sit with

If you weren't allowed to cut anyone, where would you point this capacity to create the most value?
What have you been unable to get to for two years because no one had the time?
What higher-value work are you currently buying from vendors that this team could bring in-house?
Could these people move into the AI work — owning, training, and checking the tools?

Redeployment targets — tap to add

Sketch the redeployment: who moves where, and the value it creates

Question 04 · Forced now, or just forced-sounding?

What is this decision actually resting on?

Cutting is fast and nearly irreversible. Holding capacity has option value. "Forced forever" and "inconvenient this quarter" are different decisions.

A durable, structural change — and the timing truly can't waitThis isn't going to reverse next quarter, and holding costs more than moving. A short pilot, a few weeks of data, or a quarterly targetThe evidence is thin and the cut is hard to undo.

Go deeper — reversible beats irreversible +

Questions to sit with

What exactly forces the timing — a real deadline, or a quarterly optics target?
If you're wrong, how long and how costly is it to undo a layoff versus to undo a hold?
What has the pilot not yet tested that you'd want to know before making it permanent?
What would you need to see in 90 days to know the cut is genuinely warranted?

Reversible moves that buy information — tap to add

What you'd propose instead of cutting now — to buy time and information

Your verdict — so far

—

What this rests on

Now build the case

The argument to take back to the business

Six moves that turn your answers into a case a CEO or CFO will actually hear. Each block is drafted from what you entered above — edit it in your own voice, then copy or hand it to an AI to sharpen.

1Start on their side

Open by sharing the goal, not fighting it. You're a steward of the business, not the resistance.

2Name what we're actually measuring

Put both numbers on the table at equal specificity, and name the gap between them.

3Separate the task from the role

Productivity shows up on tasks; layoffs happen to roles. Show the demand didn't move.

4Open the other door

Offer the constructive alternative — where the capacity creates more value than the salary saves.

5Buy information before an irreversible cut

Reversible beats irreversible when the evidence is thin. Propose the pilot, not the layoff.

6Close with the principle

Give them one line they'll repeat in the next meeting when you're not in the room.

Copied

“Build my argument” rewrites the six blocks from your answers above (it replaces edits). “Continue with AI” copies your whole worksheet as a prompt to paste into ChatGPT, Claude, or your own GPT.

← Back to chriscourneen.com / Visionaries 2026