Good problem to pick, Mara. Scoring interface quality without usability data means leaning on design principles, heuristics and structured expert review — interrogating the work against known-good practice and predicted behaviour rather than watching someone struggle through it.
As a staff designer at Northbay Logistics, a rubric like this gives you and your team a defensible way to make calls and build sturdier patterns early, particularly when research time is short or the build is still moving under you.
Here's a rubric you can run before a single session gets booked:
Interface Quality Rubric (Without Usability Data)
The rubric leans on craft judgement, established principles and plain reasoning to pull a pattern apart.
Stage 1: Framing & Context
Before you look at the pattern itself, get clear on what it is for and where it has to live.
- Name the job and the user's goal:
- What problem is this pattern solving for the person using it? (e.g. shortening a repeated task, making a comparison legible, collecting structured input).
- What is the person actually trying to finish when they land on it?