One-on-one conversations with your manager represent a significant resource for professional advancement, tackling obstacles, and discovering new possibilities. Yet many technical professionals restrict these meetings to routine updates, missing substantial untapped potential.
The transformative value became apparent when discussing mentorship aspirations during a one-on-one led to co-leading a project with an intern to develop an internal tool for surfacing enterprise configuration details. This assignment provided hands-on technical leadership while enabling real-world mentoring—both experiences that pushed boundaries productively. The lesson: intentional one-on-ones can reveal pathways previously unrecognized.
Numerous engineers view one-on-ones as routine standups: conveying completed work, noting obstacles, and receiving general input. Though valuable, this approach underutilizes the format's capabilities. Instead, conceptualize these sessions as architectural reviews of your professional role—opportunities to identify challenges, refine processes, and establish alignment around future objectives.
Reframing your perception of what a one-on-one can accomplish
A thoughtfully designed one-on-one with your manager transcends a simple touchpoint; it becomes a mechanism for reshaping your professional environment and long-term trajectory. System design inherently requires examining constraints, interdependencies, and sustained viability. Professional development warrants identical rigor.
Begin by reconceptualizing these interactions: they are not progress reports. Your manager already monitors your code contributions, team velocity metrics, and planning materials. Dedicate this time instead to discussing what matters most—accomplishments delivered, value generated, and areas where friction exists.
Leverage this opportunity to validate choices and obtain necessary information. When considering alternative directions, avoid simply requesting authorization—structure the discussion around trade-offs:
Here are the pros and cons of refactoring this service now versus later. How does this align with our broader business goals?
Engage your manager as a decision-making interface: supply pertinent information, expose ambiguities, and collaborate toward a well-informed conclusion.
Use one-on-ones for career versioning (even before you're "ready")
One-on-one sessions provide an excellent venue for examining career development trajectory—regardless of whether advancement is currently being pursued. Rather than postponing these conversations until promotion cycles arrive, initiate dialogue early to establish understanding, purpose, and forward momentum progressively.
When more than one year remains before considering advancement:
- Where am I already meeting expectations?
- Where should I focus on strengthening my skills?
As the next level approaches or promotion consideration becomes imminent:
- What kind of work would demonstrate readiness for the next level?
- Are there specific opportunities I can take on to grow my scope or visibility?
Approaching growth as continuous refinement rather than a singular achievement enables steady progress and adjustment based on timely input.
A practical structure for these conversations involves the Three Circles of Impact:
- Individual Contributions – The direct value of your work.
- Collaboration – How you work with and support others across the team.
- Enabling Others – Mentorship, knowledge sharing, or improving systems and tooling for your peers.
Should you lack clarity on demonstrating influence across all dimensions, your one-on-one provides the ideal setting to investigate possibilities. The critical element involves surfacing aspirations early, enabling your manager to steer you toward assignments that expand capabilities and increase influence.
Directing your efforts according to these categories strengthens the visibility of your advancement readiness—and facilitates your manager's ability to champion your progression.
Your manager can't debug what they don't see
Managers lack comprehensive insight into your daily circumstances, making one-on-ones the appropriate forum for discussing persistent impediments and vague directives.
Consider a situation involving a latency problem under investigation. The endpoint's speed marginally exceeded the service level objective (SLO) threshold, and considerable effort had already gone into enhancement. During the conversation, the manager offered an alternative viewpoint:
Are we optimizing for the right thing? We control the SLO. If the extra latency is due to how the system is designed (and if users aren't impacted) maybe the right move is to revisit the threshold instead of squeezing more performance out of it.
That exchange alone prevented substantial wasted effort and completely reoriented the problem. Frequently, the resolution exists not within your implementation—but in how you're evaluating achievement.
Make your one-on-ones work for you
Your one-on-ones will deliver substantially greater returns—and generate meaningful advancement—when you approach them as occasions for deliberate thinking, not mere status checks. Restructuring these conversations around your priorities, your circumstances, and your professional trajectory positions you to advocate more effectively for yourself and your contributions.
Initiate thinking about advancement sooner than feels comfortable. Arrive organized. Bring examples of progress, areas requiring attention, and directions for development. Keep in mind: your manager cannot resolve what remains hidden, and cannot champion your aspirations without understanding them.
Should this approach feel unfamiliar, you're in good company. The Engineer's Survival Guide provided valuable perspective on reconsidering one-on-one dynamics.
Several concepts proved particularly valuable:
- Your manager isn't a mind reader.
- You can't expect guidance if you don't come with a direction.
- Your growth is a shared effort, but it starts with you.
The sooner you recognize one-on-ones as instruments for generating impact and fostering development, the greater the advantages you'll realize.
Source: GitHub Blog