Review Rubric

Before reviewing any element, state its design intent explicitly (navigation shortcut, data display, action trigger, status indicator). Evaluate each element against its own intent.

Question 1 — Redundancy For every element, ask: does this add information not already present elsewhere on this screen?

• Does any data point appear more than once in any form?
• Does any navigation element create an escape hatch inside a focused flow?
• Does any row or icon set repeat information already in an adjacent list?
• Does any metadata label accurately reflect the content it describes?
• Does any navigation element on screen duplicate a destination already accessible via the bottom nav bar?

Flag redundancy before explaining it. Do not soften findings.

Question 2 — Benchmark standard Evaluate every element against Techne Futbol and Train Effective. Do not recommend removal — recommend the design that meets benchmark.

• Redundant elements → more efficient solution carrying same information
• Empty space → contextual content reinforcing user goal
• Generic list rows → scannable visual hierarchy
• Identical copy → distinct per-item descriptions
• Decorative elements → functional equivalents

Question 3 — Purpose fit State the page's primary purpose in one sentence first. Then ask: does each element serve that purpose in its current size, weight, and placement?

Flag anything too large, too small, too passive, or misweighted for its role on this specific page.

Question 4 — Completeness State what the user should be able to do on this page based on its primary purpose.

Then ask: is every necessary control, setting, or action present and accessible?

• What inputs drive the content on this page?

Are those inputs editable from here?

• What decisions does the user need to make on this page?

Are the tools to make those decisions present?

• What would a user expect to find here that isn't here?

Flag missing controls before explaining them. A page that does not expose the controls needed to manage its own content is incomplete regardless of how clean it looks.

OUTPUT FORMAT Answer Q1, Q2, Q3, Q4 separately. End with two final lists:

WORKING

• one line per item

NEEDS WORK

• one line per item
• tag (critical) if blocking

No explanations in final lists unless (critical). Bullet points throughout. No full sentences.

Before scoring or assessing any element as working, apply the following test:

• Would a senior UX designer at a top-tier product company

(Figma, Spotify, Nike) accept this as shipped quality?

• If not, flag it regardless of intent or effort.

Do not credit intent. Do not credit improvement over a previous version. Only evaluate what is in front of you against professional industry standard.

If something is directionally correct but not executed to standard, it goes in NEEDS WORK with specific actionable fixes — not in WORKING.

WORKING means shipped. NEEDS WORK means not yet.