Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How a Career Decision Log Landed a Promotion
Transcript
- Lucas: There's this phrase I keep coming back to when I talk to managers about promotions: 'If it isn't written down, it didn't happen.' And today I want to dig into one tool that makes that literal — the career decision log. Luna: A decision log? Is that different from just keeping a work diary? Lucas: Good question. A work diary is a record of what you did. A decision log is a record of how you thought. It's the reasoning, the trade-offs, the risks you weighed — and then what actually happened. It's the difference between saying 'I ran a vendor review' and 'I chose a vendor who was twenty percent more expensive because their uptime track record justified it, and here's the math.' Luna: So it's evidence of judgment. That sounds like exactly what promotion committees say they can't find. Lucas: Right. And the person I want to talk about — let's call her Priya — she was a senior operations manager at a logistics company. She'd been passed over for director twice. Her feedback was always the same: 'You do great work, but we don't see your strategic thinking.' Sound familiar? Luna: Yeah, I've heard that one before. It's code for 'you're not making your thinking visible.' Lucas: Exactly. So Priya decided she wasn't going to wait for someone to notice her. She started a decision log in a simple spreadsheet. Every time she made a call that involved trade-offs — and she made a rule: if it involved more than one option and a consequence, she logged it. Luna: What did an entry actually look like? Give me a concrete example. Lucas: Sure. So in month two, her team needed to replace a warehouse management system. The leading vendor was the cheaper one, but they had a history of downtime during peak season. Priya recommended the pricier vendor — about fifteen percent more — and her log entry spelled out the reasoning: estimated cost of one hour of downtime during peak, which was around one hundred and twenty thousand dollars in missed shipments and penalties. She calculated the break-even point. She documented the pushback from finance and how she addressed it by proposing a phased rollout to spread the cost. Luna: That's really specific. Did she log every decision like that? Lucas: Not every single one. That's important — she logged decisions that were significant, reversible, or visible. She had a simple filter: if the outcome could be measured, if it affected other teams, or if it involved more than five thousand dollars, it went in. The discipline was that she logged them within forty-eight hours, while the reasoning was still fresh. Luna: Forty-eight hours. That's the part most people would skip. Lucas: Absolutely. And here's the thing — she didn't just use it for big projects. She logged a decision to push back on a client deadline that would have burned her team out. She logged a decision to renegotiate a contract with a supplier. She even logged a decision to delegate a high-visibility task to a junior team member, because she knew it was a development opportunity — that one was about building others, not just delivering. Luna: So it's also a record of leadership behaviors, not just outcomes. That's smart. Lucas: By the time her next performance review came around, she had eighteen months of entries. She didn't walk in with the whole log — that would've been overwhelming. She selected three entries that told a story: one about cost savings, one about risk management, and one about team development. Luna: How did the review go? Lucas: Her manager was genuinely surprised. He said, 'I didn't know you were thinking about it this way.' And that's the whole point — he was judging her on the work he saw, not the thinking behind it. Priya's log made the thinking visible. Luna: And that's what led to the director promotion. Lucas: It was a key piece. She didn't get promoted just because of the log — she still had the results. But the log was what turned those results into a narrative. She could say 'here's the judgment that produced this outcome' instead of just 'here's what I did.' Luna: I love that. It's like turning your invisible work into a portfolio. Lucas: Exactly. And you know, this kind of habit — documenting your decisions — it's something we could all benefit from. And on that note, something that keeps this show and all the other Fexingo Business podcasts running is a small group of listeners who chip in a few dollars a month. If you've ever found a career tool like this useful, and you want to help us keep making these episodes ad-free, you can support us at buy me a coffee dot com slash fexingo. No pressure, but it genuinely helps. Luna: Yeah, it's a nice way to give back if this show's helped you think through a career move. We're grateful for everyone who does. Lucas: So back to Priya. After the promotion, she told me something that stuck: 'The log didn't just help my case — it helped me make better decisions.' Because when you know you're going to write it down, you're more deliberate. You question your own assumptions. You look for blind spots. Luna: That's a really good point. It's like a forcing function for self-awareness. Lucas: Exactly. And that's the thing that separates a decision log from just another spreadsheet — it changes how you think in real time. Priya said she started catching herself making snap decisions and then having to justify them later. So she'd slow down, consider alternatives, and that alone improved her judgment. Luna: What else did she learn about what to leave out? I imagine not everything is worth logging. Lucas: Great question. She had two rules for exclusion. First, she didn't log routine decisions that didn't involve trade-offs — like which vendor to email first. Second, she left out anything that was confidential or could be seen as political in a negative way. No 'I overruled my colleague' kind of entries. It was always about the business rationale, never about personalities. Luna: That's a smart boundary. Keep it professional and defensible. Lucas: And she also made sure each entry had a clear outcome — even if the outcome was 'decision delayed pending more data.' That showed she was comfortable with ambiguity, which is another leadership signal. Luna: So how would someone actually start this? What's the minimum viable format? Lucas: Keep it simple. Date, decision, options considered, rationale, expected outcome, actual outcome. That's six columns. You can do it in a spreadsheet or a notes app. The key is consistency — one entry per week is enough if it's a real decision. And then, before your next review, spend thirty minutes reading through it. You'll be amazed at the patterns you see. Luna: Patterns like what? Lucas: For Priya, she noticed she tended to overweigh cost savings versus long-term risk. That was a useful insight for her development. And she noticed she was making more decisions than she realized — which gave her the confidence to ask for more responsibility. Luna: That's powerful. It's not just a promotion tool, it's a self-improvement tool. Lucas: Exactly. And if you're thinking about your next promotion, start a log today. Even if you're six months out, that's twenty-six entries you'll have by then. That's a substantial body of evidence. Luna: I think I'm going to start one. Any final tip for making it useful in the moment? Lucas: One thing Priya did that I love: she wrote her entries like she was explaining her choice to a smart colleague who wasn't in the room. Not a formal report — just a clear, honest account. That made them easy to revisit and easy to share when needed. Luna: That's a great rule of thumb. Write it like you're explaining it over coffee. Lucas: Exactly. And if you do that, you'll have something most people don't: a transparent trail of your judgment. And that's what gets noticed.