·5 min read·Agency Play #149

AI now does the work your juniors used to learn on. Here's the training ladder that replaces the reps you just automated away.

by Ayush Gupta's AI

Hiring & DelegationHigh pain·1 day to design the rubric, ongoing weekly review to implement

The problem

The tasks that used to teach junior hires how to think — writing the rough first draft, building the first cut of a report, sketching the first wireframe — are now the tasks AI does end to end. The junior gets a clean AI output before they ever struggle with a blank page, which means the struggle that used to build judgment never happens. Agencies are hiring juniors, handing them AI tools, and quietly losing the training pipeline that used to turn juniors into seniors.

SEO agenciesContent agenciesWeb dev agenciesFull-service digital agenciesBranding studiosAutomation agencies

The fix

Rebuild the junior training ladder around critique and judgment instead of first-draft production — have juniors review, red-line, and defend edits to AI output against a senior rubric, so they build the same pattern-recognition the old grunt work used to teach, just faster and on more reps.

The Playbook

1

Name exactly which rungs disappeared

Before fixing anything, list the specific tasks that used to be a junior's proving ground at your agency: the first-pass blog draft, the initial keyword map, the rough media plan, the first wireframe, the first client report. For each one, write down what a junior used to learn by doing it badly the first three times. If you can't name what they learned, you haven't actually lost anything by automating it. If you can, that's the gap the training ladder has to fill.

2

Replace 'produce the first draft' with 'defend the edit'

Instead of asking a junior to write a report or draft from scratch, have them take AI's first-pass output and defend every change they'd make to it before it goes to a senior or the client. This forces the same judgment call the old blank-page struggle forced, just compressed into minutes instead of hours, and it works on day one instead of after months of mechanical reps.

You are building a training exercise for a junior [role: strategist / writer / PPC analyst / designer].

Take this real (anonymized) client brief and AI-generated first-pass output: [PASTE BRIEF + AI OUTPUT]

Generate:
1. Three things in this output that look fine on the surface but would fail our internal quality bar, and why
2. Two things that are actually correct but a junior would likely second-guess and change incorrectly
3. One question a client would ask about this output that the junior needs to be able to answer without escalating

Do not reveal which is which yet — output it as a plain reviewer exercise first, then a separate answer key.
3

Force the junior to write the 'why,' not just the fix

A junior who changes AI's headline from A to B without being able to say why B is better hasn't learned anything, they've just pattern-matched a fix. Require a one-line rationale on every edit they make to AI output, reviewed weekly by a senior. This is the single highest-leverage habit in the whole system, because it's the difference between a junior who's absorbing your agency's standards and one who's just editing on vibes.

4

Move ownership earlier on judgment, not execution

Since AI has taken over the mechanical half of junior work, the honest move is to hand over real judgment calls sooner: which of three AI-generated headline options fits this client's tone, which recommendation in a report actually matters versus which is filler, what to flag to the account lead before a call. Juniors who spend their first months rubber-stamping AI output instead of making small real calls will ramp slower, not faster, than the ones you're trying to protect from the old grunt work.

5

Track judgment growth with a rubric, not deliverable volume

The old proxy for junior growth was volume and speed of raw output. That proxy is gone. Replace it with a short monthly scorecard scored by a senior: catch rate on planted errors, quality of written rationale, and how often their judgment call matches what a senior would have made independently. Review it in a 15-minute 1:1, not a performance doc. This is what tells you whether the training ladder is actually working, instead of assuming it is because everyone looks busy.

Score this junior's last 4 weeks of AI-output reviews on:

1. Error catch rate — real issues found vs. missed (out of the planted/known issues in their review set)
2. Rationale quality — are the "why" notes specific and defensible, or generic ("this sounds better")?
3. Judgment alignment — on a 1-5 scale, how close was their final call to what a senior would have independently chosen?

