⏱ Expected: 15:30 (min 0/100)
Talk track: Welcome to the final block. Everything you've built over these two days — the Manager OS, the hiring packet, the roadmap, the growth plans, the infrastructure plan — it all converges here. This block is about leading up: communicating with executives who have limited time and broad scope, handling failure honestly, and practicing the opening of your capstone QBR.
⏱ Expected: 15:30 (min 0/100)
Talk track: Take a breath and look at how far you've come. You've built more management artifacts in two days than most new managers create in their first six months. But none of it matters if you can't communicate it to the people who control your budget, your headcount, and your team's survival. This block is where you learn that skill.
⏱ Expected: 15:32 (min 2/100) | IC-to-Manager Shift (3 min)
Talk track: Before we get into frameworks, let me name the shift that nobody talks about. As a senior IC, you communicated up by presenting your analysis. Your audience cared about your methodology, your rigor, your findings. You were judged on the quality of YOUR work. As a manager, everything changes. You're presenting your team's impact, not your own analysis. Your audience cares about business outcomes, not methodology. Your ask is no longer "here's what I found" but "here's what my team needs." And when something goes wrong — when the dashboard is broken, when the model fails — you don't fix it yourself. You explain it and own it. That shift is why every framework in this block exists.
⏱ Expected: 15:35 (min 5/100) | Tentpoles (3 min)
Talk track: Before I give you the frameworks, let me show you where you'll actually use them. As a manager, your upward communication isn't ad hoc — it happens in recurring rituals. Weekly, you check in with your VP. Monthly, you present to a broader group. Quarterly, you do a QBR — a formal review with the exec team. When something breaks, you communicate the incident upward. And semi-annually, you look back and plan forward. Every framework I'm about to teach you is a tool for one or more of these moments. The Three Questions? That's your weekly VP check-in. BLUF? That's every single one of them. Art of the Ask? That's your QBR. Communicating Failure? That's the ad hoc moment you hope is rare.
⏱ Expected: 15:38 (min 8/100) | QBR Zoom-in (2 min)
Talk track: Let me zoom in on the QBR — the Quarterly Business Review. This is the highest-stakes ritual on your calendar. The CEO, CTO, CFO, and VP Product are in the room. They control your budget, your headcount, and frankly your team's existence. They expect four things: are we on track, what did we deliver, what's at risk, and what do you need. The work does not speak for itself — you speak for the work. Analytics teams that can't articulate their value in this meeting get quietly reorged out of existence. Your capstone deliverable simulates exactly this meeting. Everything I'm about to teach you prepares you for it.
⏱ Expected: 15:40 (min 10/100) | Exec Comm Frameworks (8 min)
Talk track: The Pyramid Principle comes from Barbara Minto at McKinsey. Start with the conclusion, then supporting arguments, then data if asked. BLUF is the military version of the same idea. Here's why this is hard for you specifically: your academic training taught you to build from methodology to conclusion. Executives want the opposite — conclusion first, evidence on request. Unlearning the academic structure is the single hardest communication habit to break. You practiced BLUF in Day 1 for your executive narrative, and in Block E when you wrote your VP proposal. Now you're applying it to the highest-stakes context — the QBR.
⏱ Expected: 15:40 (min 10/100)
Talk track: They make 30 to 50 decisions a day. By the time they get to your QBR, they've already made twenty decisions. They're not being rude when they check their phone — they're cognitively depleted. Your job is to make it easy for them. Front-load everything. Plan for five minutes — if you get fifteen, great, use it for depth. But if someone says "can you do it in five?" your answer has to be "yes."
⏱ Expected: 15:40 (min 10/100)
Talk track: There are exactly three things executives want to know. First: are we on track? Give me a color — green, yellow, red. Don't make me guess. Second: what are the risks? Don't hide bad news. Executives hate surprises more than they hate bad news. If your model is underperforming, say so and say what you're doing about it. Third: what do you need from me? This is the one people forget. Executives want to help — they want to unblock you. But you have to ask. If you don't need anything, say "no asks this quarter" — that's actually reassuring. Notice these are the same four things the QBR slide listed a moment ago. That's not a coincidence — these three questions ARE the QBR structure.
⏱ Expected: 15:48 (min 18/100) | Anti-Patterns + Managing Up (6 min)
Talk track: Let me show you the failure modes. The data dump is the most common — someone pastes fifty charts into a deck and calls it a QBR. There's no narrative, no "so what." The "everything is fine" deck destroys trust — every team has risks, and if you don't acknowledge yours, the exec assumes you're hiding them. The buried ask — someone spends forty-five minutes on status and then rushes their one critical request. The jargon wall — if your VP has to Google an acronym, you've lost them. And "but first, methodology" — this is the one that will trip YOU up specifically, because you were trained to show your work. Fight that instinct. Methodology goes in the appendix. Business impact goes on slide one.
⏱ Expected: 15:48 (min 18/100)
Talk track: I watched a brilliant analytics lead walk into a budget meeting and say "we need more resources." The CFO said "doesn't everyone?" and moved on. Three months later, the same person came back with a specific ask, a cost, and a consequence. She got the hire approved in that meeting. The difference was specificity. Frame your ask as a trade-off — give the exec a choice between two concrete options. And one ask per meeting. If you bring five, you get zero.
⏱ Expected: 15:48 (min 18/100)
Talk track: There's a difference between asking and escalating. You ask when you need something — a hire, a tool, a budget. You escalate when there's a decision you can't make alone — irreversible, cross-functional, legal. Always escalate with a recommendation. "I don't know what to do" is not an escalation — it's an abdication. And once the decision is made, disagree and commit. You can argue hard in the room. But once the call is made, execute fully. Passive-aggressive non-compliance — doing the thing you were told to do but doing it badly — is worse than open disagreement.
⏱ Expected: 15:54 (min 24/100) | Communicating Failure (10 min)
Talk track: Let's talk about what happens when analytics fails. And it will fail. Your dashboard will show the wrong number. Your A/B test will have a bug. Your model will make a prediction that costs the company money. What matters is how you respond. This is where the IC-to-manager shift hits hardest — as an IC, you'd fix it quietly. As a manager, you have to explain it upward while your team fixes it.
⏱ Expected: 15:54 (min 24/100)
Talk track: The best teams run blameless postmortems. Blameless doesn't mean no accountability — it means you focus on the system that allowed the failure, not the person who happened to trigger it. Use the 5 Whys to get to a systemic root cause. And every postmortem must produce action items with an owner — a specific human being, not a team — a deadline, and a verification method. Without those three things, your action items are wishes.
⏱ Expected: 15:54 (min 24/100)
Talk track: This is the conversation nobody wants to have. Here's the framework: lead with impact, not with methodology. Don't start with "so there was a join condition in the ETL that..." Start with "the revenue dashboard showed incorrect data for three days, and two pricing decisions were made using it." That's the difference between an IC explanation and a manager explanation. The IC wants to explain the technical cause. The manager leads with the business impact. Then what happened — brief, factual. Then what you're doing about it right now. Then the systemic fix — what changes so this can't happen again.
⏱ Expected: 15:54 (min 24/100)
Talk track: The absolute worst thing you can do is hide it. It always comes out. And now you have two problems: the incident and the fact that you tried to cover it up. The second worst thing is burying it in a long, defensive email. Your VP reads the first two lines. Use this subject line format — impact level, what happened, status. All in the subject line so they know what they're dealing with before they even open the email. Lead with impact. Be direct. Your VP will respect you more for it, not less.
⏱ Expected: 16:04 (min 34/100) | Discussion: delivering worst news (15 min)
⏱ Expected: 16:04 (min 34/100)
Talk track: Let's put this into practice. Think about the worst thing happening in your case context right now. Maybe a key dashboard is unreliable. Maybe a project is behind schedule. Maybe a hire fell through. Whatever it is — you have a meeting with your VP in one hour. What do you say first? Remember the IC-to-manager shift: your instinct is to explain the technical cause. Fight it. Lead with impact. Take two minutes to think silently. Then turn to the person next to you and practice saying it out loud — that's three minutes. Then I'll open it to the room.
⏱ Expected: 16:19 (min 49/100) | VP Relationship (3 min)
Talk track: You just practiced delivering bad news. That conversation only works if you've built the relationship first. All the frameworks — BLUF, Art of the Ask, the failure framework — they only work if your VP trusts you. And trust is built before you need it, not when you're desperate. Meet with your VP regularly — you request the meeting, not them. Always bring three things: what's on track, what's at risk, what you need. Never surprise them. And understand what THEY'RE being measured on. If your VP is measured on revenue growth, frame your updates around revenue impact. You're not being political — you're being relevant.
⏱ Expected: 16:22 (min 52/100) | First 90 Days (3 min)
Talk track: Before we practice the QBR, here's the map for everything you've learned. Your first 90 days as an analytics manager. Days 1 through 30: shut up and listen. Meet every stakeholder. Audit the infrastructure — you practiced that in Block E. Don't change anything yet. Days 31 through 60: fix one visible problem. Start your cadences. Begin your Manager OS. Days 61 through 90: present your first roadmap. Make your first hire recommendation. Deliver your first exec update using everything you learned today. Notice how everything from this course maps onto these 90 days. Your Manager OS, your hiring packet, your roadmap, your infrastructure plan, your executive communication skills. It all connects. And the QBR you're about to practice? That's your day 90 presentation.
⏱ Expected: 16:25 (min 55/100) | BLUF Rehearsal — expanded (15 min)
⏱ Expected: 16:22 (min 52/100)
Talk track: This is the capstone practice moment. You're going to write the opening of your async QBR and deliver it twice. Round 1: write four sentences — the three executive questions plus your ask. Three minutes to write. Then deliver to your partner in 60 seconds. Partner gives one piece of SBI feedback — what landed, what didn't. Round 2: take that feedback, revise, and deliver again. The second delivery is always dramatically better than the first. That improvement is the learning. Go.
⏱ Expected: 16:37 (min 67/100) | AI (3 min)
Talk track: One more thing before the QBR briefing. Think back to this morning. If you drew Scenario 9 — Liam's AI-generated report with fabricated stats — you practiced giving feedback for an AI-specific failure mode. If you calibrated Kevin, you debated whether AI-augmented volume with lower reviewability counts as high performance. In Block E, you wrote about how AI changes your infrastructure or governance. These aren't hypothetical scenarios — they're happening right now in analytics teams. When you record your QBR, your roadmap should reflect the reality that your team includes AI.
⏱ Expected: 16:40 (min 70/100) | Async QBR briefing (8 min)
Talk track: OK — you've learned the frameworks, you've practiced the opening, you've felt the difference between round one and round two. Now let me brief you on the deliverable.
⏱ Expected: 16:40 (min 70/100)
Talk track: You'll submit two things: a written QBR outline and a five-minute video. In the video, you're presenting to your executive team on Zoom. You already practiced the opening — the four sentences you just delivered to your partner. In Block E, you practiced writing a VP proposal in BLUF format. The async QBR is both of those at higher stakes — the QBR outline and video together are worth 10% of your grade. Use everything you learned today. Lead with BLUF. Answer the three questions. Make your ask specific. Anticipate pushback.
⏱ Expected: 16:40 (min 70/100)
Talk track: You'll be evaluated on five dimensions. The fifth one — anticipates pushback — is where you show you can think from the executive's perspective, not just your own. Imagine your CFO watching your video. What would they interrupt to ask? "Can we do this with fewer people?" "What's the ROI?" Address that question in your video before they would ask it. That's the difference between a presentation and a conversation — even when it's a recording.
⏱ Expected: 16:48 (min 78/100) | All Graded Work (3 min)
Talk track: Here's the full picture — everything that counts toward your grade. Twenty-five percent is already done or ongoing: participation and the Day 1 checkpoint. The remaining seventy-five percent is the portfolio, due one week from today. The biggest single component is Hiring Packet at twenty percent. Roadmap plus narrative is fifteen, and the QBR — outline and video together — is ten. Don't leave the video to the last night. Record it early, watch it back, re-record if the BLUF isn't clear in the first ten seconds.
⏱ Expected: 16:54 (min 84/100) | Reflection (2 min)
Talk track: Before I close — take out a piece of paper or open a blank doc. Write down three specific actions you will take in the next 90 days. Not "be a better manager." I want dates and specifics. "Start weekly 1:1s within two weeks." "Write a BLUF summary for every exec update starting next week." "Audit my team's data infrastructure in my first month." Two minutes. These are for you — I won't collect them. But research shows that writing down intentions dramatically increases follow-through. Go.
⏱ Expected: 16:56 (min 86/100) | Course close (8 min)
Talk track: And that brings us to the close. Let me tell you what you've accomplished.
⏱ Expected: 16:56 (min 86/100)
Talk track: In two days, you've built more management artifacts than most new managers create in their first six months. You have a team charter, a hiring packet, a roadmap, growth plans, an infrastructure assessment, and you've learned to communicate all of it to executives. That's not theory — that's practice.
⏱ Expected: 16:56 (min 86/100)
Talk track: The best analytics managers I know care deeply about their people — you practiced that this morning when you gave SBI feedback to a partner and wrote a development area for someone you calibrated. They communicate clearly with leadership — you practiced that this afternoon when you delivered your worst news to a partner, wrote a VP proposal in Block E, and just delivered your QBR opening twice. And they never stop learning — you showed that by spending two days building real management artifacts from scratch. I want to acknowledge something: managing people is hard, and you've been willing to practice it in a room full of your peers. That takes real courage. You now have the frameworks. You have the artifacts. You have the practice. Now go build great teams.