# UX design project timeline

A UX design project timeline depends more on your internal process than on how fast the agency works. The speed of your stakeholder reviews, the accessibility of your users for research, and how stable your decisions remain once made are the factors that determine whether a project finishes on time. Understanding this helps you evaluate a proposed timeline more critically.

## The phases of a typical UX design engagement

Most UX design projects move through some version of the following phases. Not all projects include all phases — the specific set depends on the scope agreed at the start.

**Discovery and research.** The agency learns about your users, their workflows, the technical environment, and the existing product (if one exists). This may include user interviews, stakeholder interviews, existing analytics review, heuristic evaluation of the current product, and competitive analysis. Discovery length ranges from a week for a small and well-understood problem to six or more weeks for a complex enterprise product with specialist users.

**Definition.** The team synthesizes what they learned in discovery into a problem definition: user needs, key workflows, constraints, and design principles. This is often done as a workshop or working session with your team. Definition phases are frequently the most compressed and are also the most skipped — skipping them tends to cost more time later.

**Design exploration.** The team generates concepts, explores options, and pressure-tests ideas before committing to a direction. This phase is often invisible from the outside because the work is rough and iterative. Its length depends on how complex the problem is and how many options need exploration before a direction is validated.

**Interaction design.** Detailed user flows, wireframes, and interactive prototypes. This is typically the longest phase in terms of deliverable volume. It is also the phase most affected by stakeholder reviews — each round of feedback and revision adds time.

**Visual design.** Visual system development, high-fidelity screens, component design. This often runs in parallel with later stages of interaction design rather than sequentially after it. Projects with an existing design system to extend are faster here than greenfield visual work.

**Testing and validation.** Usability testing or other forms of design validation with real users. This may be integrated throughout the project or conducted as a distinct phase before final handoff. Skipping it is a common way to stay on schedule in the short term while introducing expensive problems later.

**Handoff and documentation.** Preparing design files, component libraries, specifications, and annotations for the development team. This phase is frequently underbudgeted relative to what a thorough handoff requires.

## What makes a project take longer than expected

The most common sources of timeline overrun are not on the agency's side of the project.

**Stakeholder reviews that take longer than planned.** If your approval process involves multiple layers of sign-off, each review cycle adds time. A design that needs three rounds of stakeholder revision takes three times as long through that phase as one that is approved in one round.

**Direction changes after decisions are made.** When a decision is made in one review and reversed in the next, work is thrown away and redone. This is the most expensive possible use of a project budget.

**Difficulty recruiting users for research.** For specialist professional users — healthcare professionals, legal specialists, enterprise IT administrators — recruitment takes longer and costs more than for general users. If you need specialist participants, factor this into the discovery timeline.

**Delayed client inputs.** Many projects require the agency to have access to existing analytics, technical documentation, style guidelines, or working sessions with your team. Delays in providing these stall the project on the agency's side.

**Scope creep.** Additional screens, flows, or user roles added after the project scope is defined extend timelines without formal process. Even well-managed agencies will often absorb small additions — until the cumulative effect becomes significant.

## How to evaluate a proposed timeline

When an agency presents a project timeline, ask the following:

**What assumptions are built in about your review process?** If the proposal assumes one stakeholder review round per phase but your approval process typically takes three, the timeline will not hold.

**What is the longest single dependency?** The critical path of a UX project is usually either user recruitment for research, or a large high-fidelity design phase with multiple review rounds. Understanding which phase is most likely to cause delay lets you plan around it.

**What happens if a phase runs over?** On a fixed-price project, overrunning one phase often compresses the next. Know in advance which phases can absorb compression without damaging quality and which cannot.

**Are testing phases included or optional?** A timeline that excludes usability testing is faster on paper. It is not faster if design problems surface during development and require costly rework.

**When does the clock start?** Some agencies treat the engagement start date as the date the contract is signed; others treat it as the date the first working session is held. Administrative delays between signing and kick-off add invisible time to the project.

## Realistic durations by project type

These are general ranges rather than firm estimates. Actual timelines depend heavily on scope, internal process, and the factors above.

A **narrowly scoped redesign** of a single user flow or section of an existing product — where research is light, the user is well-understood, and stakeholder approval is centralized — can often complete the design phase in four to eight weeks.

A **new product at the interaction design stage** — where the concept is defined but needs detailed flows, wireframes, and a testable prototype — typically takes eight to sixteen weeks depending on complexity.

A **full project from research through final visual design**, covering multiple user roles and a complete feature set, typically runs three to six months. Projects at the more complex end of this range, involving specialist users, enterprise contexts, or significant visual design and design system work, frequently run longer.

A **design system build** as a standalone engagement, divorced from a specific product project, is typically a three-to-five-month engagement — longer if it needs to be comprehensive enough to cover an entire product portfolio.

None of these timelines account for your internal review process, which is the variable with the highest impact on whether the project finishes on time.
