Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / Why Your Best Work Goes Unnoticed
Transcript
- Lucas: Let’s talk about the most dangerous trap in modern corporate life: being too good at what you do, and doing it so quietly that nobody notices. We’ve covered biases like halo effect and recency bias before, but there is a structural issue that has nothing to do with perception errors and everything to do with volume. If you are the person who fixes the server crash at two in the morning, then goes back to sleep, you have just committed career suicide. Luna: Right, because the damage was avoided, not created, so there is no dramatic story to tell. You saved the company money, but you didn’t generate the noise that gets remembered during quarterly reviews. Lucas: Exactly. And this isn’t just about introverts versus extroverts. I’m talking about a specific type of professional competence where the work itself is so seamless, so invisible, that it vanishes from the narrative. Let’s look at a concrete example from a large cloud infrastructure provider last year. There was a principal engineer named David who spent six months refactoring their deployment pipeline. He reduced build times by forty percent and eliminated three categories of security vulnerabilities. Luna: That sounds like a massive win on paper. Why didn’t he get promoted? Lucas: Because David never wrote a memo about it. He never presented a slide deck to the VP of Engineering. He just pushed the code, updated the documentation, and moved on to the next ticket. When promotion season came around, his manager couldn’t articulate his impact in words that fit the leadership competency model. David’s work was real, but it was silent. And in a hierarchy that runs on reported metrics and visible narratives, silence is interpreted as absence. Luna: So the system rewards the storyteller, not necessarily the builder? That feels incredibly unfair to anyone who finds satisfaction in the craft itself. Lucas: It is unfair, but it’s also predictable. The thing is, we often mistake 'quietness' for humility. We think if the work speaks for itself, it will be heard. But data shows that unreported achievements have a near-zero correlation with promotion velocity. In fact, there is research suggesting that employees who don’t actively broadcast their contributions are perceived as less engaged, simply because engagement is usually measured by participation in meetings and discussions. Luna: So you’re saying that by staying out of the spotlight to avoid office politics drama, you actually guarantee you’ll be left behind in the lineup? Lucas: Precisely. You are paying an invisible tax on your own competence. I call this the 'Silent Contributor Penalty.' It’s not that your boss hates you. It’s that your boss is overwhelmed, managing a matrix of projects, and they rely on signals. If you aren’t sending clear, verbal signals about your value, they assume you are either content with your current role or struggling to find direction. Both assumptions kill momentum. Luna: But doesn’t constantly talking about your work feel like bragging? Most people I know would cringe at having to narrate their daily tasks. Lucas: That’s the friction point. We confuse self-promotion with arrogance. There is a huge difference between saying 'I am the best coder here' and saying 'I designed a solution that saved the team twenty hours a week.' One is ego; the other is evidence. The problem is that most professionals are never trained in the second format. They write code, they close deals, they fix bugs, and they wait for someone to ask, 'What did you do?' The answer should already be ready. Luna: So the skill isn’t just doing the work anymore. It’s packaging the work. Is that something companies are getting better at teaching? Lucas: Not really. Most training focuses on technical skills or management theory. Very few programs teach 'impact translation.' How do you take a complex, quiet achievement and translate it into a language that executives care about? Executives care about risk mitigation, cost reduction, speed, and revenue. If your work touches any of those four pillars, you need a one-sentence summary that highlights which pillar you hit. Luna: Let’s test that. Take our engineer David again. He reduced build times by forty percent. How does he translate that for a VP who cares about revenue? Lucas: He stops talking about build times. He starts talking about developer velocity. His pitch becomes: 'By optimizing the deployment pipeline, we freed up twelve hundred engineering hours per quarter, which allowed us to ship features twice as fast as last year.' Suddenly, it’s not about code quality. It’s about product speed. That is a revenue driver. That is a promotion argument. Luna: Okay, that makes sense. It’s reframing the output from a technical metric to a business outcome. But how do you actually deliver that message without feeling like you’re interrupting every conversation? Lucas: You don’t interrupt. You create artifacts. The first tactic is the 'Friday Five.' Every Friday afternoon, spend ten minutes writing down five things you accomplished that week. Not your todo list, but your actual impacts. Then, once a month, compile these into a brief email to your manager and key stakeholders. Subject line: 'Monthly Impact Update.' It takes five minutes to write, and it creates a permanent record of your value that exists outside of memory. Luna: A monthly email. That sounds manageable. Does it work for remote teams where you don’t see your boss face to face? Lucas: It works even better remotely. In an office, you might bump into someone in the kitchen and mention a win. Remotely, you disappear digitally unless you make a deliberate effort to appear. Those emails become your digital footprint. When performance review time comes, you don’t have to guess what you did. You just attach the thread. It removes the burden of recall from your manager, which they will love you for. Luna: I like that. It shifts the burden of proof from memory to documentation. What’s the second tactic? Because I feel like some people hate writing emails too. Lucas: The second tactic is 'pre-meeting alignment.' Before you walk into a status update or a planning session, send a two-bullet summary of what you plan to discuss. Bullet one: what you achieved. Bullet two: what you need help with. This forces you to articulate your value before the conversation starts. It also ensures that if the meeting gets derailed, your contribution is still on the record in the chat history or email thread. Luna: So you’re essentially creating a paper trail of your competence. Is that considered aggressive in typical corporate culture? Lucas: Only if your culture is toxic. In a healthy culture, clarity is appreciated. Managers are terrified of surprises, both good and bad. By providing clear updates, you reduce their anxiety. You become a low-maintenance, high-output asset. That is the sweet spot. You want to be the person who makes their job easier, not harder. And documenting your wins makes their job easier when they have to justify your raise. Luna: That’s a strong angle. Making your manager’s life easier by making your value undeniable. What’s the third tactic? Because I feel like even with emails, sometimes you still get overlooked if you’re not in the room. Lucas: The third tactic is 'strategic volunteering.' Instead of waiting for tasks to be assigned, identify gaps in your team’s visibility. Did a project fail recently? Volunteer to lead the post-mortem. Did a client complain? Volunteer to draft the response framework. These are moments where you can step into the light deliberately. You are choosing to be seen in a context where your expertise is required, not just assumed. Luna: So you’re manufacturing opportunities for visibility rather than hoping they fall into your lap. That requires a lot more initiative than just doing your core job description. Lucas: It does. And that is why most people don’t do it. They view their job description as a ceiling, not a floor. But career growth happens in the spaces between the formal responsibilities. The Silent Contributor Penalty only applies if you stay within the lines. If you start drawing new lines, you change the game entirely. Luna: I wonder if this applies differently across industries. In creative fields, maybe the work itself is the portfolio. Does this advice hold up for designers or writers? Lucas: It holds up, but the mechanism is different. For creatives, the 'artifact' is the portfolio link, not the email. But the principle remains: you must curate and present your work. A designer who sends great files to developers but never explains the strategic reasoning behind their choices is just another pair of hands. A designer who presents the user research data and the business rationale is a partner. The medium changes, the strategy doesn’t. Luna: So it’s about explaining the 'why,' not just delivering the 'what.' That seems like a fundamental shift in mindset for many technical roles. Lucas: Absolutely. It’s moving from execution to ownership. When you explain the why, you demonstrate strategic thinking. And strategic thinking is the primary driver of promotions beyond the mid-level. Junior staff execute. Senior staff strategize. If you only execute, you will plateau at the mid-level, no matter how brilliant your code or designs are. Luna: That’s a hard truth. Plateauing because you were too good at the basics. I can see why so many talented people get frustrated and leave. They realize the game isn’t rigged against them, it’s just rigged against the quiet ones. Lucas: It’s not rigged. It’s just loud. And if you refuse to make noise, you will be drowned out by the mediocre people who are very good at talking. It’s a harsh reality, but acknowledging it is the first step to changing it. You don’t have to become a schmoozer. You just have to become a communicator. Luna: Communicator, not schmoozer. I like that distinction. It keeps the integrity intact while solving the visibility problem. Lucas: Exactly. Integrity means doing the work. Visibility means ensuring the work is valued. You need both. If you only have one, you’re either a ghost or a fraud. Ideally, you’re both. But getting started means picking one tactic—maybe the Friday Five—and sticking with it for a month. Just watch how the conversations change. Luna: If you've helped you think through a career move or decision, and you want to support the show's choice to remain ad-free, the link is buy me a coffee dot com slash fexingo. Lucas: Your support keeps these deep dives possible without algorithmic pressure to chase clicks. It allows us to focus on substance over sensationalism. Luna: Thanks for helping us keep the signal clean. Now, back to the question of whether you should actually send that email on Friday, or just hope your boss remembers. Lucas: Hope is not a strategy. Send the email. Document the win. Make sure the right people know exactly what you’re worth, before they assume otherwise.