{"id":3215,"date":"2026-07-28T06:35:00","date_gmt":"2026-07-28T04:35:00","guid":{"rendered":"https:\/\/andresass.com\/?p=3215"},"modified":"2026-07-03T10:48:50","modified_gmt":"2026-07-03T08:48:50","slug":"freed-capacity-after-automation","status":"publish","type":"post","link":"https:\/\/andresass.com\/en\/insights\/freed-capacity-after-automation\/","title":{"rendered":"Freed-up Capacity: What Happens to People When the Machine Takes Over"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">The Only Question in the Steering Committee<\/h2>\n\n<p class=\"wp-block-paragraph\">The automation project has been successful. The software handles document review, the error rate has decreased, and approximately one-fifth of working hours have been freed up in the affected area. In the steering committee, a single question is asked: How many positions can be eliminated? It is the expected question, and it is justified. However, the second question, which would be at least as valuable, remains unasked: What could these people achieve that has been left undone for years because no one ever had time for it? The decision of what automation ultimately brings to the company depends on these two questions.     <\/p>\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Automation answers how work will be done in the future. It does not answer what happens to the freed-up time. This decision is made by management, and it shapes every automation thereafter.  <\/strong><\/p>\n<\/blockquote>\n\n<p class=\"wp-block-paragraph\">A company whose management I <a href=\"https:\/\/andresass.com\/en\/advisory\/\">advised<\/a> during this phase immediately cut positions after the first major automation project. The savings appeared in the next quarterly report, and the calculation seemed to work out. Two years later, the second project started and made little progress. Expertise that automation would have needed suddenly became difficult to obtain, process details remained unmentioned, and testing phases dragged on. No one openly refused to cooperate. The workforce had simply learned from the first project: those who train the machine well make themselves dispensable. The second automation paid the price of the first.      <\/p>\n\n<p class=\"wp-block-paragraph\">This pattern is not solely a matter of corporate culture. It follows a logic that has repeated itself for two centuries. Three levers turn it into a controllable decision.  <\/p>\n\n<h2 class=\"wp-block-heading\">The Lesson from Two Centuries<\/h2>\n\n<p class=\"wp-block-paragraph\">In his seminal work &#8220;The Technology Trap,&#8221; Carl Benedikt Frey examined the history of automation from industrialization to the present day and revealed an uncomfortable regularity: whether people support or resist technological change depends not on the technology itself, but on whether they share in its benefits. The weavers who, as so-called Luddites, stormed machines in the early 19th century were not enemies of progress. They bore its costs without participating in its benefits and resisted this distribution. Where change was shared with those affected, it accelerated.   <\/p>\n\n<p class=\"wp-block-paragraph\">For a company, this history translates into a sober context: every automation sends a signal about what participation means. If it reliably leads to job cuts, the organization learns to slow down change, quietly and effectively, as in the example above. If it leads to new, more valuable tasks, the organization learns to accelerate change. The decision about freed-up capacity is therefore not merely a personnel issue. It is the investment decision that co-determines the pace of all future projects, including those <a href=\"https:\/\/andresass.com\/en\/insights\/insourcing-through-ai\/\">reshoring efforts that AI is making possible again<\/a>.    <\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Characteristic<\/th><th>Reflexive Reduction<\/th><th>Deliberate Redirection<\/th><\/tr><\/thead><tbody><tr><td>Impact on Costs<\/td><td>immediately visible<\/td><td>later, but growing<\/td><\/tr><tr><td>Impact on Knowledge<\/td><td>leaves the company<\/td><td>remains and becomes more valuable<\/td><\/tr><tr><td>Signal to the Workforce<\/td><td>Participation endangers one&#8217;s own position<\/td><td>Participation opens up new tasks<\/td><\/tr><tr><td>next automation<\/td><td>encounters silent resistance<\/td><td>finds allies<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">This juxtaposition is deliberately sharpened, and it does not mean that staff reduction is always wrong. There are situations where it is unavoidable. The crucial point is that the use of freed-up capacity is consciously decided and honestly communicated, rather than emerging as a residual quantity determined by quarterly pressure.  <\/p>\n\n<h2 class=\"wp-block-heading\">Lever 1: Decide on the Use Before the Project<\/h2>\n\n<p class=\"wp-block-paragraph\">What happens to freed-up capacity is usually only decided in most companies once it has already been freed up. But then it is no longer strategy that decides, but the most immediate pressure, which almost always argues for quick reduction. The same rule applies to freed-up capacity as to freed-up capital: its <a href=\"https:\/\/andresass.com\/en\/insights\/efficiency-innovation-growth\/\">use must be determined before the measure<\/a> if the savings are to be more than just a balance sheet effect.  <\/p>\n\n<p class=\"wp-block-paragraph\">Therefore, before each automation project, determine where the freed-up time will go: what proportion will be used for cost reduction, what proportion for defined new tasks, and who will be responsible for this redirection. This determination belongs in the project charter, not in the retrospective. It disciplines the project&#8217;s calculation, because an automation benefit that consists half of vaguely defined &#8220;gained time&#8221; is not yet a benefit. And it gives the workforce an honest answer to the question everyone asks anyway, before the start.   <\/p>\n\n<h2 class=\"wp-block-heading\">Lever 2: Direct Capacity to Undone Value Creation<\/h2>\n\n<p class=\"wp-block-paragraph\">In every company, there is a silent list of work that would create value and has not been done for years: clients no one systematically cares for, data sets whose quality everyone complains about but no one improves, process knowledge that exists only in a few minds and has never been documented, offers that are never followed up. This list is the natural destination for freed-up capacity, because it demands exactly what automation cannot provide and what employees bring: client knowledge, experience, and judgment. At the same time, this list quantifies the opportunity cost of a reflexive reduction: those who cut capacity immediately save salaries and simultaneously forgo the returns that the same capacity could generate in old cases, data quality, or client care.  <\/p>\n\n<p class=\"wp-block-paragraph\">Make this list explicit before capacity is freed up, and combine the redirection with targeted qualification, as the new tasks often require different skills than the old ones. This is not a minor HR matter, but a <a href=\"https:\/\/andresass.com\/en\/insights\/developing-talent-leadership-task\/\">core management task<\/a>: whoever decides which people grow into which new tasks determines the actual return of automation. A management executive whom I <a href=\"https:\/\/andresass.com\/en\/profile\/\">supported<\/a> in this redirection fully directed the freed-up time of her billing team to clarifying disputed old cases that had accumulated over years. Within a year, the team recovered claims amounting to significantly more than the savings from a staff reduction, and two team members became highly sought-after specialists for the next automation project. The capacity had not disappeared. For the first time, it was working on something that had been left undone as long as routine consumed everything.     <\/p>\n\n<h2 class=\"wp-block-heading\">Lever 3: Treat Credibility as Capital<\/h2>\n\n<p class=\"wp-block-paragraph\">The way a company handles the first freed-up capacity becomes the expectation for all subsequent projects. This expectation is an asset or a liability, and it is created not by communication, but by action. Announcements that it&#8217;s not about jobs, while cuts are made in parallel, damage trust more than an openly justified reduction, because they devalue every future promise.  <\/p>\n\n<p class=\"wp-block-paragraph\">Therefore, treat credibility as a long-term investment. If reductions are unavoidable, justify them openly, use natural fluctuation wherever possible, and clearly separate them from the projects whose success depends on the workforce. And pay attention to the measure: an organization that rushes from one restructuring to another loses the strength that sustains any <a href=\"https:\/\/andresass.com\/en\/insights\/transformation-fatigue\/\">transformation over time<\/a>. Automation is not the last project that will depend on your people&#8217;s cooperation. It is only the current one.    <\/p>\n\n<h2 class=\"wp-block-heading\">Three Questions for You<\/h2>\n\n<p class=\"wp-block-paragraph\">First: Where did the time freed up by your last automation project go? If you cannot answer, daily routine made the decision, and probably not in your favor. <\/p>\n\n<p class=\"wp-block-paragraph\">Second: What value-creating work in your area of responsibility has been left undone for years because there was never capacity for it? Does this list exist anywhere in writing, or only in the minds of those affected? <\/p>\n\n<p class=\"wp-block-paragraph\">Third: Does your next automation order already specify what proportion of the freed-up time will go into which new tasks and who will be responsible for it? If not, add this determination before the project starts. <\/p>\n\n<h2 class=\"wp-block-heading\">The Bottom Line<\/h2>\n\n<p class=\"wp-block-paragraph\">Freed-up capacity is the actual result of every automation, and it behaves like freed-up capital: its value is determined not by savings, but by its use. Reduction is a legitimate option among several, but it is the only one that prevails by itself if no one decides. <\/p>\n\n<p class=\"wp-block-paragraph\">The most expensive option is therefore the omitted decision. It first costs the undone value creation, then the knowledge of those leaving, and finally the cooperation of those remaining. Those who, on the other hand, determine before the project where the gained time will go, win twice: the efficiency of the machine and the strength of the people who no longer have to stand in its way to protect themselves.  <\/p>\n\n<h2 class=\"wp-block-heading\">Further Insights<\/h2>\n\n<p class=\"wp-block-paragraph\"><strong><a href=\"https:\/\/andresass.com\/en\/insights\/retaining-high-performers-transformation\/\">Retain High Performers<\/a><\/strong> \u2013 High performers, in particular, closely observe what happens to freed-up capacity and draw their conclusions first.<\/p>\n\n<p class=\"wp-block-paragraph\"><strong><a href=\"https:\/\/andresass.com\/en\/insights\/implementing-ai-without-overwhelm\/\">Implement AI<\/a><\/strong> \u2013 The capacity question determines trust, the implementation itself determines skill: both go hand in hand.<\/p>\n\n<p class=\"wp-block-paragraph\">All Insights can be found in the <strong><a href=\"https:\/\/andresass.com\/en\/insights\/\">overview<\/a><\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Automation has been successful, one-fifth of working hours are freed up. Now management decides: reduce or redirect. Why this choice influences every future project and how freed-up capacity becomes value creation.  <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[230],"tags":[331,242,243],"class_list":["post-3215","post","type-post","status-publish","format-standard","hentry","category-insights","tag-automation","tag-human-resources","tag-productivity"],"_links":{"self":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts\/3215","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/comments?post=3215"}],"version-history":[{"count":2,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts\/3215\/revisions"}],"predecessor-version":[{"id":3224,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts\/3215\/revisions\/3224"}],"wp:attachment":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/media?parent=3215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/categories?post=3215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/tags?post=3215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}