Open Textbook

mysummit.school - AI for Managers Blog

AI saves your team a day a week. Where does it go?

14 min read

Two numbers from BCG’s latest report. First: 42% of rank-and-file employees who use AI regularly save at least a full working day every week. Among senior leaders the figure reaches 60%. Second: 66% of those same rank-and-file employees get no instructions at all on what to spend that freed-up time on, and more than half admit they do not redirect it to anything more important.

Between those two numbers sits the most expensive leak in the modern company. A day a week per person appeared, and a day a week per person evaporated. What follows is why that happens, and what a line manager can do about it – the levers sit at exactly that level.

Read more
AI saves your team a day a week. Where does it go?
Managers and AI: The Most Frequent Users – But Not for Managing
14 min

Managers and AI: The Most Frequent Users – But Not for Managing

Of all the professions that most frequently open Claude, managers came in first. In Anthropic’s survey, they made up 23% of respondents – while accounting for roughly 7% of U.S. employment. Managers are overrepresented among AI users by a factor of three. Now the second number: management tasks make up just about 4% of all sessions. The people who manage are using AI for everything except managing.

Behind these two numbers lies the most precise description of how managers actually work with AI. And why the fear of “it will take my job” works differently in this profession than you might expect.

5 Layers of an AI Agent: What Every Manager Needs to Know
19 min

5 Layers of an AI Agent: What Every Manager Needs to Know

“Most people still think an AI agent is just ChatGPT with a good prompt.” That is the opening line of Sunil Ramlochan’s article “The AI Agent Stack Is Not a Prompt. It’s a Production System”, and the author calls this belief “a comforting myth.” The useful truth, he argues, is different: a real agent is closer to a small operating system for getting work done. It has a brain, hands, memory, rules, logs, recovery plans, and someone accountable when the agent does the wrong thing.

The article’s thesis fits in a single line: an agent is an entire stack. Reliability comes from the architecture around it, while the model itself – or a clever prompt – is just one ingredient. The picture is an engineering one, so let us approach it from the other side: what in this stack actually concerns the manager who does not write code but decides whether to put an agent to work.

AI Reports and Status Updates: A Workflow That Holds
19 min

AI Reports and Status Updates: A Workflow That Holds

Among the answers from forty managers to the question “what task would you like to speed up with AI”, one read almost like a finished procedure. Word for word: “I would like to automate the weekly project reports and send the draft to a Jira task before I approve it and publish it myself.”

That sentence contains the whole approach most people take months to reach: AI drafts, a human checks, a human publishes. The gap between that and “AI writes the report and mails it out unchecked” is wide. One is automation that works. The other is a machine for sending the team a beautifully written lie.

Reporting and status updates came out as the second-largest group of requests (in Russian) in this data set. The weekly status for the team and for stakeholders, short summaries after meetings, monthly budget execution reports, material for the daily stand-up. The demand is real, and it lands exactly where language models are strong. Here is how to build a repeatable process around it.

How to Brief Developers with AI: Specs That Hold Up
40 min

How to Brief Developers with AI: Specs That Hold Up

We asked forty managers which work task they would most like to speed up with AI. Open question, no options to pick from. The winner, by a wide margin, had nothing to do with polished slide decks or automated email. Answer after answer came back to the same thing: help me get tasks across to developers.

The wording varied. The pain did not. ‘Improve the quality of requirements our analysts write.’ ‘Make writing specs for developers faster.’ ‘Write user stories from the flows our analyst has drawn.’ ‘Check task descriptions before they go to the team.’ ‘Build a test plan from the requirements.’ ‘Standardise how our business analyst writes briefs.’ Project managers, product owners, analysts: all of them stuck at the same gap between ‘I know what I want’ and ’the team understood the same thing’.

Tellingly, this is exactly the task where language models are at their most reliable. Writing a brief is text work in its purest form: take a half-formed thought and give it a structure that can travel. Demand and the tool’s strength line up almost perfectly here. But between ‘AI is good at structuring text’ and ‘AI will write your spec’ there is a wide gap, and it is easy to fall into it.

Your Team Doesn't All Use AI. It Splits Into Thirds
10 min

Your Team Doesn't All Use AI. It Splits Into Thirds

Microsoft published a number in 2026 that sounds impressive: more than 30% of the US working population uses AI. It goes on sounding impressive right up to the point where you read the definition. Using AI, here, means 90 minutes a month. That is three minutes a working day.

If your feed is full of people writing prompts over breakfast and building agents after dinner, you will have formed the impression that AI is everywhere and everyone has mastered it. The data does not support that impression. Microsoft’s Work Trend Index for 2026 (in Russian) found that organisational factors explain 67% of the difference in AI effectiveness between companies.

Why Teams Hide How They Use AI
12 min

Why Teams Hide How They Use AI

A doctor, 31, uses AI several times a day. He built a prompt template for the tool his hospital approved, and by his own account the results are startling. His colleagues have the same tool and complain that it gives them nothing. He knows his template would fix that.

He still does not share it.

That is the opening case in an HBR study, which asks an awkward question: if AI really does raise productivity, why can’t companies see it? A global survey by KPMG and the University of Melbourne – more than 48,000 respondents – found the answer. 57% of employees admit they hide how they use AI at work.

Why AI Pilots Die Between the Demo and the Factory Floor
11 min

Why AI Pilots Die Between the Demo and the Factory Floor

The pilot was shown at the board meeting, everyone applauded, budget was approved for ‘scaling.’ Six months later, the computer vision system that caught 98% of defects during the demo is catching maybe half, quality inspectors have stopped trusting it, and the project has quietly migrated into the ‘deferred initiatives’ column. This is not a rare mishap or the fault of a particular integrator. According to RAND, this is how more than 80% of corporate AI projects end – and almost always for reasons that were visible before the project even started.

40 GigaChat Case Studies vs the Benchmark: Checking Sber's Numbers
23 min

40 GigaChat Case Studies vs the Benchmark: Checking Sber's Numbers

Sber, Russia’s largest bank and the company behind GigaChat, released a sponsored showcase: forty business cases from companies that deployed GigaChat and reported the results. EdTech, MedTech, HRTech, cybersecurity, PropTech. Polished cards, concrete numbers, real startups.

Sber’s promotional project

On the image: the “One step ahead” promo slide from the Sber500×GigaChat accelerator – 40 startups across 9 industries. Claimed effects: business processes up to x16 faster, costs down by up to 90%, up to 95% task automation, and revenue up by up to 30%.

We have a benchmark of our own: 29 models, 4,308 independent evaluations on managerial tasks. In it, GigaChat sits dead last – 29th out of 29 after the second wave of testing. That creates an interesting situation.

Not because Sber is lying. The cases are real, the startups exist, the automation works. The question is different: was this the optimal model for the tasks they were solving?

How to Implement AI in Manufacturing: A Step-by-Step Guide for Plant Leaders
26 min

How to Implement AI in Manufacturing: A Step-by-Step Guide for Plant Leaders

A shift supervisor at a mid-size machining plant spends 40 minutes every morning filling out the shift report. Manually copying equipment readings into a Word template, describing incidents in free text, cross-checking the safety log. This routine has existed since the 1970s and hasn’t changed by a single minute. AI can cut it to ten. The hard part isn’t the technology. The hard part is knowing where to start.