A mentee wants your support but doesn't know what to focus on. Their current work is going reasonably well. They don't arrive with a specific question, and asking "What are your goals?" gives you another version of "I'm not sure." How do you help without choosing a direction for them?
Start by making exploration smaller than a career plan. A useful development focus can come from something they're curious about, a part of work that feels harder than it needs to, or an opportunity they haven't had enough context to consider. You're helping them notice possibilities and test whether one matters to them.
That's different from persuading an engineer who has already said they don't want additional responsibility. Here, the person wants support. The uncertainty is about direction, not whether you have permission to impose one.
Make Room for an Unclear Focus
"I don't know" isn't a complete picture of someone's interest. They might not know what's possible, have trouble naming their strengths, or assume that a development goal must be large enough to sound impressive.
You can make the conversation easier by removing that expectation. They don't need to arrive with a title change, a grand technical specialization, or a detailed destination. Something like "I'd like to understand these design discussions better" gives you a useful place to begin.
Direction can take time to become clear through working together. That doesn't guarantee you'll discover a compelling goal, but it does argue against treating a hesitant first answer as a final verdict.
A few conversational openings might help:
- "Which part of your work would you like to understand better?"
- "What has been interesting lately, even if you don't know where it leads?"
- "Is there something you'd like to feel more comfortable doing?"
- "Would examples of possible directions make this easier to talk about?"
Use these as invitations, not required answers. If none connects, let the person explain how they think about choosing a focus instead of escalating into a longer questionnaire.
It's worth clarifying why you're meeting, too. Did they ask for advice about a particular uncertainty? Did someone suggest that you could help them explore? An unexplained mentoring assignment can leave both people trying to perform a relationship without understanding its purpose.
Keep that clarification narrow. You aren't building a complete workplace mentoring program here. You're establishing enough shared understanding to explore a useful focus with this person.
Find a Focus in Ordinary Work
When abstract goals don't produce much, recent work gives the conversation something concrete. Ask about an experience the mentee chooses to discuss. It doesn't have to be a dramatic failure or a major achievement.
Suppose, hypothetically, an engineer completes their implementation work comfortably but feels lost when several design options are debated. "Learn architecture" is one possible label. It's also broad enough to mean almost anything.
Explore what was difficult. Did they lack system context? Did they understand each option but struggle to compare tradeoffs? Were they unsure how to ask a question during the discussion? Those answers suggest different kinds of support.
You can examine ordinary experiences through a few useful lenses:
| What the mentee notices | A possible direction to explore | What still needs clarification |
|---|---|---|
| A recurring source of confusion | Understand that part of the work more deeply | Is the issue missing information or an unfamiliar skill? |
| An activity they enjoy | Try a more involved version of it | Do they enjoy the activity itself or the surrounding circumstances? |
| A task they avoid despite interest | Practice a specific part with support | What makes the first attempt difficult? |
| Work they rarely get to see | Observe or discuss an example | Would more context actually make it appealing? |
These aren't diagnoses. The mentee's explanation matters more than the focus you initially have in mind.
Don't treat friction as proof of underperformance. A capable engineer can want more fluency in something they're already handling adequately. They can also be interested in a topic that has little connection to their current difficulties.
Similarly, enjoyment doesn't create an obligation to specialize. They might like explaining one technical decision without wanting to become the person who leads every discussion. Explore the difference before translating an interest into a larger commitment.
Listening carefully before supplying your interpretation helps keep the direction grounded in what the person actually said. You can offer a hypothesis, but give them room to correct it.
Offer Possibilities Without Assigning a Destination
A mentor usually sees possibilities the mentee hasn't considered. That's useful. The risk is treating your visibility as evidence that you should make the choice.
Offer a small selection based on the conversation, and explain why each might fit. "You mentioned enjoying the discussion about failure cases. We could look at how someone identifies those cases, or we could work on explaining the tradeoffs you already see." That gives the person something concrete to react to.
Useful possibilities might include:
- Understanding a system area they're curious about.
- Explaining a technical decision more clearly.
- Comparing options before starting an implementation.
- Learning how another engineer approaches an unfamiliar problem.
- Practicing a task they want to attempt but haven't had support for.
This isn't a required menu. If no possible focus is interesting, don't keep presenting the same options with more enthusiastic wording.
You should adapt support to the individual rather than apply the same plan. Similar titles or assignments don't establish that two engineers need the same focus. Their interests, experience, and response to the conversation can differ.
Make your own preferences visible when necessary. "This is an area I enjoy, but that doesn't make it the right direction for you" is more honest than presenting your favorite topic as the obvious answer.
Also distinguish your expertise from the person's interest. You might be able to support communication well but know little about the technical area they want to explore. That doesn't invalidate the focus. It means you should be clear about what you can offer and where another perspective would be useful.
The broader soft skills used in engineering work can provide context for a communication-related interest. But linking a resource isn't the same as choosing the direction. Let the mentee decide whether that subject matches their question.
Turn a Broad Interest Into Something They Can Explore
An initial interest often needs a little definition before either of you knows how to support it. "I want to be better at design" is understandable. It doesn't yet tell you what the person wants to experience differently.
Ask what a useful change might look like in ordinary work. Perhaps they want to follow a discussion without losing the thread. Perhaps they want to explain why one option fits the constraints. Those are related, but they aren't the same focus.
Consider a hypothetical engineer who says they're interested in communicating technical decisions. You might suggest that they explain one decision from a task they already understand, then discuss which parts were difficult to make clear. That lets both of you learn more without assigning them ownership of a large project.
A manageable exploratory activity has a few characteristics:
- The mentee understands why it connects to their interest.
- It's compatible with their actual work and available support.
- The result can inform the next conversation.
- They can decide it wasn't useful without pretending the interest was never real.
Avoid making the activity larger simply to make it sound like development. A new responsibility might be appropriate, but observation, explanation, and practice can also reveal whether the direction is meaningful.
Discuss the support they want. Do they want to try independently and talk afterward? Would seeing an example first make it accessible? Would working through a small part together reduce uncertainty? Choosing a focus and choosing the method are separate decisions.
If the activity depends on workplace access or priorities, don't promise something you can't authorize. A mentor can offer advice without being the person's manager. Understanding the engineering manager's role helps distinguish those responsibilities.
The point isn't to produce a perfect goal statement. It's to make the interest specific enough that an experience can teach the mentee something about the direction.
Check Whether the Focus Is Actually Theirs
A mentee can agree with a suggestion because it sounds reasonable, not because it matters to them. You don't need to interrogate that agreement, but you should make room for an honest reaction.
Ask what appeals to them and what doesn't. If they can explain the interest in their own terms, you have a better starting point than a polite "sure." If they're uncertain, that answer is useful too.
Imagine a hypothetical mentee agreeing to practice presenting a design. As you discuss it, they explain that presenting isn't the difficult part. They want to understand how the design was chosen. Your proposed exercise was close enough to sound relevant, but it missed the actual focus.
Changing the focus there isn't a failure. It's the exploration doing its job.
You might distinguish three reactions:
| Reaction | How to respond |
|---|---|
| "That connects to something I want to understand" | Explore what support would make it useful |
| "Maybe, but I'm not sure what it involves" | Provide context or an example before asking for commitment |
| "I don't think that's what I'm interested in" | Accept the correction and look elsewhere |
Be careful with "This would be good for you." It can shut down a useful distinction between an opportunity and an obligation. A focus that matters to the mentor but not the mentee may be hard to sustain.
If there are existing work expectations that need attention, identify them plainly rather than disguising them as optional exploration. That is a separate conversation from choosing among voluntary directions.
The mentee can also use their own one-on-one topics to clarify whether a work-related opportunity fits their situation. You don't need to take ownership of that conversation or require a report of everything they discuss.
Revisit the Focus Without Turning It Into a Test
After the person tries something, ask what it revealed. Don't only ask whether they completed the activity. Completion might tell you little about whether the direction is useful.
They may discover that they liked the focus but not the proposed method. They may find that the subject was interesting in theory and less appealing in practice. Or they may realize that a different question is more important.
Useful observations include what felt interesting, what remained unclear, and whether they'd like another experience in that direction. These aren't mandatory reflections to submit. They're ways to turn an attempt into information.
You might learn, hypothetically, that an engineer enjoyed comparing design options but disliked preparing a presentation. The next focus doesn't have to be "overcome dislike of presenting." You can first understand whether the presentation was incidental to the interest you were exploring.
Likewise, don't infer lack of commitment from one activity that didn't happen. Check what got in the way. The support may have been unavailable, the work may have changed, or the activity may have been poorly chosen. Those explanations deserve consideration before you decide the relationship has no purpose.
At the same time, exploration can't depend indefinitely on you generating every idea and doing all the follow-through. Over time, the mentee needs a role in the effort. That isn't a demand for equal effort from the first conversation. It's a boundary against carrying the direction alone forever.
If the arrangement isn't useful, name that gently and specifically. "We've considered several possibilities, but none seems worth pursuing to you right now. Would it make sense to pause?" respects both people's effort without calling uncertainty a character flaw.
Ongoing one-on-one conversations can provide space to revisit interests where the relationship is managerial. They don't require every meeting to produce a new development target.
Frequently Asked Questions About Choosing a Development Focus
Does a mentee need a focus before the first conversation?
No. If they want support but can't identify a direction, exploration can be part of the mentoring. Start with experiences, interests, or questions they can describe. Don't make a polished goal the price of entry. Over time, look for participation in discovering what would make the support useful.
Should I suggest a focus when they have no ideas?
Yes, provided your suggestion is an option rather than an assignment. Connect it to something they said, explain what exploring it might involve, and let them disagree. A concrete example can help someone recognize an interest. It shouldn't override their answer when the example doesn't fit.
What if the mentee is already doing good work?
Good current performance doesn't settle whether there's something they'd enjoy understanding or practicing. Explore what they want more fluency in or what they haven't had a chance to try. Don't invent a deficiency to justify mentoring, and don't assume productive engineers must want a larger role.
How narrow should the development focus be?
Narrow enough that the person can understand what they want to explore and you can offer relevant support. "Understand why this kind of design decision is made" is easier to investigate than "be better at everything technical." It can broaden later if the experience reveals a meaningful connection.
What if they change their mind after trying something?
Treat the change as information. Ask what the experience clarified: the topic, the activity, the support, or the timing. You don't have to restart the entire relationship or persuade them to finish a direction they no longer find useful. Exploration has value when it helps someone make a better-informed choice.
When should I stop trying to find a focus?
Not after one uncertain answer. Give the relationship room to establish trust and expose possibilities. But if continued conversations depend entirely on your enthusiasm and the mentee doesn't want to pursue any direction, acknowledge that limit. Pausing support can be more honest than maintaining a plan neither person finds useful.
A Focus Can Emerge From Exploration
Helping someone choose a development focus is less about delivering the right destination and more about making possibilities understandable. Start with what they notice in their work, offer relevant options, and help them try something that reveals whether an interest is real.
Leave room for uncertainty and revision. The person doesn't need a complete career plan to benefit from support. They do need a meaningful voice in the direction, and eventually a role in the effort to explore it.