Before I managed engineers, I studied educational technology, how people learn and what tools do to help or hinder it. It shaped how I lead more than anything else I studied, because a team that is not learning is slowly becoming obsolete, and most of a manager's job is arranging for learning to happen.
The learner does the work
The first thing the field teaches is that learning is something the learner does. An excellent lecture produces nothing if the listener never does anything with it, and the same goes for an onboarding document.
So I am suspicious of anything that transfers knowledge by exposure. The engineer who read the design doc has not learned the design. The one who changed it, or explained it to someone else, has. I try not to mistake having been told for knowing.
Feedback has to be fast and specific
The second idea is that feedback changes behavior only when it is close to the action and specific. A comment on the sentence, the day it was written, changes the next one.
Engineering knows this at the mechanical level, which is why linters run in seconds, and it applies at the human level too. A review comment the day of the change teaches. A performance conversation months later does not. The most useful thing I can do for someone's growth is shorten that loop.
Scaffolding has to be removed on purpose
Scaffolding is the support that lets a learner do something they could not yet do alone, the worked example, the pairing partner. It works, and it has to be taken away as competence grows, or it becomes a crutch that stops growth where the support ends.
I think most teams are good at putting scaffolding up and bad at taking it down. The checklist written for the first month is still followed in the third year. Removing support feels like withdrawing help, and it is the moment the learning is allowed to finish.
Whatever you assess, you get more of
Every teacher learns this the hard way. Students study what is on the test. Assessment does not measure behavior so much as produce it.
Engineering teams are assessed constantly, in reviews, in what gets praised and promoted, in what is on the dashboard. Every one of those is a test, and the team is studying for it. If visible output is what gets noticed, output becomes visible and quality goes quiet. Every metric I introduce is a lesson plan, and I try to ask what it will teach before I ask what it will measure.
Why I think this matters
Most of what a manager does is set the conditions under which people learn. Who works on what, how fast the feedback comes, when the support is removed, what the assessment rewards. Any engineering leader would benefit from time spent on how people actually learn, because that is the work.
Photo source: https://photos.robertstowe.com/bengaluru
