Engineering Leadership

Why Engineering Managers Should Protect Learning Time

Telling engineers to “go learn it” is not a strategy. Learning needs real capacity, and leaders are the ones who have to protect it.

When teams are moving to a new technology stack, telling engineers to “go learn it” is not a strategy.

It sounds supportive. It even sounds empowering. But in practice, it usually means: learn it on your own time, around everything else you’re already responsible for. And that rarely works.

Learning requires capacity.

Training is real engineering work

One thing I strongly believe in is creating dedicated learning time and treating training as real engineering work.

That means it shows up in planning. It has time allocated. It’s visible to stakeholders. It’s not something engineers have to apologize for or squeeze into the gaps.

As our team prepares for a different CMS and front-end model, our learning roadmap includes JavaScript, TypeScript, React, Next.js and related modern web development skills. Those aren’t optional extras. They’re the skills the team will need to build, run and support the next platform. If we don’t invest in them now, we’ll pay for it later in slower delivery, more defects and heavier reliance on outside partners.

Operational work always wins, unless you intervene

Here’s the dynamic I’ve seen again and again: if leaders don’t protect training time, operational work will consume it every time.

It’s not because anyone decides learning is unimportant. It’s because operational work is urgent and learning is important, and urgent almost always beats important in the moment.

  • A production issue comes in. Learning waits.
  • A stakeholder needs a page by Friday. Learning waits.
  • A sprint is running behind. Learning waits.

Each individual decision is reasonable. But add them up over a quarter, and the team hasn’t learned anything. Then the new platform arrives, and everyone is expected to be productive on day one.

The only way to break that cycle is for leadership to treat learning time as protected, the same way we’d protect time for a critical release.

What protected learning looks like

In practice, protecting learning time can take a few forms:

Planned capacity in the sprint. A portion of each sprint is set aside for structured learning. It’s accounted for in commitments, so the team isn’t penalized for using it.

Learning tied to real work. The most effective learning happens close to actual use. Small, low-risk tasks on the new stack, like a prototype component or an internal tool, let people practice on something meaningful.

A clear roadmap. “Learn React” is vague. A sequence that moves from JavaScript fundamentals to TypeScript to React to Next.js gives people a path and a sense of progress.

Shared learning. Engineers presenting what they’ve learned to each other reinforces their own understanding and spreads knowledge across the team.

Leadership visibility. When I ask about learning progress in one-on-ones and team syncs, it signals that it matters as much as delivery.

It’s also about trust

There’s a cultural side to this. When engineers see that learning time is protected, they understand that the organization is investing in their future, not just extracting work from their present.

That builds loyalty and confidence, especially during technology changes, when people may be quietly worried about whether their skills will still be valued. Protected learning time is one of the clearest answers a leader can give to that worry.

The best investment

Technology changes. Platforms change. Frameworks rise and fall.

The best investment we can make is ensuring our people can change with them. A team that knows how to learn, and has the time to do it, will outlast any single platform choice.

I’d rather build that kind of team than one that is perfectly skilled for today’s stack and stuck when tomorrow’s arrives.

Nita Yang Lee

Senior Software Engineering Manager in Atlanta, leading web operations, platform modernization and engineering teams. More about me · Get in touch

Keep reading