Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How an Employee Got Promoted by Building a Business Wiki
Transcript
- Lucas: So you know how every company has that one person who just seems to know where everything is — the old file, the meeting notes from two years ago, the rationale behind a decision nobody remembers making? Luna: Right, the unofficial librarian. Half your day is saved by asking them one question. Lucas: Exactly. But what happens when that person leaves — or when a team scales so fast that nobody can keep the knowledge in their head anymore? That's the problem a mid-level marketing manager named Priya ran into at a mid-sized B2B SaaS company. And the way she solved it got her promoted to director. Luna: Okay, I'm hooked. What did she do? Lucas: She built a business wiki. Not a tech wiki, not a developer docs site — a plain-English, searchable repository of everything the marketing team needed to do their jobs. Campaign histories, sales enablement decks, product launch timelines, competitive battle cards, even the backstory on why certain pricing models were chosen. Luna: So she basically created a single source of truth. How long did that take her? Lucas: About two months of her spare time. But here's the key — she didn't just dump files into a shared drive. She structured it around the questions she heard most often. Every time someone asked 'Where's the Q3 case study?' or 'Who approved that vendor?' she added it. By the end, she had over 150 pages of curated, cross-referenced content. Luna: That's a lot of work. Did she get any pushback? Some managers might see that as scope creep. Lucas: She was smart about it. She framed it as a pilot — 'Let me try this for one quarter and see if it saves the team time.' She tracked one metric: time to onboard a new hire. Before the wiki, it took about three weeks for a new marketing coordinator to feel productive. After the wiki, it dropped to five days. Luna: Three weeks to five days. That's a concrete number that any senior leader would notice. Lucas: Exactly. And she didn't keep that number to herself. During the quarterly business review, she presented a one-slide summary: 'We reduced onboarding time by seventy-five percent, reduced repeated questions in Slack by an estimated forty percent, and we now have a searchable archive of every major campaign since 2019.' Senior leaders from other departments started asking if they could use it too. Luna: So visibility was built into the rollout. That's the piece a lot of people miss — they do great work but nobody in power sees it. Lucas: Right. Priya didn't just build the wiki and hope someone noticed. She tied it to a business metric that mattered to the VP of Marketing — efficiency, speed, reducing friction. And she offered to train other teams on the same approach. That's a leadership move. Luna: It also shows she's thinking beyond her own job title. She's solving a company-wide problem, not just a team-level one. Lucas: Exactly. And here's a detail I love: after the wiki was live for three months, she handed over editorial control to a junior team member. She set up a simple process for updates and then stepped back. That signals to leadership that she's not hoarding the project — she's building something sustainable. Luna: That's actually a really smart play. It shows she can delegate and scale impact. So how long after that did she get promoted? Lucas: About six months after the wiki launched. The VP told her later that the wiki was the first concrete evidence she'd seen of Priya operating at a director level — thinking cross-functionally, creating systems, measuring outcomes. Luna: It's interesting that the promotion came from a project that wasn't even in her job description. She basically created her own proof of capability. Lucas: That's the whole premise of this show, right? Most promotions don't come from doing your current job better. They come from doing work that looks like the next job. Priya's wiki was director-level work — building infrastructure, reducing systemic friction, making the whole team smarter. Luna: I want to dig into the practical steps. What should someone listening today take away? Say I'm a marketing coordinator or an analyst — how do I start something like this without it feeling overwhelming? Lucas: First, don't try to build a perfect wiki overnight. Priya started with the ten most frequently asked questions in her team's Slack channel. She answered them in a simple Google Doc. That's it. Then she added a new page every time someone asked a question she'd already answered. Luna: So it's really about pattern recognition — noticing what people ask again and again, and making those answers findable. Lucas: Exactly. Second, pick a tool that already exists in your company. Priya used Confluence because her engineering team already had it. She didn't ask for new budget or a new software approval. She just started filling in blank pages. Luna: That's a huge point. Any time you can work within existing systems, you remove friction for yourself and for the people approving your project. Lucas: Third, and this is the one I think is most overlooked — make it visible to the right people. Priya didn't just share the link in a team meeting. She included a screenshot of the wiki in her weekly status report for two months. She mentioned it in her one-on-ones with her manager. She offered to demo it for other teams. Luna: And when she presented it at the quarterly review, she had data. She didn't say 'I made a thing.' She said 'I made a thing and here's the impact in numbers.' Lucas: That data is what gets you promoted, not the thing itself. The wiki was the vehicle. The metric was the proof. Luna: So let's talk about something that might worry listeners: What if your company culture doesn't reward this kind of initiative? What if your manager is the type who says 'That's not your job'? Lucas: That's a real risk. Priya was lucky that her manager was supportive, but she also framed it as a small experiment — 'Let me try this for a month and see if it helps.' She didn't ask for permission upfront. She just started solving a problem and then showed results. It's harder for a manager to say no to 'I already did this and here's the data.' Luna: So act first, ask forgiveness later — within reason. Don't break anything, but don't wait for a formal mandate. Lucas: Right. And one more thing: make sure you hand it off. If you're the only person who can update the wiki, you haven't built a system — you've built a dependency. Priya trained someone else to maintain it within three months. That proved it wasn't about her ego. It was about making the team better. Luna: That's a leadership signal that's hard to fake. It says 'I care about this organization beyond my own career.' Lucas: Exactly. And that's the kind of thing that gets noticed when promotion decisions are made. Luna: You know, this episode really hits on something we try to do on this show — give you concrete, repeatable tactics. If we've helped you think through a career move or decision, we want you to know that this podcast is completely ad-free by design. We deliberately don't run ads, and we intend to keep it that way. Lucas: Yeah, and the only reason we can do that is because some listeners choose to support us directly. If that model resonates with you, the link is buy me a coffee dot com slash fexingo. No pressure, no upsell — just a way to keep the show independent. Luna: And we really appreciate the people who do. It lets us spend time on cases like Priya's instead of reading ad copy. Lucas: Alright, back to the wiki. One more thing I want to highlight: Priya's promotion didn't come from the wiki alone. She was already a strong performer. But the wiki was the piece of work that made her promotable in a way her daily tasks never could. Luna: So it's about using a side project to prove you can operate at the next level. The wiki wasn't her main job, but it showed she could think systematically. Lucas: Exactly. And I think that's the takeaway for anyone listening: look for the one piece of institutional knowledge that everybody wishes existed but nobody has time to create. That gap is your opportunity. Fill it, measure it, share it, hand it off. That's a promotion pattern. Luna: I love that framing. One gap, one system, one metric, one handoff. It's almost like a formula. Lucas: It really is. And it's repeatable in almost any role — not just marketing. An engineer could do it for code documentation. A salesperson could do it for objection handling scripts. An HR coordinator could do it for policy FAQs. Luna: The common thread is that you're solving a problem that affects everyone, and you're doing it in a way that makes leadership notice your potential. Lucas: Exactly. So if you're listening and you're thinking 'I wish my team had a better way to find X' — that's your signal. Go build the first page this week. Luna: And if you do, let us know. We might feature your story on a future episode. Lucas: That's a great idea. For now, thanks for listening — we'll see you next time on The Promotion Memo.