Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Bank Cut Loan Approval Time 70 Percent With One Email Change
Transcript
- Lucas: So there's a mid-sized commercial bank in the Midwest — I'll keep them anonymous — and their loan approval process was taking, on average, nine days. Nine days from application to a yes or no. And the loan officers were drowning in follow-up calls, borrowers were frustrated, and the bank was losing deals to faster competitors. Luna: Nine days. That's an eternity in commercial lending. What was the bottleneck? Lucas: That's the thing — they assumed it was the underwriting itself. The credit analysis, the financial modeling, the risk committee. But when they actually mapped the process, they found the real logjam was something far more mundane: an internal email that got sent back and forth between the loan origination team and the credit department. Luna: An email. The thing that supposedly takes seconds. Lucas: Right. And this wasn't some legacy system from the nineties. It was a standard internal request — the originator would email the underwriter with the application details, and the underwriter would respond with questions or a preliminary decision. But here's the kicker: the email had no subject line convention, and the body was often a wall of text. So the underwriter had to open every single email, read through paragraphs, and figure out what was actually being asked. Luna: So the bottleneck was cognitive load, not processing capacity. Lucas: Exactly. The underwriters were spending maybe forty percent of their day just parsing these emails. Figuring out which deals were urgent, which were missing documents, which needed a quick yes or a detailed review. And because the information was buried, they'd often have to reply with follow-up questions, which added another round trip. Luna: So what was the one change? I'm guessing it wasn't 'switch to Slack.' Lucas: No, it was even simpler. They redesigned the email template. Specifically, they added two mandatory fields: a subject line that had to start with a deal priority code — like 'Urgent' or 'Standard' — and a one-line summary at the top of the body that stated the ask in a single sentence. Something like, 'Requesting credit approval for $500,000 term loan to Acme Manufacturing; all financials attached.' Luna: That's it? A subject line and a summary? Lucas: That's it. But they enforced it with a simple rule: if the email didn't follow the format, it got bounced back to the sender automatically, with a note explaining the required structure. No exceptions. And they trained everyone on the new format over two lunch and learns. Luna: And what happened? Lucas: Within the first quarter, average approval time dropped from nine days to under three. That's a 70 percent reduction. And it wasn't just speed — the number of follow-up emails between teams fell by more than half, and the error rate on applications dropped too, because the summary made it obvious when documents were missing. Luna: It's almost too simple. Why did it work so well? Lucas: Because it removed the 'interpretation tax.' Before, every email required the reader to do work — to parse, to prioritize, to infer. Now, the format tells the reader what to do at a glance. It's like the difference between a messy desk and a labeled filing system. The cognitive load drops, and decisions get faster. Luna: And it's a great example of how bottlenecks often hide in plain sight. Everyone assumed the problem was complex, but it was just communication friction. Lucas: Yeah. And that's a pattern we see a lot. Companies spend millions on new software, but the real constraint is often a simple handoff between teams. This bank didn't change their underwriting model or hire more people. They just made one email clearer. Luna: It's funny, because we're sitting here talking about a bank, but this applies to any team that relies on email to pass work along. I know I've been on the receiving end of vague emails that take ten minutes to decode. Lucas: And that's exactly why we do this show — these small, tactical wins are replicable. And that's also why we keep it ad-free. We don't want to interrupt the flow with a sponsor read. If you've found value in episodes like this, and you want to help keep the lights on, you can support us at buy me a coffee dot com slash fexingo. No pressure, just if it's made a difference in your work. Luna: Yeah, we've heard from a lot of listeners who've applied these ideas and seen real results. That's what keeps us going. Lucas: So, back to the bank. The other thing that surprised me was the secondary effect on the loan officers themselves. They had been so used to chasing down approvals that they'd built entire workarounds — like calling underwriters directly, or walking over to their desks. Once the email became clearer, those workarounds disappeared, and the whole process felt calmer. Luna: So the fix didn't just speed up the process, it reduced the ambient stress. Lucas: Right. And that's a benefit that's hard to measure on a spreadsheet, but it's real. One loan officer told them it felt like 'the system finally respects my time.' That's a powerful thing to hear from your team. Luna: Was there any downside? Did the rigid format cause problems for unusual cases? Lucas: They did have a few edge cases — like a complex multi-property deal that didn't fit neatly into the one-line summary. But they added a simple workaround: if you couldn't fit the ask in one line, you could attach a one-page memo and note that in the summary. It kept the discipline without being brittle. Luna: That's a smart concession. Because the goal isn't to be rigid, it's to reduce ambiguity. Lucas: Exactly. And that's the key takeaway for me: the format is a forcing function. It makes you think about what you're actually asking before you hit send. And that clarity compounds — fewer questions, fewer errors, faster decisions. Luna: So how would someone listening spot their own version of this? What's the diagnostic? Lucas: Look for the 'email tennis' pattern. If you're seeing long email threads that go back and forth with 'just checking in' or 'any update on this?' — that's a sign the original ask wasn't clear. Or if your team has developed workarounds like phone calls or hallway conversations to get things done, that's another red flag. Luna: And you don't need to redesign the whole process. You just need to find the single handoff that's causing the most friction. Lucas: Right. And the fix might not be an email template. It could be a shared document, a checklist, or even a color code. But the principle is the same: make the information architecture so obvious that the next person doesn't have to think. Luna: It's almost like you're designing for your future self, too. Because when you write a clear email, you're saving your own time when you have to look back at it later. Lucas: That's a great point. And it's interesting — the bank they actually kept the old emails in their archive, and they found that about 30 percent of the follow-up emails were just people asking for clarifications that were already answered in the original thread. So the change essentially eliminated an entire category of wasted work. Luna: Thirty percent of follow-up emails just disappeared. That's not nothing. Lucas: And that's the thing about operational improvements — they often pay for themselves in ways you don't anticipate. The bank didn't have to reduce headcount or cut costs; they just freed up time that got reinvested in faster service and more business development. Luna: So this isn't just a cost-saving move, it's a growth enabler. Lucas: Exactly. And I think that's the broader lesson for any business: before you invest in a new tool or a new process, ask yourself if there's a communication bottleneck that's making your current system slower than it needs to be. Sometimes the highest roi change is a template, not a technology. Luna: I love that. And it's a nice reminder that the best fixes are often the ones that feel almost too simple to be effective. Lucas: Yeah. So next time you're staring at a process that feels stuck, take a look at the emails. There might be a nine-day problem hiding in a three-second read.