Product work needs plans a team can ship as tests: a stated theory, a measured baseline, and a sample size fixed before the first user hits the treatment. Start with the blueprints and defaults below.
Mental Accounting and Salience, applied to one rename: does turning “Savings Pocket 2” into “Save for Phone” change how much of that balance gets spent?
Scope: a single label change framed as a product experiment a team can run without rebuilding the feature.
Read more ›CBA's published result compared credit cards with each other. This blueprint asks whether the same transparency holds when credit sits next to entirely different ways to pay.
Next step after a first win: the follow-on test once an in-category result is already live.
Read more ›A pre-selected option wins far more often than the identical option when people must actively choose it, across nearly every domain where the effect has been measured.
Shipping choice: every default in the product chooses for the user, even when nobody on the team named it as a decision.
Read more ›Maps the full default spectrum: opt-in, opt-out, forced choice, and the newer designs that sit between those poles.
Product language check: “just add a default” hides several distinct decisions, each with its own tradeoffs.
Read more ›Asks whether showing how close a customer already sits to booking raises completion rates.
Reusable pattern: funnel-progress cues that travel to other multi-step flows beyond home loans.
Read more ›