Who This Helps
This is for junior analysts who need to explain why a number tanked. You have the data, but the story is fuzzy. You want to ship a clean analysis with clear recommendations. The Finance Basics for Operators course gives you the framework to do that fast.
Mini Case
Imagine you track weekly revenue. Last week it dropped 12%. Your boss wants one root cause by Friday. You have 7 days of transaction logs, cost data, and customer counts. Where do you start?
In the Finance Basics for Operators course, one mission is "Unit Economics Snapshot." It teaches you to calculate contribution margin. That's your first clue. If margin slipped, the problem is cost or price. If units sold dropped, the problem is volume.
Do This Now (5 Steps)
- Pull the raw numbers. Get last week's revenue and the week before. Write them down. Example: Week 1 = $50,000. Week 2 = $44,000. Drop = $6,000.
- Split revenue into price and volume. Revenue = price x units sold. Did price change? Did volume drop? If price stayed at $100, then units fell from 500 to 440. That's a 12% volume drop.
- Check contribution margin. Contribution margin = revenue minus variable costs. If variable costs per unit stayed at $60, then margin per unit is $40. Total margin dropped from $20,000 to $17,600. That's a $2,400 loss.
- Look for one big driver. Scan your data for a single change. Maybe a key customer stopped ordering. Or a marketing campaign ended. In the "Cost Structure Triage" mission, you learn to find the top cost driver. Apply that here.
- Write one recommendation. Don't list everything. Pick one action. Example: "Restart the email campaign to the top 10 customers. Expected recovery: 8% volume increase in 2 weeks."
Avoid These Traps
- Don't blame everything on seasonality. Seasonality is real, but it's a lazy answer. Prove it with last year's data.
- Don't present raw numbers without context. A 12% drop means nothing alone. Compare to target or historical range.
- Don't skip the margin check. Revenue drop could hide a margin problem. Fix the wrong thing and you waste time.
- Don't recommend without a number. "Improve marketing" is weak. "Increase email frequency by 20%" is actionable.
- Don't overcomplicate. Three charts max. One root cause. One recommendation.
Your Win by Friday
By Friday, you'll have a one-page analysis with one root cause and one clear recommendation. Your boss will see you as the analyst who finds the real problem. And you'll feel like a finance operator, not just a number cruncher. Plus, you'll have a solid example for your next review. Not bad for a week's work.