『Why Automating Tasks Isn't the Same as Redesigning a Role』のカバーアート

Why Automating Tasks Isn't the Same as Redesigning a Role

Why Automating Tasks Isn't the Same as Redesigning a Role

無料で聴く

ポッドキャストの詳細を見る

【Amazonプライム会員限定】今ならプレミアムプランが4か月 月額99円。

10月19日まで。※適用条件あり
This week I want to go deeper into an idea I touched on before: your job descriptions might actually be hiding how your business really works. I use a detailed example, a salesperson named Jennifer, and follow her through an entire day to show that "salesperson" isn't really one job. It's a bundle of completely different kinds of work, administrative tasks, predictable execution, pattern recognition, and high-value human judgment, that all got stitched together simply because one person had to do all of it.Once you stop asking "how much of Jennifer's job can AI do" and instead pull the bundle apart into its individual responsibilities, initial contact, qualification, scheduling, nurture, negotiation, closing, you can make a much smarter decision about how each piece should actually be executed. This is part of what I call work architecture, the first section of my AI Labor Architecture framework in my new book, The AI Workforce. Try this yourself: pick one important person on your team, forget their title for 30 minutes, and just follow the actual work that crosses their desk.Episode Timeline & Highlights[0:00] – Where would you even start explaining how your business works?[0:35] – Why a job description shows how work got bundled, not what the work actually is[1:04] – Introducing Jennifer, a top salesperson, and her simple-sounding job title[1:32] – Following Jennifer through a full day: a lead comes in and she makes contact[1:58] – The research and qualification work: comparing a lead against past successful customers[2:25] – The scheduling grind: calendar links, availability, and the back and forth to book a meeting[2:57] – Preparing for and running the meeting, then handling objections when they don't buy right away[3:20] – The nurture and follow-up work that keeps an opportunity from disappearing[3:32] – Pricing, approvals, and contract negotiation on the way to finally closing the deal[4:04] – Breaking down the four different types of work bundled into "salesperson"[5:12] – Why intelligent work has always required a person, and how that shaped the modern job[5:41] – Jennifer's job title as simply the container used to organize the work, not the work itself[6:16] – Why "how much of Jennifer's job can AI do" is the wrong question to start with[6:49] – Pulling the job apart into its individual responsibilities: qualification, research, scheduling, and more[7:30] – What it looks like once each responsibility can be assigned independently[8:04] – The real shift: not replacing Jennifer, but no longer treating Jennifer as the architecture[8:40] – Why most businesses will preserve the same work bundles even after adding AI[9:46] – Why the assumption behind those bundles has now changed[10:17] – The exercise: pick someone important and follow their actual work, not their job description[10:52] – Why the real job usually isn't captured in the written job description at all[11:25] – What makes your best people better: the judgment and context nobody ever documented[12:01] – The risk of only automating obvious tasks and calling it a redesign[12:43] – Realizing a "job" might actually be six or twelve separate responsibilities[13:50] – Separating the work, the responsibility, and the execution once again[14:23] – Revisiting Jennifer: an incredible closer spending half her week on work that doesn't need her[15:20] – Where this shows up everywhere: managers as human routing systems, founders making decisions they should have handed off years ago[15:41] – Introducing work architecture as part of the AI Labor Architecture framework[16:27] – The 30 minute exercise: forget the title, follow the actual work[17:37] – Where to find The AI Workforce and get notified when it's available5 Key TakeawaysA Job Title Is a Container, Not the Work Itself — "Salesperson" bundles together administrative tasks, predictable execution, pattern recognition, and high-value judgment into one title, simply because a person had to do all of it. The title hides how different those tasks actually are.Stop Asking "Can AI Replace This Person" — That question treats a job as one unit. The more useful question is what the individual responsibilities inside that job actually are, so each one can be assigned to whoever or whatever executes it best.Job Descriptions Capture Activity, Not Judgment — What makes your best people valuable is usually the context and judgment they've built up that was never formally written down: knowing what to ignore, when to break the process, which customer needs a call instead of an email.Talented People Often Carry Work That Doesn't Need Them — A skilled closer spending half her week on scheduling and data entry isn't a personal failing, it's an architecture problem. Once the bundle is pulled apart, that mismatch becomes visible.Try the 30 Minute Exercise on One Important Person — Pick someone on your team, ignore their title, and track everything...
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません