Skip to content
Fundur

How every item is made

Eight stages. All of them ship with the file.

Every item in the catalogue is made the same way, and the record of that work is part of what you download — the questions, the alternatives, the reasoning and the decisions, next to the artwork they produced.

Scroll — the eight stages, one at a time

What you are actually buying

A finished design, and the thinking that got there. 

Most files arrive as artwork and leave you to work out the rest. These arrive with the workflow attached, so the next screen — the one that isn't in the download — is one you can design yourself, the same way.

Stage 01 of 08

Understand

The brief, the business, the constraints.

In your download

The brief as it was actually answered, with the constraints that shaped it.

Use it yourself

Swap in your own constraints and you have the brief for your next screen.

Stage 02 of 08

Map landscape

Comparative analysis — what exists, what works.

In your download

The comparative sweep — what already exists, and what each one gets right.

Use it yourself

The shortlist saves you the week of looking.

Stage 03 of 08

Gap analysis

What's missing between where they are and where they need to be.

In your download

The distance between where the product was and where it needed to be.

Use it yourself

The same gap, named for your product, is the whole argument for a redesign.

Stage 04 of 08

User profiling

Audiences, jobs to be done, usage patterns.

In your download

Audiences, jobs to be done, and the usage patterns the design assumes.

Use it yourself

Check them against your users before you ship — the mismatches are your edits.

Stage 05 of 08

Information architecture

Structure, navigation, hierarchy.

In your download

Structure, navigation and hierarchy, with the alternatives that lost.

Use it yourself

The rejected structures tell you what not to try when yours has to differ.

Stage 06 of 08

Wireframes

Flows, layouts, states.

In your download

Flows and layouts with every state drawn — empty, loading, error, full.

Use it yourself

The state list is a checklist you can run against any screen you add.

Stage 07 of 08

Design system

Tokens, components, patterns.

In your download

Tokens, components and patterns, named consistently and documented.

Use it yourself

Extend it rather than restyle it, and the tenth screen still matches the first.

Stage 08 of 08

Build-ready front end

The handoff that doesn't need translating.

In your download

The coded implementation, where one exists — no handoff translation.

Use it yourself

Read it to see exactly how the design was meant to behave under load.

Why it is in the download at all

On the day you have no time, borrow the method.

A design you can't extend is a design with a shelf life. Everything here is published with enough of its own reasoning that you can carry it forward — adapt it to a brief it wasn't drawn for, defend it to a team that didn't commission it, and design the next screen in the same language.

01

The questions, not just the answers

Every stage is published with what was asked before anything was drawn. In a crunch you can run the same questions at your own desk and get to a defensible answer without starting from a blank page.

02

The decision, and why it went that way

Each item carries the one insight it turns on, the reasoning behind it, and the options that were rejected. When someone asks why the table paginates instead of scrolling, the answer is already written down.

03

A method you can re-run

The eight stages are the same eight every time, so the second item you buy teaches you the shape of the first. Use it as a checklist for the screens you have to design yourself.

Two ways to use it

Download a finished piece, or have these eight stages run on your product.