Your manager has probably forgotten what you did last month

Your manager is going to forget

Your manager is going to forget something you did this week. Probably more than one thing.

They're not checked out, and this doesn't mean they don't care about your career. They manage several people, they're in back-to-back meetings, and they carry everything else that comes with being a person. Groceries to buy, a flight to figure out, a conversation they're still processing from last night. By the time your performance review arrives, the work you did in the first half of the year might as well not have happened.

This is the problem the weekly update solves. Not communication as a general virtue. Not relationship-building as a feel-good exercise. It solves the memory problem: theirs and yours.

Why this isn't a manager problem

It's tempting to frame this as a management failure. Your manager should be paying attention. Their job is to know what you're doing.

But think about what their day actually looks like. Managing several people while sitting in five hours of meetings and fielding crises they didn't plan for. They go home and none of it stops. The job is one layer on top of a full life, same as yours, except with more stakeholders and less control over their schedule. You are not the only layer.

This doesn't mean you should wait for your manager to fix it. It means the belief that good work will be noticed automatically is a bet you're making against how organizations actually function.

The gap between what you've done and what your manager can articulate when your name comes up in a promotion conversation is the thing that costs people careers. It's not usually a skills gap. It's a visibility gap. And weekly updates are one of the simplest tools for closing it. For more on why visibility matters for promotion, see how to ask for a promotion as a software engineer.

What the research shows

A 2018 survey by Interact and Harris found that 63% of managers fail to recognize their employees' achievements. A 2025 Predictive Index study of 1,000 U.S. workers found that 46% said their boss only somewhat or rarely understands their work, and 44% had been passed over for a raise or promotion because their manager didn't fully understand their contributions.

The problem runs in both directions. A Perceptyx State of Employee Listening survey found that 50% of managers believe they frequently initiate career conversations with their reports. Only 21% of employees agreed.

What these numbers describe isn't a bad-manager problem. It's a structural recognition gap that's common across organizations of every size. The distance between what managers think they know about their reports and what employees actually experience is wide, and it's consistent. Expecting your manager to bridge it unassisted is optimistic.

The document your manager needs in that room

The weekly update isn't about being a good communicator. It's about creating a documented record before the quarter ends and everyone forgets.

Think of it as building the file your manager needs when they're in that room without you. Promotion conversations happen without you present. Your manager stands in front of their peers and defends why you deserve the next level. They say what they know. They say what they remember. And they say it with the specificity your updates gave them, or they have to improvise.

Engineers who advance faster aren't always the strongest engineers. They're the ones whose managers can explain what they do and why it matters.

If self-promotion at work still feels uncomfortable, think of it this way: you're not promoting yourself. You're giving your manager the material they need to advocate for you. They want to advocate for you. Make it easier.

What to actually send

The format matters less than the frequency. Here's one that works.

The format

Three bullets, sent Friday afternoon:

• What you shipped or completed this week
• What you unblocked, for yourself or for others
• What you're focused on next week

Keep it under 150 words. Send it wherever your manager actually reads — Slack DM, short email, whatever your team uses. No preamble, no explanation for why you're sending it. Just send it.

The first time will feel slightly awkward. Send it anyway. If your manager replies, great. If they don't, that's fine too. The record exists either way.

The consistency that compounds

Do this for eight consecutive Fridays and you'll have a paper trail covering your last two months. Start twelve weeks before your review cycle and your manager has something concrete to work from during calibration. For a deeper look at what makes these messages effective beyond just sending them, how to write weekly updates that get read covers the craft behind the format.

What this looks like when it works

Without the update

Picture an engineer who resolved a production outage on the payments service in January. Real impact. She fixed it overnight, the team moved on. Nobody wrote it down. By October, her manager remembered the incident happened but not the specifics: who led it, what the actual impact was, whether it was documented afterward.

With the update

Her peer on the same team had sent a weekly note on January 14th:

"Resolved payments service outage, $40K revenue restored, root cause documented for on-call runbook."

During calibration, her manager read it directly from that message.

One bullet. Written in three minutes on a Friday afternoon. That's the difference between your manager saying "she did strong work this year" and "she resolved the January payments outage, recovered $40K in revenue, and documented it so the team doesn't hit it again."

Key takeaways

• A 2025 Predictive Index study found 44% of workers have been passed over because their manager didn't understand their contributions. The visibility gap is common, not exceptional
• Weekly updates aren't a communication habit; they're a lobbying document your manager pulls from when advocating for you in calibration
• Three bullets, every Friday: what you shipped, what you unblocked, what's next