[AI experiment] Managing Up Means Managing Communications Debt

[benbalter]

⚠️ AI drafting experiment — a draft, not for publication as-is.

This post was produced by an experiment: mining 16 years of this blog's archive with Azure AI Foundry, drafting the highest-potential ideas in my voice, and gating each draft against this repo's own anti-AI-pattern Vale style. It's committed with published: false and opened as a draft PR for review and voice comparison — not to merge blind.

Model in the diff: gpt-5.4. A gpt-4.1 draft of the same idea is included below so you can A/B the voice.

Before this could ship, a human must

• Replace every [BRACKETED] placeholder with a real number or lived anecdote.
• Verify or delete any specific statistic — some figures were model-invented and are not real.
• Edit for voice; several drafts in this batch share a "problem → playbook → objection → start small" spine — vary it.
• Fix internal links (e.g. communications debt currently points at leaders-show-their-work).

🅱️ gpt-4.1 A/B variant — same idea, different model (click to expand)

Title: Managing Up Means Managing Communications Debt
Description: If your boss’s boss doesn’t see your best work, you’re quietly sabotaging your career. Here’s how to manage up by showing your work—and kill communications debt for good.

---

Picture this: Promotion season rolls around, and leadership is reviewing the usual stacks of nominations, impact statements, and team summaries. Out of [NUMBER: "30 engineers"], more than half who were passed over had zero visible evidence of meaningful wins in the last year. Not because they weren’t doing real work—in fact, I can name three off the top of my head who were shipping critical features, leading incident response, and unblocking others daily. The problem? Their contributions were invisible to anyone not in their immediate orbit.

You’ve probably heard the complaint: “My skip-levels never see what I do—until it’s too late.” Here’s the uncomfortable truth: If that’s you, it’s not just happenstance. It’s a symptom of unmanaged communications debt, and it’s quietly compounding against you, month after month.

Why your wins go unseen

It’s convenient to blame organizational structure. Management layers, time zones, bigger teams—all friction. But in practice, most overlooked contributions die in a black hole of DMs, hallway chats, and meetings where only three people are present. If your wins exist only in the memories of your immediate team, skip-levels and cross-functional partners are never going to piece together your impact when it counts. They need written, discoverable proof—URLs, not whispers.

The result? Your effort is spent, but the receipts are missing. And when the question comes—“Who made this happen?”—even the best boss will default to what’s documented.

Communications debt is career debt

Here’s where the engineering mindset pays off: Communications debt is just technical debt with a different suffix. Every undocumented win, every solved problem that never leaves your Slack DM, is a liability. Sure, you can pay it off later—when you’re frantically assembling a brag doc at review time, or when your boss asks for a retroactive promo packet. But like all debt, interest accrues. The more you defer, the harder it is to reconstruct, and the less credible it sounds. “Did that really happen? Was it really that impactful? Where’s the artifact?”

I’ve seen engineers do hero-level work for years, then get leapfrogged by someone who simply did a better job of working out loud. Caremad is great—doing the work is half the job. The other half is showing your work in a way that leadership can see, evaluate, and point to later.

This isn’t about performative self-promotion or spamming your team with status updates. It’s about building an accessible, auditable trail that reduces communications debt—not just for your own sanity, but for your boss (and their boss) who can’t be everywhere at once.

The dangers of a missing narrative

If you don’t write your own professional story, someone else will, and odds are good that story will be incomplete at best. Managers are juggling dozens of reports. Skip-levels know you as an abstraction, or worse, not at all. When impact is measured, recency bias and visibility bias win. That means last-minute fire drills—often more visible—get more credit than long-term foundational work.

The only way around this: Equip your management chain with clear, linkable proof of what you’ve done, why it matters, and how you did it. Don’t assume they know. Don’t assume your boss will connect all the dots. Make it impossible to miss.

A playbook for managing up asynchronously

