INTRO

At 9:12 on a Tuesday morning, a newly appointed mentor receives a spreadsheet from the person they are supposed to be helping. The file is beautifully organized. There are columns for career goals, current obstacles, possible solutions, deadlines, and one particularly interesting heading: "Mentor's Decision." Beneath it are questions about applying for a promotion, challenging a manager's opinion, volunteering for a difficult assignment, and whether to accept an invitation to join a new project. The mentor stares at the screen. Apparently, they have been promoted to Chief Executive Officer of Someone Else's Career, a position they never applied for and which, according to the calendar, comes with absolutely no additional vacation days.

The situation is absurd, but the misunderstanding behind it is remarkably ordinary. Someone becomes a mentor because they have experience worth sharing. Someone else becomes a mentee because they want to learn from that experience. Both arrive with perfectly reasonable intentions. Then, almost imperceptibly, the relationship begins rewarding the wrong behavior. The mentee brings a problem, the mentor supplies an answer, and everybody feels productive. The mentor enjoys being useful. The mentee enjoys avoiding an uncertain decision. The conversation ends with a clear recommendation and perhaps even a reassuring smile. Unfortunately, the next unfamiliar problem produces exactly the same dependency. Nothing has necessarily gone wrong with the advice. Something has gone wrong with the purpose of the relationship.

Giving answers is especially tempting when you genuinely know what you are talking about. Experience allows you to recognize familiar situations, anticipate obstacles, and identify mistakes that less experienced colleagues have not yet encountered. Watching someone struggle with a decision you could make in thirty seconds can be uncomfortable. Why allow a long discussion when you already know a sensible solution? Because the answer in your head may be the result of years of observations, experiments, embarrassing meetings, and decisions you would rather not repeat. Handing someone your conclusion without helping them understand the reasoning can save time today while doing very little to improve their judgment tomorrow. Efficiency and development are not always the same thing.

This does not mean a mentor should become mysteriously incapable of providing information. If your mentee needs to know how a particular approval process works, explain the process or point them toward an authoritative source. There is no educational benefit in responding, "What does approval mean to you personally?" when someone is trying to submit an expense request before the deadline. The real distinction lies between supplying information and assuming responsibility for another person's judgment. Facts, procedures, and specialist knowledge can be shared directly. Decisions involving competing priorities, personal aspirations, uncertain consequences, and professional values usually deserve a different kind of conversation.

Of course, there is an equally irritating alternative: the mentor who has discovered the magnificent power of questions and now refuses to make a declarative statement under any circumstances. Ask whether a project deadline is realistic, and they ask how you define realism. Explain that two departments disagree, and they wonder what disagreement represents in your professional journey. Eventually, you begin considering whether the office printer might offer more practical guidance. Questions are valuable when they reveal missing information, challenge assumptions, or help someone examine a choice. They become exhausting when they are performed like a technique rather than used with genuine curiosity. A good mentor knows when to ask, when to explain, when to listen, and when to admit that neither person currently knows enough.

Consider someone preparing to lead a high-profile initiative. They ask whether they should accept the opportunity. An enthusiastic mentor may immediately recommend saying yes, remembering how a similar assignment accelerated their own career. But perhaps the mentee is already managing two demanding projects, lacks authority over the necessary resources, and wants to deepen technical expertise rather than move toward general management. The opportunity might still be worthwhile. What matters is that the decision should reflect the mentee's circumstances, not the mentor's preferred version of professional success. The most useful conversation may uncover what the role actually requires, which trade-offs are acceptable, and what information needs to be clarified before committing.

Your own career history deserves a place in mentoring, but it should not become the official instruction manual for everyone else's future. Perhaps you advanced by taking risks, switching organizations, or working exceptionally long hours during a particular period. Those experiences can illuminate decisions, especially when you explain their costs and limitations alongside their benefits. They cannot establish what another person should value. Circumstances change, organizations differ, and people have legitimate priorities outside their professional ambitions. A mentor who insists that every worthwhile career follows the route they personally traveled is offering a guided tour of their autobiography. Interesting, perhaps, but not necessarily the destination the visitor had in mind.

