For UX and product designers

Design UX with rigor: back your decisions with the industry's top references.

Rubik guides you through every design phase and validates your process against Nielsen Norman Group, IxDF, WCAG, Stanford d.school, Material Design and many more.

Create my free account

Knowledge base built on 64 principles from:

Rubik: Desk research step with instructions, deliverable and validation result

Phases to cover any type of project.

Structured steps, all connected.

Design principles with verifiable sources.

Hallucinations or unjustified decisions.

Step 36 of 36

100%

Test your design

Already have something ready? Find out its quality in a minute.

Paste the address of any page. We'll run a limited test, checking only against the knowledge base's interface principles and WCAG 2.1, and return every finding with the rule it breaks, its author and its source. No account.

Seeing is believing

This is what happens when you validate a deliverable.

Two real examples, with the sources Rubik cites.

UX input:

nombre": "Emma Müller", "demografía": { "edad": 31, "ocupación": "Arquitecta y diseñadora freelance", "ciudad": "Berlín, Alemania" }, "comportamientos_observados": [ "Investiga cuidadosamente antes de reservar.",

If you don't have real users, the AI will mark the persona as "Proto-persona — not validated".

ValidateAdd template

Add templateValidate

PreviousNext

UX input:

"Necesitamos rediseñar la app porque la competencia tiene mejores interfaces y estamos perdiendo market share. La solución sería implementar un chatbot con IA y agregar más features al dashboard para que los usuarios dejen de irse a otras plataformas. El problema es que no tenemos suficiente presupuesto para marketing digital."

A good problem statement centers on the user and their need.

ValidateAdd template

Add templateValidate

PreviousNext

Validate my own deliverable

The problem

Without a process, every project is an experiment.

Some good designers produce inconsistent work not for lack of talent, but for lack of structure.

Starting from scratch

Without a repeatable process, quality varies from one project to the next and is almost impossible to defend.

Not knowing if it's good

Is a sitemap with 9 items per level correct? Without a reference, there's no way to know.

AI invents citations

Generic tools cite principles that don't exist or distort the original source.

There's no standard

Without an explicit criterion, the quality of a deliverable ends up being an opinion.

Who it's for

One process. Three ways to use it.

Rubik works out the process for your project: from a 3-day sprint to a complete 4-month process.

UX designer

Stop starting from scratch on every project. Research, personas, architecture, wireframes, prototype and testing — with the quality criteria defined at each step.

Product designer

Connect design with business: JTBD, problem statement, design KPIs, prioritization of findings and developer handoff. The language your PM and your development team already speak.

Agency team reviewing deliverables on a table

Freelancers and agencies

PDF reports by phase or for the whole project, with every source cited. Stop selling confidence: deliver proof.

How it works

From zero to validated deliverables in five steps.

Each step tells you what to do, the AI validates what you deliver and Rubik rates it against real sources.

Select whether you'll run a complete project or a single-phase one.

Partial process

Work on just one specific phase — useful when you've already advanced part of the process in another tool.

Select

Complete process

UX design process to run in 6 phases, from discovery to testing. Ideal for new products or complete redesigns.

Recommended for most projects

Select

14 questions about your project. Rubik works out the ideal process: a 3-day Express or a complete 4-month one. The process adapts to you, not the other way around.

Project context

Tell us what you're building.

What's your product called?

Nómada

What type of project is it?

new productRedesignNew featuretargeted improvement

Describe what the product does:

Una app móvil que permite a viajeros planificar itinerarios colaborativos, descubrir experiencias locales y gestionar reservas en un solo lugar.

One or two sentences is enough

What problem does it solve for the user?

Los viajeros pierden horas alternando entre múltiples apps para planificar, y no pueden coordinar fácilmente con sus acompañantes de viaje.

What business goal must it meet?

Alcanzar 50K usuarios activos mensuales en los primeros 6 meses y lograr un 12% de conversión a plan premium.

Continue

Type C

Complete process

All phases active

