hebel. today · 13 November 20268 / 80

AI at Work · AI Adoption in Teams

Companies shift from AI adoption to economic outcomes

Wharton researchers found that only 28% of managers report strongly positive returns on AI investments, with success depending on workflow transformation rather than headcount reduction. High-ROI departments track growth metrics like net-new revenue or…

Wharton researchers found that only 28% of managers report strongly positive returns on AI investments, with success depending on workflow transformation rather than headcount reduction (Cashless). High-ROI departments track growth metrics like net-new revenue or customer satisfaction, whereas those measuring efficiency through hours saved rarely achieve significant gains.

Amazon now warns its engineers against tokenmaxxing, where high consumption of AI tokens becomes a hollow productivity proxy that increases costs without improving customer outcomes (Karine Allouche from Human x AI). Engineering teams at Docusign focus on shipping velocity and reliability, requiring human sign-off for any autonomous pull request to maintain system integrity (Nick Lucchesi from The New Stack).

Genetech pairs AI-native junior engineers with senior architects to ensure rapid prototypes meet long-term stability standards (Shamim Rajani from The Leadership Lens). This approach allows teams to leverage AI for speed while keeping experienced staff accountable for architectural quality and judgment.

  • SAP expects to generate over €2 billion in efficiency gains by replacing expensive AI models with cheaper alternatives for routine tasks (Karine Allouche from Human x AI).
  • Docusign maintains accountability by requiring human approval for any autonomous agent action that could affect production systems (Nick Lucchesi from The New Stack).
  • The HR team at a company achieved nearly 3x productivity per employee by setting clear AI usage expectations and gamifying skill levels from L1 to L4 (The CHRO Office).

Try today · 30 min

Build a baseline for one AI-assisted workflow

Pick one active AI use case in your team and gather its current performance data.

You need

  • Current processing time
  • Current error rate
  • Current human effort in hours
  • Inference and integration costs

Steps

  1. Identify the specific workflow where AI is currently deployed.
  2. Record the time spent on the task before AI assistance.
  3. Document the number of errors or quality issues per 100 units of output.
  4. Calculate the total cost including model usage and human review time.
  5. Create a simple spreadsheet comparing these baseline figures against current post-AI performance.

One email instead of your newsletter pile.

Forward the newsletters you already get (a Gmail filter does it) and tell Hebel your goals. Every morning it reads them with 20,000 others and sends one short email, with one small thing to do today. Fewer emails, not more. Free during beta.

Start my paper →
LinkedIn X

Sources

  1. Cashless on hebel. →Wharton survey of 1,400 managers reveals that only 28% see positive ROI, highlighting the difference between efficiency-focused and growth-focused AI strategies.

  2. Karine Allouche, Human x AI on hebel. → ✎ Written by a personAmazon and SAP emphasize moving away from vanity metrics like token consumption toward business outcomes and cost-effective model selection.

  3. Nick Lucchesi, The New Stack on hebel. → ✎ Written by a personDocusign engineering details how they moved beyond initial tool rollout to a sustainable operating model with clear guardrails and reusable agents.

  4. Shamim Rajani, The Leadership Lens on hebel. → ✎ Written by a personGenetech explains how pairing junior engineers with senior architects balances AI speed with the need for long-term architectural stability.

  5. The CHRO Office on hebel. →An HR leader describes how setting explicit productivity goals and gamifying AI skill levels helped the company reach 95% of its 3x efficiency target.

  6. Sharique Nisar, The Efficiency Playbook on hebel. → ✎ Written by a personA practical playbook for scaling AI that suggests establishing baselines and measuring cost per successful outcome rather than just counting tokens.

More in AI at Work

Turn your repeated work into reusable AI skills

Does AI replace the worker or the task?

Companies trade junior headcount for senior talent leverage

Sign in to Hebel first

Likes, your collection and done Hebel need an account. We email you a six digit code; no password.