Real mentoring also happens in imperfect conditions. Mentees arrive tired, distracted, uncertain, or reluctant to discuss something important. Managers make contradictory demands. Development opportunities disappear because budgets change. Some people genuinely want to improve but cannot control the structures limiting their responsibilities. Others enthusiastically agree to ambitious plans and then struggle to act on them. These situations cannot all be repaired with a more inspirational question or a motivational speech about leaving your comfort zone. Sometimes the useful contribution is identifying an organizational obstacle, changing an unrealistic expectation, or recognizing that a particular issue requires support beyond the mentor's expertise.

Boundaries matter for the same reason. Being a mentor does not automatically make you someone's manager, therapist, recruitment agent, personal advocate, or permanently available emergency adviser. You may sometimes offer practical help that overlaps with those roles, but the nature and limits of that help should be understood. Confidentiality, availability, decision-making authority, and responsibility for follow-through deserve clear discussion. Without those agreements, goodwill can gradually turn into frustration. The mentee feels unsupported because their expectations were never discussed; the mentor feels exploited because they have become responsible for obligations they never consciously accepted.

Throughout this book, we will examine what useful mentoring looks like when conversations stop being theoretical. You will learn how to identify the problem underneath an apparently straightforward request, offer feedback that can actually influence behavior, and share experience without making yourself the model everyone must imitate. We will explore how to turn interesting conversations into meaningful action, prepare someone for uncomfortable professional situations, and allow enough room for mistakes without ignoring genuine risks. Just as importantly, we will consider what happens when the relationship itself becomes difficult: when commitments are repeatedly missed, advice turns out to be wrong, trust is damaged, or the mentor realizes that the situation calls for a different kind of professional support.

None of this requires becoming a flawless conversational genius. There will be moments when you interrupt too quickly, make an assumption, or offer a recommendation that seemed excellent until reality developed other plans. You may occasionally discover that the mentee's solution is better than yours, which can be particularly inconvenient if you have already delivered a confident five-minute explanation of why your approach is superior. The goal is not to eliminate every mistake or turn mentoring into an elaborate system of worksheets and techniques. It is to develop enough awareness to recognize what the other person needs, what you can responsibly offer, and when your instinct to help is beginning to interfere with their independence.

The ultimate measure of mentoring is not how indispensable you become. It is what the other person can understand, decide, and accomplish when you are no longer sitting beside them. That includes the ability to recognize when they genuinely need expertise, to seek it thoughtfully, and to remain responsible for their own choices. Independence does not require professional isolation. Experienced people consult colleagues, challenge their assumptions, and ask for help throughout their careers. The difference is that they know why they are asking and what they intend to do with the answer.

Now return to that spreadsheet with the mysterious "Mentor's Decision" column. You do not need to delete the file, deliver a lecture about personal responsibility, or announce that all future questions must be submitted in writing with supporting evidence. You could begin by asking the mentee how they have approached one of those decisions, what matters most to them, and where your perspective might genuinely help. Perhaps you will share a relevant experience. Perhaps you will discover an important fact they have overlooked. Perhaps the conversation will end without a final decision because something still needs investigating. What matters is that the ownership of the decision stays where it belongs. A successful mentor does not need to become the search engine for an entire career. The more valuable achievement is helping someone become capable of finding, evaluating, and acting on their own answers.

Chapter 1 - Congratulations, You're the Answer Department. How Mentoring Quietly Turns into Dependency

At 2:46 on Monday afternoon, Helen receives an email from her mentee, Oliver. The subject line reads, "Quick question about tomorrow's update." Attached is a presentation concerning a customer retention initiative. Oliver wants to know which figures to emphasize, how to explain a delay, and whether the final slide should contain a recommendation or simply summarize the current situation. Helen has been working in commercial management for fifteen years. She recognizes the problem immediately, opens the presentation, rearranges two slides, rewrites the recommendation, and sends the file back with a friendly message. Total time: eleven minutes. Excellent mentoring, apparently. Oliver is delighted. Helen feels useful. The following Monday, she receives another presentation with almost identical questions. By Thursday, she has corrected three emails, reviewed a meeting agenda, and helped choose the wording of a message to a senior director. Somewhere along the way, she has acquired a second job without remembering an interview.

The strange thing is that nobody has requested this arrangement explicitly. Oliver believes he is learning from an experienced professional. Helen believes she is helping a promising colleague avoid unnecessary mistakes. Both are acting with good intentions. Yet their relationship has developed a predictable pattern: Oliver encounters uncertainty, Helen resolves it, and the immediate difficulty disappears. What remains untouched is Oliver's ability to handle similar uncertainty independently. His documents improve whenever Helen reviews them, but she has little evidence that his underlying judgment is improving. If she takes a week off, the quality of his decisions may depend less on what he has learned than on whether he can persuade someone else to review his work.

