I’m Susan, Lead Product Designer at Monzo. We’ve just published a blog post on how Monzo designers are shipping safer, faster product improvements, and why that matters for product quality and customer trust.
It covers how we’re closing the gap between design intent and what gets shipped. Focusing on details like copy, UI consistency, and edge cases shape which can impact how reliable and trustworthy a product feels.
We’re addressing this by enabling designers to make small, well-scoped changes directly in production code, within the same engineering guardrails and safety standards. It’s about reducing friction, improving velocity, and taking more direct responsibility for outcomes, in partnership with engineering.
The post shares how this is working in practice, from first changes shipped to how designers are using tools like Cursor and Claude Code to understand and contribute to codebases, all while working closely with engineering through review and release processes.
We’d love to answer any questions you have, either on the blog or on how this is working in practice at Monzo.
Designers are learning to ship safely with AI and engineering support
I’ve never learned Go, but with AI’s help I’ve written a handful of lines and made small changes to our backend.
and on that note…
No offense meant but Monzo already have a reputation on here for shipping half baked features. Now knowing that people who don’t have much/any experience of coding (or don’t know the language they’re writing in) are shipping changes erodes my trust in Monzo.
>When designers ship code, the same expectations apply around quality, review, and safety as any other production change. Designers are not bypassing engineering. Code review is mandatory and deployment remains with engineers who have completed the required safety checks.
This seems to me like only a good thing. There are checks in place and the speed that Monzo will be able to make improvements will only increase.
Indeed, this might even open the door to sorting things like
Maybe if the changes are tweaks to content/layout then yes it may be an overreaction but the author says they have shipping changes to the backend despite never learning Go.
I hold financial apps to a much higher standard than pretty much any other apps I have installed and for me this is a red flag.
A minor observation on that front, seeing as it is mentioned. When moving money between accounts and pots (in the Android app), as you type in a value the totals for each change. That however does not occur when adding to the investments ISA with the values staying fixed. I thought to myself that it seems strange that there would be more than one “control” for doing that sort of thing, so maybe it is a bug rather than an inconsistency
