How it works

Six steps.
No guessing.

Every nicedesigning project follows the same six-step structure. The steps exist to prevent the problems that make design projects expensive: late structural changes, unclear handoffs, and misaligned expectations.

01
Day 1
Discovery Brief

We align on goals, audience, and scope before anything is designed. A written brief is produced and signed off by both sides before we begin.

We review any existing materials, brand guidelines, analytics data, and competitor context before the session. Output: a written brief document. Neither side starts work without it.

02
Days 2-5
Research

We review existing site performance, audience behaviour, and competitive context. For brand identity projects we also conduct category research.

Where analytics access is provided, we review traffic, exit pages, conversion funnels, and device breakdown. Research informs the structural and messaging decisions that follow.

03
Week 1
Wireframes

Structure before style. Black-and-white layout maps for every page establish information hierarchy and user flow before colour or typography enter.

Wireframes are reviewed and signed off before visual design begins. Changes at wireframe stage cost hours. Changes at visual design stage cost days. The sign-off is the line that separates them.

04
Weeks 2-3
Visual Design

Full visual design in Figma for all pages, desktop and mobile. Component library built first, then full page compositions, then responsive breakpoints.

We design systematically: design tokens (colour, type, spacing) first, then reusable components, then pages. This ensures consistency without repetition. Accessibility is addressed at the design stage, not as a post-build checklist.

05
Week 3
Prototype & Revisions

An interactive Figma prototype you can click through on a real device. Structured revision round collects all feedback at once.

One structured revision round per project scope. Feedback is collected in a single session, implemented together, and confirmed before handoff. Multiple rounds of single-comment feedback are not how revision works here.

06
Week 4
Handoff

Annotated Figma file with every spacing value, colour code, and component state documented. Your developer builds without guessing.

Handoff includes: Figma source file with full annotations, SVG and PNG asset exports, design token export (CSS variables and JSON), and a developer walkthrough session. The file is a specification, not a mood board.

Start with
a brief.

Step one. The rest follows.