This is one reason unproductive mentoring can be surprisingly difficult to recognize. There may be no obvious conflict, missed meeting, or dissatisfied participant. On the contrary, the relationship can produce impressive amounts of visible activity. Files are improved, difficult messages are rewritten, and decisions are reached faster. Helen might even receive enthusiastic feedback about how generously she shares her expertise. But activity is not the same as development. A finished presentation shows that a presentation was finished. It does not establish who understood the problem, weighed the alternatives, or learned something applicable to the next assignment. If the mentor supplies all three, the mentee may be collecting excellent documents while remaining uncertain about how to produce them.

The central difficulty is that solving a problem and developing a problem-solver are different objectives. They sometimes overlap, but they are not interchangeable. During a genuine emergency, speed and accuracy may be more important than creating a learning opportunity. At other times, a slightly slower conversation can provide lasting value because the mentee participates in the reasoning. The mentor's task is to recognize which objective matters in the situation at hand. That requires more judgment than simply answering every question quickly, and rather more patience than most organizations include in their official descriptions of mentoring.

The invisible transfer of responsibility

Look more closely at Oliver's presentation. His first question concerns which figures should appear on the opening slide. Helen could answer immediately because she knows the audience and understands the commercial implications. Instead, imagine that she asks what decision the presentation is intended to support. Oliver explains that the management team must decide whether to extend a customer retention initiative. Helen then asks which figures would help the audience judge that decision. After some thought, Oliver identifies the change in customer retention, the cost of the initiative, and the limitations of the available data. He had originally planned to lead with the number of customer contacts because it looked impressive. The conversation reveals that he was selecting information according to how persuasive it appeared rather than how useful it was for the decision.

Helen can now share her experience more precisely. She might explain that senior leaders often need to understand the relationship between outcomes, costs, and uncertainty before approving additional investment. She can also point out that the retention figures require careful interpretation because the initiative has not been running for long. Oliver still benefits from her knowledge, but he must decide how to organize his argument. The useful outcome is no longer a presentation that happens to look like something Helen would produce. It is Oliver's developing ability to connect information with the purpose of a business discussion.

The distinction becomes clearer when we separate different kinds of requests. Some concern facts the mentee does not know. Others require judgment about several reasonable options. Some involve authority: the mentee cannot make a decision because somebody else must approve it. Still others are requests for reassurance disguised as technical questions. A person asking, "Is this email okay?" might need a factual correction, help assessing the audience, confirmation of a required procedure, or simply relief from the discomfort of sending a difficult message. These needs can sound similar, but the appropriate responses differ considerably. Treating every request as an invitation to rewrite the document overlooks what the person actually needs.

There is no virtue in refusing to provide straightforward information. If Oliver does not know where the approved reporting definitions are stored, Helen can tell him. If a figure must be calculated according to an established method, he needs that method rather than an inspirational conversation about numbers. Likewise, if a document contains a material error that could mislead decision-makers, correcting it promptly matters more than preserving an educational atmosphere. The opportunity for development lies in explaining the significance of the information and involving Oliver in the appropriate next step, not in withholding necessary knowledge.

For a genuinely inexperienced mentee, asking for an independent recommendation too early can also create unnecessary pressure. Someone who has never worked with customer retention data may lack the concepts needed to compare alternatives. Helen may first need to demonstrate how an analysis is constructed, explain common limitations, or work through an example alongside Oliver. Gradually, she can transfer more of the reasoning to him. Independence develops through appropriate responsibility supported by relevant knowledge. Throwing someone into unfamiliar work and announcing that the discomfort is educational is not mentoring. It is an administrative decision with optimistic branding.

When helpfulness becomes a queue

After recognizing the pattern, Helen examines their communication between meetings. She discovers that Oliver frequently sends questions the moment they occur to him. Some are important, but many concern ordinary decisions that fall within his responsibilities. Because Helen usually responds quickly, waiting for her opinion has become part of his working process. Neither person intended to create this dependency. It emerged because requesting an answer was easy, receiving one was rewarding, and nobody had clarified what belonged in their mentoring conversations.

