Marco Gaietti is a seasoned expert in Business Management with decades of experience in management consulting. His career has been defined by a deep focus on strategic management, operations, and the nuances of customer relations, helping global organizations navigate complex structural shifts. In this conversation, Gaietti breaks down why the current corporate obsession with AI-driven headcount reduction is a “category error,” arguing instead for a radical redesign of work that prioritizes performance and growth over simple cost-cutting.
The discussion explores the limitations of traditional task-inventory methods and the necessity of a “whiteboard-first” approach to organizational design. Gaietti highlights how major players like IBM have saved millions of hours and billions in cash flow by refocusing talent on high-value innovation rather than routine maintenance. He also addresses the staggering 58-percentage-point gap between executive perceptions of redeployment and the actual employee experience, offering a roadmap for leadership to move beyond a narrow productivity mindset toward a more sustainable, growth-oriented future.
Many companies inventory tasks to calculate AI-driven headcount cuts, yet business needs are often case-dependent and unwritten. How does starting with a “blank whiteboard” change the design of an AI agent? What specific steps should leadership take to build human roles around these agents instead of just automating existing duties?
Starting with a blank whiteboard forces leadership to abandon the “how do we automate what we do today” mindset, which is often flawed because much of what we do today shouldn’t be done at all. When you design an AI agent first, you are mapping a process as it should work in an optimized state, rather than just paving over old, inefficient cow paths. Leadership must follow a strict sequence of “eliminate, simplify, and then automate” to ensure they aren’t digitizing waste. This shift requires executives to identify the core value an agent provides and then intentionally build human roles to handle the “case-dependent” nuances that a job description never captures. By doing this, you create a symbiotic relationship where humans are not just operating around a machine, but are freed to handle the complex, organizational-dependent problems that AI cannot touch.
Integrating AI has helped some organizations free up billions in cash flow and millions of people-hours. Beyond simple automation, how can technical staff shift from routine maintenance to high-value product features? Can you provide a step-by-step example of how these saved hours translate into measurable business growth rather than just lower expenses?
At IBM, we saw this transition firsthand when AI helped free up $4.5 billion in free cash flow and saved a staggering 22 million people-hours over three years. For technical staff, this meant shifting from spending 80% to 90% of their time on repetitive coding or maintenance to focusing on architecture and new feature development. To translate this into growth, an organization first identifies the “drudgery” tasks, automates them, and then explicitly reassigns those saved hours to a “growth backlog” of products that were previously sidelined due to lack of bandwidth. This moves the needle from a 40% reduction in operating budgets to an all-time high in employee engagement, because the staff is finally working on the future of the company rather than just keeping the lights on. It’s a sensory shift from the exhaustion of maintenance to the excitement of creation, which ultimately drives market share.
Reducing entry-level hiring is often seen as a logical short-term move when AI is introduced. How can organizations instead redeploy these new hires to pursue untapped market segments? What are the strategic risks of maintaining a narrow productivity mindset instead of a growth-oriented one for junior talent?
While cutting entry-level roles might look good on a quarterly report, it is a strategically narrow move that starves the organization of its future energy. Instead of seeing junior talent as a cost center, companies should view them as an agile force that can be redeployed to capture small and medium-sized business segments that were previously too expensive to pursue. If you use AI to handle the basic data entry and research, these new hires can spend their time building relationships and exploring these untapped markets. The risk of a productivity-only mindset is that you eventually run out of “fat” to cut and find yourself with a hollowed-out middle management pipeline. You lose the “to do what” factor that gets employees excited, and you risk losing an entire generation of talent that understands your culture from the ground up.
While most HR leaders claim to offer redeployment programs, only a small fraction of employees actually recognize them. Given that rehiring often costs more than internal mobility, why does this massive perception gap exist? What infrastructure is required to identify talent for future needs before resorting to layoffs?
The perception gap is massive—a 58-percentage-point difference between the 77% of HR leaders who say they offer redeployment and the mere 19% of employees who actually feel it. This gap exists because many of these programs are “paper programs” that lack the necessary infrastructure, such as internal talent marketplaces or proactive skill-mapping tools. To bridge this, companies need a robust internal mobility system that tracks skills in real-time, allowing leadership to see who can be moved before a department is downsized. We know that for 73% of HR leaders who track it, rehiring costs significantly more than redeployment, so the financial incentive is there. The infrastructure must include high-quality outplacement and internal “talent scouts” who treat existing employees with the same urgency as external candidates.
Downsizing a specific department might yield minor financial gains, but it often misses broader performance improvements. How should executives weigh small headcount savings against the potential for organization-wide transformation? What metrics should leadership prioritize to ensure they are not focusing on the wrong problem during an AI rollout?
Executives often fall into the trap of solving the “wrong problem” by focusing on a 10% or 30% reduction in a specific department, which rarely makes a material financial difference to a large corporation. Instead of prioritizing headcount as a primary metric, leadership should focus on “time-to-value” and “employee engagement” scores, which were seen to hit all-time highs at companies like IBM during their transformation. You have to weigh the minor savings of a layoff against the massive opportunity cost of lost innovation and the friction created by a demoralized workforce. Transformation should be measured by how much “freed-up” time is successfully converted into new revenue streams or improved customer satisfaction. If your AI rollout doesn’t result in your team doing better, more meaningful work, you haven’t transformed; you’ve just shrunk.
What is your forecast for AI’s impact on the workforce?
My forecast is that we are moving toward a “post-task” era where the value of a human worker is defined not by the list of chores they complete, but by their ability to orchestrate AI agents toward creative and strategic goals. While 87% of HR leaders are currently eyeing layoffs, the companies that will truly win are those that treat AI as a catalyst for a 40% improvement in operational efficiency that is immediately reinvested into new market opportunities. We will see a shift where “management” becomes less about supervising tasks and more about designing workflows where human intuition and AI speed coexist. The initial wave of cuts will likely lead to a “rebound hiring” phase as companies realize they’ve cut too deep into their creative muscle and must pay a premium to bring talent back. Ultimately, the successful organizations will be those that answer the “to do what” question with a vision for growth, rather than just a plan for reduction.
