My Manager Does Not Know What I Do

You're sitting in your 1:1. Your manager asks how things are going. You say "good." They ask if you need anything. You say "nope." You talk about a sprint blocker for five minutes. The meeting ends. Neither of you has any more information than you started with.

Now multiply that by 26 weeks. When calibration arrives and your manager needs to present a compelling case for why you should be promoted, they have 26 weeks of "things are good" to work with. They can't describe your biggest win. They can't explain the technical complexity of the project you led. They can't name the cross-team collaboration you drove. Because you never told them.

This is the most common and most preventable reason engineers get passed over. Not bad performance. Not a bad manager. Just a manager who doesn't have the information they need to advocate for you.

Why your manager doesn't know

Before you decide your manager doesn't care, consider the structural reasons they can't keep track.

They're managing six to twelve other people. Each of those people has projects, blockers, career goals, and calibration cases of their own. Your manager physically cannot track the details of everyone's work at the level of depth required for a strong calibration pitch. Gallup research found that managers with more than eight direct reports show measurably lower engagement scores for their teams — and lower engagement correlates with less effective career development conversations.

They see outputs, not the work behind them. Your manager sees that the feature shipped. They don't see the three weeks you spent debugging the race condition, the design decisions you made about data modeling, or the cross-team negotiation that unblocked the integration. The visible part of your work is the tip. The calibration-relevant part is everything underneath.

They're optimizing for different things. While you're focused on code quality and technical execution, your manager is thinking about team velocity, headcount planning, stakeholder management, and quarterly OKRs. Your individual career trajectory is one of twelve things on their plate, and it's rarely the most urgent one.

Remote work made it worse. In-office, managers absorbed context passively — overhearing conversations, seeing whiteboard sketches, watching you debug live. Remote work eliminated all of that ambient information. Now they only know what's explicitly communicated. If you don't communicate, you're invisible.

What this costs you

When your manager can't describe your work, three things happen in calibration.

Your case is thin. Instead of specific wins with quantified impact, your manager presents a vague summary: "They're solid, they deliver, they're a good team player." That's not a promotion case. That's a description of someone who should stay at their current level.

You're vulnerable to challenge. In calibration, other managers push back on candidates they don't know. If your manager can't answer detailed questions about your contributions — "What specifically did they do on the migration?" — your case crumbles under even mild scrutiny.

Someone else gets the slot. Promotion slots are limited. When it's your case versus another engineer whose manager can rattle off three specific wins with numbers, you lose. Not because you're worse, but because your case was worse.

The irony is that the engineers who most need their manager to know their work — the quiet, heads-down builders — are the ones least likely to tell them.

How to fix it without becoming insufferable

You don't need to turn every 1:1 into a self-promotion session. You need a system that keeps your manager informed with minimal friction for both of you.

Send a weekly update

This is the single highest-leverage habit for managing up. Every Friday, spend five minutes writing a short update to your manager. Three sections:

• What I shipped/progressed — one or two bullet points on the most meaningful work
• What I'm focused on next week — signals your priorities without asking for permission
• Anything I need from you — blockers, decisions, or context you're missing

That's it. Five minutes of your time. Your manager reads it in 90 seconds. Over six months, they have 26 data points about your work. When calibration comes, they're not reconstructing your year from memory — they're pulling from a documented trail.

The weekly update isn't just a communication tool. It's the raw material your promotion case is built from.

Reframe your 1:1s

Stop treating your 1:1 as a status meeting. Your manager can get status from the weekly update, from standups, from Jira. The 1:1 is for things that only work in a conversation.

Talk about impact, not tasks. Not "I'm working on the billing refactor" but "The billing refactor is going to reduce failed transactions by about 20%, and I'm navigating a tricky dependency with the payments team to make it work."

Name your wins out loud. If you had a good week, say so. Not bragging — just reporting. "The monitoring dashboard I built went live last week. The SRE team is already using it for their weekly reviews. I think this is going to cut their triage time significantly."

Ask for their perspective. "From your seat, is there anything about my work or how I'm operating that I should adjust?" This creates a feedback loop that prevents surprises in review season.

Give them calibration ammunition

Two to three weeks before calibration, give your manager a short document with your strongest three to five wins. Not a full self-review. A cheat sheet. Each win should include the situation, what you did, and the result.

This isn't extra work — it's work you should already be doing for your self-review. You're just sharing it earlier so your manager has time to absorb it, ask questions, and build a case they can defend under pressure.

Make your cross-team work visible

Cross-team contributions are the ones most likely to be invisible to your manager. If you unblocked another team, led a cross-team design review, or drove an API integration across service boundaries, your manager probably doesn't know the details — because the stakeholders on the other side aren't reporting to them.

When you do cross-team work, tell your manager. Not as a brag. As a data point. "Hey, I wanted to flag that I spent most of this week working with the checkout team on the payment integration. The API contract we agreed on should unblock them for the next sprint."

What if you've already tried and your manager still doesn't get it?

Some managers are genuinely checked out. They don't read your updates. They speed through 1:1s. They can't describe your work even when you've explained it multiple times.

If that's your situation, you have three options:

Escalate the visibility. Use your skip-level 1:1, cross-team presentations, and internal documentation to make your work visible to people beyond your direct manager. If your manager's pitch is weak, having a second voice in calibration who knows your work changes the equation.

Document relentlessly. If your manager won't absorb the information verbally, make sure it exists in writing. Weekly updates, design docs, post-mortems — create a paper trail that's undeniable even if your manager doesn't engage with it proactively.

Have the direct conversation. "I want to make sure you have everything you need to represent my work in calibration. I've noticed that some of my contributions haven't come up in our conversations, and I want to fix that. Can we spend ten minutes going through my top wins so we're aligned?" That's not confrontational. That's collaborative.

If none of these work after a sustained effort, you may be dealing with a manager problem that no communication strategy can fix. But that's a different article for a different day.

---

Your manager isn't going to track your work for you. That's not a failure on their part — it's a structural reality of managing a team. CareerClimb's AI coach Summit helps you build the communication habits that keep your manager informed and your promotion case strong. Download CareerClimb and stop hoping your manager noticed.