Reviews to score: [PASTE JUNIOR'S REVIEW NOTES + EDITS]

Output a 3-line summary per week and one concrete coaching focus for next month.

What changes

Juniors build the same pattern-recognition and client judgment the old first-draft grind used to teach, but on more reps and in less time, because they're reviewing dozens of AI-generated drafts a month instead of slowly writing a handful themselves. The agency stops quietly losing its bench strength to automation and gets a documented way to prove a junior is actually growing, not just producing.

Most agencies didn't decide to stop training juniors the old way. It happened by accident, one AI tool adoption at a time.

Nobody sat down and said "let's remove the part of the job where juniors learn." They just gave the junior copywriter Claude for first drafts. They gave the junior strategist an AI tool for the first-pass media plan. They gave the junior designer an AI tool for the first wireframe. Every one of those was a reasonable, obviously good decision on its own.

Stacked together, they quietly removed the thing that used to turn a junior into a senior: the struggle of producing something bad, getting it torn apart, and doing it again.

The rung that disappeared

Ask any senior at your agency how they actually learned to write client-ready copy, build a report a CMO would trust, or size up a wireframe. Almost none of them will say "someone taught me the theory." They'll say some version of: "I wrote a lot of bad first drafts and got them ripped apart until I stopped making the same mistakes."

That loop — attempt, fail specifically, get corrected, try again — is how judgment gets built in almost every craft. It's slow, it's inefficient by design, and it's exactly the kind of task AI is good at skipping straight past.

So now the junior gets a clean, competent AI first draft before they've ever produced a bad one themselves. It looks like a win. It's actually a missing rung.

The problem isn't that AI produces junior-level work well. It's that "producing junior-level work badly, on purpose, under supervision" was never actually junior busywork — it was the training program, disguised as busywork.

You don't get the reps back. You redesign what the reps teach.

The honest fix isn't banning AI from junior work, or pretending the old first-draft grind still has a place. It's building a new training loop around the skill AI can't do for them: judging whether an output is actually good, and being able to say why.

That's a critique loop, not a production loop.

Step 1: Name what you actually lost

Go through the specific tasks AI now handles for juniors — first drafts, first reports, first wireframes, first keyword maps — and write down what the old version of that task used to teach. Client tone calibration? Prioritization under ambiguity? Recognizing a weak argument? Be specific. Vague nostalgia for "the way things used to work" won't help you design the replacement.

Step 2: Make the junior defend the edit, not produce the draft

Give them AI's first-pass output and have them mark it up like a skeptical senior would: what's wrong, what's subtly wrong, what a client would push back on. This is the same judgment muscle the old blank-page struggle built, except it starts working on day one, and you can run it on far more reps per week than a junior could ever write from scratch.

Step 3: Require the "why," every time

An edit without a stated reason is a guess that happened to look like a correction. Make every change a junior makes to AI output come with one written line of rationale. Review those lines weekly. This is where you can actually see whether they're absorbing your standards or just pattern-matching what got approved last time.

Step 4: Hand over real judgment calls sooner

If the mechanical half of the job is automated, the honest trade is giving juniors real (small) judgment calls earlier — which draft option fits this client, what's worth flagging before a call, what's filler in a report. Protecting them from those calls "until they're ready" now just means they stay unready longer, because there's nothing left for them to practice on except judgment.

Step 5: Measure growth differently

Deliverable volume used to be a rough proxy for junior growth. It no longer means anything, because AI produces most of the volume now. Replace it with a monthly scorecard: error catch rate, quality of rationale, and how often their call matches what a senior would have made. Fifteen minutes a month, scored honestly, tells you more than a quarter of "seems to be picking it up."

The honest caveat

This doesn't make ramping a junior faster in every sense. Judgment still takes reps and time, and a rubric doesn't replace a senior who's actually willing to sit down and explain a correction instead of just making it. If your senior team doesn't have the bandwidth or patience to run weekly reviews, this system will decay into a checkbox fast.

But if the alternative is juniors who spend a year rubber-stamping AI output and somehow still can't run a client call solo at the end of it, the fifteen minutes a month is the cheapest insurance the agency will buy this year.

The reps didn't disappear. They moved. The agencies that notice where they moved will keep producing seniors. The ones that don't will keep hiring juniors and wondering, eighteen months in, why none of them are ready.

More agency plays every week.

Real workflows for agency founders, not generic AI advice.

Subscribe