Why the “easy” feature is always last in line.
The iPad launched in April 2010. Apple shipped its first built-in iPad Calculator in iPadOS 18, in 2024 — 14 years later. It wasn’t forgotten. It kept losing a math contest that every feature plays: prioritization. Try the model teams actually use below.
Drag to rotate · bars re-rank live
Tune “Calculator app”
RICE = (Reach × Impact × Confidence) ÷ Effort. Move the sliders and watch Calculator fight for a slot against four rival projects.
The formula, worked
RICE (from Intercom) scores a feature as:
Default Calculator example: Reach 60 (percent of users per quarter who might open it) × Impact 1.0 (nice, not transformative — everyone already has a phone calculator) × Confidence 0.8, divided by Effort 2 person-months = 24.0. Meanwhile “Fix crash & bug debt” scores 70 × 2 × 0.9 ÷ 3 = 42.0. The calculator loses — every quarter, for years.
Notice the trap: low effort helps the score, but low impact caps it. A feature that is merely convenient can be out-prioritized indefinitely by anything that moves retention, revenue, or platform strategy.
What the tweet gets right
“Apple can’t ship a calculator but will build your niche product in one update” is really a lesson about platform risk: a platform owner ships anything whose Reach × Impact beats its Effort — including your product’s core feature. That’s called Sherlocking (after Apple’s Sherlock absorbing the app Watson in 2002). If your startup’s moat is one obvious feature with huge reach, its RICE score inside Apple is enormous — you are on the roadmap whether you like it or not.
Defenses: own proprietary data, own the relationship (accounts, community), or serve a niche whose Reach is too small to clear a platform’s bar — the same math that protected you is the math that starved the calculator.