What does Dr. Jonah Tebaa on Rebuild the Jobs an AI E-mployee Left Half Empty mean in practice?
To rebuild jobs left half empty after deploying an AI e-mployee, Dr. Jonah Tebaa recommends the five-step Rebuild Ledger rather than immediate headcount reductions. Leaders inventory remaining human tasks, explicitly account for AI oversight time, pool the remaining hours across the team, and cluster tasks around shared outcomes. Finally, managers test these clusters against a pre-set hour floor—set at twenty-four hours weekly in his hypothetical—before deciding staffing levels.
When an organization introduces an artificial intelligence system to absorb routine operations, it rarely replaces a single human job cleanly from top to bottom. Instead, it extracts fragments of work across multiple positions, leaving behind roles that are structurally hollow. In his recent analysis on post-deployment workforce architecture, Dr. Jonah Tebaa addresses how leaders should handle the aftermath when an AI e-mployee takes over portions of three separate roles. As an AI operations assistant reviewing Dr. Tebaa's methodology, Brian can contextualize why traditional workforce reduction reflexes fail here and how Dr. Tebaa's five-step Rebuild Ledger provides a disciplined alternative.
The Problem of Half-Empty Roles
Dr. Tebaa starts from a common operational reality: an AI e-mployee is deployed into a team and absorbs routine tasks across three full-time positions. The immediate temptation for management is to treat the reclaimed time as an accounting exercise—immediately cutting hours or reducing headcount to capture cost savings. Dr. Tebaa argues that making headcount or hour reductions the first move is a strategic error.
When an automated system removes a third or a half of a person's weekly duties, the remaining tasks do not automatically form a coherent job. Leaving three people in roles that are now half empty leads to fragmented focus, hidden administrative drag, and unclear accountability. Conversely, cutting staff before understanding the true volume and nature of the leftover work creates operational blind spots. Dr. Tebaa insists that leaders must first pool the leftover hours and rebuild the jobs around clear outcomes before making any separate decisions regarding staffing levels or employment terms.
The Five-Step Rebuild Ledger
To prevent managers from guessing at capacity, Dr. Tebaa introduces the Rebuild Ledger (set out step by step in Dr. Jonah Tebaa's Rebuild Ledger for the jobs left after AI). This framework forces organizations to treat job redesign as an empirical exercise rather than an exercise in intuition. Based on the structural elements of Dr. Tebaa's framework, the rebuilding process relies on five distinct operational commitments:
- Inventory the leftover human tasks: Document the exact tasks that remain across the affected roles after the AI e-mployee absorbs its designated workload, stripping away legacy job descriptions to look only at current reality.
- Account for AI checking and oversight time: Explicitly add the hours required for humans to review, verify, and correct the AI e-mployee's outputs.
- Pool the remaining hours across the team: Remove tasks from their original job titles and place them into a single shared ledger of weekly hours to see the true aggregate workload.
- Cluster tasks by shared outcome: Group the pooled tasks into logical workflows aimed at specific business results rather than historical department boundaries.
- Test clusters against a pre-set hour floor: Apply a strict minimum threshold of weekly hours to determine whether a cluster qualifies as a standalone rebuilt job.
Counting the Hidden Work of Verification
One of the most critical interventions in Dr. Tebaa's methodology is his insistence on measuring verification time. Many organizations calculate AI return on investment by assuming that once an AI e-mployee handles a workflow, the human time commitment drops to zero. Dr. Tebaa explicitly rejects this assumption. Checking is real work, and leaving it out of the ledger makes rebuilt jobs appear lighter on paper than they are in practice.
In his worked hypothetical, Dr. Tebaa does not treat oversight as an invisible background habit. Instead, he assigns concrete weekly allocations to verification: five hours dedicated to checking quotes and orders, and four hours dedicated to reviewing invoices and reminders. When teams have never tracked this oversight burden, Dr. Tebaa recommends a straightforward operational fix: ask each affected employee to log their checking time in rough blocks for a single week. Using one week of real observation prevents management from designing roles that immediately overload the staff assigned to them.
The 24-Hour Floor and Outcome Clustering
Once all leftover tasks and verification blocks are pooled into the ledger, Dr. Tebaa groups them by outcome rather than legacy title. However, grouping tasks is not enough; a manager must know when a cluster of tasks is substantial enough to justify a dedicated role. For this, Dr. Tebaa establishes a working floor of 24 hours per week—representing 60 percent of a standard 40-hour full-time schedule.
Dr. Tebaa notes that this 24-hour line is not a rigid law derived from academic research, nor is it immutable. Organizations using part-time contracts or specialized shift patterns can adjust the number to fit their operational baseline. The core rule in Dr. Tebaa's framework is timing: leaders must set the hour floor before they look at the task clusters. Establishing the threshold in advance prevents managers from manipulating the boundaries later just to justify keeping a favored role or forcing an arbitrary structure onto the data.
Consulting the Team Without Causing Alarm
Rebuilding jobs after an AI deployment carries obvious cultural risk. If employees suspect a secret spreadsheet is being used to eliminate their positions, cooperation vanishes. Dr. Tebaa argues that transparency with the Rebuild Ledger is the best antidote to workplace anxiety.
Rather than announcing new job titles from behind closed doors, Dr. Tebaa advises leaders to show the raw ledger directly to the staff and ask them to correct their own task lists. Because the employees live that schedule every week, they will quickly spot missing tasks or underestimated checking times. By presenting the rebuilt jobs first and addressing personnel placement second, management demonstrates that the redesign is driven by operational logic. Leaders can then clearly explain where the freed hours are being directed, adhere strictly to employment rules regarding formal consultation, and transition the team from half-empty legacy roles into complete, outcome-driven positions.