Score: 9/1269%

Key variables

Type: New product
Timeline: not yet defined
Research: not yet defined
Screens: not yet defined

Follow the instructions for each step, load the guide template, and then add your input following your own judgment.

Instructions

What is it?

In this phase you write the project brief, defining the problem to solve, the target users and the success criteria that will guide the whole design process.

How to do it

1
Define the main problem the user faces
2
Identify user segments and their needs
3
Establish the project's success metrics
4
Document technical and business constraints
5
Benchmark at least 3 competitors
6
Validate the brief with key project stakeholders

UX deliverable:

Summarize the scope and context of the deliverable in 2-3 sentences

ThemesFindingsNext steps

Friction in the checkout process

62% of users drop off at the shipping address step
Form fields don't have autocomplete enabled

alta

Lack of trust in the transaction

No security badges shown during checkout
Users look for return guarantees before paying

media

Unclear shipping options

Shipping costs only appear on the last step
No delivery date estimate visible in the summary

baja

Add templateValidate

The AI reviews it against real principles and returns feedback with the sources cited.

Validate my own deliverable

The 6 main phases

The complete process. Not just the pretty part.

Six phases, thirty-six steps. Each with its template, its quality criteria and its reference principles.

Phase 1

Discovery

User research, competitive analysis and heuristic evaluation to understand the problem before designing.

Phase 2

Definition

Personas, journey maps, JTBD, problem statement and design KPIs to define the right problem.

Phase 3

Information architecture

Content inventory, sitemap, user flows and content matrix to structure the solution.

Phase 4

Ideation and wireframes

Structured ideation, design principles and Lo-fi and Mid-fi wireframes to generate and validate solutions.

Phase 5

Prototyping

Design tokens, components, Hi-fi UI, WCAG accessibility and complete developer handoff.

Phase 6

Testing and validation

Testing plan, results synthesis, prioritization of findings and validation against the defined KPIs.

The differentiator

Other AIs improvise. Rubik cites.

The difference between Rubik and any other AI tool is simple: Rubik never cites a principle that doesn't exist.

Comparison between a generic AI and Rubik
	Generic AI
Verifiable sources for principles with author, source and year	—	Yes
Feedback with findings, a description of the principle and a link to the original source	—	Yes
Reports when something is missing: it doesn't assume, it doesn't hallucinate	—	Yes
6 phases and 36 steps adapted to your project	—	Yes
Validation and rating of deliverable quality against explicit criteria	—	Yes

Quality system

Know exactly how good your work is.

Every deliverable gets a quality level based on the step's criteria and the knowledge base principles.

Not validated

Critical problems or incomplete deliverable. It must be fixed.

Blocks progress on the step

Fair quality

Meets the minimum. Important improvements are recommended.

Allows marking as completed

Medium quality

Good work. Some optional improvements available.

Allows marking as completed

High quality

Complete, specific and well-documented deliverable.

Professional-level work

Frequently asked questions

Before you ask.

Does Rubik design for me?: No. Rubik doesn't replace your judgment: it structures and verifies it. You design; Rubik tells you whether the deliverable meets industry principles and what it's missing.
Where do the principles come from?: From principles extracted from Nielsen Norman Group, IxDF, WCAG 2.1, Laws of UX, Atomic Design (Brad Frost) and JTBD (Christensen). Each with author, source and year. You can browse them all in the knowledge base, no account needed.
Is it useful if I already have my own process?: Yes. You can skip steps and use Rubik only as a validation layer over the deliverables you already produce.
Is it for product design or only UX?: Both. The Definition and Testing phases cover JTBD, design KPIs, prioritization of findings and handoff: right where product design connects with business and development.
Are my projects private?: Yes. Your projects are private and are not used to train models.
How long until I see something useful?: The brief is 14 questions. Your first validated deliverable is ready in about 10 minutes.

Your next project doesn't have to start from scratch.

Create your free account and validate your first deliverable today.

Create your project for free!

Free · No credit card