Use one-to-ones to make career decisions
Bring a concrete development question to your manager, leave with a decision and owner, and keep routine project updates from consuming the whole meeting.
Use a development one-to-one to resolve one concrete question about expectations, opportunities, or support. Bring a recent example and a specific request, then record what was agreed, who will act, and when you will revisit it.
Instead of asking whether you are doing well, show a recent design decision and ask what you would need to handle independently next time. Then agree on one suitable task and who will review it.
“Everything is going well; keep doing what you are doing” is pleasant feedback. It does not tell you which responsibility to take next, what evidence is missing, or how your manager will help. A useful development conversation needs a question more specific than “How is my career going?”
Bring a question that needs a conversation
Separate project status from development. A short written update can explain what shipped and what is blocked. The conversation can then address an uncertain expectation, a difficult working relationship, or a development opportunity. Urgent problems should not wait for a recurring meeting merely to preserve the agenda.
Mary Abbajay’s Managing Up encourages a more deliberate working relationship with a manager. Her team’s public account of managing up includes prepared check-ins and adapting communication to working preferences. That supports asking how to work together; it does not make you responsible for compensating for every management failure.
Choose one question for the meeting. For example: “Which part of a small project should I own next to practise earlier technical judgement?” Or: “The feedback says I should communicate sooner. At which point in this recent task would you have wanted an update?” Those questions have possible answers you can act on.
Try the decision
A manager says a developer should take on more scope. What makes the one-to-one useful?
Neither person can tell what will change or when to review it.
Next step: Ask for one observable task and a decision owner.
This is an illustrative decision with stated assumptions. It cannot establish your employer’s policy or predict an individual career outcome.
Use a recent example to make expectations concrete
Consider an illustrative developer who wants to progress beyond implementing already-defined tasks. They bring a short options note they wrote, the decision it supported, and the point where a senior engineer had to intervene. They are not asking the manager to reconstruct months of work from memory.
The question becomes: “I compared the options, but I did not notice the dependency on another team until review. Is identifying those dependencies part of the independence you expect at the next level? What would a good example look like?”
The manager can now distinguish a skill gap from a lack of opportunity or unclear expectations. Perhaps the developer needs more practice. Perhaps they were never included in the conversation where the dependency was known. Those situations need different responses; “be more proactive” does not distinguish them.
Use the explanation of changing judgement and scope to frame the discussion, then ask how your own organisation defines the work. A public career ladder is a conversation aid, not your employer’s promotion policy.
Leave with an agreement, not encouragement alone
An agreement should name an action that somebody controls. In the example, the developer might draft the next bounded options note, while the manager arranges an early conversation with the affected team. A senior colleague agrees to review the assumptions before implementation begins.
Also agree what work makes room for the development task. If the opportunity is added on top of a full workload, its cost has not disappeared. Ask whether the task changes a delivery commitment or replaces something else. A learning opportunity without time or support can become an avoidable failure.
A simple closing is enough: “I will do this. You will arrange that. We will review this example after the task. Does that capture what we agreed?” A review date is useful when it is realistic; the exact cadence is less important than following through.
Document the agreement as a development step, not a promised promotion unless that promise was explicitly made by someone authorised to make it. The promotion packet can later collect the resulting evidence; it cannot substitute for the work or the organisation’s decision.
Handle vague answers and repeated cancellations
If the answer stays broad, ask for one recent example and one expected difference. If your manager does not know, ask who can clarify the expectation and when you can return to it. It is better to record an unresolved question than to invent a shared understanding.
If meetings are repeatedly cancelled, send the question and request a workable alternative. A written response or a shorter discussion may be enough for some issues. A sensitive concern may need a private conversation rather than a widely shared project thread.
Repeatedly unavailable support is information about the environment, not automatically a failure of your preparation. Use appropriate internal support channels where necessary. Do not turn “managing up” into a rule that the employee must quietly tolerate neglect, retaliation, or disrespect.
Keep a small record you will actually revisit
Keep the question, the example, the agreement, and the follow-up in an appropriately private work document. Avoid recording unnecessary personal information about other people. Confirm the arrangement with your manager and follow the organisation’s information-handling rules.
At the next discussion, begin with what happened. Did the task occur? Did the promised support arrive? What did the example show? That produces a sequence of useful decisions rather than a collection of encouraging conversations.
When the main obstacle is ambiguous feedback, use the feedback-to-practice method. When the opportunity is too large or poorly supported, define the stretch assignment’s boundaries before accepting it.