A practical way to leave your next 1:1 with a clearer expectation, a useful opportunity, and something to revisit.

An engineer has a blank career map while a manager offers reassurance without direction

You finish your update, your manager says everything looks good, and there are still seventeen minutes left on the call.

So you ask about a company announcement. You discuss next quarter. Someone mentions their vacation, and the meeting ends pleasantly enough.

Later, you’re still wondering what you need to get better at, whether anyone notices the work you’re doing, and how to get a project that stretches you.

Honestly, a friendly conversation can be reassuring and still leave you completely unsure what to do next.

I don’t think the answer is another enormous list of clever questions to memorize. Nobody needs to interview their manager like a podcast guest every Tuesday.

For the next conversation, try bringing one real situation that needs clarification. Then work toward an expectation, an opportunity to act on it, and a time to check what happened.

Give the conversation something small enough to examine

Suppose you’re a backend engineer who has been fixing bugs and maintaining an internal API. You want more ownership, but the feedback so far is that you’re doing fine and should keep being proactive.

That sounds positive. It also leaves quite a lot of room for interpretation.

Does proactive mean noticing a dependency before it blocks a release? Proposing a smaller scope? Talking to the team that owns an unreliable integration? Volunteering for every unclaimed task until your calendar becomes a crime scene?

Those are different behaviors, with very different consequences.

Bring one recent example, such as a release that waited for another team’s API change. Explain what you noticed, when you raised it, and what you did. Then ask which part of your handling met expectations and which part could have been stronger.

This is a fictional example to practice with. In your actual meeting, use an event both of you can inspect rather than borrowing someone else’s story.

Move from a label to an observable behavior

Imagine the manager explains that the dependency became visible too late for the team to adjust its plan.

Now there is something useful to discuss. You can check whether that account matches what happened and ask what earlier action was realistically available.

Perhaps the desired behavior is to identify the dependency during planning, bring two possible responses, and ask for a decision before work stalls. That is much more actionable than trying to become a generally more proactive person by Thursday.

A vague request to be proactive becomes specific actions around a project dependency

I prefer four connected questions when feedback feels slippery.

  • Ask which recent situation illustrates the feedback, so you are discussing the same event.
  • Ask what a stronger response would have looked like at your level and within your authority.
  • Identify an upcoming piece of work where you can try that response.
  • Agree on when you will review it and what evidence will make the discussion useful.

You do not have to ask these as a rapid-fire checklist. Follow the conversation, especially if the example reveals missing information or a genuine disagreement.

If you’re also preparing for interviews, use a real instance of this process to rehearse a feedback-and-conflict question. Explain the feedback, how you checked it, what you changed, and what happened afterward. If the outcome is still unknown, say so rather than inventing a tidy ending.

Four connected steps turn feedback into an observation, an expectation, an opportunity, and a review

Ask for the opportunity, not just the instruction

Sometimes you understand the feedback perfectly well. What you lack is a place to act on it.

If you are expected to demonstrate project ownership but only receive isolated tickets, another reminder to show leadership does not resolve the mismatch.

For our backend example, propose a bounded assignment. You could own the dependency plan for the next API change, coordinate the review with the partner team, and report the unresolved decisions before implementation starts.

Then discuss the support that makes that assignment possible. Who introduces you to the partner-team owner? Which decisions can you make? Who steps in when two teams disagree on priority?

Also ask what existing work moves out of scope. Development opportunities should not quietly become an extra job squeezed into the same week.

Your manager might suggest a different assignment or explain that the team has no suitable work right now. Either answer gives you more information than another general encouragement to take initiative.

Make room for feedback you disagree with

Specific feedback is easier to examine, but specificity does not automatically make it correct.

Suppose you raised the dependency during planning, documented the risk, and were told to proceed anyway. Accepting the entire delay as your failure would erase an important part of the situation.

Bring the timeline calmly and separate what you controlled from what required another person’s decision. Ask whether the concern is the timing of your warning, its clarity, the follow-through, or something else.

You might discover that your manager never saw the earlier note. You might also discover that you reported the risk but did not make the required decision clear. Those findings call for different changes.

The aim is to understand the expectation well enough to act on it, while keeping the account of what happened accurate. Agreement achieved by deleting inconvenient facts is not especially useful feedback.

Leave a short note that both of you recognize

Before ending the meeting, summarize the next step and give your manager a chance to correct your understanding.

For the fictional dependency example, the note can be very small.

  • I will draft the dependency plan before implementation starts, including two options and the decision we need.
  • My manager will confirm the partner-team owner and help resolve the priority conflict if necessary.
  • We will revisit the plan at our next 1:1 and inspect whether the dependencies and decision owners are clear.
  • We still need to decide which existing task moves out of scope.

A shared note records the engineer’s action, the manager’s action, the review point, and an unresolved scope decision

Keep this in an appropriate shared work document rather than relying on memory. Record a proposed agreement as proposed until it has actually been agreed.

GitLab’s public 1:1 guidance offers a useful reference here. It recommends a consistent agenda that both people contribute to, and suggests adding topics in advance so there is time to think. That is one organization’s approach, not a requirement that every team copy its meeting cadence.

For your own agenda, a few sentences about the situation and the help you need can be enough. You are preparing a conversation, not submitting a thesis.

Revisit the evidence before chasing the next vague goal

At the next meeting, return to the assignment. Show what you tried and ask what the work demonstrates now.

Maybe the dependency plan made the decision obvious, but the partner team still could not commit. Maybe your options were useful, but you missed an important constraint. Either result can support a better next discussion than merely reporting that you tried harder.

Keep performance, development, and promotion as separate questions. Useful growth work does not automatically establish readiness for another level, and readiness does not automatically create an available promotion.

If promotion is the goal, ask about the actual criteria, the evidence still missing, and the decision process. A scoped assignment can contribute evidence without becoming a promise about the outcome.

Notice when the missing piece is outside your control

There are limits to what a well-prepared agenda can accomplish.

Your manager may not have authority to offer different work. Priorities may keep changing. Feedback may remain vague even after you ask for examples, or agreed support may repeatedly fail to arrive.

Record the unresolved issue and discuss the options available in your organization. Depending on the situation, that could mean a different assignment, another source of technical feedback, a career conversation through the normal management channels, or considering other teams.

Different gaps require different responses, and a clearer conversation cannot guarantee an opportunity or promotion

This is not a test of whether you can phrase the perfect question. Managers share responsibility for clear expectations and useful feedback, and an engineer cannot manufacture opportunities that the organization will not provide.

Nor does every 1:1 need a measurable deliverable. Trust, workload concerns, and an honest conversation about how you’re doing belong there too.

But when you arrive wanting direction, it is reasonable to leave with more than reassurance. Bring one real situation, find the expectation behind the label, and agree on a next step you can both revisit.

You don’t need to transform the entire relationship in one meeting. A clearer conversation about one piece of work is a perfectly worthwhile place to start.

~ Emily