The Time It Takes to Teach

A senior technician has two things on her bench: a repair that needs finishing and a beginner who needs to understand why she has stopped.

She can complete the check herself in a few minutes. Explaining it will take longer. The newcomer will ask a sensible question that opens another question. They may need to look at a safe practice example before the point becomes clear.

The repair total at the end of the day will count one kind of work. Unless the employer has made a place for teaching, it may fail to count the other.

This is a quiet way to weaken a first rung. The organization promises development, then rewards the people capable of providing it as though teaching were an interruption they should absorb for free.

A mentor’s goodwill can carry a learner through a difficult afternoon. It cannot be the entire staffing plan.

Teaching uses scarce attention

Natalia Emanuel, Emma Harrington and Amanda Pallais studied software engineers at one large U.S. retailer, using office closures and returns to examine changes in proximity. Their analysis found more feedback and better code quality when coworkers were near one another, especially for younger or less-tenured staff. Experienced engineers gave up some of their own coding output. The setting and nonrandom design limit generalization; the result does not establish that office attendance alone teaches people or that remote work is universally inferior.¹

The cost is important. Time spent helping a colleague is time that cannot simultaneously be spent on another task. If an employer wants both tasks done, it needs to allow for both.

This may sound obvious. Yet consider how easily teaching becomes invisible in an ordinary performance review. A senior employee finishes fewer tickets because she answers questions, checks drafts and helps a newcomer avoid an error. A colleague who does none of that finishes more. If the review looks only at completed tickets, the organization can reward the behavior that leaves its future staff less prepared.

The remedy is not to invent a flattering title for the first employee. Give the work a place in the workload and evaluate it sensibly. What learning responsibilities has she accepted? How much time is available? Which other tasks have been reduced? Who covers when she is absent?

Teaching may also require support for the teacher. Being good at a task does not automatically make it easy to explain. A skilled worker may skip steps that have become familiar. They may need help designing a safe first assignment or giving feedback that identifies the actual problem.

A workplace should make it possible to learn how to teach without pretending that every experienced employee wants the same role.

A named person needs a real appointment

A new employee may be told that anyone will be happy to help. Sometimes this is true. Sometimes it means that everyone assumes someone else is responsible.

A named mentor gives the beginner a place to start. But a name alone is not enough. The arrangement needs time, scope and a backup.

At the repair shop, the trainee might observe selected work, practice on approved training material and meet the technician for a short review before taking on another task. The technician knows which decisions the trainee may make and which remain outside their role. When she is away, someone else is clearly responsible for checking the work.

This is more useful than placing the trainee beside a busy person and hoping proximity will turn into instruction. Being close can make a question easier to ask. It cannot create time that the schedule has already spent.

The mentor should also know what to do when a learner needs support beyond the mentor’s role. A problem with pay, access or harassment should not depend on the teacher solving everything personally. Someone else in the organization or program must have responsibility for those issues, with a route the learner can understand.

Otherwise the relationship carries too much weight. The mentor becomes teacher, assessor, advocate, administrator and gatekeeper. The beginner may be afraid to raise a concern because the same person influences every outcome.

A good teaching relationship needs trust. It also needs a wider structure that keeps trust from becoming dependence on one person’s favor.

Put questions where they can be answered

Interruptions are real. A beginner cannot expect every question to receive an immediate, lengthy reply. A mentor cannot expect a beginner to guess which unanswered question might cause harm.

Separate the urgent from the ordinary. A possible safety issue, privacy breach or serious customer problem needs a clear immediate route. A question about improving a draft may be collected for an agreed review. The categories depend on the work, and they should be explained before the learner has to decide under pressure.

For ordinary questions, a small record can help. What are you trying to do? What have you tried? What result did you expect? Where are you stuck? The purpose is to make the problem easier to understand, not to make asking so laborious that the beginner gives up.

A mentor can then see whether several questions share the same missing concept. If they do, another correction may be less useful than a short teaching session. A team can also improve its instructions when many newcomers trip over the same unclear step.

Do not confuse a quieter learner with a learner who needs less help. Some people hesitate to interrupt. Others ask quickly because the workplace has made that easy for them. The review should include a chance to surface uncertainty without rewarding the most forceful voice.

Ask about a decision, not only whether everything is fine. Which part of this task felt least clear? What would you want checked before it goes further? Those questions give the person a concrete place to begin.

The answer may reveal a gap in the teaching as well as a gap in the learner’s knowledge.

Distance changes the design problem

Remote work can make casual observation harder. It can also make a job possible for someone who cannot manage a daily journey, needs a different physical environment or lives far from an employer. An entry system must consider both sides.

A recent experiment by Lisa Ho, Suhani Jalota and Anahita Karandikar offered short-term digital work to women outside the labor force in West Bengal. Home-based and childcare-flexible arrangements increased take-up compared with office work; later work offers also showed greater take-up among some women without earlier work experience. The study concerned selected households and a short job, not a universal remote-career model. Access and teaching conditions need to be designed together.²