Here’s what actually works. No magic. No self-aggrandizing. Just a repeatable system that makes your work legible up the chain:

1. Maintain a brag doc—continuously.

   • Start a running doc (template, your tool of choice) visible to your manager at all times.
   • Add links—not just bulleted claims. Pull requests, issues, RFC comments, demos, design docs.
   • Tag others where appropriate. Evidence of collaboration credits everyone.
   • Review it monthly, not just at review time. Set a recurring calendar reminder if you need to.

2. Send a weekly or biweekly digest.

   • Choose a cadence that’s sustainable. Friday afternoon works because it closes the context loop for the week.
   • What to include: Major work completed, decisions made, blockers resolved, open questions, and anything you want to highlight for visibility (positive or negative).
   • Keep it concise—bullet points, with URLs and @mentions as receipts.
   • Optional: For distributed or async teams, post in a shared, persistent channel (not just a 1:1 DM), so others can see and chime in.

3. Show your work in public forums.

   • Default to open. Use issues, pull requests, and team threads whenever possible, even if the audience feels small.
   • Decisions, failures, weird edge cases—share them in a place where they’re searchable and referenceable.
   • If you accidentally do something important in a DM or meeting, take 60 seconds to copy/paste the key outcome to the relevant channel. It’s annoying at first. It becomes muscle memory.

4. Close the loop on wins and problems.

   • When you land something, circle back to say what happened, what’s next, and who was involved. “Shipped X; results so far are Y; next step is Z.”
   • When things break, document the learning and the fix, not just the failure. This buys you credibility and a permanent point of reference for the next person in your shoes.
   • Reflection beats perfection. It’s fine if you didn’t do everything right—just leave a trail.

5. Level up your manager.

   • Assume your boss is juggling [NUMBER: ex: “12 reports and three cross-team projects”]. They want to make you look good, but you have to give them the ammunition. When you send your digest or update your brag doc, call out anything you want elevated upward (“I think this is promo-worthy”; “Would love for this to be shared at the next all-hands”).
   • Don’t wait for your manager to ask. Make it habitual for them to reference your work. This is how you get your wins re-broadcasted in rooms you never enter.

What doesn’t work

• Relying on annual reviews to tell your story. By then, the trail is cold and context is lost.
• Thinking your boss or manager is tracking everything for you. They’re not—they’re busy and human.
• “Heads-down” as a brand. Great for focus, deadly for visibility. Quiet excellence is only a career strategy if someone’s writing your highlight reel for you.
• Waiting for invitations to share. If you don’t proactively surface your work, your peers who do will be the ones remembered first.

Counterpoint: Isn’t this just self-promotion?

There’s a fine line between showing your work and spamming the channel. Nobody likes the person who turns every standup into a TED talk about their own brilliance. But there’s a spectrum: At one end is the loud, performative self-promoter. At the other is the silent workhorse, quietly racking up wins nobody ever sees. The sweet spot is visible, linked, and referenceable work—so your boss, skip-levels, and future you can point to it without eye rolls.

If you’re worried about overdoing it, ask a trusted peer or manager for feedback. In my experience, almost nobody does too much. Most of us do far too little.

Leaders show their work—so should you

If you want to see what this looks like in action, watch any high-functioning open source project. Leaders show their work by default, not just for posterity, but because it lowers communications debt across the entire system. The next contributor, the next manager, even your future self, benefits from that permanent, transparent trail.

Engineering organizations talk a big game about transparency, but most still operate in the shadows. By building your own async system for managing up, you kill communications debt before it compounds, and you transfer value to your team, your leadership, and your future career.

Skip-levels don’t see what you do in the moment. But with the right system, they will when it counts. Build your receipts early—and you’ll never scramble for evidence again.

---

🤖 AI experiment via Claude Code · drafted on 2026-08-01 with Azure AI Foundry (gpt-5.4 primary, gpt-4.1 A/B) · linted against the repo's AIPatterns Vale gate.