In short
A focused feature or workflow may take 3–6 weeks, while an MVP product-design engagement commonly takes 8–16 weeks. Complex roles, platforms, research access, data, design-system work, and stakeholder review can extend it. The schedule shortens most safely by narrowing the workflow and making decisions promptly.
Planning ranges
| Scope | Typical range |
|---|---|
| UX audit | 1–3 weeks |
| Focused workflow | 3–6 weeks |
| MVP product design | 8–16 weeks |
| Complex multi-role product | 12–24+ weeks |
Typical phases
Discovery and evidence: 1–3 weeks
Align on outcome, users, current workflow, data, constraints, risks, and research questions.
Structure and flow: 1–4 weeks
Model entities, roles, journeys, information architecture, wireframes, and important states.
Visual system and detailed design: 2–6 weeks
Establish typography, colour, components, responsive behaviour, content, data, interaction, and accessibility.
Prototype and validation: 1–3 weeks
Test representative tasks, revise the model, and document remaining uncertainty.
Implementation collaboration: overlaps development
Resolve behaviour, component, data, and responsive questions while production code exposes missing states.
What changes the schedule
- number and depth of workflows;
- roles and permissions;
- data complexity;
- web and native platforms;
- research recruitment;
- content readiness;
- existing design system quality;
- stakeholder access;
- integration and technical constraints;
- number of review loops.
Move faster safely
Prioritise one core journey, use real content and data, reserve decision time, test low-fidelity structure early, reuse sound components, and begin engineering collaboration before every screen is polished.
Common questions
Can UI/UX design be completed in two weeks?
Yes, for an audit, prototype, or narrow workflow with ready evidence and fast decisions. It is not a reliable timeline for a complete product.
Does research slow the project?
It adds calendar time while reducing the risk of designing and building the wrong workflow. Focus research on consequential uncertainty.
Can development start before design finishes?
Yes, after core structure and representative components stabilise. Keep designers and engineers collaborating as implementation reveals details.
What usually causes delay?
Unresolved rules, content, stakeholder disagreement, participant access, and late technical constraints cause more delay than interface production.
When is design complete?
When the agreed workflows and states are clear enough to build and test—not when every future product possibility has a screen.
