Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Building a Career FAQ
Transcript
- Lucas: So there's this senior data analyst at a large insurance company — let's call her Priya — who noticed something frustrating. Luna: What's that? Lucas: Every time someone from underwriting or claims needed to understand her team's data pipeline, they'd ask her the same questions. What fields are available? Why is this number different from that report? Who do I talk to if something breaks? Luna: Classic knowledge bottleneck. I've been that person. Lucas: Right. And Priya's manager was spending about two hours a week fielding these same questions, forwarding emails, scheduling quick calls. So Priya did something simple but smart. Luna: She built a FAQ. Lucas: Exactly. Not a full knowledge base, not a wiki — just a living document with the top twenty questions she heard most often. She organized it into three sections: core responsibilities of her team, common troubleshooting steps, and escalation paths for when something needed a human decision. Luna: And she just sent it to her manager? Lucas: She shared a draft with her manager first, got feedback, then posted it on their team's internal SharePoint site. She also added a note at the top: 'Last updated March 2026. If you have a question not covered, add it to the comments and I'll respond within 24 hours.' Luna: That's a smart move — creates a feedback loop so the document doesn't go stale. Lucas: Within a month, three other departments were using it as a reference. Her manager forwarded it to the director of data strategy, who then shared it with the VP. Priya didn't just solve a problem — she created an artifact that made her visible to people two levels up. Luna: And that became part of her promotion case. I've seen this pattern before — the career FAQ is almost like a mini-portfolio of your expertise. Lucas: Exactly. Six months after she launched it, Priya was promoted to associate director. Her manager explicitly cited the FAQ as evidence of her leadership and her ability to scale herself. Luna: But I'm wondering — does this only work in larger companies where there's a clear need for documentation? If you're at a startup with 50 people, everyone already knows who to ask. Lucas: That's a fair point. But I'd argue the FAQ can be even more powerful in a smaller company, because you're probably the only person who knows your domain. A FAQ means you don't have to repeat yourself every time the CEO has a question about metrics. Luna: So it's about saving time for higher-ups, not just for yourself. Lucas: Exactly. Priya's FAQ saved her manager roughly eight hours a month. That's a tangible metric. When you can say, 'I created a resource that saves the team X hours per month,' that's a promotion-ready data point. Luna: What about someone who's an individual contributor with no direct reports? Does a FAQ still make sense? Lucas: Absolutely. Think of it as a way to document your personal processes. For example, a graphic designer might create a FAQ about brand guidelines — 'Where do I find the logo files? What's the approved color palette? How do I request a stock photo?' That's useful for the whole marketing team and shows you're thinking about systems, not just tasks. Luna: And if you're not a natural writer? Some people freeze up at the idea of writing a document. Lucas: Start small. Just list five questions you answer most often. Write one sentence answers. Then test it with one colleague and ask if it helped. You don't need a perfect document — you need a useful one. Luna: I also like that Priya included an escalation path. That's a subtle power move — it shows you understand the organizational structure and who owns what decision. Lucas: Exactly. That section was actually what caught her director's attention. It mapped out not just technical steps but human ones: 'If the data refresh fails after 3 retries, contact the platform team lead.' That's operational maturity. Luna: And it makes her look like a leader, not just a doer. Lucas: Right. The FAQ became a sponsorship artifact. Her director started referencing it in meetings: 'Priya's team has a great doc on this, I'll send it around.' That kind of mention is gold for visibility. Luna: So if someone listening wants to build their own career FAQ this week, what's the concrete first step? Lucas: Track your inbox. For the next three days, every time someone asks you a question you've answered before, write it down. By Friday, you'll have at least ten questions. Pick the top eight to ten, write clear answers, and share with your manager as a 'first draft' asking for feedback. That low-pressure framing invites collaboration. Luna: And you mentioned keeping it updated — how do you prevent it from becoming a dusty relic? Lucas: Set a quarterly calendar reminder to review it. Priya also added a changelog at the bottom — every time she updated it, she noted the date and what changed. That way, anyone can see it's actively maintained. Luna: A changelog also signals that you're meticulous. That's a promotion-worthy trait. Lucas: If we've helped you think through a career move or decision, you might want to support the show. It keeps us ad-free and lets us keep digging into stories like Priya's. You can buy us a coffee at buy me a coffee dot com slash fexingo. Luna: Yeah, we really appreciate that kind of listener support. It helps us keep the focus on practical, actionable career tactics. Lucas: So back to the FAQ — one more thing that made Priya's successful. She didn't just write it and walk away. She promoted it. She mentioned it in team meetings, added a link to her email signature, and when someone asked a question covered in the FAQ, she'd reply with a link and say 'I covered this in our team FAQ — let me know if you need more detail.' Luna: That's a great habit. It trains people to check the document first, which reinforces its value. Lucas: Exactly. And over time, the FAQ became the single source of truth for her domain. When she was promoted, her replacement had a ready-made onboarding guide. That's legacy-building. Luna: I think the key takeaway is that a career FAQ is a low-effort, high-visibility move. It doesn't require a big budget or a special project — just observation and a bit of writing. Lucas: And it works across industries. Priya was in insurance, but I've seen similar stories in tech, healthcare, even retail. The format is universal. Luna: Alright, so this week's challenge: identify your top five repeated questions and draft answers. Share with one colleague by Friday. Lucas: That's a solid action step. And if you do it, let us know how it goes — we might feature your story in a future episode.