Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Creating a Knowledge Base
Transcript
- Lucas: Luna, I want to tell you about a promotion story that I think is going to surprise a lot of people — because the work involved was almost invisible. Luna: I love those. What's the angle? Lucas: So there's this software engineer — let's call her Priya — who worked at a midsize SaaS company, maybe 400 employees, engineering team of about 60. She was a mid-level engineer, solid performer, but not the loudest person in the room. Luna: Right, the quiet contributor archetype we've talked about before. Lucas: Exactly. And she noticed something that was driving her crazy: the same questions were being asked in Slack, over and over. How do I set up the dev environment? Where's the API documentation for the payments service? Who owns the user authentication module? She estimated that the engineering team was losing about 15 hours per person per month just answering the same questions. Luna: That's huge. For a team of 60, that's 900 hours a month — wasted. Lucas: Right, and it wasn't just wasted time. It was also a signal that the company's institutional knowledge was trapped in people's heads and in outdated wikis. New hires took about six months to become fully productive, and even senior engineers were constantly interrupting each other. Luna: So what did she do about it? Lucas: She decided to build a knowledge base from scratch. But she didn't just start writing documentation randomly. She first audited the top 100 recurring questions from the team's Slack history over the past year. She categorized them — dev setup, deployment, architecture, code review practices, etc. Luna: So she did the homework first. Did she get buy-in from her manager? Lucas: She actually didn't ask for permission initially. She just started building it in Notion — a shared workspace the company already used. She wrote clear, searchable guides for each of those 100 questions. And she linked the relevant Slack messages, code snippets, and contacts for each topic. Luna: That's smart — she used existing tools and didn't need a big budget or a project plan. Lucas: Exactly. Then she automated a weekly 'office hours' slot — a recurring one-hour video call where anyone could come and ask questions. She also set up a Slack bot that would automatically reply to common questions with a link to the relevant knowledge base page. Luna: So she made the knowledge base the first line of defense. That's really proactive. Lucas: Within three months, the impact was undeniable. Onboarding time for new engineers dropped by 40 percent. The number of repeat questions in Slack fell by about 60 percent. And her manager noticed. Luna: I bet. Did she get promoted? Lucas: She did. Her manager nominated her for a promotion to senior engineer, citing specifically the knowledge base as evidence of leadership, cross-functional collaboration, and systems thinking. Luna: That's the key, right? She didn't just do her job better — she made everyone else's job easier. That's exactly the kind of thing that gets you noticed for promotion. Lucas: And here's the interesting part: the work she did is often seen as 'unsexy.' Documentation is not glamorous. But she treated it as a product — she defined the user need, measured the impact, and iterated. Luna: It's also a form of leadership. You're basically saying, 'I see a problem that affects the whole team, and I'm going to solve it.' That's not just engineering — that's ownership. Lucas: Exactly. And that's why I think this story is so powerful. It's not about writing code that's 10x faster or launching a flashy feature. It's about reducing friction for everyone. Luna: So what's the takeaway for someone listening who wants to try something similar? Lucas: First, find the pain. Look for the question that gets asked every single week — in Slack, in meetings, in hallway conversations. That's your signal. Luna: And don't ask for permission to start documenting. Just start. Use whatever tool the company already uses. Lucas: Right. Second, measure the before and after. Priya had data: 15 hours per person per month, 40 percent faster onboarding. That's the ammunition you need when you make your case for promotion. Luna: And third, make it visible. She didn't hide her knowledge base. She linked it in every Slack reply, she promoted the office hours, she made sure people knew it existed. Lucas: Exactly. Visibility is part of the strategy. If you do great work but nobody knows about it, it doesn't help your career. You don't have to be obnoxious, but you do have to be intentional. Luna: And I love that her promotion wasn't based on some dramatic, one-time hero moment. It was based on consistent, systematic improvement. That's sustainable. Lucas: Right. And it's a model that works in almost any role, not just engineering. A marketer could build a knowledge base of campaign playbooks. A sales rep could document common objections and rebuttals. A product manager could build a knowledge base of user research findings. Luna: The common thread is: identify the recurring questions, solve them at the root, and make the solution accessible. Lucas: Exactly. And if you're listening and you've found this episode helpful, you know, we try to keep these episodes ad-free and focused on practical advice. If that's valuable to you, you can support the show at buy me a coffee dot com slash fexingo. It's a small way to keep things going. Luna: Yeah, we really appreciate it. And it helps us keep the focus on stories like Priya's. Lucas: So back to the knowledge base. One more thing I want to highlight: Priya also did something really smart with her knowledge base. She didn't just write it once and forget it. She set up a quarterly review process where she would update the most popular pages based on new questions and feedback. Luna: So it evolved. A lot of knowledge bases die because they get stale and people stop trusting them. Lucas: Right. She treated it as a living document. And that's a great habit for anyone. If you build something, you need to maintain it. Otherwise it becomes a liability. Luna: So the lesson is: build it, maintain it, and make it visible. That's a career strategy. Lucas: Exactly. And that's it for this episode of The Promotion Memo. Next time, we'll look at another angle on getting visibility without being the loudest person in the room. Luna: See you then.