Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How a Quiet Employee Got Promoted by Redesigning a Broken Process
Transcript
- Lucas: You ever notice how some of the most talented people at work stay invisible for years, then suddenly land a promotion because they fixed something nobody else even realized was broken? Luna: Totally. And often it's not the loudest person in the room — it's the one who quietly documents a problem and hands you a solution. Lucas: Exactly. That's the story we're looking at today. Sarah Chen was a mid-level operations analyst at a regional bank — let's call it Heartland Financial. She'd been there about three years, solid performer, but not on anyone's fast-track list. Luna: What was the broken process she found? Lucas: It was their commercial loan documentation handoff. When a loan officer closed a deal, they'd print the full file and physically walk it to the documentation team. That team would re-enter data manually into their system, then print a checklist and walk it back for signatures. Every single loan. Luna: That sounds like a time machine back to 1995. Lucas: Right? Sarah noticed that this process caused an average delay of 4.2 days per loan, and about 12 percent of files had data-entry errors that required rework. She spent two weeks tracking every step — shadowed both teams, recorded timestamps, counted the rework incidents. Luna: And she didn't just complain about it — she built a case. Lucas: Exactly. She calculated that the inefficiency was costing the bank roughly two point three million dollars a year in wasted labor and delayed interest income. Then she designed a simple digital handoff using a shared spreadsheet with validation rules — no new software purchase needed. Luna: That's smart. She kept the solution cheap and low-risk. Hard for leadership to say no. Lucas: She pitched it to her manager, who was initially skeptical — change is uncomfortable. So Sarah asked if she could run a two-week pilot with just four loan officers. The pilot cut the average handoff time from 4.2 days to 1.1 days, and eliminated errors entirely. Luna: That's the kind of data that gets a VP's attention. Lucas: It did. Her manager presented the results up the chain, and Sarah was asked to roll out the process across the entire commercial lending division. Within six months, she was promoted to a process improvement manager role — a new position created partly because of her work. Luna: So the promotion wasn't just a pat on the back — it was a recognition that she had the skills to keep finding and fixing these problems. Lucas: Right. And that's the key for anyone listening who feels like they're doing solid work but not getting noticed. Process redesign is a low-visibility activity until you frame it properly. The framing matters. Luna: What's the right way to frame it? Lucas: You don't say, 'Hey, this process is terrible and everyone is wasting time.' That's blaming people. Instead, you say, 'I noticed an opportunity to improve our turnaround time and reduce rework. Here's the data, and here's a solution I'd like to test.' Luna: It's an autopsy without blame — focusing on the process, not the people. Lucas: Exactly. Sarah also did something smart: she involved the people whose work would change. She asked the documentation team what frustrated them about the current system, and incorporated their suggestions. That turned potential resistance into allies. Luna: So she built a coalition before she even pitched the solution. Lucas: Yes. And that's a skill that screams 'ready for the next level.' Executives see someone who can collaborate across functions and implement change without causing drama. Luna: For listeners who want to try this, what's the first step? Do you just start timing everything? Lucas: Start by picking one recurring task that feels unnecessarily painful — something you or your team does at least once a week. Map out every step, even the tiny ones. Then ask: which steps don't add value? Which are just workarounds for a bad system? Luna: And if you don't have a clear cost metric like Sarah did? Lucas: Time is a cost. If a process takes ten hours a week across a team of five, that's fifty hours. Multiply by average hourly burdened cost — say fifty dollars — and you've got twenty-five hundred dollars a week. That's a hundred thirty thousand a year. That number gets attention. Luna: So the real move is: find a drag, quantify the drag, propose a fix, and test it small. Lucas: Exactly. And if you do that even once, you've just demonstrated initiative, analytical thinking, and change management — all in one project. Luna: It's almost like a promotion cheat code for people who don't love self-promotion. Lucas: It really is. And it's one of those things where, if we've helped you think through a career move or decision, a couple of dollars a month is genuinely what keeps these shows going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Luna: Yeah, it makes a real difference. We're ad-free because of listeners who chip in, and it lets us keep digging into stories like Sarah's. Lucas: So back to the practical takeaway: the next time you're frustrated by a clunky process at work, don't just vent. Document it, quantify it, and propose a fix. You might be one spreadsheet away from a promotion. Luna: And if you want a template for that business case, we'll link one in the show notes. Lucas: Good idea. For The Promotion Memo, I'm Lucas. Luna: And I'm Luna. See you next time.