Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Use Strategic Follow-Up After a Big Meeting
Transcript
- Lucas: Let me ask you something, Luna: when was the last time you had a really productive meeting — not one of those status-update things, but a real decision-making conversation — and then you walked out, and the next day, nothing happened? Luna: Honestly, that happens to me more than I'd like. You leave thinking everyone's aligned, and then two weeks later you realize nobody followed through. Lucas: Right. And the culprit is almost always the same: no strategic follow-up. I'm not talking about a quick 'thanks for your time' email. I mean a deliberate, structured follow-up that locks in decisions, clarifies next steps, and — crucially — reinforces your position in the room. Luna: So you're saying the meeting isn't over when the meeting ends. Lucas: Exactly. The meeting is the first inning. The follow-up is where you actually win or lose. And yet most people treat it like a chore — they dash off a one-liner or they wait too long and the momentum dies. Luna: What's 'too long'? I've heard twenty-four hours is the sweet spot. Lucas: Depends on the context. For a high-stakes decision with a senior leader, forty-eight hours is actually better. It gives you time to reflect, gather any supporting data, and write something that doesn't sound rushed. I'll give you a concrete example. Luna: Please. Lucas: A product manager I know — let's call her Priya — was up for a promotion to senior PM. She had a one-hour meeting with the VP of product to pitch a new feature roadmap. The VP was interested but noncommittal. Most people would have sent a quick 'thanks' and waited. Priya did something different. Luna: What did she do? Lucas: She waited exactly forty-eight hours. Then she sent a three-paragraph email. First paragraph: a one-sentence summary of the decision they'd reached — which was, 'we're going to prioritize the customer onboarding improvements over the new analytics module.' Second paragraph: she named two action items, one for herself and one for the VP. And third paragraph: she explicitly credited a colleague in the meeting who had suggested a key insight. That last part is crucial. Luna: Crediting someone else — that's smart. It shows you're not just self-promoting, you're a team player. But does it actually move the needle on your promotion? Lucas: In her case, yes. The VP later told her manager that the follow-up 'made the decision real.' It forced closure. And by crediting the colleague, she built social capital — that colleague became an advocate. She got the promotion three months later. Luna: Okay, but I can think of a risk. If you follow up too formally, especially with a senior leader, it can come across as presumptuous — like you're trying to hold them accountable before they've had time to think. Lucas: That's a great point. The key is calibration. With a peer, you can be more direct. With a boss, you frame it as 'here's what I heard, please correct me if I'm wrong.' With a senior executive, you want to make it easy for them to say 'yes, that's right' without committing too much. Luna: So the language matters as much as the timing. Give me a template for each. Lucas: For a senior leader, something like: 'Thanks for the conversation on Tuesday. My understanding is that we're moving forward with the onboarding changes, and I'll draft a timeline by Friday. Please let me know if I've missed anything.' That's low-pressure and invites correction. Luna: And for a peer? Lucas: More direct: 'Great meeting. I'll take point on the data pull. Can you confirm you'll set up the stakeholder review by Thursday?' You're locking in accountability. Luna: I like that. But what about the channel? Is email always best? I've seen people follow up on Slack right after a meeting and it feels too immediate. Lucas: Slack is for quick confirmations. For anything with decisions and next steps, email is better because it's searchable and permanent. But here's a nuance: if you're following up with someone who primarily communicates via Slack, mirror their style. The rule is: match the channel of the person with the most power in the room. Luna: That makes sense. So let's talk about the content itself. You mentioned three paragraphs. What if the meeting didn't produce a clear decision? Do you still follow up? Lucas: Absolutely. In fact, that's when follow-up is most powerful. If the meeting ended ambiguously, your follow-up can crystallize the open questions and propose a path forward. You're essentially doing the work of synthesis that nobody else is doing, which positions you as the person who drives action. Luna: That's a big claim. Can you give me a real-world example where that worked? Lucas: Sure. I worked with a marketing director who attended a cross-functional meeting about a product launch. The meeting ended with three conflicting priorities and no owner. She sent a follow-up that said: 'I heard three potential directions. Based on our budget constraints, I'd recommend Option A. I've drafted a brief and can share it by Wednesday. Would anyone like to suggest adjustments before I proceed?' She effectively set the agenda. Luna: And nobody pushed back? Lucas: One person did. But because she had documented the options and her reasoning, the discussion stayed constructive. Within a week, her recommendation became the plan. She got credit for unblocking the team. Luna: Okay, I'm convinced. But I want to push on one thing: the risk of over-following-up. If you send a recap after every single meeting, people might start ignoring you. Lucas: You're right. Strategic follow-up means being selective. I'd say follow up for meetings where a decision was made, where you have a clear action item, or where the outcome affects your work. If it's a routine status meeting, a quick one-liner to your immediate team is fine. The goal is to add value, not to create noise. Luna: So the bar is: would the recipient benefit from having this in writing? If yes, send it. If not, skip it. Lucas: Exactly. And here's another layer: the best follow-ups don't just recap — they also tee up the next conversation. You end with a forward-looking question: 'Should we schedule a follow-up in two weeks to review progress?' That keeps the momentum going and shows you're thinking ahead. Luna: That's a good habit. I'm going to try that. But I wonder — does this apply differently in remote or hybrid settings? Because when you're not in the same room, the follow-up is even more important. Lucas: Way more important. In remote meetings, people multitask. They might not have absorbed everything. A well-written follow-up becomes the single source of truth. And because there's no hallway conversation afterward, the follow-up is your only chance to reinforce your contribution. Luna: Right. So if I'm on a Zoom call with my boss and two other directors, I should send a follow-up that highlights the key decisions and my action items, and I should CC everyone who was there. Lucas: Yes, but be careful about cc ing too many people. If you're following up after a one-on-one, keep it between the two of you. For a group meeting, include everyone. And if you're following up with a senior leader, consider bcc ing yourself so you have a record without cluttering their inbox. Luna: That's a pro tip. I've never thought of bcc ing myself. Lucas: It's a small thing, but it helps you track your follow-ups and refer back later. Alright, let me bring this home with a framework I like. Think of it as the three T's: timing, tone, and takeaway. Luna: Okay, walk me through each one. Lucas: Timing: within 24 to 48 hours, depending on the stakes. Tone: calibrated to the recipient — deferential for senior leaders, collaborative for peers, direct for reports. Takeaway: always include one clear action item or decision that moves the ball forward. If your follow-up doesn't have a takeaway, it's just a thank-you note. Luna: And what about the subject line? Does that matter? Lucas: Huge. Use a subject line that makes the email easy to find later. Something like 'Follow-up: Q3 Budget Meeting — June 18, 2026' or 'Recap: Product Roadmap Discussion.' Avoid vague subjects like 'Thanks' or 'Meeting follow-up.' Luna: That's practical. I'm going to start doing that today. Lucas: Quick honest thing — we're able to make episodes like this because of listeners who chip in monthly through buy me a coffee dot com slash fexingo. No ads, no sponsors, just a small group of people who find the show useful and want to keep it going. If you've ever used a follow-up tip from this show and it worked for you, that's the reason we keep making them. Luna: Yeah, it's a good model. And it keeps us honest — we don't have to cater to advertisers, just to our listeners. So if you get value from the show, consider joining that group. Lucas: Alright, back to the follow-up. One more angle I want to touch on: the strategic follow-up when you didn't get what you wanted in the meeting. Luna: Ooh, that's interesting. So the meeting didn't go your way, but you still follow up? Lucas: Especially then. If your proposal was rejected, a strategic follow-up can keep the door open. You write something like: 'I appreciate the feedback on the proposed timeline. I'll revise the plan with the constraints we discussed and share a new version next week.' That shows resilience and a willingness to adapt. Luna: And it prevents the idea from dying completely. You're essentially buying time to regroup. Lucas: Exactly. The worst thing you can do after a setback is go silent. Silence signals defeat. A follow-up signals that you're still engaged and looking for a path forward. Luna: That's a great mindset. I think the takeaway for me is: the follow-up is not an afterthought. It's a continuation of the conversation, and it's where you either lock in your wins or recover from losses. Lucas: That's the whole episode right there. The meeting is where you pitch. The follow-up is where you close.