The design process for SaaS products is iterative by necessity. Unlike a one-time software build, SaaS design never really ends. The product keeps changing, users keep sending feedback, and competitors keep shipping features. So the process has to keep up.

It typically starts with discovery and research. Designers run user interviews, dig into behavioral data from tools like Mixpanel or FullStory, read through support tickets, and poke around competitor products. The goal is to understand what problems are actually worth solving before anyone opens Figma. In an embedded design team setup, this research runs continuously alongside the product team rather than happening once at project kickoff.

Next comes ideation and strategy. Designers map user journeys, sketch out information architecture, and produce low-fidelity wireframes. These get shared with stakeholders early, which sounds obvious but makes a real difference. Catching a bad idea at the wireframe stage takes an hour to fix. Catching it after engineering has built it takes weeks.

Then the work moves into UI design and prototyping. Designers build high-fidelity screens in Figma, pulling from the product's design system, which is basically a library of reusable components, typography, color tokens, and interaction patterns. Prototypes simulate the actual user flows so there's something real to test against.

Usability testing comes next. Real users or internal stakeholders work through the prototype while designers watch for friction. What trips people up, what gets ignored, what causes confusion. Those findings go back into the design before anything is handed to engineering.

The handoff phase involves annotated mockups, design specs, and developer-ready assets. In embedded team models, designers stay involved during the build, answering questions and checking that what gets coded actually matches what was designed. Small deviations compound fast.

After launch, the team reviews product analytics and user feedback to see whether the design decisions actually worked. That review feeds the next research cycle, and the loop starts again.

This is what separates SaaS products that keep improving from ones that quietly go stale. The process is the product.