Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Building a Knowledge Base for New Hires
Transcript
- Lucas: So, we talk a lot on this show about getting promoted by solving a visible problem. But there's one category of problem that I think people overlook because it sounds administrative — documentation. Luna: You mean building a knowledge base? Because I've seen that work. Lucas: Exactly. Let me give you a real case. There's a senior analyst named Sarah Mitchell at a mid-sized financial services firm — about three thousand employees. She joined a team where everyone was drowning in ad hoc questions from new hires. Every month, a new batch of analysts would start, and the same questions would eat up senior people's time. Luna: Right, the classic 'tribal knowledge' problem. It's in people's heads, not written down anywhere. Lucas: Exactly. Sarah spent her first three months watching this pattern. She noticed that her manager was spending roughly four hours per week answering the same five questions about how to access data sets, who to contact for permissions, which templates to use. So she started taking notes. Not just for herself — she built a structured wiki. Luna: Did she tell anyone she was doing it, or just quietly build it? Lucas: She did it quietly at first. Over a month, she documented the top twenty questions, with step-by-step guides, screenshots, and links. Then she shared it with her manager as a draft. Not as a finished product — as a 'here's something I started, does this seem useful?' That framing is important. It's low-risk. Luna: And the manager's reaction? Lucas: The manager forwarded it to the head of the department within an hour. Because it solved a pain point that everyone felt but no one had time to fix. The department head then asked Sarah to expand it to cover the entire division. She got a formal project, a timeline, and a small budget. Luna: So she turned a side project into a real initiative. That's a classic move — start small, show proof of concept, then let leadership pull you into something bigger. Lucas: Exactly. And here's the metric that made it stick. After six months, the new hire ramp time — the time it takes a new analyst to independently handle a client request — dropped from eight weeks to about five and a half. That's a 31 percent improvement. Sarah measured it by comparing time-to-first-completed-task before and after the wiki. Luna: That's a concrete number she could put in her promotion packet. 'Reduced onboarding time by 30 percent across the division.' That's the kind of language promotion committees understand. Lucas: Right. But let's talk about the specific tactics that made her knowledge base work, because most wikis fail. They become stale, nobody updates them, nobody reads them. Sarah did three things differently. Luna: What was the first? Lucas: She built it in a living document — a shared Google Doc — not a formal Confluence page or SharePoint site. The theory was that if it's too rigid, people won't contribute. She made it easy for anyone to add a question and answer. She also set up a monthly 'wiki review' reminder where she'd ask two junior people to check if anything was outdated. Luna: So she crowdsourced maintenance. That's smart because it's not sustainable to be the sole editor. Lucas: Exactly. Second thing: she tied every entry to a real person. Instead of a generic answer, she'd write 'for data access, contact Priya in IT — here's her direct line.' That made the wiki feel like a directory, not a manual. New hires could immediately act. Luna: That also gave Priya visibility. I bet Priya appreciated being listed as the go-to person. Lucas: Probably. And third: she added a 'quick start' checklist at the top — the first five things every new hire should do on day one. That removed the overwhelm factor. New hires often don't know where to start. A simple checklist gives them a path. Luna: So the knowledge base wasn't just a dump of information. It was designed for the user. That's rare. Lucas: Exactly. And here's where the career payoff came. After a year, Sarah's wiki had become the default onboarding resource for the entire division. The VP of operations mentioned it in an all-hands meeting as 'the kind of initiative that makes our team stronger.' Sarah got promoted to associate director six months later. Luna: And she didn't just get promoted — she built a reputation as someone who solves systemic problems. That's a different league from just doing your job well. Lucas: Right. She wasn't just documenting; she was scaling knowledge. That's a leadership behavior. And you don't need to be a manager to do it. Luna: I think a lot of people hesitate because they feel like documentation isn't 'real work.' But if it saves dozens of hours per month across a team, that's real leverage. Lucas: Absolutely. Look, if today's episode helped you think about a project like this — or even just gave you one concrete idea to try — that's what we're here for. If it was worth a coffee to you, you can find us at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. No pressure at all, but listener support is what keeps this show ad-free and focused on real tactics like Sarah's. Luna: Yeah, and we honestly love hearing that these episodes spark something. So thank you to anyone who's chipped in. Lucas: Anyway, back to the tactics. So once Sarah had a working wiki, she didn't stop. She started tracking usage — how many views each page got, which pages had the most edits. She shared that data with her manager quarterly. Luna: So she turned the wiki into a data product. That's even more impressive. Lucas: Exactly. She could say 'page two on data access has been viewed 400 times this quarter — that's the most common bottleneck. We should automate that process.' That shifted her from librarian to process improvement analyst. Luna: And that's the kind of upward spiral that leads to promotion. She kept adding layers of value. Lucas: One more thing: she made sure to credit others. In every update email, she'd name the senior analyst who contributed a new section, or the IT person who verified a process. That built goodwill and made people want to contribute. Luna: So she wasn't hoarding the spotlight. She shared credit, which made the wiki a team asset, not a personal project. Lucas: Exactly. And that's the kind of behavior that makes senior leaders think 'this person is ready for a larger role.' Because they're not just executing — they're enabling others. Luna: I want to ask about a potential pitfall. What if someone builds a knowledge base and their manager says 'that's not your job' or 'focus on your actual work'? Lucas: That can happen. The key is to frame it as solving a problem that's already on the manager's radar. If the manager is constantly answering new hire questions, they already feel the pain. You're offering a solution, not extra work. Also, start small. Don't build a hundred-page wiki overnight. Share a one-pager first. Luna: So test the waters with a mini version. That makes sense. Lucas: Exactly. And if the manager still says no? Then you know that team culture doesn't value documentation. That's useful information too. Maybe that's not the right place to invest. Luna: Good point. So Sarah's story isn't just about building a wiki. It's about reading the room, finding a pain point, and adding value in a way that's visible but not self-promotional. Lucas: Yes. And the promotion followed because she made her team more efficient. She didn't ask for a promotion first — she did the work, measured the impact, and then the recognition came. Luna: One thing I'd add: if you're going to try this, pick a knowledge domain that's high friction. Don't document something that's already easy. Find the area where people complain the most. Lucas: That's the sweet spot. Sarah picked the onboarding process because it was clearly broken. Everyone felt it. So the payoff was immediate and obvious. Luna: And once you have that win, you can expand to other areas. It builds momentum. Lucas: Exactly. The takeaway is: look for knowledge that's trapped in people's heads, and free it. That's a career move dressed up as a helpful project. Luna: I think a lot of people will hear this and think 'I could do that.' And they should. It's low risk, high visibility. Lucas: Alright, that's it for this episode. Next time we'll talk about how one employee got promoted by automating a compliance process. That one's a little different — it involves regulatory risk. Should be interesting. Luna: Looking forward to it. Thanks for listening.