Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Build a Reputation as the Go-To Person at Work
Transcript
- Lucas: So we are 50 episodes in, Luna. Fifty episodes of office politics, influence, and getting things done. Luna: That is genuinely wild. I feel like we've covered everything from strategic silence to surviving a merger. Lucas: Right, and there's one topic I keep hearing from listeners — especially people who are early in their career or mid-level — that we haven't touched yet. How do you become the go-to person in your organization? Luna: That's such a loaded term though. 'Go-to person' can mean a lot of things. It could be the person who knows the legacy codebase, or the one who always has the answer about PTO policy. Lucas: Exactly. And the nuance matters because being the go-to can either turbocharge your career or trap you in a role where you're too busy helping everyone else to advance your own work. I want to ground this in a real case. Luna: Please. Give me a real person. Lucas: I was talking to a senior engineer at a mid-sized SaaS company — let's call her Priya. She led the data migration for a platform overhaul that affected four departments. She didn't volunteer for it. She was asked because she had worked on a smaller migration two years earlier. Luna: Okay, so she already had some credibility. Lucas: Right. But here's what she did differently. Instead of just executing, she documented every step — the schema changes, the edge cases, the rollback procedures. And she shared that documentation proactively with the teams that would be affected. Luna: That's smart. She built a reputation for being prepared and transparent. Lucas: Exactly. Within three months, people started coming to her not just for migration questions but for anything involving cross-functional data. She became the informal 'data bridge' between engineering, product, and customer success. Luna: But there's a downside, right? Once you're that person, the requests pile up. Lucas: That's the critical tension. Priya told me she felt stretched thin until she adopted what I call the 'Three-Bucket Method' for triaging requests. Bucket one: quick answers that take less than five minutes — she answers immediately. Bucket two: deeper questions that require context — she schedules a fifteen-minute call. Bucket three: requests that she can't or shouldn't handle — she redirects to the right person or resource. Luna: So she's not saying yes to everything. She's sorting and routing. Lucas: Exactly. And the redirection part is key. If you just say 'I don't know' or 'I'm too busy,' you lose the go-to status. But if you say 'I don't have the bandwidth right now, but talk to Sarah in finance — she just handled a similar issue,' you still look helpful. Luna: That's a great tactic. It also builds social capital with Sarah, because you're sending her a referral. Lucas: Right. Priya also told me she tracks her response time. She aims to respond to any request — even if it's just an acknowledgment — within two hours. That creates a sense of reliability that makes people trust her. Luna: Two hours feels aggressive, but I get it. If someone emails you and you reply 'Got it, I'll get back to you by Friday,' that's still a response. Lucas: Exactly. It's about managing expectations. Now, the flip side I want to discuss is the promotion trap. Priya was so effective as the go-to person that her manager started to see her as irreplaceable in her current role. She nearly got passed over for a promotion because they 'couldn't afford to lose her on the migration.' Luna: Oof. That is the classic bottleneck paradox. You become so valuable where you are that they don't want to move you. Lucas: Priya solved it by deliberately training two junior engineers on the migration processes. She created documentation, held office hours, and slowly distributed her knowledge. That made her replaceable in the best possible way. Luna: So the strategy is: be helpful enough to be known, but generous enough to share the spotlight. Lucas: Exactly. And that's the real art of being the go-to person. It's not about hoarding knowledge. It's about being the node that connects people to solutions, even if you're not the solution yourself. Luna: I want to add one more angle. There's a risk of becoming the go-to for things that are actually someone else's job. Like, if you're always the person who knows how to fix the printer, you're not building strategic value. Lucas: Great point. You need to be selective about what you become known for. Priya intentionally chose data migration because it was high-visibility and aligned with the company's strategic goals. She avoided becoming the go-to for things like scheduling meetings or formatting spreadsheets. Luna: Right. So there's a curation aspect. You have to gently deflect low-value requests while embracing high-value ones. Lucas: And that's where the 80/20 rule applies. 80 percent of your go-to reputation should be built on one or two core competencies that are critical to your team or company. The other 20 percent can be helpful but not essential. Luna: I think a lot of people, especially women and underrepresented groups, feel pressure to say yes to everything to prove their worth. That can backfire. Lucas: Absolutely. Priya mentioned that she used to say yes to every request because she was afraid of seeming unhelpful. It wasn't until she started using the Three-Bucket Method that she felt in control. And her promotion eventually came through — she's now a staff engineer. Luna: Good for her. So the takeaway is: be the go-to person for the right things, set boundaries, and make yourself replaceable by lifting others. Lucas: You know, it's funny — we've done 50 episodes on office politics, and this idea of 'strategic generosity' keeps coming up. Whether it's sharing credit, or training others, or redirecting requests, the people who get ahead are the ones who build others up while protecting their own trajectory. Luna: That's a good note to land on. But before we wrap, I want to ask — if someone is listening and thinking about how to start building their go-to reputation, what's the first step? Lucas: First step: identify a recurring pain point in your team that nobody owns. It could be a documentation gap, a process bottleneck, or a knowledge silo. Then, quietly become the person who addresses it. Not with a big announcement — just do it. Luna: And when someone notices, you're already the go-to. Lucas: Exactly. That's how you build reputation without self-promotion. Luna: Hey, speaking of building something — if this episode helped you think about your career, or if you've gotten value from the podcast over these 50 episodes, we have a small ask. Lucas: Yeah, it's really simple. We keep this show ad-free because we believe in giving you undiluted, practical advice. If today's episode was worth a coffee to you, you can support us at buy me a coffee dot com slash fexingo. Luna: That link — buy me a coffee dot com slash fexingo — it's also in the show notes. No pressure, just if it feels right. Lucas: And honestly, even if you just share an episode with a colleague who might need it, that helps too. Alright, back to the topic — one more thing I want to mention about being the go-to person. Luna: Sure, what's that? Lucas: The timing of when you build that reputation matters. If you try to become the go-to person during a period of high instability — like right after a layoff or a merger — you may get pulled into too many directions. Priya actually waited until after the migration dust settled to start training others. Luna: So there's a strategic window. You want to be visible but not overwhelmed. Lucas: Right. And sometimes the best time to build that reputation is when you're new. People have low expectations, and if you deliver quickly, you stand out. But if you overcommit early, you can burn out fast. Luna: It really is a balancing act. I think the key is to be intentional about what you say yes to. Lucas: Absolutely. And with that, we'll leave you to think about what your 'one thing' could be. Thanks for listening to episode 50. Luna: See you next time.