The Next Input - Issue 145

Meta's 20% Cut and the Lazy AI Strategy

Pokemon Sleeping GIF

lazy Snorlax

⚡ The Briefing — 60 sec

🛠️ The Playbook — The AI Work Redistribution Engine

Mission
Turn AI-driven productivity gains into smarter workload design instead of defaulting straight to headcount cuts.

Difficulty
Intermediate

Build time
3–5 hours

ROI
Reduce burnout, protect trust, and convert AI efficiency into measurable operating leverage without gutting the team.

0) Why This Matters

A lot of companies are treating AI as a cost-cutting narrative first and an operating system second.

That is the lazy version.

The better move is to use AI to redesign how work gets allocated, escalated, approved, and completed. Meta’s reported layoff planning shows how quickly AI investment and labour reduction can get bundled together, while ChatGPT’s growing app integrations show the opposite force at work: a single AI layer coordinating more and more everyday tasks across tools and services.

If you are an operator, the question is not “Will AI remove work?” The question is:

Which work should disappear, which should shrink, and which should get better?

That is where a redistribution engine matters.

It helps you:

  • identify repetitive work that should be automated

  • protect judgment-heavy work that still needs people

  • shorten low-value effort before cutting roles

  • prove gains in throughput, not just payroll savings

1) Architecture

Component

Tool

Purpose

Owner

Failure mode

Task intake

Forms / inbox / CRM / ticket queue

Capture incoming work

Operations

Work arrives with poor context

Work classifier

GPT-5.4 / Claude

Classify tasks by type, complexity, and risk

AI system

Misclassification

Automation layer

Make / Zapier / custom scripts

Execute low-risk repetitive actions

Ops / Engineering

Broken automations

Human routing layer

Airtable / dashboard / ticket board

Route medium- and high-judgment work to staff

Team lead

Bottlenecks

App action layer

ChatGPT apps / connected services

Complete cross-tool actions from one interface

AI system

Unclear permissions or failed actions

Metrics layer

BI dashboard / spreadsheet

Track hours saved, throughput, and overrides

Operations

No visibility into actual gains

2) Workflow

  1. Capture recurring work items from inboxes, CRMs, forms, and task queues.

  2. Use an AI classifier to label each task by complexity, urgency, and decision risk.

  3. Automatically complete low-risk, repeatable tasks through workflow tools or app integrations.

  4. Route medium-complexity tasks to a human with an AI-generated draft or recommendation attached.

  5. Keep high-stakes decisions with humans, using AI only for summarisation, retrieval, and prep work.

  6. Measure where hours were removed, where response times improved, and where human judgment still added the most value.

3) Example Prompts

Task Redistribution Prompt

You are an operations designer.

Review the following workflow tasks and classify each one as:
- automate fully
- automate with human approval
- assist only
- keep fully human

For each task, explain:
1. why it belongs in that category
2. what risk is involved
3. what tool or system should handle it

Workload Compression Prompt

You are redesigning a team's workload after AI adoption.

Given the current task list, identify:
- which tasks can be reduced in time
- which tasks can be removed entirely
- which tasks become more important because AI handles the rest

Return:
1. a new workload split
2. estimated hours saved per week
3. key risks if the team cuts too aggressively

Human Handoff Prompt

Prepare a concise handoff for a human reviewer.

Include:
- task summary
- context retrieved
- AI recommendation
- confidence level
- what decision the human needs to make

Keep it short and operational.

App-Orchestrated Action Prompt

You are coordinating actions across connected apps.

Goal:
Complete the user's task using the minimum number of steps.

Rules:
- prefer approved connected apps
- confirm assumptions before high-impact actions
- flag any missing permissions or missing data
- return a short action summary

Task:
[insert task]

4) Guardrails

  • Do not treat “hours saved” as automatic permission to cut people.

  • Protect judgment-heavy work even if it looks slower on paper.

  • Require approval for actions involving money, customers, or legal exposure.

  • Audit which tasks were automated versus merely accelerated.

  • Review team morale alongside productivity metrics.

  • Separate workflow redesign from pure headcount reduction.

5) Pilot Rollout — 3 hours

  1. Pick one team with a high volume of repetitive, low-leverage work.

  2. List every task they perform in a normal week and estimate time spent.

  3. Classify those tasks into automate, assist, and keep-human categories.

  4. Build one lightweight workflow that auto-completes a low-risk task and drafts a medium-risk one.

  5. Track time saved, error rate, and human override rate across 10–20 live examples.

  6. Reallocate saved hours into higher-value work before making any staffing decision.

6) Metrics

  • Hours saved per workflow

  • Throughput per employee

  • Average response time

  • Human override rate

  • Percentage of work fully automated

  • Percentage of staff time shifted to higher-value tasks

  • Employee satisfaction after workflow redesign

Pro Tip: If your first AI win only shows up as a payroll line item, you are probably leaving the better upside on the table.

🎯 The Arsenal — Tools & Platforms

  • GPT-5.4 · task classification, draft generation, and workload redesign logic · GPT-5.4

  • Claude · strong structured reasoning for workflow triage and review · Anthropic

  • Make · automate low-risk operational steps across systems · Make

  • Airtable · simple routing layer for human review and work queues · Airtable

  • ChatGPT Apps · connected actions across music, shopping, travel, and other services inside ChatGPT · Apps in ChatGPT

Copy-paste prompt block:

You are helping redesign a team's work allocation in the age of AI.

Given the workflow below:
1. break the work into discrete tasks
2. classify each task as automate, assist, or keep-human
3. estimate weekly hours saved
4. identify which tasks should use connected apps or workflow tools
5. identify where human approval must stay
6. propose a 6-step pilot rollout
7. list the top 5 risks of doing this badly

Workflow:
[insert workflow here]

Return the answer in markdown with sections for:
- Task map
- Recommended automation split
- Human review points
- Tools
- Risks
- Pilot rollout
- Metrics

💡 Free Office Hours

If you are trying to use AI to redesign work without turning the whole thing into a blunt cost-cutting exercise, I run free office hours to help map the workflow, the tooling, and the safest pilot path.

🕹️ Game Over

AI will absolutely change the shape of work. The real question is whether you redesign the job or just delete it.

— Aaron Automating the boring. Amplifying the brilliant.

Subscribe: link