RICE Prioritisation Framework applied on FilmSlate

Question 1

What was the goal of the FilmSlates onboarding optimisation project?

Answer 1

o increase activation from 32% to 40% by reducing friction in sign‑in and onboarding.

Question 2

How does RICE help prioritise onboarding changes?

Answer 2

RICE compares ideas using Reach, Impact, Confidence, and Effort, showing which changes deliver the most activation improvement per unit of work.

Question 3

What was the Reach for the onboarding changes?

Answer 3

All new sign‑ups (~2,000/month). Email‑only login, role selection, and trial banner each reached the full onboarding population.

Question 4

How was Impact estimated for each change?

Answer 4

Email‑only login → High (2), reduces friction.

Role selection → Medium (1), personalises experience.

Trial banner → Medium (1), clarifies value and nudges activation.

Question 5

How was Confidence scored?

Answer 5

Email‑only login → High (80–100%), backed by benchmarks.

Role selection → Medium (70–80%), supported by interviews.

Trial banner → Low (50–60%), less tested.

Question 6

How was Effort estimated?

Answer 6

Email‑only login → 0.5 person‑months.

Role selection → 1 person‑month.

Trial banner → 0.5 person‑months.

Question 7

What were the RICE scores for each change?

Answer 7

Email‑only login → 7,200 (highest).

Trial banner → 2,400.

Role selection → 1,400 (lowest).

Question 8

What did the RICE scores reveal about prioritisation?

Answer 8

Email‑only login was the most impactful per effort, trial banner second, and role selection lowest. This sequencing helped explain trade‑offs transparently.

Question 9

How can this example be used in interviews?

Answer 9

“I applied RICE to FilmSlates onboarding changes. Email‑only login scored highest, so we prioritised it first. This showed stakeholders how we balanced reach, impact, confidence, and effort to hit our activation goal.”

Question 10

Interview Tip

Answer 10

If asked about this, you can say:
“In RICE, Effort is a rough estimate of person‑months, not a detailed sprint plan. For FilmSlates, email‑only login and trial banner were small engineering/design tweaks, so 0.5 person‑months was realistic. Role selection was heavier, so we estimated 1 month. The point was to compare relative effort, not to forecast exact delivery timelines.”

Question 11

Clarify the Purpose of RICE Effort

Answer 11

Effort in RICE is relative, not absolute.

It’s meant to compare options consistently, not to forecast exact delivery timelines.

You can explain: “We’re not committing to delivery dates here — we’re comparing relative effort so we can prioritise.”

Question 12

Show the Breakdown

Answer 12

Email‑only login (0.5 person‑months):

Mostly backend/frontend tweaks.

Minimal design work.

One engineer could complete in ~2 weeks.

Role selection (1 person‑month):

Requires UX design, new UI, backend logic, testing.

More complex, hence higher effort.

Trial banner (0.5 person‑months):

Lightweight UI addition with copywriting and analytics tagging.

Small design + frontend work.

By showing the reasoning, you make the numbers credible.

Question 13

Anchor Against Benchmarks

Answer 13

Compare with similar past tasks: “When we simplified login for another product, it took about 2 weeks. That’s why we estimated 0.5 person‑months here.”

Stakeholders trust estimates more when they see precedent.

Question 14

Emphasise Relative Comparison

Answer 14

Even if the numbers feel “low,” the important point is relative ranking.

Email‑only login is clearly lighter than role selection, so it should score higher.

You can say: “Whether it’s 2 weeks vs 4 weeks or 0.5 vs 1 person‑month, the ratio is what matters.”

Question 15

Invite Engineering Validation

Answer 15

Don’t defend alone — involve engineers early.

Ask: “Does 0.5 person‑months feel right for email‑only login? If not, what’s a better estimate?”

This builds trust and shows you respect their expertise.

Question 16

Interview Tip
If asked about effort estimation, you can say:

Answer 16

“In RICE, effort is a rough, relative measure. For FilmSlates, email‑only login and trial banner were small tweaks, so we estimated 0.5 person‑months. Role selection was heavier, so 1 month. The point wasn’t precision but relative comparison. I validated these estimates with engineering to ensure credibility.”

Question 17

Scenario: Engineer Pushback
Engineer: “0.5 person‑months for email‑only login feels way too low. We’ll need more time.”

Answer 17

Strong Response Structure
Acknowledge Expertise
“I hear you — engineering effort is always best validated by the team.”
→ Shows respect, avoids defensiveness.

Clarify RICE’s Purpose
“In RICE, effort is a relative estimate to compare options, not a delivery commitment. The goal was to highlight that email‑only login is lighter than role selection.”
→ Reframes the discussion around prioritisation, not deadlines.

Invite Validation
“If you think it’s closer to 1 person‑month, let’s adjust. The important thing is the ratio — email‑only login should still score higher than role selection.”
→ Keeps transparency, shows flexibility.

Anchor with Evidence
“We based 0.5 months on similar past work where simplifying login took about 2 weeks. But if this case has hidden complexity, I’d rather update the estimate now than risk surprises later.”
→ Builds credibility with precedent.

Question 18

Interview Tip
If asked about this in an interview, you can say:

Answer 18

“In RICE, effort is a rough, relative measure. For FilmSlates, we estimated email‑only login at 0.5 months because it was a small tweak, while role selection was heavier at 1 month. When engineering challenged the estimate, I clarified that RICE isn’t about exact timelines but relative comparison, and I invited them to adjust. That way, prioritisation stayed transparent and collaborative.”