Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Owning Process Documentation
Transcript
- Lucas: So here's a story I've been sitting on for a few weeks. A mid-level operations analyst at a midsize regional bank — let's call the bank Coastal Federal — got promoted to vice president about six months ago, and the reason isn't the usual one. Luna: Let me guess: she didn't build a dashboard, didn't write a sponsorship memo, didn't automate her boss's calendar. Lucas: None of the above. She got promoted by owning process documentation. Specifically, she took a broken loan-approval workflow that everyone knew was a mess but nobody had time to fix, and she documented the hell out of it. Luna: Process documentation sounds like the kind of task people delegate to interns. How does that get you to VP? Lucas: Exactly the reaction most people have. But here's the detail. This analyst — her name is Sarah, I spoke with her — she noticed that the commercial loan approval process had an average cycle time of twelve days, but the actual underwriting work took maybe three. The other nine days were dead time: handoffs between departments, manual data entry, approvals sitting in inboxes. Luna: So she mapped the whole thing. Lucas: She spent two weeks just observing and taking notes. She shadowed loan officers, credit analysts, the documentation team, even the mail room — because physical documents were still moving around. She built a flowchart that had 47 steps and 14 decision points. Then she presented it to her manager and said, 'I'd like to document the current state and propose a target state.' Luna: Did her manager give her the time? Because most managers would say 'we don't have budget for that.' Lucas: Her manager said yes, but with a caveat: 'You can spend 10 percent of your time on this, and only after you finish your regular tasks.' So she did it on evenings and weekends for about three months. She interviewed twenty-two people, documented every role's perspective, and identified fourteen specific bottlenecks. Seven of them were process gaps — no standard procedure existed. Five were technology gaps — people were using Excel when they could have used the core system. Two were policy gaps — outdated rules that added extra approval layers. Luna: And then she didn't just hand the document to her manager and hope for the best. Lucas: She scheduled a meeting with the senior vice president of commercial lending, brought a printed binder with color-coded maps, and walked through the bottlenecks one by one. She didn't propose a system implementation or a reorg. She proposed eliminating seven bottlenecks through simple changes: standardizing email subject lines for approval requests, moving one approval step earlier in the workflow, and creating a shared tracker so everyone could see where a loan was in the pipeline. Luna: Simple changes, but nobody had written them down. The knowledge was all tribal. Lucas: Exactly. The SVP was impressed, approved the changes, and within four months the average cycle time dropped from twelve days to five. The documentation became the official standard operating procedure for the entire commercial lending division. And when the chief credit officer — who reports to the CEO — needed to understand the process for a regulatory review, he grabbed Sarah's binder. Luna: So she became the subject-matter expert by writing things down. That's a classic move, but I don't think people realize how powerful it is until you see a concrete example. Lucas: She told me something that stuck: 'I didn't invent anything new. I just made the invisible visible.' And that visibility made her the obvious person to promote when the VP of operations left. The chief credit officer specifically told HR, 'I want Sarah. She knows how the bank actually works.' Luna: So the promotion wasn't because she was a great operations analyst. It was because she became the institutional memory. Lucas: Right. And that's the key distinction. Process documentation is often dismissed as 'busywork' or 'paper pushing.' But when done right, it transforms tacit knowledge — the stuff in people's heads — into explicit knowledge that an organization can scale. And the person who owns that translation becomes indispensable. Luna: I've seen this work in reverse, too. I had a friend at a tech company who refused to document anything because she thought it made her replaceable. She guarded her process knowledge like a trade secret. And when her team reorganized, she was the first to be laid off — because nobody knew what she did. Lucas: That's the fear, right? If I write it down, they can give it to someone cheaper. But the evidence suggests the opposite. Sarah's documentation didn't replace her — it amplified her. The CCO didn't say 'great, now I have the binder, I don't need her.' He said 'she's the person who built the binder, she's the person who thinks about this systemically.' Luna: So there's a strategy here. It's not just 'document everything.' There's a way to do it that makes you look strategic, not clerical. Lucas: Sarah had three rules she followed. First, she documented the process that mattered to senior leaders — loan approvals, not the office supply ordering process. Second, she framed it as a diagnostic, not a description. She didn't just say 'here's how we do it.' She said 'here are the fourteen things costing us time and money.' Third, she made it visual. The color-coded flowchart was what got the SVP's attention. Luna: I want to linger on the visual point. Because a lot of documentation is just walls of text in a Word doc. Nobody reads that. Lucas: Sarah used Microsoft Visio — nothing fancy — but she also created a one-page summary that showed the before and after. The before had 47 steps and 14 decision points, all tangled. The after had 28 steps and 7 decision points, streamlined. That one-pager was what the CCO took to the board presentation. He literally held it up and said 'this is what we've accomplished.' Luna: So the documentation became a communication tool, not just a reference manual. That's a huge shift. Lucas: And it's a shift that anyone can make. You don't need to be a process expert. You just need to be willing to observe, ask questions, and write things down in a way that tells a story. The promotion didn't come from the documentation itself — it came from the systems thinking it revealed. Luna: Let me play devil's advocate. What if you document a process and your manager takes credit for it? Or what if the documentation reveals that the process is broken because of your manager's decisions? Lucas: Both real risks. Sarah was lucky that her manager was supportive and that the SVP was the kind of leader who rewards initiative. But I think the way to mitigate that is to share the documentation broadly, not just with your direct boss. She presented to the SVP directly, bypassing her manager's layer. That's a calculated risk — you need to know your organizational culture. Luna: Also, if the documentation reveals a problem caused by your manager, you frame it as a systems issue, not a people issue. 'The current process results in X delay' is safer than 'Bob in underwriting is slow.' Lucas: That's exactly what Sarah did. She never named names. She referred to 'approval step 4.2' not 'the SVP who sits on requests for two days.' That depersonalization made the document feel objective and safe. Luna: And if the process is already well-documented? What if you join a company that has SOPs for everything? Lucas: Then you document the gap between the SOP and reality. There's always a difference between the official process and the actual process. Sarah found that seven of her fourteen bottlenecks were steps that didn't have any documented procedure — people were making it up as they went. In a highly documented environment, you could audit the SOPs against what people actually do and find discrepancies. That's even more valuable, because you're catching drift. Luna: So the real skill is not documentation per se — it's the ability to see the system and make it visible. That's a leadership skill. Lucas: Exactly. And it's one that's often overlooked because it doesn't have a flashy title like 'project management' or 'data analytics.' But in Sarah's case, it took her from a mid-level analyst to a VP in 11 months. That's a pretty concrete return on investment. Luna: If this episode has helped you think about how to make your own work more visible, or if you've ever used documentation to advance your career, that's exactly the kind of real-world strategy we try to bring every week. And the reason we can keep doing that, without ads or sponsors, is because of listeners who support the show at buy me a coffee dot com slash fexingo. It's a small gesture that makes a big difference for us. Lucas: Yeah, and we mean that genuinely. Every contribution helps us cover production costs and keeps the podcast ad-free. If you find value in these episodes, that's the best way to say thanks. Alright — back to the topic. Sarah's story raises a question: how do you choose which process to document if you're starting from zero? Luna: I imagine you'd want something that's both painful and visible. Lucas: Right. Painful means it's causing real friction — delays, errors, customer complaints. Visible means senior leaders already know it's a problem. Sarah's loan approval process was perfect because the bank's CEO had mentioned in an all-hands meeting that loan turnaround time was a competitive disadvantage. So she was aligning with a stated executive priority. Luna: That's smart — she used the CEO's own words as her charter. So even if someone questioned why she was spending time on documentation, she could say 'the CEO said this is important.' Lucas: Exactly. And once she had the documentation and the results, she made sure the CCO knew about it. She sent him a brief email with a link to the one-pager and said 'here's an update on the loan process improvements, happy to discuss.' He replied within an hour. Luna: So the documentation was the hook, but the promotion came from the visibility she built around it. She didn't just do the work — she marketed the work. Lucas: That's the final lesson. Documenting the process is step one. Making sure the right people see it is step two. And Sarah did both without ever being pushy or self-promotional. She let the numbers speak. Twelve days to five days. That's a number any executive understands. Luna: I think the takeaway for our listeners is: pick a process that's broken, visible, and relevant to a senior leader's agenda. Document the current state, identify the bottlenecks, propose simple fixes. Then share it broadly. You might not become a VP in 11 months, but you'll definitely get noticed. Lucas: And if you do, come back and tell us your story. We love featuring listener cases. For now, thanks for listening. Lucas and Luna signing off.