Talk track: Welcome to the last block of Day 1. You have your Manager OS and your hiring plan. Now we answer the question every executive asks: where is this team going, and why should I fund it? By the end of this block you will have a roadmap, the start of an executive narrative, and you will have survived your first red-team exercise. We also have a hard stop at 17:10 for the Day 1 Checkpoint submission.
⏱ Expected: 15:30 (min 0/100)
Talk track: Three outcomes for this block. You'll build a roadmap, start an executive narrative, and survive a red-team exercise.
⏱ Expected: 15:32 (min 2/100)
Talk track: Roadmaps for analytics teams are fundamentally different. A product team ships features users can see. Your best work is often invisible — the analysis that prevented a bad launch, the data quality fix nobody noticed. The roadmap is your translation layer. Without one, you are at the mercy of whoever yells loudest.
⏱ Expected: 15:32 (min 2/100)
Talk track: A good roadmap does four things. It translates your work into business language. It protects your team from drive-by requests. It creates mutual accountability. And it forces explicit trade-offs instead of implicit ones where your team burns out trying to do everything.
⏱ Expected: 15:32 (min 2/100)
Talk track: Here is what we are building. North Star and guardrails, RICE-scored initiatives, a Now/Next/Later roadmap, an executive narrative, and a red-team exercise. Everything feeds into your Day 2 QBR, so treat this as a real draft.
⏱ Expected: 15:32 (min 2/100)
Talk track: The single biggest mistake new analytics managers make is treating the roadmap like a project plan. A Gantt chart says we will deliver feature X on March 15th. A roadmap says we believe investing in churn modeling this quarter will reduce monthly churn by two percentage points, and here is why we believe that. If your roadmap has specific dates on it, you have built a Gantt chart and you will be held to those dates. Roadmaps communicate direction, priorities, and trade-offs. They are living documents that change as you learn.
⏱ Expected: 15:32 (min 2/100)
Talk track: Analytics work has inherent uncertainty — you do not know what you will find in the data until you look. You promised March 15, the data was messy, and by the time you delivered in April, Marketing had lost confidence and hired a consultant. This is the Gantt chart trap.
⏱ Expected: 15:32 (min 2/100)
Talk track: Now contrast the Gantt chart approach with a roadmap-style commitment. Churn modeling is our top priority this quarter. We expect to deliver within Q1. Biggest risk is data completeness. This is honest. When the timeline shifts, you are updating an estimate, not breaking a promise. The trust dynamics are completely different. Executives can handle uncertainty. What they cannot handle is being surprised.
⏱ Expected: 15:37 (min 7/100)
Talk track: The three-horizon model is the simplest roadmap structure that actually works. The Now column is what your team is actively building this quarter. These items are committed and staffed. The Next column is what you plan to do next quarter, scoped enough that you could start tomorrow if priorities shifted. The Later column is directional — it shows where you think the team is heading, but the details are intentionally vague.
⏱ Expected: 15:37 (min 7/100)
Talk track: The key insight is that commitment level decreases as you move from Now to Later. You are making strong promises about Now, tentative plans for Next, and directional bets for Later. This is honest and it protects you from the Gantt chart trap we just discussed.
⏱ Expected: 15:42 (min 12/100)
Talk track: Each item must answer why it matters to the business — not to your team. T-shirt sizing gives enough info for trade-offs without false precision. Dependencies must be visible. The VP test: can someone two levels above you understand this without a follow-up question?
⏱ Expected: 15:42 (min 12/100)
Talk track: RICE comes from Intercom. Reach is how many people or dollars are affected. Impact is how much it moves the needle. Confidence is your honest assessment. Effort is person-months plus compute costs — GPU training and LLM API costs can dwarf labor. The real value is the conversation it forces: when you cannot estimate Reach, that tells you to do more discovery.
⏱ Expected: 15:42 (min 12/100)
Talk track: Here is the important thing about RICE: the score is not the answer. The score is the starting point for a conversation. If the model says project A scores higher than project B but your gut says otherwise, that disagreement is the most valuable part of the exercise. Dig into it. Maybe your gut is picking up on a dependency the score does not capture. Maybe your confidence estimate is too generous. The point is not to let a formula make your decisions. The point is to make your reasoning visible so other people can challenge it.
⏱ Expected: 15:42 (min 12/100)
Talk track: Four initiatives head-to-head. The Data Quality Audit scores highest because it touches everything and costs one person-month. The unsexy work wins — that is RICE working as intended, challenging your assumptions about what is most valuable.
⏱ Expected: 15:42 (min 12/100)
Talk track: Now watch what happens when you adjust confidence on the Experimentation Platform from fifty to thirty percent. The score drops from twenty-five hundred to fifteen hundred. Does that change your Q1 plan? These are the conversations RICE is designed to provoke. RICE tells you where to argue, not what to decide.
⏱ Expected: 15:48 (min 18/100)
Talk track: Every analytics team needs a North Star metric — the single number that best captures the value you deliver to the business. For a growth analytics team, it might be monthly active paying users. For a risk analytics team, it might be loss rate. The North Star gives your team focus. Below the North Star sit your guardrails. These are the metrics that must not get worse while you pursue your North Star.
⏱ Expected: 15:48 (min 18/100)
Talk track: Guardrails are the metrics that must not get worse while you chase the North Star. If your North Star is revenue per user, your guardrails might be user satisfaction and data quality SLA adherence. Without guardrails, you optimize yourself into a corner.
⏱ Expected: 15:48 (min 18/100)
Talk track: The North Star is the number your team rallies around. Guardrails constrain how you pursue it. Input metrics are the levers your team can actually pull — activation rate, retention rate. Without input metrics, you have a destination but no steering wheel.
⏱ Expected: 15:48 (min 18/100)
Talk track: Four common mistakes. Vanity metrics that feel productive but drive no outcome. Metrics you cannot influence. Metrics that move too slowly to steer by. And metrics you cannot actually measure.
⏱ Expected: 15:48 (min 18/100)
Talk track: The test is simple. Three questions. Can your team directly influence it? Does it move when you do good work? Does leadership care about it? If the answer to all three is yes, you have found your North Star. If any answer is no, keep looking. Do not settle for a metric that fails even one of these tests — it will steer your team in the wrong direction for an entire quarter before you realize the problem.
⏱ Expected: 15:48 (min 18/100)
Talk track: The metrics tree is the bridge between your team's daily work and the number the CEO reports to the board. Start at the top with the business outcome your executive sponsor cares about most. Then identify your North Star. Break that into input metrics, the levers your team can actually pull.
⏱ Expected: ~15:48 (min 18/100) | SKIP — advance past
Talk track: At the bottom, list the specific activities that move those input metrics. When a stakeholder asks why you are spending three weeks on churn modeling, you point to the tree. If you cannot draw this tree, your roadmap is disconnected from the business.
⏱ Expected: 15:52 (min 22/100)
Talk track: Frame trade-offs as choices, not complaints. Never say "we can't" — instead say "here's what it would cost." Quantify cost of delay. And remember: Product and Engineering are partners, not opponents.
⏱ Expected: ~15:52 (min 22/100) | SKIP — advance past
Talk track: Let me script out how this actually sounds in practice. Your VP of Product shows up wanting a dashboard for a feature launch. This happens every week in every analytics team. The wrong way is to say we do not have bandwidth. That is a wall. The VP hears no, gets frustrated, and either goes around you or escalates to your boss. Either way, you lose.
⏱ Expected: ~15:52 (min 22/100) | SKIP — advance past
Talk track: Start with "absolutely" — that is a yes. Lay out options with real costs. You never said no. You made the trade-off visible and made it their decision. Nine times out of ten the VP picks option two or three, and you are a strategic partner, not a bottleneck.
⏱ Expected: 15:55 (min 25/100)
Talk track: The two-page executive narrative is the most important document an analytics manager writes. Five sections, written in prose — not bullets. Prose forces clarity of thought. This is the document your VP forwards to the C-suite. Every word matters.
⏱ Expected: 15:55 (min 25/100)
Talk track: Let me show you what each section looks like when it is done well. This is a condensed example for a fictional analytics team at MarketBridge, the two-sided marketplace. Look at the Context section — three sentences, and you know the team size, what they support, and where they stand. No jargon.
⏱ Expected: 15:55 (min 25/100)
Talk track: The What We Did section has one clear outcome with before and after numbers, and it shows who actually uses the work. Customer Success reviews the top fifty at-risk accounts weekly — that shows your work is integrated into a real business process, not sitting on a shelf.
⏱ Expected: 15:55 (min 25/100)
Talk track: The What We Learned section is where most narratives fall flat. People write platitudes. This example shares a genuine surprise — product usage intensity is a weaker churn predictor than support ticket sentiment. That is the kind of insight that makes a VP lean forward.
⏱ Expected: 15:55 (min 25/100)
Talk track: The What is Next section explains the priority, quantifies the opportunity cost in analyst-months, and explains why this is the highest-leverage investment. Every section earns the reader's attention by being specific, quantified, and connected to business outcomes.
⏱ Expected: 15:55 (min 25/100)
Talk track: And What We Need is a specific, dated ask with a clear consequence. Not we need more resources, but we need the event schema migration by April fifteenth or our Q3 initiative is blocked. Notice the pattern: specific, quantified, and connected to business outcomes.
⏱ Expected: 16:00 (min 30/100)
Talk track: BLUF — Bottom Line Up Front — is a military communication concept that every analytics manager should internalize. Executives do not have time to read through your methodology to find the conclusion buried on page two. The bad example buries the lead under a pile of process description. The good example takes six seconds to read and communicates the most important information immediately. That is respect for your reader's time.
⏱ Expected: 16:00 (min 30/100)
Talk track: Four rules. No jargon — if you write AUC in an executive narrative, you have failed. Quantify everything. One page, one main idea. And write for the person with three minutes between meetings. Every sentence must earn its place.
⏱ Expected: 16:03 (min 33/100)
Talk track: A risk register forces you to name what could go wrong. Your top three risks should appear on slide two of every executive presentation — right after the summary. Executives trust leaders who name risks early.
Talk track: You have 30 minutes. Define your North Star and guardrails. Brainstorm at least eight initiatives — do not self-censor. RICE score each one. Place them into Now, Next, and Later. Use the template. I will circulate to help.
Talk track: Twenty minutes. Focus on Context and What is Next. Write in complete sentences — bullets are tempting but resist. This draft feeds into your Day 2 QBR. Polish comes later.
Talk track: Pair up with someone from a different case context. Eight minutes — four each direction. Find the fatal flaw. Be constructive but do not pull your punches. This simulates what happens when you present to your VP. Better to find the flaws now.
⏱ Expected: 17:06 (min 96/100) | Debrief (1 min)
Talk track: Raise your hand if your partner found a flaw you had not considered. Good — that is the point. Take thirty seconds to jot down the key insight. You will update your roadmap after class — this is exactly what happens in real quarterly planning.
⏱ Expected: 17:07 (min 97/100) | Checkpoint upload + Close
Talk track: By 17:10 you need to submit three artifacts. These are drafts — I am grading on completeness, not polish. If a section is rough, fine. If it is empty, not fine. This checkpoint is worth 10 percent of your grade, pass-fail. Upload before you leave the room.
⏱ Expected: 17:07 (min 97/100) | Checkpoint upload + Close
Talk track: Day 2 next Monday. Block D is growth and performance. Block E is infrastructure — data stacks, build versus buy, working with engineering and IT. Block F is executive communication — leading up, handling failure, and your async QBR. Before then: continue your hiring packet, draft your PGP, and review your roadmap.
⏱ Expected: 17:07 (min 97/100) | Checkpoint upload + Close
Talk track: That wraps Day 1. Let's take a moment to look at what you've built.
⏱ Expected: 17:07 (min 97/100) | Checkpoint upload + Close
Talk track: You walked in this morning with a case context and an empty folder. You now have a team charter, a stakeholder map, a hiring plan, a roadmap, and an executive narrative. That is the core of a Manager OS. Day 2 adds the people dimension, infrastructure planning, and executive communication. Submit your checkpoint artifacts now. See you on March 23.