This evidence should make an easy slogan uncomfortable. Bring everyone back to learn ignores people for whom the journey or schedule prevents entry. Let everyone work anywhere and the learning will take care of itself ignores the support a newcomer may need.

Instead, ask what the work requires. Does a learner need to observe a physical process? Could a safe demonstration or a scheduled session provide part of that access? Which feedback can happen through a shared document, a call or a recorded explanation? What needs an in-person setting, and how can that setting be made reachable?

A remote beginner should know when questions will be answered. A message left without a response for two days is not equivalent to a colleague available at the next bench. A hybrid beginner should not miss every important discussion because the team keeps placing it on the day they cannot attend.

These are design choices. They are not proof that one location works best for everyone.

Nor should flexibility become a demand to perform two full jobs at once. Working from home does not make care duties disappear. A humane employer asks whether the hours and support are workable, rather than treating a person’s home as an unlimited source of unpaid coordination.

Let people see the reasoning

Experienced workers often leave a trail of finished decisions without the reasoning that produced them. A newcomer sees the final repair note, the approved response or the corrected design, but not the uncertainty that came before it.

A mentor can occasionally open that process. Explain why one possible action was rejected. Show how you checked a doubtful assumption. Describe what would have made you stop and ask someone else. Keep private information protected and choose a case suitable for teaching.

This is different from narrating every thought all day. That would be exhausting for both people. Select a moment that reveals a decision the learner will soon need to make.

At the repair bench, the technician might explain why the reported symptom is not enough to justify replacing a part. The lesson is about checking before acting. The trainee does not need permission to perform a hazardous procedure to understand that a guess and a diagnosis have different status.

The learner can then explain the decision back, using their own words. If the explanation reveals a misunderstanding, correct it before the next task adds more complexity. When the learner is ready, let them propose the next safe check within the approved training setting.

Teaching works better as a shared examination of the task than as a performance of the expert’s brilliance. A mentor who can admit uncertainty also models an important boundary: expertise includes knowing when the available information is insufficient.

The beginner should leave the exchange with a clearer method, not merely a stronger impression that the senior person is clever.

Do not build the route around unpaid generosity

Some people will teach because they care, even when the organization gives them little support. This is admirable in the person and risky as a system.

The arrangement can fail when that person leaves, becomes overloaded or is promoted into a role with less time. It can also distribute teaching unfairly. The colleague who is approachable may receive more requests than the colleague who makes questions unpleasant. If only individual output is rewarded, being helpful can become a disadvantage.

A team should make the contribution visible without turning every conversation into a bill. A regular workload discussion can include teaching duties. A manager can ask whether the number of learners fits the available mentors. A program can prepare shared examples so that every teacher does not have to invent the same exercise from nothing.

There is a place for peer support too. Newcomers can compare interpretations, practice explaining a concept and identify questions to bring to a qualified person. But peers should not be left responsible for decisions they are not yet able or authorized to make. A group of beginners can share a misunderstanding as readily as they can help one another.

A support channel should therefore have a clear way to reach expertise. The aim is to make help available at the right level, rather than place everyone in a group chat and call the job done.

Pay and recognition should follow the responsibility. Teaching is part of producing the workforce, and it belongs in the organization’s account of its work.

The learner needs more than approval

A mentoring relationship can become comfortable without producing progress. The learner enjoys encouragement. The mentor enjoys being helpful. Neither side asks whether responsibility is growing.

Choose a few concrete signs to review. Can the learner handle a familiar task with less prompting? Do they identify a relevant risk earlier? Can they explain why a correction was needed? Have they tried a harder task under suitable supervision? The signs should fit the role and remain open to revision.

Avoid treating speed as the only sign. A learner may slow down because they now see a risk they previously missed. That may be progress, even while it creates a new need for practice. Later, the person may become both careful and faster. The sequence need not be perfectly smooth.

Also ask whether the role offers enough variety. If the learner repeats a narrow task indefinitely, the mentor may be unable to observe broader growth. A rotation or a different assignment can provide new evidence, provided it does not move the person into unsafe work.

At some point, another reviewer should be able to understand what the learner has done. A brief, accurate record of responsibilities and observed work helps prevent the relationship from becoming a private judgment that disappears when the mentor leaves.

The learner deserves something more portable than a kind person saying they seem promising.

Make teaching survive an ordinary week

The test of a mentoring plan is not the welcome session. It is a busy Tuesday when a customer is waiting, a colleague is absent and the beginner has found a problem no one expected.

Does the learner know where to go? Is someone responsible for reviewing the decision? Can the mentor take the time without being penalized for failing another impossible target? Will the team learn something from the problem, or merely hurry past it?

We cannot remove every pressure from working life. We can stop building entry roles that fail as soon as normal pressure arrives.

The technician returns to the bench. The repair still needs finishing. The trainee has understood why the first guess was not enough and can now describe the next approved step. The conversation took time, and the employer planned for it.

That last detail changes the meaning of the scene. Teaching has become part of the job. The newcomer is no longer relying entirely on a favor, and the experienced worker is no longer paying the hidden cost alone.

A first rung becomes more reliable when the people holding it have been given the time to do so.

Sources and limits