Ali Dalton (@alidalton) header
Ali Dalton (@alidalton) profile picture

Product Design Partner → https://teapawt.org/t.co/bRnaTlsz9h Design that moves revenue for startups | 10+ years | 50M+ users | $13M+ impact Ex Citi, Mercedes, Sky, NatWest

Book a call →
Joined April 2023
Photo by Ali Dalton (@alidalton)Photo by Ali Dalton (@alidalton)Photo by Ali Dalton (@alidalton)Photo by Ali Dalton (@alidalton)Photo by Ali Dalton (@alidalton)Photo by Ali Dalton (@alidalton)Photo by Ali Dalton (@alidalton)Photo by Ali Dalton (@alidalton)Photo by Ali Dalton (@alidalton)Photo by Ali Dalton (@alidalton)
Seeing a few new faces here, so thought I'd reintroduce myself... Hey, I'm Ali. I run a product design studio helping founders and product teams build better software. I've spent over 10 years designing products used by more than 50 million people, contributing to over $13 million in business impact along the way. I've worked on products for the likes of Mercedes-Benz, Citi, Virgin, Sky, NatWest, BCG and many more. And here's something I've noticed over the years: As software products grow, the experience doesn't always keep up. → New features get added → User journeys become more complicated → Design inconsistencies start creeping in → Teams get so focused on shipping that UX takes a back seat Eventually you've built a powerful product that's harder to use than it should be. And that starts affecting more than just design. Users struggle to see the value, onboarding becomes a bottleneck and adoption & conversion suffer. That's where I come in. I work with founders and product teams to improve the experience, remove friction and turn complex software into products that perform better. It's also what I share here: Product design, UX, lessons from real projects and the thinking behind better software. If you're building a software product and the experience isn't keeping up with the business, DM me. Let's chat! - Ali
2
1
15
16,854
If you’re a Series A SaaS founder shipping a feature a month while activation stays flat, the next feature probably isn’t the fix. At a major UK telecoms company with over 5 million customers, mobile checkout was converting at 8%. We didn’t start with new features or a visual redesign. We started by mapping the journey customers were already getting stuck in. Six weeks later, checkout was converting at 24%. A confusing product rarely looks like a design problem on a spreadsheet. It shows up as: → Trial users who sign up and never reach the part worth paying for → Sales demos doing the job onboarding should be doing → Support answering the same “where do I find…” questions every week → Engineers reworking features after launch because people couldn’t use them In my experience it starts in one of three places: a flow with too many steps, navigation that grew one feature at a time, or a product built in pieces nobody fitted together. Fixing what’s already there is usually worth more than the next feature.
5
1
4
195
Photos sell a flat, but the floor plan is what tells you if it works. Explored joining the two, so every photo shows which room it is and where it was taken from.
6
209
If you're a founder who can get a polished screen out of AI in an afternoon, the screens were never the expensive part. I've spent 10+ years designing products used by 50M+ people, and every new tool, from Photoshop to no-code to AI, has replaced only the delivery part of design. We redesigned a customer journey by looking at where people got stuck, what information was missing and which parts created avoidable demand, and it delivered £11M in NPV over three years and cut calls by around £5M a year. The goal was to stop customers needing to contact the business at all, and 86% of them preferred the new experience. Use AI for the screens, but spend your own time on what to build, why it matters and when something is wrong.
2
7
317
Plenty of my product work this year has been improving journeys that already exist, rather than designing from scratch. That work needs a different approach to a blank page: Not just a better version of every screen. A product with users already has habits built around it, and changing everything at once throws those away along with the problems. That might mean: → finding out which parts people already rely on before touching anything → fixing the step support keeps having to explain → keeping the words customers have already learnt → changing one thing at a time so you can see what moved → leaving the parts that work exactly as they are The referral project I worked on this year was like that: the flow was getting people through, but more than 90% of the support calls came after they'd signed up. That's what improving an existing product comes down to. Not starting again. Finding the few places it's letting people down and leaving the rest alone.
5
127
I worked on a resourcing platform for a global consulting firm that reported over $14 billion in annual revenue. Being available didn't mean someone was right for the work, or that the budget fit. The interesting design problem was showing those trade-offs in one place.
1
3
75
Most photo apps make you edit one picture at a time, but people judge a trip by how the whole set looks 📸 Explored treating the album as the thing you edit, not the photo.
2
5
216
Most expense tools let anyone add a category, so software ends up split across three of them and the budget only watches one. Exploring spotting the duplicates and merging them in one step.
8
330
I worked on a mobile checkout project in the telecoms industry where conversion increased from 8% to 24% in just six weeks. We reduced the journey from 12 steps to 7. It's a good example of why I think improving an existing product can be more valuable than constantly adding new features. Sometimes there's a lot of value sitting inside the experience you've already built.
2
179
The moment after you tap a button is usually dead space in an interface. Explored letting that button become the thing you're waiting on, then turn back into the next step.
5
14
347
Property search Native app experience 🏠
15
775
Designing everything around a design system from day one can actually hold back creativity. Especially now with tools like Claude Code. Sometimes I just want to open Figma, explore ideas, try things out and focus on making something really good. Without worrying whether every decision fits an existing component or design token. Once I'm happy with the design I can use Claude Code to turn those decisions into a proper system, following the structure I've already defined. What used to involve a lot of manual cleanup and back and forth is now much easier. I can focus on the craft first and let AI help with the structure afterwards. Let the design inform the system, rather than the system dictating the design.
30
1
1
95
4,866
Photos sell a flat, but the floor plan is what tells you if it works. Explored joining the two, so every photo shows which room it is and where it was taken from.
4
136
I'm enjoying being able to design without worrying about fitting everything into a design system from day one. Right now I'm designing in Figma with raw values, focusing on the craft and exploring ideas without too many restrictions. Once I'm happy with the direction, I build a skill that lets Claude Code turn those decisions into a proper system, using the structure I've already defined. It used to involve a lot more manual cleanup and back-and-forth. Now I can spend more time designing how things should look and work.
4
1
8
221
Email app for an AI startup…
3
1
9
486
If you’re a fintech startup selling to businesses, your customers are probably stalling on a screen that says “pending”, signed up but unable to move money. I saw this up close designing the onboarding for a native FX payments app at a banking group that now serves over 20 million customers. That one word can mean three very different things: → The bank is still checking their identity → Someone in their business needs to approve their access → There’s a security step they still need to finish Only the first one means waiting. The other two need someone to act, and the customer can’t tell which. So they chase support about the wrong thing, or sit waiting on a step that’s actually theirs. The fix is to give each state its own message: who’s acting, what they’re waiting on, and what happens next. “Waiting for your account admin to approve your access. We’ll let you know when you can make a payment.” Sign up gets a business in, but the screens before its first payment decide whether it becomes a customer.
2
7
335
If you’re a startup founder running a free trial, some of your churn is probably decided at sign up, by a first charge the customer didn’t see coming. They start the trial happily, the payment lands, and it turns into a cancellation, a refund request or an angry support ticket. I spent six months redesigning the subscription sign-up for one of the UK’s biggest broadcasters around one question: what will I pay when the trial ends? So before anyone committed, we made it clear: → The price once the trial finishes → The date of the first payment → How to cancel, and by when → A countdown as the trial end got closer In testing, 86% of people preferred the new version. A lot of subscription teams treat pricing clarity as friction that costs conversions. It doesn’t remove the drop-off, it moves it earlier, to where it’s cheaper. If the first payment surprises them, you haven’t converted a customer, you’ve delayed a cancellation.
2
4
242
If you’re a Fintech startup growing through referrals, the reward usually isn’t the problem, it’s not knowing when it’ll arrive. So customers contact support, and a channel that should run itself starts costing you time. I worked on the referral experience for a digital bank that now serves over 2 million customers. What we found was that people understood how to earn the reward, but couldn’t work out when they’d get it. That uncertainty was showing up as support demand, not as a broken flow. The experience needed to answer three questions: → Am I eligible for the reward? → Have I completed everything required? → When will I actually get paid? We answered them across the referral landing page, an in-app progress widget and a dashboard, so customers could see where they stood at every step. If customers have to ask support what happens next, it’s a product problem, not a support one.
5
262
I try to show a founder something interactive within 48 hours of a new brief. Before that most of the brief is guesswork about what they'll respond to. Once they can click through something real, they react to it, and the brief gets sharper. That's what the first two days are for. Something real enough to react to, not something polished.
4
197
When an AI agent gets one thing wrong, most products make you start again from the top. Explored a work log where you can fix the one decision it got wrong and re-run only what came after.
5
1
42
1,598
Exploring letting one tab widen to hold whatever you're in the middle of, from basket to delivery time. Light vs Dark 💡
6
234