11

Blog · November 13, 2026 · 6 min read

How We Run a Product Design Engagement, Step by Step

Most founders who call a design studio have been burned once already. They paid for a discovery phase that produced a slide deck, then a design phase that produced a Figma file, then waited while engineering rebuilt everything from scratch and quietly dropped half the decisions. By the time anything shipped, the original problem had moved.

We built our engagement process to make that sequence impossible. Every step below exists because we watched a specific failure happen often enough to design against it. Here is exactly how we run a product design engagement at UX Signal Studio, in order, with the reasoning behind each choice.

Step 1: A 30-minute call that ends with a decision

The first conversation is free and it has one job: decide whether there is a real design problem we can move in a short window. We ask what decision your team is stuck on, what metric would tell you it worked, and what has already been tried.

Plenty of calls end with us saying the problem is somewhere else. A pricing question dressed up as a redesign, a sales process gap, an engineering bottleneck. We would rather say that on day zero than sell a project that cannot win.

What you leave with: a plain read on whether design is the lever, and if it is, which flow we would start with.

Step 2: Capture the product as it works today

Before anyone sketches, we capture the live experience. Real screens, real entry points, real error and empty states, the marketing page that set the expectation, and the emails that follow signup. For regulated products we also capture the compliance copy, consent moments, and verification steps, because those are where trust usually breaks.

We do this because memory lies. Teams describe the flow they designed, and customers experience the flow that shipped. The gap between those two is almost always where the opportunity sits.

Every observation gets tied to a screen and a date. If we cannot access something, we record it as unknown and leave it at that. Guessing at a flow we never saw is how audits lose credibility with engineers.

Step 3: Frame the decision before the design

This is the step most processes skip, and it is the one we protect hardest. We write down the specific decision the work has to support, in one sentence. Something like: "Should identity verification happen before or after the user sees their first balance?" or "Which of these three onboarding paths do we cut?"

A framed decision does three things. It keeps scope honest, because anything that does not serve the decision waits. It gives engineering a reason for every screen. And it gives leadership a way to judge the result without arguing about taste.

We also write down what would change our mind. If the data, the regulator, or a user session points the other way, we already agreed in advance that it wins.

Step 4: Design in working software

Once the decision is clear, we build. Our default output is a working, clickable version of the flow in real code, running on real devices, with real states. Figma still has a place for exploring layout and visual direction early, but the thing your team reviews is something they can tap through on a phone.

We work this way for four reasons:

  • Edge cases show up immediately. Loading states, validation errors, slow networks, and long names break in code and hide in mockups.
  • Engineering inherits the reasoning. Your developers get structure, states, and copy they can read and reuse.
  • Reviews get faster. Stakeholders react to a flow they can use, which ends abstract debates quickly.
  • Testing starts sooner. A working flow can be put in front of customers the same week it exists.

AI tools speed this step up a lot. They generate scaffolding, draft variations, and handle repetitive build work. Senior designers decide what gets built, what gets cut, and what the product should say at every high-stakes moment. That split is deliberate, and we never hand judgment to a model.

Step 5: Review against the decision, then cut

Every review starts by rereading the one-sentence decision from step 3. Then we walk the flow as a customer would, on the device they would use, and ask whether this version makes the decision obvious.

Reviews end with a cut list. We remove screens, fields, options, and copy that do not earn their place. In our experience, the strongest version of a flow is usually shorter than the first one, and the hardest part of the job is defending what got removed.

We review with a small group on purpose: the person who owns the outcome, an engineer who will maintain the code, and us. Large review rooms produce compromise designs that nobody owns.

Step 6: Hand over something your team can run

The engagement ends with a handover built for the people who stay. That means the working flow, the decisions and the evidence behind them, the open questions we could not answer, and a walkthrough with product, design, and engineering together.

We hand over enough structure that your team can extend the work without us. If you want us back for the next flow, great. If you never call again because the team has it handled, we count that as a good engagement too.

What we refuse to do

A process is defined as much by its refusals as its steps. On every engagement, we say no to:

  • Discovery phases with no build at the end. Research that never touches software tends to stay in a folder.
  • Pixel-perfect mockups of flows nobody has validated. Polish comes after the flow survives contact with users.
  • Junior handoffs. The senior people on the first call are the senior people doing the work.
  • Design by committee. One owner, one decision, one cut list.
  • Pretty screens that skip the hard states. Errors, holds, denials, and recovery get designed first in regulated products.
  • Retainers with no defined finish line. Each engagement has a decision it supports and a point where it is done.

Why it is built this way

Complex products, especially in fintech, health, insurance, AI, marketplaces, and B2B SaaS, carry real cost when a flow is wrong. A confusing verification step loses customers who never come back. An unclear consent screen creates legal exposure. An AI feature that hides its confidence erodes trust slowly and then all at once.

Those stakes reward a process that captures reality first, frames one decision, proves it in working software, and leaves a team that can keep going. Speed comes from removing the steps that produce artifacts nobody uses, and AI-native execution lets a small senior team move like a much larger one without giving up judgment.

Questions founders usually ask

How long does an engagement take? It depends on the decision. We scope the window on the first call once we know which flow matters most, and we tell you up front when a problem is too big for one engagement.

Do we need a designer on our team first? No. Many teams we talk to have engineers and a founder making design calls. The handover in step 6 is written for exactly that team.

What if we already have Figma files? Bring them. We treat them as evidence of intent in step 2 and compare them against what actually shipped.

Can you start with an audit instead? Yes. If you want a quick read on your live pages first, run them through our free UX Scan and bring the results to the call.

Start with one decision

If your team is stuck on a flow that matters, tell us the decision you are trying to make. We will tell you honestly whether design is the lever and where we would start.

Book a discovery call, or email us at ash@uxsignalstudio.com.

Let’s talk about your next step

Have a question or a project in mind?

Tell us where you are and what you want to figure out. We’ll review your message and reply within two business days.

Contact UX Signal Studio

We’ll use your details to respond to your inquiry. This form does not subscribe you to a mailing list. Privacy policy.

Prefer to talk? Book a discovery call

Get the next essay in your inbox

One practical piece on UX and product design, every week or two. No noise.