Helen decides not to announce a dramatic new policy under which all questions will be ignored until the mentee achieves enlightenment. Instead, she explains what she has noticed. "We're spending a lot of time reviewing individual pieces of work," she tells Oliver. "I'd like us to spend more time on how you make those decisions, so you don't need my review for every similar situation." She proposes that routine questions come to their scheduled discussions unless there is a genuine reason to address them sooner. When Oliver does bring a decision, she asks him to explain his current assessment and where he wants another perspective.

This arrangement is not a demand that Oliver complete an essay before earning the privilege of asking for help. If he has an urgent factual question, a brief message may be appropriate. If he faces a serious risk outside his authority, he should follow the organization's escalation procedures rather than wait for their next mentoring session. Helen is not his line manager, and her availability should never substitute for required approvals or operational support. The point is to prevent ordinary mentoring from becoming an unofficial approval system that neither person is responsible for maintaining.

Their first meeting under the revised arrangement feels slightly awkward. Oliver arrives with a draft recommendation concerning an advertising experiment. He explains that the early results are encouraging but the available sample is small, and he proposes continuing the experiment before recommending wider investment. Helen disagrees with one assumption about the cost. Previously, she might have replaced his conclusion with her preferred recommendation. This time, they examine the assumption and identify the information required to test it. Oliver adjusts his analysis and decides which recommendation he will submit through the proper approval process. Helen contributes expertise without becoming the author of his decision.

Something important has changed, although it would be difficult to celebrate with a conventional productivity metric. Helen may have spent more time discussing this recommendation than she would have needed to rewrite it. Oliver, however, understands why his original assessment required revision. More importantly, he has practiced a form of reasoning he can use when considering a different commercial proposal. A mentoring relationship sometimes needs to sacrifice a little immediate convenience to develop a capability that will reduce repeated dependence later.

The distinction matters for the mentor's workload too. A relationship built around instant answers can gradually absorb an unreasonable amount of time. Each individual request appears small, making it difficult to notice the accumulated cost. Five minutes before a meeting, another question during lunch, and a brief review before leaving the office do not look significant in isolation. Together, they may prevent the mentor from fulfilling their actual responsibilities. Clear boundaries protect both participants. The mentor can provide thoughtful attention during agreed conversations, while the mentee learns not to confuse access to an experienced person with unlimited access to that person's working day.

What progress looks like when you're not holding the pen

The most useful evidence of improvement is not necessarily a reduction in the total number of questions. Oliver might begin asking more sophisticated questions as his responsibilities expand. That can be a sign of progress rather than dependency. What matters is the nature of those questions. Is he seeking basic approval for choices he is capable of making, or is he testing assumptions about unfamiliar consequences? Does he arrive without considering alternatives, or can he explain his reasoning and identify the precise uncertainty that remains?

Helen can assess this through actual work rather than elaborate scoring systems. After a difficult assignment, she may ask Oliver which decisions he made without assistance, which required additional information, and what he would approach differently next time. She should also notice whether he transfers his learning to new situations. Someone who has learned to construct a clear recommendation should gradually demonstrate that ability in contexts beyond the original presentation. Perfect independence is neither realistic nor desirable. Competent professionals still consult colleagues and request expert judgment. The relevant change is that they know what they are asking for and remain responsible for using the answer.

There is also an emotional adjustment. Oliver may initially feel less supported because Helen no longer supplies immediate reassurance whenever he doubts himself. Helen may feel less visibly useful because fewer documents arrive for her heroic corrections. Both need time to recognize the value of a relationship in which the mentor's contribution becomes less obvious. That is one of mentoring's awkward features: doing it well can eventually mean performing fewer of the activities that once made you feel successful.

Several weeks later, Oliver sends Helen a message about a proposed change to the retention initiative. The message contains his assessment, two viable options, the main uncertainty, and the decision he intends to recommend. He asks for her perspective on a possible consequence he has not encountered before. Helen reads it and realizes that she does not need to reorganize his analysis or write his conclusion. She offers one observation and suggests an appropriate source for the missing information. Oliver handles the rest.

The relationship has not become colder or less useful. It has become more demanding in the right places and less demanding in the wrong ones. Helen still contributes experience, but Oliver is learning to turn that experience into his own judgment. The presentation files are no longer joint productions disguised as his work. They are increasingly his decisions, supported when necessary by an experienced colleague. And somewhere in Helen's inbox, a small administrative miracle has occurred: the words "Can you just do a quick final check?" have finally stopped appearing quite so often.