Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / The Invisible Work That Gets You Promoted
Transcript
- Lucas: There is a specific kind of professional paralysis that happens when you are technically excellent but promotion-proof. You hit every metric, you ship every quarter, yet you remain stuck at the same level while peers with half your output move up. The reason is rarely competence. It is usually that you have become so efficient at removing friction for everyone else that you look like you are just doing your job, rather than leading. Luna: Right, because leadership is often defined by the ability to make complex things look simple. If you are solving problems before anyone notices them exist, you aren't creating the signal that executives need to justify a raise. Lucas: Exactly. In organizational behavior research, this is called organizational glue work. It includes mentoring junior staff, documenting tribal knowledge, mediating cross-team conflicts, and onboarding new hires. These activities are critical for company health, but they are notoriously difficult to quantify in a performance review because they don't show up as discrete outputs. They show up as the absence of chaos. Luna: So you are essentially subsidizing the efficiency of your team without getting credit for the margin you created. Lucas: Precisely. And here is the trap. When you are busy being the glue, you often have less time to produce the shiny, high-visibility projects that get noticed by upper management. So you end up in a double bind. You are indispensable to your immediate team, which keeps you busy, but invisible to the wider organization, which keeps you from moving up. Luna: It feels like a punishment for being helpful. Why does the system reward noise over stability? Lucas: Because stability is hard to see. Noise is loud. I looked at data from several mid-sized tech firms last month regarding promotion cycles. The most common complaint from engineers and analysts stuck at senior individual contributor levels was that they felt their contributions were undervalued compared to those who spoke loudly in meetings or led high-profile initiatives. But when we dug into the stakeholder maps, we found these stuck individuals were actually the primary nodes of information flow. They knew everything. They just didn't broadcast it. Luna: That sounds exhausting. Being the central hub means you carry the cognitive load for everyone else's uncertainty. Lucas: It is. And the danger is that this role can become permanent if you don't actively manage your visibility. Let me give you a concrete example. Sarah, a senior product manager at a logistics platform, was promoted three times faster than her cohort not because she shipped more features, but because she started tracking and reporting her glue work differently. She realized her director only saw feature completion rates. Luna: Did she start complaining about her workload? Or did she reframe how she presented her impact? Lucas: She reframed it. She stopped saying, 'I spent ten hours onboarding two new hires.' She started saying, 'My onboarding framework reduced ramp-up time for new hires by forty percent, saving the team roughly fifteen hundred engineering hours annually.' She translated human capital activities into financial efficiency metrics. Suddenly, her glue work wasn't just nice to have support. It was a cost-saving lever. Luna: That is a brilliant pivot. She turned soft skills into hard ROI. But does that work in all industries? Not everyone has direct access to those kinds of financial models. Lucas: It works anywhere there are stakeholders. The key is identifying what your stakeholders value. For some, it is risk mitigation. For others, it is speed. If you are in a regulated industry, your glue work might be ensuring compliance documentation is never late. That reduces legal exposure. You frame it as risk reduction. If you are in sales, your glue work might be creating battle cards for reps. That increases win rates. You frame it as revenue enablement. The activity is the same. The narrative changes based on who holds the purse strings. Luna: So the first step is mapping who decides your next promotion and what their specific anxiety is right now. Lucas: Yes. And then aligning your invisible labor to soothe that anxiety. Most people try to promote themselves by highlighting what they enjoy doing. You have to promote yourself by highlighting what keeps your boss awake at night. If your boss is worried about churn, and you spend your weekends helping struggling clients stay calm, that is not just customer service. That is retention strategy. You need to put that in writing. Luna: But there is a limit. You can't just do infinite glue work. At some point, you burn out or your own projects stall. Lucas: This is the crucial part. Visibility without boundaries is self-sabotage. You have to protect your capacity for high-leverage work. The goal is not to do more. The goal is to ensure that the work you are already doing is recognized as strategic. Once you have established that reputation, you can say no to low-value requests. You become selective about where you apply your glue. You focus on areas that have upward mobility potential. Luna: It sounds like you are describing a shift from being a worker bee to being an architect of the workflow. Lucas: Exactly. Worker bees follow the hive. Architects design the hive. There is a difference between being helpful and being structural. Helpful people fix problems as they arise. Structural people build systems that prevent problems from arising. Executives hire architects. They rarely promote pure helper roles because helpers are replaceable. Architects are not. Luna: So how do you prove you are building systems when the result is that nothing breaks? How do you sell the absence of fire? Lucas: You sell the near-misses. You document the crises that didn't happen because of your intervention. This requires discipline. You have to keep a log. Not just of what you did, but of what would have happened if you hadn't done it. This is counterfactual thinking. 'If I hadn't standardized this reporting process, the finance team would have missed the deadline by two days, triggering a penalty clause.' That is a powerful statement. Luna: That feels risky though. Admitting you almost caused a problem might backfire. Some managers prefer to think everything is under control. Lucas: Only if you frame it correctly. You don't say, 'I saved us from disaster.' You say, 'We identified a systemic vulnerability in our reporting pipeline and implemented a control layer that eliminated that risk.' It shifts the focus from heroics to governance. Governance is what directors love. It implies scalability. It implies that the solution doesn't rely on you personally showing up every day. Luna: Scalability is the keyword. If your glue work dies when you leave, it is not a system. It is just you working hard. Lucas: Spot on. That is the test. Can someone else replicate your impact in thirty days? If the answer is no, you are still a worker bee. If the answer is yes, you are an architect. Your job is to move from the former to the latter. You do this by documenting your processes, training your successors, and delegating the routine aspects of your glue work. Luna: Delegating glue work seems counterintuitive. Isn't that just passing the buck to someone else? Lucas: No, it is empowering. Often, the people who complain about too much glue work are junior employees who want to do meaningful project work but are trapped in administrative limbo. By creating a structured onboarding or mentoring program, you give them a path to contribute meaningfully while you focus on higher-level strategy. You turn a burden into a development opportunity for your team. That is leadership. Luna: It transforms the dynamic from exploitation to mentorship. That changes the culture of the whole department. Lucas: It does. And culture change is highly visible. Executives notice when teams start functioning autonomously. They notice when turnover drops. They notice when new hires become productive in weeks instead of months. These are all metrics of your effectiveness as a leader, even if you weren't the one coding the software or closing the deals. Luna: So the takeaway is: stop hiding your help. Make it structural, measure its impact, and delegate it to scale it. Lucas: Yes. And remember, you cannot expect people to value what you do if you do not define it. Be explicit about your role as the organizer, the stabilizer, the enabler. Say it in reviews. Say it in one-on-ones. Say it in public forums. 'My focus this quarter was reducing operational drag across three departments.' That sounds like a title. That sounds like a promotion candidate. Luna: It sounds like someone who is ready for the next level. Because the next level is literally managing the drag for everyone else. Lucas: Precisely. You are practicing the job before you get it. The question is whether you are making sure they know you are practicing. Luna: Thanks for listening. If we've helped you think through a career move or decision, please consider supporting Fexingo Business directly. Your contribution keeps these conversations ad-free and allows us to dig deeper into topics like this one. You can find us at buy me a coffee dot com slash fexingo. Lucas: It really does make a difference. Knowing that listeners are behind us lets us take the time to research these subtle dynamics instead of just skimming the surface. Luna: Yeah, it helps us bring you these specific case studies instead of generic advice. Lucas: Back to the topic. One final thought on delegation. When you hand off your glue work, you must provide the context, not just the task. Give them the map, not just the coordinates. Otherwise, you haven't delegated; you've just dumped. Luna: That distinction between delegation and dumping is probably the single biggest barrier to effective leadership development. Lucas: It is. And it requires patience. You will have to redo their work once or twice. But that investment pays off in freedom. You gain the bandwidth to identify the next bottleneck. You move from fixing yesterday's problems to preventing tomorrow's failures. Luna: Which brings us back to visibility. Preventing future failures is a story that gets told at the annual review. Lucas: Exactly. It is the ultimate signal of executive presence. You are not reacting to the world. You are shaping it. And you are doing it in a way that makes the entire organization stronger, not just your own corner of it. Luna: So the next time you feel overwhelmed by the invisible work, ask yourself if you are building a system or just carrying a load. Lucas: And if it is just a load, start designing the cart. Then recruit a driver. Then stand back and watch it roll. Luna: What part of your current role is holding you back from that view?