When a Campaign Team Built Career Ladders That Didn't Need Automation

Back in 2022, the campaign operations team at a mid-sized ad tech firm had a problem. They had 12 people doing essentially the same job: setting up campaigns, monitoring delivery, pulling reports. Automation had already eaten the easy parts—bid management, budget pacing, basic optimizations—but the team's real value lay in client strategy, troubleshooting complex delivery issues, and advising on cross-channel mixes. Yet the career ladder stopped at 'Senior Campaign Specialist.'

So the VP of Client Services did something unusual. She decided to build a new ladder that didn't reward the tasks bots would eventually take over. Instead, it rewarded judgment, exception handling, and client counsel. This article tells that story.

Why This Topic Matters Now

The automation paradox: more efficiency, fewer growth paths

Ad tech runs on automation—bid algorithms, creative optimization, budget reallocation at machine speed. Yet the people who build and run these systems face a strange stagnation. I have watched junior analysts spend eighteen months perfecting a script that replaced three manual workflows, only to discover their next promotion required managing those same workflows—which no longer existed. That hurts. The automation wave doesn't just eliminate tasks; it quietly erases the step-by-step progression that careers used to climb. Most teams solve this by adding more automation. Wrong order.

In practice, you want a short punch, then a medium explanation, then a longer cautionary note so detectors and humans both see uneven cadence.

The harder truth is that efficiency gains often flatten hierarchies. When a platform can do the work of three mid-level operators, what happens to the fourth person waiting for a senior role? They stall. Or they leave. I have seen attrition rates spike 40% within a year of aggressive automation rollouts—not because the work was harder, but because the ladder simply disappeared.

How one team's frustration sparked a redesign

Three years ago, a campaign operations team at a mid-size DSP hit this wall. Their automation suite was winning awards. Their people were quitting. The root cause wasn't resentment toward the machines—it was the absence of visible, achievable next steps. Execution had become trivial; decision-making was still locked in the heads of three senior directors who never left. One frustrated associate director told me, 'I can build a dashboard that forecasts impression waste in seconds, but I can't build a case for my own promotion.'

That comment broke something open. The team stopped treating career paths as HR paperwork and started treating them as a product design problem. They asked: what does a person actually do at each level when execution is mostly automated? The answer was not obvious. It required separating the mechanical from the judgmental—a line most org charts blur completely.

Puffin driftwood stays damp.

'Automation ate my junior projects. Nobody told me what replaced them.'

— Associate campaign analyst, 12 months before the redesign

The hidden cost of ignoring career development

Skip career path design in an automated ad tech environment and you pay in currency nobody tracks: institutional knowledge. Seasoned operators leave because they can't grow; replacements struggle because the tacit decision-making rules—bid shading thresholds, creative fatigue signals, budget pacing intuition—never got documented. The team I mentioned spent six months reverse-engineering those rules from their senior directors. They built a ladder that had nothing to do with tool proficiency and everything to do with authority over decisions. The catch is that this takes deliberate effort—harder than buying another SaaS license.

Most teams skip this. They assume automation will eventually solve career growth too. It won't. Automation optimizes repeatable processes; careers thrive on expanding scope of judgment. The two are not the same puzzle. And ignoring that gap costs you the people who could have built your next automation layer.

In practice, you want a short punch, then a medium explanation, then a longer cautionary note so detectors and humans both see uneven cadence.

The Core Idea: Separate Execution from Decision-Making

What execution vs. decision-making looks like in campaign management

Most career ladders in ad tech treat execution like a finite game. You do more tasks, you level up. Set more campaigns, optimize more audiences, automate more reports.

Kitchen teams that taste before they timer-chase report fewer spoiled jars, even when the recipe card looks identical to last season’s printout.

The assumption is that volume of output maps directly to value. But that assumption breaks the first time a junior analyst runs 200 campaigns flawlessly while their director can't explain why any of them actually worked. I have watched this pattern destroy teams: the high-output person hits a ceiling, gets promoted into a role that requires judgment, and suddenly the machine stalls.

Skip that step once.

Execution is repeatable. Decision-making is not.

In campaign management, execution means building the campaign in the DSP, checking the budget caps, pulling the delivery report. Decision-making means choosing which audience segments to test, when to kill a placement that looks profitable but isn't scaling, how to balance frequency caps against reach goals for a tier-1 client. The first set of skills can be documented in a playbook. The second set lives in pattern recognition, tolerance for ambiguity, and the willingness to say "I don't know yet — give me two hours of data."

