Andreas Timm

Tag: execution speed

  • Q1 layoffs hit a four-year low. Tech’s share went up 40%.

    Q1 layoffs hit a four-year low. Tech’s share went up 40%.

    What was announced

    Challenger, Gray & Christmas reported in late March 2026 that U.S. employers announced 217,362 job cuts in Q1 — the lowest Q1 total since 2022. Within that aggregate, technology-sector cuts ran at 52,050, up 40% versus Q1 2025. In March specifically, AI was cited as the rationale for 15,341 cuts — 25% of the month’s total — making it the leading single reason for U.S. layoffs for the first time on the Challenger record. Major contributors to the technology figure: Dell’s annual filing-disclosed restructuring, Oracle’s March layoffs, and Meta’s Reality Labs reduction.

    What it means

    The aggregate-down, tech-up, AI-leading combination is not three separate stories. It is one story told from three angles. The aggregate number is down because the broad U.S. economy is operating with reasonable employment; sector-by-sector cuts in legacy industries are running below historical norms. The technology number is up because the sector is going through a structural reallocation — capital is shifting from headcount-led growth to compute-led growth, and the cost base of large software companies is being explicitly redesigned around that shift. AI is the leading cited reason because it is the strategic narrative that justifies the redesign to investors, customers, and remaining employees.

    The implication for the rest of 2026: technology-sector hiring patterns will continue to diverge from the broader economy. Companies will hire aggressively for ML, infrastructure, agent operations, and applied research while shrinking headcount in functions that AI is augmenting or displacing. Net headcount may decline, but the per-employee compute and capability budget rises sharply. That changes what “growth” looks like in the financial reporting of the sector.

    Andreas’s view

    My read on this: the Q1 numbers are not a downturn signal — they are a transformation signal masquerading as cost discipline. Tech companies are not in distress. They are restructuring around the assumption that a smaller, AI-augmented workforce produces equal or greater output at a different cost basis. Some of those bets will be right; some will be the Block experience at smaller scale, where the rehire follows the cut by six to twelve weeks. The Q2 and Q3 numbers will tell us how clean the underlying productivity gain actually is.

    I don’t think the AI-as-cited-reason metric stabilizes here. It rises through 2026. Once the framing carries an investor-relations multiple — which Block demonstrated — the disclosure pattern shifts in its direction across the sector. By year-end, AI-cited cuts will likely cross 30% of monthly U.S. totals, and that will look more like a permanent baseline than a peak.

    The way I see it: the Challenger headlines document neither a labor crisis nor a productivity victory. They are capturing a sector-wide capital reallocation with a coherent strategic logic and uneven execution quality. The more interesting question to me is which side of that reallocation any given business is on — and whether its cost base reflects the structure it has today or the structure it intends to have in 18 months.

    Three things I’m watching

    Three things I’m watching as this plays out:

    1. I’ll be watching whether companies are tracking the technology-sector comparison for their own organization: revenue, headcount, and per-employee compute spend versus the closest five public-market peers. That gap is where structural exposure shows up first.
    2. I’ll be watching whether organizations hold a meaningful distinction in their communications between AI-driven productivity reductions — workflow-modeled, with measurable output — and broader restructuring justified by other factors. The market may not differentiate; but the ones with rigorous operations will.
    3. I’ll be watching Q3 unit economics against any Q1 workforce action. The reduction is on the books in Q1; whether the underlying productivity thesis holds shows up in Q3 output measures, not headcount.

    References and related signals

  • MCP became infrastructure and Apple decided to rent cognition

    MCP became infrastructure and Apple decided to rent cognition

    What was announced

    Two announcements in the week of March 2–8, 2026 redrew the agent landscape. Anthropic’s Model Context Protocol crossed 97 million installs, with every major AI provider now shipping MCP-compatible tooling — moving the protocol from experiment to default infrastructure for tool-calling agents. Apple confirmed that the redesigned, AI-powered Siri targeted for release alongside iOS 26.4 will be powered by Google’s Gemini model running on Apple’s Private Cloud Compute. In parallel, Anthropic rolled out memory features to all Claude users and deployed Opus 4.6 as an add-in inside Microsoft PowerPoint and Excel.

    What it means

    The MCP install count makes the connectivity layer between agents and tools a solved problem at the standards level. That is a meaningful shift. For two years, the friction in shipping agents was that every tool integration was bespoke; the integration debt scaled linearly with the number of tools and the number of agents. With MCP at default-infrastructure scale, the integration cost is closer to fixed than linear, and the bottleneck moves from connectivity to orchestration and governance.

    Apple’s decision to rent cognition from Google for Siri is the more strategically loaded story. It signals that even the most vertically integrated consumer-tech company in the world has concluded that building competitive frontier-model capability inside the company is not the right capital allocation. The Private Cloud Compute envelope handles the data-sovereignty argument. The Gemini choice handles the capability argument. The combination is an explicit acknowledgment that frontier-model capability has consolidated at a tier of providers most companies will rent from, not build alongside.

    Andreas’s view

    My read on this: the agent stack is settling into a recognizable shape. Standards layer (MCP, becoming generic). Frontier-model layer (a small number of providers — OpenAI, Anthropic, Google, with regional players underneath). Application layer (where most enterprise value is created). The interesting strategic action for the next 24 months is in the application layer, where the questions are which workflows to embed, which data to expose, and which orchestration logic to own.

    I don’t think Apple’s choice is anomalous. It is the start of a wave. Companies that have been building internal frontier-model capabilities will increasingly find that the math does not work — the capex is consumer-internet scale, the talent is concentrated at three or four employers, and the capability gap to “good enough internal model” widens every six months. The economically rational answer for almost everyone is: rent the cognition, own the integration and the data envelope around it. Apple has now made that a defensible board-level position.

    The way I see it: the most important architectural question right now is whether the cognition layer (rented, frontier-model, expensive but improving exponentially) is clearly distinguished from the integration layer (owned, workflow-specific, where the moat actually lives). Where those layers are blurred, I’d expect companies to find themselves overpaying on one side and under-investing on the other. The Apple-Google deal is the clean reference architecture for how that separation can look.

    Three things I’m watching

    Three things I’m watching as this plays out:

    1. I’ll be watching whether companies architect the cognition layer and the integration layer separately — treating frontier-model providers as utilities while building proprietary infrastructure around workflow integration and the data envelope.
    2. The companies that preserve optionality will be the ones that default to MCP-compatible tooling for new agent integrations. The standards layer is no longer a strategic differentiator — the question is how quickly organizations stop treating it as one.
    3. I’ll be watching how internal frontier-model build efforts hold up against the Apple-Gemini reference case. Where differentiation rests on owning the model, I’m interested to see whether those bets come with a credible 36-month capex and capability projection — and what happens when they don’t.

    References and related signals

    • Crescendo AI: latest AI news and developments
    • Related signal: Anthropic’s Opus 4.6 PowerPoint and Excel integrations move frontier-model capability deeper into the enterprise default tooling, accelerating the rented-cognition pattern.
    • Related signal: NVIDIA GTC 2026 (March) emphasized agentic frameworks and Fortune 500 production deployments — the application layer is where the next wave of enterprise AI value is being created.
    • Related signal: 95% of generative AI pilots still fail to reach production. The connectivity layer being solved does not solve the operating-model layer.
    • Related signal: Apple choosing Gemini over OpenAI for Siri changes the competitive math for every enterprise still scoping a frontier-model partnership.
  • AI is becoming the narrative for layoffs. It is not yet the cause.

    AI is becoming the narrative for layoffs. It is not yet the cause.

    What was announced

    Through the week of February 16–22, 2026, the AI-cited layoff story moved from edge case to mainstream framing. AI was cited as the rationale for 4,680 February job cuts in the U.S. — roughly 10% of the month’s total. Baker McKenzie announced 600–1,000 layoffs (up to 10% of global headcount) framed as a pivot to AI-augmented service delivery. Dow disclosed 4,500 cuts in January with explicit AI-strategy framing. A Harvard Business Review piece in the same window argued that companies are laying off based on AI’s potential, not its measured performance. An Oxford Economics report from January concluded that many AI-cited layoffs were the consequence of past overhiring, not present AI productivity.

    What it means

    Two things are happening at once. First, AI productivity is real for specific workflows and starting to show up in unit-cost reductions. Second, “AI” is becoming the public-facing rationale for cost actions that boards and CEOs have wanted to take for other reasons — overhiring during 2021–2022, deteriorating margins in slower-growth segments, restructuring to a target operating model that was already in motion. The two stories overlap, and the public communication does not distinguish between them.

    For employees, the framing matters because “we are restructuring” and “AI is replacing your role” carry different signals about whether the function comes back. For investors, it matters because the market is pricing AI-cited cost reductions as durable while restructuring-cited cost reductions are typically priced as one-off. CEOs who choose the AI framing get a multiple uplift. That incentive structure tells you why the framing is becoming dominant.

    Andreas’s view

    My read on this: the next 12 months will see a steady drift toward AI-as-explanation in layoff communications, regardless of whether AI is the underlying driver. The reason is not deception — it is signaling. CEOs need a forward-looking story that the cost base will stay reduced, and “AI productivity” is a cleaner story than “we hired too aggressively in 2022.” The public record will eventually reconcile this; quarterly earnings will reveal which companies actually shipped the productivity gain and which simply downsized.

    I don’t think the workforce numbers are yet the right metric to watch. The right metric is the ratio of revenue per employee in the months after the cut. If revenue per employee climbs durably, the AI framing was substantively correct. If it plateaus or reverses while operational quality declines, the framing was a positioning move and the company will be hiring back inside 18 months — at higher cost and lower morale.

    The way I see it: when a CEO presents an AI-cited workforce action, the productivity model behind it should be specific enough to name which workflows, which output measures, which time horizon, and which control group. Where those answers are vague, the action is restructuring with AI vocabulary. That is not necessarily wrong, but the distinction matters — and I think it matters most at the board level, where the conversation should reflect what is actually driving the decision.

    Three things I’m watching

    Three things I’m watching as this plays out:

    1. I’ll be watching whether companies maintain a clear internal distinction between AI-driven productivity actions (with a workflow-level model behind them) and AI-framed restructuring actions (justified by other reasons). Both can be valid; conflating them confuses execution, and the ones that keep the distinction clean are more likely to deliver what they promised.
    2. The companies that track revenue per employee monthly for the 12 months following any AI-cited workforce reduction will have the clearest view of whether the productivity gain actually materialized — and I’ll be looking at that number as the most honest signal in the public record.
    3. I’ll be watching how specific companies get in their external communication around AI-related workforce changes. Vague “AI is making us more productive” framing tends to erode credibility internally faster than a precise statement of which work has been automated and which has been redesigned — and over the next year, that credibility gap will start showing up in retention and hiring data.

    References and related signals

  • The pilot-to-production gap is an execution problem, not a model problem

    The pilot-to-production gap is an execution problem, not a model problem

    What was announced

    Through the week of February 9–15, 2026, the enterprise AI deployment story sharpened around a paradox: 95% of generative AI pilots still fail to reach production, yet 42% of enterprises now run agentic AI in production and 72% have agentic systems live in production or pilot. Microsoft’s February enterprise update reframed Copilot from “assistant” to “governance-first agent” capable of completing entire workflows. Oracle introduced Fusion Agentic Applications for finance, supply chain, and HR. OutSystems research released the same week reported that 94% of enterprises adopting agentic AI now flag agent sprawl as a primary concern.

    What it means

    The two statistics are not in conflict. They describe two different populations of organizations. The 95%-pilot-failure number describes how the average enterprise treats generative AI: a proof-of-concept budget, a small team, and a handoff to operations that never happens. The 42%-in-production number describes a smaller cohort that has done the operational work — governance, identity, runtime monitoring, rollback procedures, and explicit ownership of the agent fleet. The gap between the two cohorts is not technical. It is procedural.

    Microsoft’s “governance-first agent” framing acknowledges this directly. The next phase of enterprise AI is not better models. It is the operating discipline around models — who deploys them, who owns them when they misbehave, who pays for the inference, and how the organization rolls back a bad agent without disrupting downstream work. That is a CIO problem, not a CTO problem.

    Andreas’s view

    My read on this: the production cohort is pulling away from the pilot cohort, and the gap is widening every quarter. The companies in production are accumulating an operational learning curve — what governance looks like, how to staff agent operations, how to track agent behavior in production, how to compose agents into workflows without losing accountability. The companies still iterating on pilots are accumulating learnings about prompts and demos. Those are different skill sets and they compound at different rates.

    I don’t think the next 12 months reward the companies that pick the best model. They reward the companies that figured out how to operate any reasonable model at production scale, with controls, with monitoring, and with an explicit chain of accountability when an agent does the wrong thing. Agent sprawl is the leading indicator that the operations layer is missing — when 94% of practitioners flag it as a top concern, the conversation has moved past whether agents work and onto whether they are manageable.

    The way I see it: the clearest signal a board can get on where an organization actually stands is whether the CIO can produce a production agent inventory — by name, by owner, by usage volume, by incident count. If the question produces a list, the organization is in the production cohort. If it produces “we are still piloting,” it is in the failure cohort, and the strategic gap to peers will be visible in operating costs by mid-2027.

    Three things I’m watching

    Three things I’m watching:

    1. I’ll be watching whether companies can produce a named, owned, monitored agent inventory with rollback procedures on demand — that capability is the clearest proxy I have for whether a real agent operating model exists or not.
    2. The organizations that interest me are the ones shifting pilot evaluation from “did the demo work” to “did the agent ship to production with controls in place” — and backing that shift by defunding pilots that stay in demo mode past a fixed time-box.
    3. The question I’d be asking myself is whether a dedicated agent-operations lead — with explicit authority over the production fleet and seniority equivalent to the head of enterprise systems — is in place. Without single ownership, sprawl is the default outcome, and I expect that to show up clearly in incident and cost data over the next several quarters.

    References and related signals

  • When 88% of organizations have adopted AI, adoption stops being the question

    When 88% of organizations have adopted AI, adoption stops being the question

    What was announced

    The Stanford HAI 2026 AI Index landed in mid-January with a set of numbers that close out a debate. Organizational AI adoption reached 88% globally. Global corporate AI investment more than doubled in 2025 to $581.7 billion. Generative AI hit 53% population adoption within three years — faster than the personal computer or the internet. Four out of five university students now use generative AI as part of their coursework.

    What it means

    When adoption crosses the 80% line, the question of “should we adopt” becomes structurally uninteresting. Every relevant comparison group has already answered it. What remains is differentiation — and differentiation in a world of universal access is harder, not easier, than in a world of selective access. The strategic margin moves from access to integration depth, from licenses to workflow penetration, and from procurement decisions to operating-model decisions.

    The investment number is the more telling signal. $581.7 billion of corporate AI investment in a single year is a capital allocation that prices in a specific belief: that AI capability will compound at a rate that makes today’s spending the cheap option in retrospect. That belief either turns out to be correct, in which case the laggards face a permanent gap, or it overshoots, in which case the survivors of the correction still own infrastructure and skills the laggards do not.

    Andreas’s view

    My read on this: the AI Index numbers are not a celebration of momentum, they are a notice of obsolescence. Adoption was the entry-level metric — the one that let companies say “we are doing AI” without committing to anything that mattered. With 88% adoption, that metric is exhausted. The companies that conflate “we have AI deployed” with “we have an AI strategy” will be the ones surprised in 18 months when peers with the same headline adoption rate are operating at a fundamentally different unit-economics base.

    I don’t think the next two years will be about adopting more. They will be about routing work differently — deciding which functions become AI-native, which roles get redesigned, which middle-management layers compress, and which workflows get rebuilt from the ground up rather than augmented. The companies treating this as a tooling question will keep the org chart they had in 2024 and bolt assistants onto it. The companies treating it as a structural question will redesign for AI-native operations and harvest a different cost base.

    My expectation is that boards still reporting on adoption rates are measuring the wrong thing entirely. The number that matters is the percentage of work routed through AI-native processes versus AI-augmented legacy processes. Those are two different cost structures and two different competitive positions. The first is a step change. The second is a feature.

    Three things I’m watching

    1. I’ll be watching whether companies move away from adoption KPIs toward integration-depth KPIs — specifically, the percentage of revenue-generating workflows that are AI-native, not just AI-touched.
    2. The companies that stand out to me will be the ones that build the comparison the AI Index doesn’t make for them: how their spend per FTE on AI infrastructure and tooling stacks up against the 90th-percentile peer in their sector. If that number isn’t visible to leadership, it isn’t informing strategy.
    3. I’ll be watching whether organizations use the next 12 months as a workflow-redesign window rather than a tooling-procurement window. The structural opportunity narrows the moment competitors finish their redesign.

    References and related signals

  • Humanoids crossed from demo to deployment in one week

    Humanoids crossed from demo to deployment in one week

    What was announced

    At CES 2026 in Las Vegas (Jan 5–9), a cluster of robotics announcements crossed the same threshold in a single week. Boston Dynamics unveiled the production-ready electric Atlas with Hyundai committing the first fleet to its Metaplant in Savannah, Georgia, and announced a partnership with Google DeepMind to integrate Gemini Robotics models into the platform. LG demonstrated CLOiD performing real household work — laundry, dishwasher loading, food preparation — in a staged living environment. EngineAI introduced the T800 with a $25,000 starting price and mid-2026 shipping. CES listed 40 companies referencing humanoids on the show floor.

    What it means

    A human factory engineer in navy work clothes works alongside a matte-white humanoid robot at a metal workbench.
    Side by side, not face to face.

    For three years humanoids were a category of demo videos. CES 2026 is where the category became a category of contracts. Production is committed, factories are named, prices are listed, and the foundation-model layer (Gemini Robotics, comparable initiatives at other labs) supplies the cognitive component that previously made every demo brittle. The constraint is no longer “can it walk on stage.” The constraint is “what does the deployment workflow look like, and who owns the integration.”

    From this follows a second-order effect: industrial buyers now have a real procurement question to answer in 2026 — not in 2030. Hyundai’s timeline (Atlas at Metaplant, dedicated robotics factory targeting 30,000 units per year by 2028) is the explicit benchmark. Every competing automaker, every large logistics operator, and every contract manufacturer now sits with a known reference deployment to react to.

    Andreas’s view

    My read on this: the news is not that the robots are good enough. The news is that buyers have decided they are good enough to commit — and the price has moved into range. At $25,000, a humanoid sits below the annual cost of an industrial worker in most developed markets. That shifts the question from “is this technology real” to “where does it amortize fastest.”

    My three takeaways:

    1. The barrier that fell was cognitive, not mechanical. The hardware has been close to ready for years. What changed is that foundation models — think Atlas plus Gemini Robotics — absorbed the cognitive deficit that kept robots out of unstructured environments. CES 2026 looks different because the system is different, not just the chassis. I think anyone framing this as “better robots” is underestimating the speed of what comes next.

    2. The 2030 humanoid timeline is already stale. In my view, this is now a 2026 pilot conversation for any organization with manufacturing, warehousing, or fulfillment in its operations footprint — anywhere unit-level labor is the dominant cost driver. Not as a capex bet, but as a learning investment. The compounding advantage goes to whoever builds operational muscle around these systems first.

    3. The real cost of waiting isn’t hardware — it’s the operating model. Hardware will be available to everyone. What won’t be available off the shelf is three years of deployment experience. My expectation is that late movers won’t just be buying machines from competitors — they’ll be importing the playbook for how to use them.

    References and related signals

  • The agentic year begins underprepared

    The agentic year begins underprepared

    The year opens with a measurable gap. McKinsey’s 2026 trust maturity survey, fielded in December and January, puts twenty-three percent of organizations into the scaling phase for agentic systems and thirty-nine percent into experimentation. The remaining majority — nearly two thirds — has not yet begun scaling AI across the enterprise. The capability frontier moved twelve to eighteen months faster than the operating models around it. That gap is no longer an experimentation question. It is the year’s defining strategic risk.

    The boards that close this gap first will not be using better models than their competitors. They will be running organizations that can metabolize what the models already do. The constraint is no longer technology. It is adoption — and adoption is a leadership problem.

    The shift is structural, not cyclical

    Agentic systems are not a new feature inside a familiar product. They are a new class of worker. They take a goal, decompose it into steps, hold state across those steps, call other tools, recover from errors, and return a completed unit of work. That changes what a job is, not how a job is done.

    The 2025 narrative — copilots, productivity boosts, ten percent uplift — is over. The 2026 question is harder. What units of work no longer require a human originator? What units of work now require a human reviewer instead of a human executor? Which decisions can be delegated to a system that explains its reasoning? The companies asking these questions on a Monday morning are reorganizing. The companies still benchmarking model accuracy are stalling.

    The shift is one-way. No board will vote in 2027 to remove agentic systems from a workflow they reduced from forty hours to four. The architectural choices made this year will compound.

    Diagram of one human silhouette passing a goal to a central node that branches into multiple task arrows
    Goal in, decomposition out, no human in the loop between.

    The role change has already happened on the ground

    Inside organizations that have actually shipped agentic systems, the role redefinition is happening informally, by individual contributors, ahead of any HR process. A senior analyst who used to write three reports a week now reviews twelve agent-drafted reports a week and signs off on the analysis. A staff engineer who used to write three pull requests a day now reviews fifteen agent-generated pull requests a day. An account manager who used to draft proposals now edits proposals the agent has built from CRM context.

    The work that survives is judgment, taste, accountability, and relationship. The work that does not survive is execution under specification. Job titles still describe the second category. Job content has already shifted to the first.

    First-line managers feel this most acutely. They were trained to manage humans doing execution work. They are now managing humans doing review work, who in turn are managing systems doing execution work. That is a different management discipline — closer to portfolio management of automated processes than to people management of execution teams.

    A figure at a desk with twelve document icons floating above, marking one of them
    Three reports a week became twelve reviews a week.

    The organizational consequence is delayering

    Span of control widens when the work below each manager becomes more automated and more reviewable. McKinsey’s parallel work on the state of organizations points in the same direction: companies that scale agentic systems also flatten by removing one to two layers of middle management. The economic logic is direct. Middle layers existed to translate strategy into execution and to coordinate the humans doing that execution. When the execution is increasingly handled by systems and the translation is increasingly handled by models, the layer is doing less.

    This is not the 2024 layoff cycle that hit individual contributors. This is a 2026 reorganization that compresses the manager-of-managers layer. It is structurally different and politically harder. The people most threatened by it are the people running the budget meetings about it.

    Organizations that resist the delayering will have a temporary cost advantage and a permanent decision-velocity disadvantage. Decision cycles compress when fewer humans need to be in the loop. The competitor who removed two layers will commit to a market move three weeks faster. Over a year, that compounds into a different market position.

    Two org-chart pyramids side by side, the right one flatter, with an arrow indicating compression
    The middle layer compresses, span of control widens.

    So what boards should do this quarter

    Two actions belong on the Q1 agenda. First, demand a workforce plan that names the units of work moving from human execution to human review, with a twelve-month horizon. Vague AI strategies are no longer acceptable as deliverables; the question is which jobs, which tasks, which review cadences, which accountability lines.

    Second, name an executive owner for the operating-model redesign — not for AI strategy as a separate track, but for the way the company will be organized around the systems it has already deployed. The CHRO and the COO are the natural owners. The CTO is not. The technology decision is downstream of the operating-model decision, and treating it as upstream is how organizations end up with sophisticated tools and a 2023 org chart.

    The year that just started will be measured by the gap between capability and operating model. The companies that close it first set the pace for the rest of the decade. The risk is not moving too fast. The risk is moving too late. Execution speed will separate leaders from followers.