Break The Job Down Before You Add Someone New
Write the 10 recurring tasks you expect, sort them into four work types, and use that map to decide whether to hire, automate or redesign.
Start by listing the 10 things you expect the new person to do on a regular basis. Not the title, not the credentials — the actual, repeatable work. Then group those tasks into four categories: judgment, relationship, repetition and coordination. That simple exercise will often show whether you really need another hire or whether the team is struggling with a clogged process that a new résumé won’t fix.
Organizations default to hiring when teams feel stretched, but people are an expensive band‑aid. Growth generates two kinds of work: new, value-generating activity and the overhead of keeping that activity running. It’s the latter that quietly fills job descriptions with chores born of poor design. Recent government research found only about one in six to one in five firms reporting broader AI use late last year and early this year, though bigger companies and knowledge-focused units used it more. And those same functions — sales, marketing, strategy and IT — are often where work like lead routing, follow-up, scheduling and content handling creates pressure for extra heads.
Automation can free capacity, but it helps only when it’s aimed at the right tasks. A survey-style industry report shows roughly nine in 10 organizations use AI somewhere in the business, yet advanced deployments remain uncommon. Field evidence is precise: a study of more than 5,000 support agents recorded roughly a one‑seventh productivity lift with AI assistance, with the biggest gains for less experienced staff. Another controlled trial found sharp improvements when AI was applied to tasks within its competence, and notable drops in results when teams pushed it beyond that zone. The takeaway for managers: don’t treat every bullet in a job posting as equally suited to a human.
Here’s how to think about the four buckets and the choices they imply. Judgment tasks require discretion and carry consequences — things like hiring decisions, contract negotiations, creative strategy and sensitive client escalations; these typically need a named person to own outcomes. Relationship work centers on trust and human connection — sales conversations, coaching, partnership development and high‑stakes recovery work. Repetition covers high-frequency, rule‑based chores: reminders, scheduling, routine data updates and templated messages — prime candidates for automation pilots. Coordination captures the activity that exists because systems or teams don’t talk to each other — moving information between tools, chasing approvals or reconciling versions — and often calls for process redesign before any technology is layered on.
Apply a simple rule of thumb at the founder or manager level. If most of the bottleneck is judgment or relationship work, recruiting or investing in staff development is probably warranted. If it’s mainly repetitive, build and test automation before committing to ongoing payroll. If coordination dominates, rework the workflow so fewer handoffs and manual copy‑pastes are needed. When a role mixes all three, split the work so the person focuses on the parts that require a human and the rest is handled by systems or redesigned processes. As one operations leader I spoke with put it: “We started treating job postings as luggage for broken processes — once we unpacked the tasks, the solution became obvious.” In short, map the work first; pick people and tools second.
Comments