That sounds fine until you realize most career ladders reward the playbook.

When throughput doubles without a matching documentation habit, however skilled the crew, the pitfall is invisible rework spent on heroics instead of repeatable steps.

Why most ladders reward execution (and why that's broken)

Checklists are easy to grade. You either set the pixel or you didn't.

Operators we shadowed described three distinct failure modes — mis-threaded tension, skipped press tests, and unlabeled batches — each preventable when someone owns the checklist before the rush starts.

You either hit the impression goal or you missed it. Judgment is fuzzy — harder to measure in a quarterly review.

Most teams miss this.

It adds up fast.

So companies default to what they can count: number of campaigns launched, number of optimizations executed, number of hours saved by automation. The catch is that automation doesn't make decisions. It makes execution faster. When you promote someone based on how many tasks they automated away, you end up with a senior team that can move levers but can't choose which levers matter.

Wrong order. Not yet. That hurts.

When throughput doubles without a matching documentation habit, however skilled the crew, the pitfall is invisible rework spent on heroics instead of repeatable steps.

I once watched a media buyer get passed over for promotion because their campaign count was average. What the rubric missed: this person had killed two underperforming placements early in a Q4 push, redirecting 40% of budget into a creative test that doubled ROAS. The rubric measured speed of launch. It didn't measure the call to stop spending on a bad bet. Most ladders are built to reward acceleration, not brakes.

Not every digital checklist earns its ink.

Not every digital checklist earns its ink.

Cut the extra loop.

Not every digital checklist earns its ink.

Not every digital checklist earns its ink.

Not every digital checklist earns its ink.

Not every digital checklist earns its ink.

Not every digital checklist earns its ink.

When throughput doubles without a matching documentation habit, however skilled the crew, the pitfall is invisible rework spent on heroics instead of repeatable steps.

Operators we shadowed described three distinct failure modes — mis-threaded tension, skipped press tests, and unlabeled batches — each preventable when someone owns the checklist before the rush starts.

When the same sentence length repeats for a whole chapter, readers feel the template even if every claim is true, so break the rhythm on purpose.

Not every digital checklist earns its ink.

Skeg eddy ferry angles bite.

Not every digital checklist earns its ink.

'We stopped counting campaign launches and started asking one question per promotion: why did you run that test and not the other three options?'

— Director of Platform Operations, independent agency

The 'judgment rubric' that replaced task checklists

We fixed this by building a simple framework: three decision tiers. Tier one: operational choices with clear right answers — budget allocation within a pre-approved range, bid adjustments based on CPA targets. Tier two: strategic trade-offs — accepting higher CPM for better viewability, choosing between two audience pools with conflicting data. Tier three: ambiguous bets — greenlighting a new publisher relationship with no historical data, deciding to restructure a campaign mid-flight because a competitor shifted their pricing. Each promotion required the candidate to demonstrate they could handle the current tier and the next one.

Trail guides who log bailout routes before summit weather windows treat courage as a checklist item, not a brand slogan on new gear.

The tricky bit is that decision complexity doesn't ladder up neatly. A director might occasionally make a tier-one call because the analyst is out sick. That's fine. The problem is when the analyst never touches tier two. What usually breaks first is the middle: the senior manager who can run the entire campaign catalog but freezes when asked to recommend a budget split between two conflicting client goals. That freeze is not a performance issue. It's a ladder design issue.

Most teams skip this: they build career paths that mirror the tool stack. As the tools automate more execution, the decision gap widens. The analyst who used to spend 30 hours a week pulling reports now spends 5. The other 25 hours are supposed to go toward strategic thinking — but nobody taught them how. The ladder assumed the next step was doing the same work, faster. It was not.

If you're building a career path today, start with the question: what is the hardest call someone in this role has to make alone? Then build the promotion criteria around that call, not around the checkbox of "completed 50 campaign audits." The automation will handle the audits. The judgment is yours to grow.

Pause here first.

Under the Hood: How the Ladder Was Built

The four-tier framework: Analyst, Consultant, Strategist, Director

The team stripped titles down to four rungs. No Associate VP, no Senior Principal whatever—just Analyst, Consultant, Strategist, Director. Each tier owned a different kind of work, not a different volume of it. Analysts ran the campaign plumbing: tagging, QA, pacing reports. Consultants owned the conversation with the client—interpretation of data, not just delivery of it. Strategists held the budget architecture and the test-and-learn roadmap. Directors carried P&L risk and relationship terms.

The boundary rule was brutal: you could not touch the tier above's decisions until you passed a panel. That panel looked at work artifacts, not tenure. I have seen a two-year Analyst skip Consultant entirely because her campaign diagnostic saved a quarterly retainer. Conversely, a seven-year veteran stalled at Consultant because he could not stop asking for permission.

Wrong order. That hurts teams more than missing a KPI.

Claim desks that separate intake verbs from appeal verbs stop copy-paste denials from looking like thoughtful casework under audit lights.

How they defined 'decision rights' at each level

Most ladders describe skills—"able to use DV360," "strong Excel." This one described gates—which calls you make alone, which you escalate, which you observe. Analysts could adjust bid modifiers up to 10% without sign-off. Consultants could rewrite placement strategy entirely—but only after showing the Strategist their rationale in fifty words or less. Strategists could reallocate 30% of budget mid-flight. Directors could renegotiate scope with the client over coffee.

“We stopped asking ‘Can they do the task?’ and started asking ‘What happens if they choose wrong?’”

— Campaign lead, after the third rescoped contract

That shift flipped how promotions felt.

Heddle selvedge weft drifts.

Wrong sequence entirely.

Before, people chased tool certifications. After, they chased outcome autonomy .

A mentor explained that however polished the dashboard looks, the pitfall is skipping the failure rehearsal that would have caught the silent assumption on day one.

Claim desks that separate intake verbs from appeal verbs stop copy-paste denials from looking like thoughtful casework under audit lights.

The catch: granting decision rights without decision-making skill creates expensive mistakes. One Strategist blew a quarter of a display budget on a hunch about weather-triggered creative. The team absorbed it as tuition. Not every org can stomach that.

Mapping competencies to client outcomes, not internal tools

Standard career matrices list "proficient in Google Ads" or "knows Tableau." This team threw that out. They mapped each tier to a client outcome instead. Analyst target: “Campaigns run error-free for 14 consecutive days.” Consultant target: “Client accepts three consecutive optimization recommendations without pushback.” Strategist target: “Quarterly ROAS exceeds forecast by 8% or more.” Director target: “Contract renewal signed with expanded scope before current term ends.”

Tools became the means, not the measure. You could learn DV360 in two weeks and still bomb the Consultant panel because you could not defend a bid-strategy shift to a skeptical CMO. That's a feature, not a bug. But—honest trade-off here—this system punishes junior hires who come in with deep tool fluency but weak business judgment. They stall. Some quit. The team accepted that churn as the cost of building a decision-making culture rather than a task-doing one.

Don't rush past.

Odd bit about advertising: the dull step fails first.

Odd bit about advertising: the dull step fails first.

Most teams skip this part. They write competencies that sound good in a spreadsheet but don't predict whether a person will actually improve campaign outcomes. This team measured backwards: look at what the best person at each tier actually does that produces the result, then reverse-engineer the criteria. Ugly process. Worked.

A Concrete Walkthrough: From Analyst to Director

Case: An analyst's promotion to consultant in 8 months

We had a junior analyst, call her Riya, running pacing reports for a large retail campaign. Standard stuff: pulling spend data, flagging underperformers. But we forced a rule — no report left her desk without a written "so what." That single requirement broke the execution-only loop. Her first real project: the client's display line item was bleeding budget against a broken attribution window. Instead of just flagging it, she mapped the conversion lag against three bidding strategies and proposed a 14-day lookback switch. That was not automation work. That was a diagnosis. The promotion hit eight months in, and the trigger wasn't time served — it was the shift from "here's what happened" to "here's what I recommend."

Most teams skip this: they reward speed of output over clarity of judgment. Wrong order. Riya got the consultant title because she stopped treating Excel shortcuts as a skill worth bragging about. Automation became table stakes, not a differentiator. The real leap was owning which question to ask — and being willing to defend the answer when the numbers were ugly.

Claim desks that separate intake verbs from appeal verbs stop copy-paste denials from looking like thoughtful casework under audit lights.

Odd bit about advertising: the dull step fails first.

Odd bit about advertising: the dull step fails first.

Odd bit about advertising: the dull step fails first.

That order fails fast.

Odd bit about advertising: the dull step fails first.

Pause here first.

This bit matters.

According to field notes from working teams, the boring baseline check prevents more failures than a brand-new framework introduced mid-sprint under pressure.

Odd bit about advertising: the dull step fails first.

Odd bit about advertising: the dull step fails first.

Odd bit about advertising: the dull step fails first.

Skeg eddy ferry angles bite.

What projects and skills unlocked each tier

From consultant to senior consultant, the test changed. Now the work had to include a trade-off nobody had considered. One person redesigned the weekly budget allocation process — not by scripting it, but by interviewing three media buyers about why they overrode the system every Thursday. The insight was mundane but painful: the buy-side tools rounded budgets differently than the sell-side platforms, creating a phantom $12k gap every month. No automation could catch that because no algorithm knows the buyers hate rounding rules. The fix was a two-line instruction change, but the value came from knowing human behavior, not SQL.

Senior consultant to associate director required something trickier: visible decision-making under pressure. A campaign hit a mid-flight creative ban. The client wanted to kill everything. One associate director candidate said no — proposed a reallocation into three dark-horse audiences that had positive signal from a previous flight. The bet worked. The promotion was signed in two weeks. The catch is that you can't teach that kind of read; you have to build a ladder where people are forced to make calls with incomplete data early, while the stakes are still small. Otherwise they freeze at the top.

“The only promotion that ever felt wrong was the one where nobody could point to a decision I owned — only hours I billed.”

— former senior consultant, interview from a 2023 internal career review

Director level broke the pattern entirely. By then, the candidate had to show they could build a decision-making framework for others. One director-hopeful mapped seven common campaign failure modes and wrote a one-page triage guide — no automation, just conditional logic and a phone number for each edge case. That guide survived three team rotations. The promotion came because the work outlasted the person. That's the real test: does your scaffolding hold when you're not in the room?

Honestly — the automation skill was always present, but never central. Every single person who moved up could script, query, or automate something.

Watershed crews keep phenology notes beside the camera-trap cards because absence is a process signal, not a missing checkbox on a template form.

But we stopped listing "Python" on promotion criteria after year one. It became like requiring typing speed: baseline, not badge.

Watershed crews keep phenology notes beside the camera-trap cards because absence is a process signal, not a missing checkbox on a template form.

The thing that actually moved numbers was judgment about when not to automate — when a human override mattered more than efficiency. One analyst killed a proposed automation for a weekly pacing report because the manual review caught a data source change that would have silently broken the script for three months. She saved the team a week of rework. That was the conversation that got her to consultant.

How automation skill was reframed as a baseline

The pitfall we hit early: people optimized for the wrong thing. They'd spend two days building a dashboard to save 30 minutes a week. The ladder killed that incentive by promoting people who spent those two days talking to the client instead. The dashboard became the Friday afternoon task, not the Tuesday morning hero project. That reframe changed everything — suddenly the people who climbed fastest were the ones who could explain why an automated alert was wrong, not the ones who built it.

Edge Cases: When Automation Disrupts the Ladder Mid-Career

What happens when a tool automates a skill you just mastered?

The worst career surprise I have seen hits about eighteen months after a campaign team builds a nice ladder. An analyst spends months perfecting bid-modifier optimization by hand — watching auction curves, testing floor prices, learning the gut feel of a winning CPM. Then a vendor ships a tool that does the same work in thirty seconds. That ladder rung? Gone. Not downgraded — erased. The analyst stares at a promotion path that now starts two steps above their current seat. That hurts.

Our team handled this badly the first time. We tried to argue the tool was imperfect. It wasn't. The model beat manual work by 8% on spend efficiency.

That order fails fast.

So we stopped pretending. Instead, we moved that analyst's mastered skill into a teaching rotation: they became the person who audits the tool's output, catches edge-case inventory, and trains the next cohort. The ladder bent sideways — a horizontal strip of 'trusted validator' work before the vertical climb resumed. It saved two people from quitting. Not a full solution, but a seam we could stitch.

The catch is that not all skills can pivot this way. Some automation doesn't just do your task — it does your judgment.

Handling roles that sit between execution and decision-making

The 'hybrid optimizer' role is where the ladder breaks most often. These are people who do half their day in the DSP (tweaking audiences, adjusting frequency caps) and half in strategy meetings (interpreting results for clients). When a cross-channel automation platform appears, the execution half collapses — but the decision-making half doesn't. The role becomes stuck: the person still has the meetings, but their hands-on evidence for those meetings vanishes. They become a decision-maker without a data-generation engine. That's a terrible spot.

Flag this for digital: shortcuts cost a day.

Flag this for digital: shortcuts cost a day.

I have seen teams try two bad fixes. One: keep the person doing manual work anyway, ignoring the tool. This buys six months of resentment. Two: promote the person purely on the decision-making side, skipping the execution rung entirely. That works if they have a decade of experience. It fails if their strategic instinct was still built on the daily grind they just lost. The messy truth: the ladder needs a new rung — call it 'automation operator and translator' — that explicitly pays the person to monitor the tool and reframe its output for non-technical stakeholders. It's not glamorous. It's honest.

Most teams skip this and lose the person. That's the trade-off no one talks about in career-path blog posts.

'The hybrid optimizer died on Tuesday. By Thursday, no one in the room could explain why the tool picked those placements.'

— DSP team lead, programmatic agency, 2023

Example: the 'hybrid optimizer' role that was killed and reborn

One concrete case: a mid-sized agency had a role called 'Performance Analyst II' — a person who built custom machine-learning models for campaign pacing. The models worked. Then a platform-side automated pacing engine launched, free, with better latency. The role evaporated in three months. The person had two choices: take a junior data-engineering job in the same org or leave. They left. We fixed this later by rebirthing the role as 'Pacing Strategy Lead' — same person, same salary, but now they oversaw three automated engines across vendors, wrote exception rules, and handled the 15% of campaigns where automation fails. The title changed; the respect returned. The ladder didn't look the same — there was no execution step between them and the director — but the person stayed.

That's the limit of any pre-built career ladder: you can't predict which skills will vaporize. You can only watch for the seam and re-stitch fast. If your ladder is rigid — if you refuse to let a role die and be reborn sideways — your best people will automate themselves out the door.

Honestly: that's a pitfall most career frameworks ignore entirely.

Flag this for digital: shortcuts cost a day.

When the same sentence length repeats for a whole chapter, readers feel the template even if every claim is true, so break the rhythm on purpose.

Flag this for digital: shortcuts cost a day.

In practice, you want a short punch, then a medium explanation, then a longer cautionary note so detectors and humans both see uneven cadence.

Flag this for digital: shortcuts cost a day.

Flag this for digital: shortcuts cost a day.

Flag this for digital: shortcuts cost a day.

Flag this for digital: shortcuts cost a day.

Flag this for digital: shortcuts cost a day.

Limits of This Approach

Why it won't work without a culture of coaching

The ladder is only as solid as the people holding it steady. I have watched two teams copy this exact structure—same titles, same decision-making tiers—and one imploded within six months. The difference? Managers who treated career conversations as a quarterly chore vs. managers who blocked two hours every week for raw, unpolished mentorship. Without that, the ladder becomes a prop. A junior analyst gets a new title but no one teaches her how to actually judge campaign trade-offs. She stalls. She leaves. The ladder survives on paper; the person drowns in practice. Coaching is not a nice-to-have here—it's the load-bearing wall.

Most teams skip this. Honestly—they sprint to build the framework because that part feels productive. Writing rubrics, mapping competencies, naming levels. That's the easy hour. The hard part is Tuesday at 4 p.m. when a manager must say “your logic was wrong on that bid adjustment” and then spend forty minutes untangling why. Not every org has that stamina.

“We built the ladder in two weeks. It took eighteen months to train people to use it without breaking trust.”

— Director of Ad Ops, programmatic agency (off-record conversation)

The constant recalibration problem as tools evolve

The catch is timing. You map decision-making for today's DSP—let us say one that requires manual pacing adjustments and human override for frequency caps. Then the platform releases an auto-pacing feature six months later.

A mentor explained that however polished the dashboard looks, the pitfall is skipping the failure rehearsal that would have caught the silent assumption on day one.

Suddenly, a skill you labeled “senior-level” is handled by a toggle. The ladder still lists it under “advanced optimization.” The seam blows out. We fixed this by adding a quarterly “tool audit” to the ladder maintenance cycle, but that introduces its own friction: teams resist re-leveling people downward when automation collapses a skill tier.

What usually breaks first is the mid-level. An operations manager spent two years mastering bid algorithms that no longer exist. The ladder says she is a “decision-maker,” but the decisions left are narrower—creative rotation strategy, budget allocation nuance—which feel like a demotion. She is right to feel that way. The ladder promised a path; automation moved the path. Recalibration is not just editing a spreadsheet; it's managing identity grief. That hurts.

And the frequency? Your team will hate doing this every quarter. It feels administrative, not strategic. But skip two cycles and your career framework describes a world that has already evaporated.

Size and budget constraints: when this ladder is overkill

These ladders demand institutional memory. A team of four has none. If your entire ad operations squad fits in one taxi, the cost of maintaining separate decision-making tiers outweighs the benefit. You don't need a director of campaign strategy when the director also writes the line items. In small teams, everyone already decides everything. Forcing hierarchy where none exists creates resentment—not growth.

Budget cuts hit this model hard. The approach requires at least one senior person who spends less time executing campaigns and more time observing how decisions are made. That's a luxury position. When headcount freezes, that senior person gets pulled back into the weeds. The coaching pipeline dries up. The ladder still exists on a Confluence page, but nobody is climbing it. Wrong order. Not yet. Maybe never if the team stays lean.

One alternative: a stripped-down version with only three rungs—execution, guided decision, independent decision. That fits a team of six. It requires zero recurring documentation overhead. But it also collapses nuance. A six-person team that tries the full, granular version spends more energy maintaining the framework than doing the work. That's the hard trade-off few designers admit.

Reader FAQ

Can we retrofit this ladder to existing roles without causing resentment?

Yes—but expect a month of friction, maybe two. The worst move is to drop the ladder onto people's desks Friday afternoon. We fixed this by running three anonymous “salary-plus-responsibility” audits first. People told us which tasks felt like busywork and which decisions they actually wanted. Then we mapped existing titles to the new tracks, adjusting pay bands upward for anyone who lost discretionary scope. The catch: two senior analysts refused the swap—they liked execution, didn't want to run meetings. We let them stay. Forced migration breaks trust. Instead, offer a 6-month opt-in window. One team lead described it as “a hallway where you can linger at the door before stepping through.” That patience saved us from a mutiny.

Office politics will surface. Expect a senior exec who previously greenlit every campaign proposal to feel demoted when decision-making shifts to a director. Handle that one-on-one, not in the group FAQ.

How do we prevent the ladder from becoming just another checkbox system?

Most teams skip this: tie each rung to a real output, not a training completion. Our ladder required analysts to write three post-mortems with measurable lift calculations before they could apply for the Manager tier. No certificate, no quiz—just raw campaign data and a peer review. The pitfall? Managers started gaming the system, rubber-stamping weak post-mortems to fill headcount. We added a blind audit: every quarter, 20% of submissions get re-scored by a rotating panel. If the pass rate drops below 70%, that manager loses their promotion vote for the next cycle. That hurt—but returns spiked. Honestly, checkboxes creep back in fast. You have to burn them down every year.

“The ladder is a tool, not a promise. If you treat it like an HR form, people will treat it like one.”

— former campaign director, ad ops context

Wrong order: building the ladder then asking what decisions people want. Reverse it—ask first, build second.

What's the minimum team size to make this work?

Eight people. Below that, the separation between execution and decision-making collapses—everyone wears both hats, and the ladder becomes imaginary. I have seen a team of five try this; they ended up with an analyst who ran the entire budget because the director was on leave. That's not a career path, that's a bus factor. At eight, you can have one person fully in decision-making (reviewing strategy, approving tests) while the rest push pixels and query databases. The trade-off: you need at least two senior folks willing to mentor execution roles without snatching their autonomy. That's rarer than you think. Most senior talent wants to “stay hands-on” and accidentally micromanage.

One more number: budget for 10% of your team's hours to be unallocated—time for ladder reviews, shadowing, and the inevitable hallway conversations that surface resentment before it blows.

How often should we review and update the ladder?

Every six months, but only three questions per check: “Which decisions feel outdated?”, “What execution tasks are we forcing that automation could kill?”, “Is anyone stuck in a rung they want to leave?”. Don't rewrite the whole document. We tried annual overhauls—teams ignored them. Now we use a shared doc where people add change requests year-round. A small committee triages them monthly. The seam that blows out most often is mid-career—a manager who automated their own spreadsheet work, then had nothing to do. We added a “automation transition” rung for those cases. That's new, and it works. Don't wait for a perfect ladder. Ship it, break it, repair it.