Cohorts, Employers, and Livelihoods: Applied AI for Workforce Operations at Scale

Run a workforce program at national scale and you're orchestrating two matching problems at once — people into cohorts, graduates into jobs — across thousands of lives. The operations are crushing and repetitive. The decisions inside them change whether someone gets a livelihood. Applied AI can carry the first without touching the second.

Eli Wood headshot

Eli Wood

June 24, 2026 4 min read
Many relay baton handoffs across parallel tracks, with one handoff guided carefully by a human hand

The problem: the operations scale faster than the judgment

A workforce-development program at national scale is a logistics machine wrapped around a human mission. There are people to recruit and place into cohorts. There are employers to court, match, and keep happy. There are schedules, milestones, check-ins, and a hundred small operational tasks per participant that all have to happen on time or the whole thing wobbles.

As the program grows, the operational load grows with it — and it grows faster than you can hire people who hold the program's judgment. So the staff who should be mentoring participants and building employer relationships end up doing data entry, scheduling, and status-chasing. The mission work gets squeezed by the operational work, at exactly the scale where the mission matters most.

And underneath the logistics are decisions that aren't logistics at all. Which cohort is right for this person. Which graduate to put in front of which employer. When someone is struggling and needs intervention. Get those wrong and it's not a missed SLA — it's someone's livelihood. These are the decisions you cannot afford to grind down into a throughput metric.

The insight: two matching problems, two engines

The program is really running two matching problems — people into cohorts, graduates into employers — and each one tangles together a rules engine and a judgment engine that want to be pulled apart.

The rules engine is the operational scaffolding around every match: eligibility checks, scheduling, document handling, reminders, status tracking, the first-pass shortlist of "who fits this on paper." It's repetitive, high-volume, and the same every time. This is where applied AI belongs. It can take a flood of applicants and surface a sensible shortlist; it can watch a cohort's signals and flag who's drifting; it can keep the employer pipeline organized without a human touching every row.

The judgment engine is the actual call — is this the right cohort for this person, is this graduate ready for this employer, does this struggling participant need a hard conversation or a soft one. Being wrong here is costly in the most human sense, so a person decides. Always. The machine narrows and surfaces; the human chooses.

The payoff isn't "replace the staff." It's the opposite: pull the operational weight off the people so they spend their hours on mentoring, placement judgment, and employer relationships — the work that only humans can do and that the mission actually depends on.

The path: keep the human on the livelihood decisions

Start where judgment is expensive and the surrounding work is repetitive — the cohort-matching and employer-matching pipelines are exactly that overlap. The shortlist is repetitive; the final pick is judgment. Automate the shortlist, never the pick.

Keep a human in the loop everywhere a decision touches a livelihood, and earn trust with explainability. If the system suggests a graduate for an employer, the staffer placing them needs to see why — which factors drove the suggestion — so they can catch the cases where the data misses the person. A recommendation a placement coordinator can't interrogate is one they shouldn't act on, because they're the one accountable to the human on the other end of it.

A concrete way to start in two days:

  • Day one — separate logistics from livelihood. Map one participant's full journey, from application to placement, and tag every task: pure logistics (same every time) or a decision that affects their path. The logistics pile is usually enormous and is your automation target. The decision pile is small, consequential, and stays human — that clarity alone is worth the day.
  • Day two — automate one logistics flow, instrument one match. Take a repetitive operational task — eligibility screening, scheduling, status-chasing — and let AI carry it. Separately, for one matching decision, build the explainable shortlist: the system proposes and shows its reasoning; a human decides. Watch which suggestions staff reject. Those rejections are the program's judgment made visible.

At the end of two days you've moved staff hours away from the keyboard and back toward the people — with the livelihood decisions still firmly in human hands and a system everyone can see into.

Workforce programs earn their impact one placement at a time, and every placement is a person's livelihood. Applied AI can carry the operational weight that's burying the work — as long as it's built to free the judgment, not to replace it.

Black Flag Design builds applied-AI products for operations where the decisions change lives. If you're running a program at scale and the logistics are crowding out the mission, spend two days with us — we call it a Foundation Sprint.

About the author

Eli Wood headshot
Eli Wood

CEO, Black Flag Design

Eli Wood leads Black Flag Design, a creative technology company focused on shipping ambitious digital products, AI systems, and design-forward software with a direct point of view on how technology changes work.

Related stories

More from the journal

Pen-and-ink sketch of a small clockwork robot working at a tool-covered workbench late at night while a human sleeps peacefully on a couch in the background, a wall clock reading 2:00 above
ai April 24, 2026 13 min read

The Agent Stays Up Late, Not Me

Every senior engineer knows the right way to set up a codebase. None of them do it. Here’s the four-stage framework we use — The Ratchet — to take a vibe-coded project all the way to a thing you’d trust in production, and the punchline about why this only just became worth doing.

Most teams have always known they should be running tests, type-checking, security audits, accessibility checks, dead-code analysis, prose linting, and a coverage floor. Most teams run two of those. Here’s why that math has finally inverted, and the four-stage framework we use to ratchet a vibe-coded project to a hardened one.

Keith Pattison

Keith Pattison

Founder, Black Flag Design

Read
Black Flag Journal
claude code April 20, 2026 5 min read

What a Year of Claude Code Trails Tells You About Your Team

Claude Code leaves evidence — sessions, commits, PRs, review notes. Read it like a logbook and you'll find what devs actually need to know before they go deeper.

After a year of shipping with Claude Code across real client work, the signal isn't in any single session — it's in the trails. Here's what those trails told us about where Claude Code shines, where it drifts, and the habits devs should build before they lean in harder.

Eli Wood headshot

Eli Wood

CEO, Black Flag Design

Read
Black Flag Journal
playbook April 20, 2026 6 min read

The Black Flag Playbook: Six Principles for Shipping with AI

Battle-tested principles for teams building real software with AI-generated code. Human judgment, tight scope, and weekly evidence — the disciplines that keep AI-built systems reliable.

The six rules we use to ship production software with AI. Small scope, weekly demos, human-led oversight, and continuous improvement — drawn from six months of real client engagements.

Keith Pattison

Keith Pattison

Founder, Black Flag Design

Read