Aziz daiya

Split a taxi booking flow into two screens. Booking details on one, fare and payment on the next.

Client pushed back. Dispatchers create these bookings all day, and two steps meant two clicks and two loads every single time. For someone doing this dozens of times a shift, that adds up fast.

Went back to one screen. Everything a dispatcher needs to create a booking, in one place and no step switching.

Not every flow benefits from breaking it into steps. If the task is repetitive and the person doing it is fast and experienced, fewer screens can actually be less work.

Founder usually knows what they want the product to contain. Sometimes they even have a rough idea of how a screen should work. I do not treat that first requirement as the final answer. Before designing, I understand what user actually needs/wants to do.

For example, on operations product, request for dashboard might actually about helping someone delayed shipments, decide which need attention, and take action quickly.

Those details matter more to me than deciding which cards or charts should be on screen. I worked both ways. When I start with requested design, I usually end up making more changes later because workflow was not clear enough. so I spend more time understanding task before I start designing screen. It saves me from designing wrong thing first.

While working on Gold Investment Fintech Project, we had one discussion before starting the UI.

Should jewellery be on the home screen?

The thinking was simple.

People are saving money to buy jewellery, so why not show it first?

Instead of discussing the layout, I asked one question.

"What should a user do the first time they open the app?"

If users don't start saving, they never reach the point of buying jewellery.

That changed the discussion.

We kept the first version focused on one thing.

Start saving automatically.

Once users built that habit, buying gold came next.

Jewellery came after that.

We didn't remove any features.

We just changed when they should become part of the journey.

#ProductDesign #MVP #MobileApp

Founders are building products faster than ever with tools like v0, Galileo, and Lovable.

They're great at generating UI.

But as soon as a product grows beyond a few screens, the real design challenges begin.

This carousel covers a few places where AI-generated interfaces often fall short and where product design creates the most value.

Swipe through, and let me know if you've run into any of these while building or designing a product.

Many fintech forms try to be "complete" instead of being easy to complete.

Here's a flow I redesigned for a payments SaaS — the Add Beneficiary screen.

The original put everything on one screen: personal details, bank or UPI selection, verification, additional fields, two CTAs.

Nothing was broken. But users had to process the entire workflow before taking the first step.

The fix wasn't fewer fields. I

t was fewer decisions at once.

New flow starts with one question: "How do you want to add them?"

From verification first, details next, save at the end.

The principle: don't make users think about the whole task.

Just the next step.That's the difference between a form that feels long and a flow that feels effortless.

#ProductDesign #Fintech #UXDesign