Who This Helps
This is for you, Junior Analyst. You see a KPI drop and need to explain it fast. You want to ship a clean analysis with clear recommendations, not a messy spreadsheet. The Finance Basics for Operators course gives you the framework to do this in one focused session.
Mini Case
Imagine you track weekly revenue. Last week it was $50,000. This week it's $44,000. That's a 12% drop. Your boss wants answers by Friday. You have 7 days to find the root cause and recommend a fix. No pressure, right? Let's make it simple.
Do This Now (5 Steps)
- Pull the numbers. Get the last 4 weeks of revenue data. Break it by product line. Look for the line that dropped most. In our case, Product A dropped 20%.
- Check the unit economics. Use the Unit Economics Snapshot mission from the course. Calculate contribution margin per unit. If margin is thin, a small drop in sales hurts more.
- Find the weak line. In our case, Product A's contribution margin is 30%. That's lower than Product B's 45%. The drop in sales of Product A caused most of the revenue loss.
- Ask why. Did a competitor lower price? Did a customer churn? Did a marketing campaign end? Check the data. In our case, one big customer stopped buying Product A.
- Recommend one action. Don't list 10 ideas. Pick one. For example: call the lost customer, offer a discount, or shift marketing to Product B. State the expected impact: if we win back that customer, revenue goes up 8%.
Avoid These Traps
- Don't overcomplicate. You don't need a 20-slide deck. One page with the root cause and one recommendation is enough.
- Don't guess. If you don't have data, say so. Then get it. Don't make up a story.
- Don't blame. Focus on the metric, not the person. Say "the drop came from Product A" not "the sales team failed."
- Don't ignore cash. Profit and cash are different. The Cash vs Profit Reality mission in the course explains why. A drop in revenue might still mean positive cash flow if costs are low.
Your Win by Friday
By Friday, you'll have a one-page analysis. It will show the root cause (Product A lost a customer), the impact (12% revenue drop), and one clear recommendation (win back that customer). Your boss will say "good work" and you'll feel like a pro. Plus, you'll have a repeatable process for next time. That's the win.
And hey, if you can explain a KPI drop in one page, you're already ahead of half the team. Keep it simple, ship it clean, and enjoy the weekend.