Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Building an Internal Tool
Transcript
- Lucas: So Sofia is a data analyst at a mid-sized logistics firm — we'll call it LazerShip — and she had been in her role for about three years. Good performance reviews, solid with SQL and Tableau, but she kept hearing the same feedback: she needed more 'strategic impact' to move to senior manager. Luna: Right — that classic vague feedback. 'Strategic impact' usually means 'do something we didn't ask you to.' Lucas: Exactly. And Sofia noticed something. Every Monday morning, three different teams — operations, finance, and sales — each ran their own weekly report from the same raw data source. They were essentially building the same pivot tables, just formatted differently. And they all complained it took hours. Luna: So she saw a repetitive pain point that everyone had accepted as just the cost of doing business. Lucas: Right. And instead of writing a memo about it or suggesting a meeting, she just spent about two hours over a weekend building a prototype in Python that pulled the data, applied the three different templates, and emailed the PDFs automatically. She showed it to her manager on Tuesday. Luna: Two hours? That's surprisingly little. Usually these projects balloon. Lucas: That's the key insight. Sofia scoped it ruthlessly. She didn't try to build a dashboard with a front end. She just automated the worst part — the copy paste repeat cycle. Her manager was impressed enough to let her spend ten percent of her work week refining it. Three weeks later it was live for all three teams. Luna: So she turned a weekend prototype into a company-wide tool. What happened next? Lucas: She didn't just hand it over. She documented it — wrote a one-page setup guide, recorded a five-minute Loom walk-through, and offered to train each team's point person. That made it sticky. Within two months, the operations director mentioned the tool in a quarterly review as a 'major efficiency gain.' Luna: That's the smart part. She didn't just build it — she made sure the right people knew she built it, without having to boast. Lucas: Right. And when promotion season came, Sofia's manager had a concrete story: 'She saved three teams roughly five hours a week, reduced errors, and she did it on her own initiative.' That's a much stronger case than 'she has strategic potential.' Luna: And she got the senior manager title? Lucas: She did. With a fifteen percent raise. But here's what I find interesting — she told me that the promotion was almost incidental. The real shift was that people started seeing her as someone who builds solutions, not just someone who runs queries. That changed how she was assigned projects too. Luna: So it's a rebranding, but through a tangible deliverable. I love that. What about the risk of over-committing? Some people worry that building a tool means you own it forever, and it becomes a maintenance burden. Lucas: That's a real concern, and Sofia handled it well. She made sure the tool was simple enough that someone else could take it over. She trained the operations team to handle basic updates. She didn't make herself indispensable — she made the process scalable. That's actually more promotable than being the sole keeper of the flame. Luna: So the lesson is: build something that solves a clear, shared pain, keep it small, and hand it off. Don't try to build the perfect system. Lucas: Exactly. And there's another angle. Sofia's tool wasn't a flashy machine learning project. It was a simple script that saved people from a dull task. In most companies, the boring automation is the most visible, because everyone feels the pain of the boring task. Luna: Yeah, executives don't care about the tech stack. They care about 'five hours a week back per team.' That's a language everyone understands. Lucas: Right. And Sofia framed it that way in her promotion packet. She didn't write about the Python libraries she used. She wrote: 'Before this tool, the weekly report took four hours and had an average of two errors per month. After, it takes fifteen minutes and has zero errors in six months.' Luna: That's a killer metric. And it's easy to verify. So for someone listening who wants to try this, what should they look for? Lucas: Look for a task that is repetitive, takes at least an hour per week, involves multiple people doing the same thing, and has no single owner. The classic sign is when people say 'oh, that's just how it is.' That's the opportunity. Luna: And then prototype fast, not perfectly. Lucas: Yes. Even a half-solution that saves ten minutes per person per week is a win if you can show the math. And then — this is critical — make sure your manager knows you did it. Not in a braggy way, but by cc'ing them on the email where you announce the tool to the team. Luna: Or better yet, ask your manager to introduce it. That gives them credit too, and they'll champion it. Lucas: Sofia did exactly that. She said 'Hey, I built this thing, want to send it out under your name?' Her manager said yes, and then in the promotion meeting, that manager had skin in the game to argue for Sofia. Luna: That's a pro move. It's not self-promotion, it's strategic generosity. Lucas: Exactly. And it works because most managers are overloaded and would love to look good with a new tool. You're giving them a gift they can share. Luna: So the takeaway: find a pain point, build a tiny fix, let your manager take the bow, and let the results speak. That's a promotion story anyone can write. Lucas: Quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making stories like Sofia's available to everyone. No ads, no sponsors, just listener support. If this show has helped you think through a career move or decision, that's the only reason we can keep doing it. Luna: Yeah, and we really mean that. It's a small group that keeps this going, and it lets us stay focused on practical stuff like this, not on selling you something. Lucas: So back to Sofia — one more thing. She told me the biggest surprise was how much she learned about the business by building that tool. She had to understand what each team actually needed, not just what they asked for. That business acumen is what ultimately got her promoted. Luna: So the tool was a vehicle for learning the business. That's really the hidden benefit. Lucas: Right. So if you're stuck in a role where you feel like you're just executing tasks, look for the rote work that everyone hates. Build a tiny solution. Hand it off. And watch how that changes your visibility. Luna: Great advice. And if you have your own promotion story, we'd love to hear it. Until next time. Lucas: Take care, everyone.