Projected Growth Investing
Use an interactive outcome projection to make a long-term financial commitment feel tangible.
In practice: Monzo
Projected growth investing makes a long-term financial commitment tangible by turning it into a simulation the user can steer: a growth chart, a deposit slider, and a likely-range band that shows outcomes without overpromising.
Future value made visible
A projection chart shows how monthly deposits could grow over time, turning an abstract decision into a concrete number the user can picture and adjust.
Guided fund choice
A fund-choice flow presents a few risk options with an expandable breakdown, so a daunting decision becomes a few completable steps.
Context without overload
Fund details show investment geography and past performance with clear context, giving the user enough to judge the choice without burying the risk.
Why it works
A multi-year projection connects today's deposit to a future balance, helping users act on long-term intentions. A likely-range band and plain disclaimer signal that projections are estimates, not promises, which makes the whole chart more credible.
Behavioral principles
Future Self-Continuity
Making the future balance visible helps users act on behalf of their later selves.
Steerable Simulation
A slider that moves the outcome lets users learn how a small change today compounds.
Goal-Gradient Motivation
Seeing the gap between deposits and projected growth gives a reason to contribute a little more now.
Trust Through Uncertainty
A likely-range band and plain disclaimer make the projection credible rather than salesy.
Design considerations
Projections must show uncertainty and never imply guaranteed performance, and investment risk, fees, and suitability need to stay visible rather than buried under an optimistic chart.
Implementation prompt
Use the pattern above as the reference, then prototype the same behavior in your own product surface.
I want to incorporate the Projected Growth Investing approach, inspired by Monzo, into my product. The goal is to translate the behavior design principle into a real product flow, not just a standalone UI component. Please suggest how to implement this in the product: • Explain where this pattern should appear in the user journey • Define the behavior it should encourage • Suggest the data, states, and product logic needed to support it • Include user-facing copy that feels calm, respectful, and appropriate for the product context • Identify risks, edge cases, and ways to avoid pressure or manipulation For implementation, propose: • Product flow changes • Required screens or states • Interaction logic • Success and failure states • A lightweight rollout plan for testing whether the pattern improves engagement.