We Design Extraordinary Things
UI-UX-Design-Questions-and-Answers.png

UI/UX Design Questions & Answers

UI/UX Design Questions & Answers from The Skins Factory, with practical insights on fintech, SaaS, enterprise, healthcare, agentic AI & copilots, cybersecurity, and more from 25+ years of product design experience.

When Should a Project Manager Bring UI/UX Designers Into a Software Project?

— QUESTIONS & ANSWERS

When Should a Project Manager
Bring UI/UX Designers Into a Software Project?

Project Management + UI/UX Delivery

Project manager approaching a luminous green doorway in brutalist architecture, representing the right time to bring UI/UX designers into a software project
Quick Answer

Bring UI/UX designers in as soon as there is enough of a product idea to start making decisions. You do not need to arrive with a finished feature list, complete user flows, or a fully written requirements document. An experienced UI/UX team can help define those things before development starts locking assumptions into code.

The ideal point is when the product goal and intended users are clear enough to begin a productive conversation, but there is still time to shape the feature set, challenge the workflow, uncover missing states, and change direction without rewriting code. Sometimes even that is more than you need to start: a strong design team can help turn a rough concept into the product structure itself.

01 Timing

Bring UI/UX In Before Engineering Has to Guess

When design starts too late, developers are forced to make product and interaction decisions simply to keep the build moving. A project manager can prevent that by bringing UI/UX into the schedule while the product is still flexible enough to change.

02 Product Definition

UI/UX Can Help Define the Product

UI/UX does not have to begin with a finished product definition. Early design work can help determine what belongs in the first release, which features support the core idea, how users should move through the product, what each screen needs to contain, and where additional states or decisions are required.

In the right engagement, the design process helps figure out what the product should be. It is not simply illustrating requirements someone else has already completed.

03 Design Runway

Design and Development Can Overlap

UI/UX does not have to finish an entire product before engineering begins. Once a workflow is approved and stable enough to build, development can move forward while design continues into the next area. The key is maintaining enough of a design runway that engineering is not waiting, guessing, or building around unresolved decisions.

04 Decision Points

The Project Manager Protects the Decision Points

The project manager does not need to make the design decisions. The PM’s job is to make sure the right decisions happen at the right time, the right people are involved, and unresolved questions are visible before they become schedule or development problems. UI/UX should be treated as part of product planning and delivery, not as a visual step added after the software has already taken shape.

From the Work

Recognize Me

Social Discovery Mobile App

Recognize Me shows how early UI/UX can begin. The client came to The Skins Factory with a single sentence: “I want to be able to put a name to a face.” There were no finished screens, user flows, or feature list waiting for us. We helped define the product itself, outlining the core feature set, mapping user flows, working through low-fidelity wireframes, and then designing the complete high-fidelity application.

The project ultimately expanded into more than 600 screens across light and dark modes, multiple colorways, and several profile connection modes. The lesson for a project manager is not the screen count. It is that UI/UX can be brought in while the product is still an idea and help turn that idea into something structured, testable, and ready for engineering.

View the Recognize Me Project

Common Questions

Frequently Asked Questions

Can UI/UX begin before all requirements are finalized?

Yes. The product goal and intended users should be clear enough to begin discussing the experience, but every feature, state, and requirement does not need to be solved in advance. UI/UX can help expose, organize, and define many of those requirements.

What if the team only has an idea and not a feature list yet?

That can still be enough to begin. An experienced product design team can help translate the core idea into a feature set, user flows, screen requirements, and priorities for the first release. The design process can be part of product definition, not just execution.

How far ahead of development should UI/UX be?

Far enough that the next workflow entering development has been thought through, reviewed, and approved, including the important states and interactions. Developers should not routinely be waiting for design or inventing missing behavior themselves.

Have an Idea but Not a Fully Defined Product Yet?

The Skins Factory can get involved before every feature, workflow, and screen has been defined. We help product teams turn early concepts into practical feature sets, user flows, wireframes, interface designs, and developer-ready product experiences. If you already have requirements, we can work from them. If you are earlier in the process, we can help shape what needs to be built.

THE REALLY, REALLY SHORT FORM

Have an idea? Let's chat.

Thank you for reaching out.

We will be in touch within one business day.