Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Solving a Cross-Functional Bottleneck
Transcript
- Lucas: There's a pattern I keep seeing in promotion stories that's almost too simple to believe — you don't ask for the promotion. You solve a problem so obvious that the company has to create a role around you. Luna: That sounds nice in theory, but most people I talk to feel like the obvious problems are already owned by someone. Or they're too big to take on alone. Lucas: That's exactly the objection. But the successful cases I've studied zero in on a specific kind of problem — the cross-functional bottleneck. It's a handoff between two teams that everyone hates, nobody owns, and that slows down real work every single day. Luna: And that's the sweet spot. Because if it's not owned, there's no turf to fight over. You can just step in. Lucas: Right. So let me tell you about a marketing coordinator — let's call her Priya — at a mid-sized SaaS company. She noticed that every campaign launch was delayed by at least two days because the creative team's final assets sat in a review queue on the product team's side for an average of seventy-two hours. Luna: That's a classic. Creative blames product, product blames creative, and nobody measures it. Lucas: Exactly. So Priya spent two weeks just tracking the handoff. She pulled timestamps from their project management tool and found that forty percent of delays came from one single step — the product team's legal review. There was no standard checklist, so reviewers kept asking for the same compliance language over and over. Luna: So she didn't just complain — she had a number. That's the move. Lucas: She built a simple Slack bot that prompted the reviewer with a five-item checklist: Has the disclaimer been included? Is the pricing current? Are the testimonials approved? The bot also sent a reminder if the review sat longer than four hours. Approval time dropped to four hours on average. Luna: And did she go to her boss with a slide deck saying 'promote me'? Lucas: No. She wrote a one-page memo titled 'Reducing Campaign Launch Friction.' She documented the baseline — three days — the fix — the Slack bot — and the new average — four hours. She attached a note from the product team lead saying it was the best process change all quarter. Then she sent it to her VP of marketing. Luna: That memo is essentially a job application for a role that doesn't exist yet. Lucas: Exactly. The VP forwarded it to the head of operations, and within three weeks, Priya had a new title: operations associate, focused on cross-functional process improvement. Fifteen percent raise, new scope, and she never once said 'I want a promotion.' Luna: I love that she didn't try to own the whole problem. She picked one handoff, one metric, one fix. That's the difference between a project that gets noticed and a project that gets ignored. Lucas: And the key insight is that the bottleneck wasn't a secret — everyone knew the handoff was slow. But nobody had quantified it. By putting a number on the pain, Priya made it undeniable. Luna: So for someone listening who wants to try this, how do you even find the bottleneck? You're not a process consultant. Lucas: I'd say start with your own inbox or calendar. What's the recurring delay that makes you sigh? The report that always comes in late, the approval that needs three follow-ups, the data that's never ready. Track it for one week. I bet you find a pattern. Luna: And once you have the pattern, you need a fix that's lightweight — Priya's bot was a weekend project, not a six-month system implementation. Lucas: Right. The fix should be proportional to the problem. You're not rebuilding the ERP system. You're adding a checklist. The goal is to show you can diagnose and solve, not to build a monument. Luna: You know, if this episode helped you think about a bottleneck you could solve — honestly, if it was worth a coffee to you, the show runs on listener support. There's a link at buy me a coffee dot com slash fexingo. Lucas: Yeah, that's a small way to keep us ad-free and focused on real stories. And we appreciate it. So back to Priya — I think the other smart move she made was getting the product team lead to endorse her memo. Luna: That's a visibility hack right there. When someone from another team vouches for your work, it's ten times more credible than you praising yourself. Lucas: Absolutely. She asked the product lead, 'Would you be willing to say this helped your team?' and he wrote two sentences. That endorsement traveled further than any self-promotion could. Luna: So the playbook is: find a cross-functional delay, track it for a week, build a lightweight fix, get a stakeholder to endorse it, and document the before and after in a one-page memo. Lucas: That's it. And the beauty is you don't need a special project budget or a mandate. You just need a problem that's annoying enough that people will thank you for solving it. Luna: One thing I'd add — Priya's story worked because the bottleneck was visible to the VP. If your bottleneck is invisible to senior leadership, you might need to surface it first. Lucas: Great point. In that case, the memo should include a line like 'This delay currently costs the company roughly X hours per month across the team' — translate it into time or money. That makes it visible even to executives who don't see the day-to-day. Luna: What if you try this and your boss says 'thanks, but that's not your job'? Lucas: That's a signal. Either your boss is territorial, or they don't see the value of process improvement. In either case, you've learned something about the culture. And you can still share the memo with a skip-level — just frame it as 'I wanted to share an idea that could help the team.' Luna: I've seen people hesitate because they think 'I'm not technical enough to build a bot' or 'I don't know how to code.' But the fix doesn't have to be tech. It could be a shared Google Sheet with conditional formatting, or a recurring calendar reminder. Lucas: Exactly. Priya happened to use Slack because her company already used it. But I've seen people solve bottlenecks with a physical whiteboard in a shared hallway. The tool doesn't matter — the insight matters. Luna: So the real skill is diagnosis. Seeing the system instead of just the task. Lucas: That's it. And once you start looking, you'll see bottlenecks everywhere. The question is which one is small enough to fix in a week, big enough to matter, and owned by nobody. That's your promotion ticket. Luna: Alright, let's say someone finds their bottleneck tomorrow. How do they present it without sounding like they're complaining? Lucas: You lead with data, never with frustration. Say 'I noticed our average approval time is three days. I think we could get it to four hours with a checklist.' That's solution-oriented. The minute you say 'this is so frustrating,' you sound like a complainer. Luna: And what about scale? Priya's fix saved a few hours a week. Is that enough to get promoted? Lucas: It was enough because she showed she could see a problem no one else had quantified. That's a signal of strategic thinking. Companies promote people who make the whole system work better, not just their own tasks. Luna: So the takeaway: stop asking for a promotion and start making the promotion inevitable. Lucas: That's the headline. Next episode, I want to talk about what happens after you get the promotion — how to avoid the 'accidental manager' trap. Luna: That's a good one. I've seen people get promoted into management and crash because they never wanted to manage people. Lucas: We'll cover that. For now, if you've got a bottleneck story or a question, send it in — we read every message.