Monzo · Product sense · Mid · 45 to 60 minutes

Should Monzo productise user made saving hacks?

Monzo is a digital bank that offers current accounts, spending tools, and savings features in a mobile app. Answer this product management case and get it graded line by line against a weighted rubric.

product sense
user insight
prioritization
trade off analysis
metric design

The situation

You are a PM in Monzo's money management area. A few highly engaged customers have built their own saving routines using Monzo's integrations with tools like IFTTT, and the pattern has caught internal attention. Separately, customer research suggests many people want to save more but struggle both to begin and to keep the habit going once life gets busy. Your director asks you to recommend whether Monzo should invest in a new in app savings feature inspired by these user created behaviors, or leave this as an advanced workflow for enthusiasts. Why now: Monzo wants to deepen everyday value for current account customers, but any savings experience must feel trustworthy, simple, and broadly understandable. The tension is that power user setups can be clever, but they often require too much effort and configuration for mainstream customers. A very simple mechanic might drive adoption, but it could also feel gimmicky or fail to fit different income patterns. You need to define the user problem, decide whether this is worth building now, and propose a product direction that improves habit formation without adding financial stress or operational complexity.

What to produce

Write a 1 to 2 page product recommendation memo.

Your answer must

State the core user problem in plain language, including the difference between helping people start saving and helping them keep the habit.
Recommend whether Monzo should productise this opportunity now, and identify the target user segment your recommendation is for.
Propose one MVP concept and one credible alternative you considered, with the main trade offs of each.
Explain the key product principles and user experience choices needed to make the feature mainstream rather than just useful for power users.
Define success metrics, leading indicators, and a first experiment or launch plan to reduce risk.

Constraints

Use only capabilities Monzo could plausibly build inside its existing app and savings experience, no new external partners or offline programs.
The solution must be understandable without third party automation tools or complex setup.
The design must avoid increasing the risk of customers missing essential payments or feeling tricked into saving.
Assume one cross functional squad can work on this for one quarter.

Format

Use sections for problem, target user, recommendation, options considered, MVP, metrics, and risks.

How Monzo actually played it

Monzo traces how a savings habit invented by a power user with an IFTTT integration in 2018 became an official product that saves 1p on day one, 2p on day two and so on to 3.65 pounds on day 365. The post explains how research on why people struggle to save shaped the mechanics. A tidy case of turning user-invented behavior into a mainstream feature.

Watch what power users invent with your integrations for product ideas.
Validate the underlying need with research before productising.
A simple mechanic can beat a complicated setup that only enthusiasts complete.
Design for sticking to the habit, not only starting it.

Built from Building the 1p Saving Challenge by Monzo.