This executive brief earns you visibility

 

The BIR framework for executive email updates Inside my program, I teach something called the BIR method. It forces your thinking to level up before you hit send.   BIR = Bottom Line, Insight, Result.   A three bullet update. And each bullet has a job.   B: Bottom Line State your recommendation or POV in one clear sentence. This is where most updates go wrong. People lead with context because they’re trying to be “thorough.”   Executives lead with the point. “What do I recommend?” “What decision or alignment do I need?” “What is the headline?”   Check in: One sentence. If it takes three, you don’t have a bottom line yet.   I: Insight Share 1 to 2 key signals or data points that shaped your bottom line. This is where you prove you’re not guessing, and you can make a judgment call.   “What’s the one number that matters?” “What changed that informed this recommendation?” “What’s the key risk or constraint?”   Check in: 2 to 3 insights max. If you have 6, you haven’t prioritized.   R: Result Show the impact, trade-off, or business outcome. This is the “executive” part. Because VPs don’t just want information. They want consequences.   “What does this protect or unlock?” “What are we trading off?” “What happens if we do nothing?”   Check in: Connect upward. If there’s no impact on goals leadership cares about, it’s noise.   Plug and Play Template: a VP-level BIR status update Here’s what a strong BIR update actually looks like.   Subject: [Topic] Decision needed by [Day/Date] Bottom line: I recommend [Option A] to achieve [desired outcome] by [date]. Insight: Key signals: [1 metric or signal] and [1 risk/constraint]. Result: This will [business impact/protection]. The trade-off is [what you give up]. I need [decision/approval/alignment] by [date].   Optional add-on (only if useful): Details and supporting data: [link / doc / attachment]   Example: Subject: [Project] Recommendation for next step Bottom line: I recommend delaying launch by 2 weeks to reduce risk without losing adoption. Insight: Early feedback shows meaningful onboarding drop-off and we found a critical bug in testing that will impact first-run success. Result: This protects Q3 targets and avoids a messy rollback, but we need alignment today so we can reset timeline and comms.   That’s it. No diary. No play-by-play. No “here’s everything we did this week.” A clear concise and contextual update.   Why executives remember this format Because it matches how senior leaders think.   Executives evaluate outcomes, not activity. They want what changed and what it means. Bottom line first signals ownership. You’re not reporting. You’re leading. Result forces trade-offs and judgment. Which is what separates “Junior updates” from “executive brief”.     And when you write like this consistently, leaders start coming to you differently.   They ask you questions that sound like: “What do you recommend?” “What’s the trade-off?” “Walk me through the decision.”   That’s not just better communication. That’s repositioning with your most important stakeholders.