Leading in the AI Era Module 4 · Lesson 4.3 · Leading capable people

Develop, recognize, retain: protected time to learn and improve the work

Updated

Beginner

What you'll learn

~10 min
  • Decide how much protected learning time a team gets, and who protects it
  • Name what a domain expert and a builder each bring when paired on a workflow
  • Name the recognition that goes to people who test, review, maintain and improve workflows, not only to those who build

You leave this lesson with: a one-page plan for one team that sets its protected learning time, its pairings and the recognition it gives.

Protected time to learn

Access to a tool is not the same as time to learn it. An employee given a license and a full calendar has no room to try something that might not work on the first attempt.

A BCG survey of more than 10,600 leaders, managers and frontline white-collar employees in 11 countries and regions found that regular use among the frontline subgroup had stalled at 51%, that regular use was much higher among those with at least five hours of training, and that only about one-quarter of frontline employees said they received leadership support (BCG, AI at Work, June 2025). That is a correlation from a self-reported survey, not proof that training causes use. It does point at what a leader controls: time, and visible support.

Protected means the time is on the calendar, the work is covered, and a manager does not take it back at the first deadline. The cited survey does not establish how much learning time this team needs. Agree the amount and the review date with the team, using its workload and existing commitments to decide what is realistic. Name who will protect that time when urgent work arrives.

Learning time also needs a design. In a randomized trial reported by Anthropic, a vendor, 52 mostly junior software engineers learned a new set of programming tools either with an AI assistant or by hand. On a quiz afterwards about the tools they had just learned, the assistant group averaged 50% and the hand-coding group 67% (Anthropic, 52 engineers). The quiz measured understanding, not productivity; time to finish the task differed by about two minutes, which was not statistically significant. It was one short task with one set of tools, so it does not show long-run skill loss. It does suggest that learning time should ask people to understand what the tool produced, not only to accept it.

Pair a domain expert with a builder

In a two-day session with university research staff, researchers with deep knowledge of their own field produced working analyses once someone sat with them for those two days. The researchers knew what a correct answer looked like and which shortcuts were wrong. The person beside them knew how to get the tool to act.

In that session the researchers produced analyses they judged correct; no time or productivity was measured, so treat pairing as a practice to try and review, not a proven gain.

The pairing has a shape you can copy. The domain expert owns the question and decides whether the result is right. The builder, whether a colleague with technical skill or a person who has used the tools longer, owns the mechanics. Each can say no to the other. Rotate the pairs so knowledge spreads and does not sit with one person.

Recognize the people who test, review and maintain

Building a new workflow is visible. Testing it against the old way, reviewing its output, maintaining it when something changes and improving it after launch is less visible, and is the work that makes it last.

Check whether recognition includes testing, review and maintenance as well as building. Ask the people doing that work whether its time and responsibilities appear in their workload and performance criteria.

Make the recognition specific. Name the reviewer who found the error before it left the team. Credit the person who rewrote the instructions after a process change. Put maintenance and review in job descriptions and performance conversations as work, not as a favor. A government agency program might add a line to its quarterly report listing each workflow, its owner and who last tested it.

💬Decision: one star builder, one tester

A company team has one colleague who built a successful report workflow and another who has twice caught errors in its output before they reached customers. The annual recognition award traditionally goes to one person, though it can be shared.

  1. Give it to the builder, following the tradition, since the workflow was the visible achievement.
  2. Split this year’s award between them, name what each person contributed, and add testing and maintenance to the recognition criteria for next year.
  3. Give it to the tester, since the errors caught are the proof the workflow can be trusted.

Pick one before you open What happens.

ℹWhat happensclick to expand
  1. Give it to the builder: It keeps the tradition and recognizes real work, but it tells the team that building is what counts and checking is not.
  2. Split this year’s award: Both the builder and the tester are recognized, and the criteria change for next year.
  3. Give it to the tester: It corrects the signal Choice 1 sends, but overlooks the person who made the workflow exist.

Choice 2 holds up, because it names both contributions, and changing the criteria means next year’s choice does not depend on a one-off exception.

KNOWLEDGE CHECK

A manager agrees weekly learning time with an analyst. In the third week a deadline arrives. What keeps the time protected?

Key takeaway

LEADERSHIP DECISION
Protect learning time for one team and name the person who defends it from the next deadline
IMMEDIATE ACTION
Pair one domain expert with one builder on a real workflow this month, and add testing and review to the criteria your recognition uses
SUCCESS MEASURE
Changes in how the team does its work that came from the learning time, each shown working by the person who made it at the agreed review date
Search lessons