Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Owning Their Performance Review
Transcript
- Lucas: Luna, I want to talk about something that sounds almost too boring to matter — the annual performance review. Luna: Oh, the thing everyone dreads and half the people just recycle from last year? Lucas: Exactly. But there's a specific case — a woman named Aisha, mid-level operations manager at a regional bank — who turned her self-evaluation into a promotion document. She went from operations manager to director in six months, and the vehicle was literally that five-page form. Luna: Okay, you have my attention. I've seen a lot of people treat that form as a chore. What did she do differently? Lucas: First, she stopped thinking of it as a backward-looking report. Most people write a list of accomplishments — I did X, I led Y, I saved Z dollars. That's fine for a footnote, but it doesn't tell a story. Aisha reframed the whole thing as a strategic memo. She started with an executive summary that answered one question: 'What did I do this year that directly moved the bank's key metrics?' Luna: So she tied her tasks to the bank's actual priorities. That makes sense. But what were those metrics? Lucas: The bank had three big ones that year: reduce customer churn by 8 percent, increase cross-sell ratio from 1.4 to 1.7, and cut operational costs on the back-office side by 4 percent. Aisha's day job was managing the team that handled loan documentation processing. Not exactly glamorous. But she realized that when her team made errors, it delayed loan approvals, which frustrated customers and drove churn. So she quantified: every 1 percent reduction in documentation errors correlated with a 0.3 percent improvement in customer retention. She built a small data model to prove it. Luna: That is very different from 'I managed a team of five processors.' Lucas: Right. And here's where it gets clever — she didn't stop at past results. She devoted the last page of her self-evaluation to a proposal. She called it 'Next Horizon: Reducing Documentation Cycle Time to Boost Cross-Sell.' She basically pitched a new project that would free up loan officers to spend more time selling. She even estimated the revenue impact — $2.3 million annually if they hit her targets. Luna: Wait — she proposed a new initiative inside her performance review? That's gutsy. Did her boss know she was doing that? Lucas: She says she gave her boss a heads-up a week before the deadline — framed it as 'I want to make sure my review is useful for our planning conversation.' Her boss was initially skeptical, but Aisha had already run the numbers by the finance team, so the estimates were solid. By the time the formal review meeting happened, her boss's boss had already seen the document because Aisha had cc'd her on the submission. That was intentional. Luna: So she not only wrote a forward-looking review, she also made sure the right people saw it before the meeting. That's the part that feels harder — getting visibility when you're in the middle of the org chart. Lucas: Before we dive deeper — and this ties in, because it's literally about how we make these episodes possible — I'll mention that a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo. That's what funds us keeping this ad-free and focused on cases like Aisha's. If it's helpful to you, that's the place. Luna: Yeah, and it genuinely lets us dig into the details without cutting to a commercial break. So back to Aisha — how did she get her boss's boss to actually read the document? Lucas: She didn't send it as a cold attachment. She scheduled a 15-minute 'pre-read walkthrough' with her skip-level — the senior vice president of operations — three days before the formal review. The excuse was that she wanted to align her self-assessment with the division's strategic goals. That meeting lasted 25 minutes and ended with the SVP asking if she'd be interested in leading a pilot for the cross-sell initiative. Luna: Okay, so she basically created her own promotion conversation before the performance review even happened. But what about people in more rigid environments? I'm thinking of government, or heavily unionized shops, where the review process is locked down and you can't just add a proposal page. Lucas: That's a fair challenge. In those settings, the self-evaluation form might have strict character limits or specific fields. Aisha's approach can still work, but you adapt it. Instead of a separate proposal page, you use the 'career goals' section or 'development plan' field. You write something like: 'To prepare for next-level responsibilities, I would like to design a pilot that reduces documentation cycle time by 15 percent, which I estimate could generate $2.3 million in cross-sell revenue.' You keep it within the form's structure but you plant the seed. Luna: And you still share it with the skip-level beforehand? Lucas: If the culture allows it, yes. But if direct contact with skip-levels is discouraged, you can ask your boss to forward it. You say: 'I've included an aspirational goal in my review that I think aligns with what the SVP is prioritizing. Would you feel comfortable sharing that section in your 1-on-1 with her?' That way, you're not circumventing your boss, you're enlisting them. Luna: I like that — it turns the review into a collaborative document. Let's go back to the structure. You mentioned an executive summary. What else did Aisha include? Lucas: She had four sections. First, the executive summary — three bullet points that linked her work to the bank's three key metrics. Second, a 'Results vs. Targets' table where she listed each of her goals from the previous year, her actual results, and a brief explanation of variance. Third, a narrative called 'Cross-Functional Impact' — she documented five instances where her team's work helped other departments, like reducing loan processing time for the retail banking team. Fourth, the forward-looking proposal we talked about. Luna: The cross-functional piece is interesting. Most people only talk about their own team. But if you can show that you're making the whole organization better, that's a much bigger story. Lucas: Exactly. One of her examples: she noticed that the compliance team was constantly asking for rework on documentation because the loan officers weren't trained on new regulations. So she created a half-day training session for loan officers. Result: compliance rework dropped by 40 percent, and loan officers were happier because their deals closed faster. She gave the credit to the compliance team in the review, but her name was on the initiative. Luna: That's smart — she's generous with credit but still takes ownership. Did that come across in the document? Lucas: Absolutely. She wrote: 'I partnered with the compliance team to design and deliver a training module that reduced rework by 40 percent. The success was a direct result of collaboration with Jane in Compliance and Tom in Retail Lending.' She named them. That built goodwill and also showed she could lead cross-functionally without claiming all the glory. Luna: So the document itself becomes a piece of networking. People feel good about being mentioned, and they're more likely to support you later. Lucas: Right. And that leads to the outcome: six weeks after her review, she was asked to lead a larger project. Four months after that, when the director role opened up, she had a portfolio of visible work and testimonials from two VPs who had been copied on her review. She got the promotion without formally applying. Luna: Whoa — she didn't even apply? The role was just offered to her? Lucas: That's the ideal scenario, right? The review document had made her visible enough that when the position was created, the SVP thought of her first. She went through a formal interview process, but it was more of a formality. The decision had already been made. Luna: Okay, but let's be realistic — not every company works that way. Some places require you to apply and go through a panel. How does the review help in that scenario? Lucas: It still helps, because your self-evaluation becomes part of your application packet. When you apply for an internal role, the hiring manager often asks for your recent performance reviews. If yours reads like a strategic document instead of a list of tasks, you stand out. Aisha's approach gave her a narrative she could reuse in her cover letter and interviews. Luna: So it's not just about the review itself — it's about creating a document that you can leverage across multiple opportunities. Lucas: Exactly. And the timing matters. Aisha started working on her self-evaluation six weeks before the deadline. She collected data, talked to stakeholders, and refined her language. Most people spend two hours the night before. She invested maybe 20 hours over a month. That's the difference. Luna: Twenty hours feels like a lot. But if it leads to a promotion that comes with a 20 percent raise, the ROI is pretty clear. Lucas: It is. And you don't have to do it all in one go. She blocked off one hour every Tuesday and Thursday to work on it. It was a side project for a month. Luna: One more thing — what about the tone? How do you avoid sounding like you're bragging or inflating your role? Lucas: Aisha used data as a shield. When you say 'I saved $500,000,' it sounds like a claim. When you say 'The process changes my team implemented reduced rework by 30 percent, resulting in $500,000 in cost savings, as validated by the finance team,' it sounds like a fact. Data shifts the perception from self-promotion to reporting. Luna: That's a good rule. Let me ask you this — if someone is in their first performance review at a new company, can they still use this strategy? Lucas: Absolutely, but you adjust the forward-looking part. You might not have enough data to show past impact. So you lean into what you've learned in the first few months and propose a project based on that learning. For example: 'I've observed that the onboarding process for new hires takes 45 days, which is above industry average. I'd like to lead a project to reduce that to 30 days by streamlining the documentation handoff.' That shows you're already thinking strategically. Luna: That's smart — it turns your lack of history into an asset because you have fresh eyes. Lucas: Exactly. And one last thing — after she got the promotion, Aisha sent a thank-you note to every person she had named in her review. She said it was the best investment of 30 minutes she ever made. Those people became her strongest advocates in the new role. Luna: So the performance review isn't just a form — it's a relationship-building tool, a career narrative, and a pitch document all in one. Lucas: That's the takeaway. Your next review is probably months away. But if you start preparing now — even an hour a week — you can turn that boring form into the document that changes your trajectory.