Junior Analyst: Prioritize Your Next Experiment with Story Arc

Who This Helps

You're a Junior Analyst who just finished a deep dive. Now you have a pile of possible next experiments. Which one do you run first? This is for you if you want to ship clean analysis with clear recommendations — and stop wasting time on low-impact tests.

Mini Case

Meet Li Wei. She's a Junior Analyst at a subscription service. After pulling data on user churn, she found three possible experiments: a pricing change, a feature tweak, and a new onboarding flow. She used the Story Arc from the Data Storytelling for Stakeholders course to map each option against business impact and effort. The pricing change had a 12% potential lift but needed 7 days of engineering work. The onboarding flow had only a 3% lift but could ship in 2 days. Li Wei picked the pricing change — and her recommendation got approved in one meeting.

Do This Now (5 Steps)

1. List your experiment candidates. Write down every test you're considering. Don't filter yet.
2. Score each on impact. Use a simple 1-3 scale. 1 = small, 3 = big. Be honest.
3. Score each on effort. Same 1-3 scale. 1 = easy, 3 = hard.
4. Plot them on a 2x2 grid. Put impact on one axis, effort on the other. Your winner is high impact, low effort.
5. Write one key message. What's the single experiment you recommend? State it like Li Wei did: "Run the pricing test first."

Avoid These Traps

• The shiny object trap. Don't pick the experiment that sounds coolest. Stick to your impact-effort grid.
• The paralysis trap. Don't wait for perfect data. Use your best estimate and move.
• The kitchen sink trap. Don't recommend three experiments at once. Stakeholders need one clear ask.
• The ego trap. Don't ignore a low-effort win because it's not flashy. Small wins build trust.
• The forget-the-audience trap. Your stakeholder doesn't care about your process. They care about the decision.

Your Win by Friday

By Friday, you'll have one prioritized experiment recommendation. You'll present it with a clear ask and a short rationale. Your stakeholder will say yes — and you'll ship clean analysis that actually moves the needle. That's a good week.