Skip to content
UXE Award

Digital product design awards: a guide for SaaS and product teams

Why most digital product design awards are built for marketing sites, what a product team should look for instead, and how to enter a SaaS product so we see the work that actually took the year.

The UXE editors6 min read

Search digital product design awards and most of what comes back was designed for agency portfolios: a gallery of hero shots, judged on how the work looks in a still. Product teams enter, lose to a parallax microsite, and conclude awards aren't for them. The problem isn't the work. It's that nobody was scoring the parts that took the year.

What product work is actually made of

The value in a SaaS product is rarely on its first screen. It's in the bulk-edit flow that stops a customer support team from hand-editing 400 rows. It's in the permissions model that a new admin can understand in one sitting. It's in the empty state that tells someone what to do next instead of congratulating them on having nothing.

None of that photographs well. All of it is scoreable — if a programme asks about it.

Two ways of looking at the same product

What a gallery award sees

  • The marketing site and the first-run screen
  • Type, colour, motion, art direction
  • One journey, chosen by you, at its best
  • The product as a still image

What we actually look at

  • The tenth screen in, where the work lives
  • Whether a real task finishes without help
  • Error, empty, loading and permission states
  • The product as a thing people use on a Tuesday

Four things to check before you enter anywhere

  • Is there a category for a product, not a website? If every category is a site type, you're in a web-design award wearing a different name.
  • Is accessibility scored, or a checkbox? For B2B and public-sector buyers, accessibility is procurement, not virtue. An award that ignores it can't help you sell.
  • Is performance scored? Perceived speed is a design decision and a retention lever. Almost no design award measures it.
  • Can an editor get in? If the product is behind a login, does the programme have a way to give its judges access? If not, they are scoring your screenshots.

How to enter a SaaS product properly

The entry itself is a design problem: you have a cover, eight screens and three short sections to make someone understand a product they will use for twenty minutes. Here's the arrangement that works.

How to build the entry
  1. 01

    Pick one job

    The single task the product exists to make survivable. Not the feature list.

  2. 02

    Show the middle

    Skip the marketing page. Start where the work happens.

  3. 03

    Show the edges

    Empty, error, loading, permission-denied. This is where craft is visible.

  4. 04

    Prove the outcome

    One number with a method behind it beats five without.

The screens that change a score

Eight screens of a populated dashboard tell us one thing eight times. A better set covers the whole arc of the job:

  • The first screen a new account sees — genuinely empty, not seeded with demo data.
  • The screen where the main task is done, at realistic density. Real row counts, real names, real text lengths.
  • A destructive action and its confirmation, if the product has one.
  • An error that the product handles well — validation, a failed save, a connection dropping mid-edit.
  • Something on a narrow viewport, if the product is used on one.
  • A settings or permissions screen, where complexity usually collects.

If you have a before-and-after — the old flow and the new one — show both. Editors score the current product, but the comparison tells them what the decision was worth.

Writing the case study for people who will use the product

The three fields on the entry form are Challenge, Approach and Outcomes. The common failure is writing them for an investor instead of a judge.

The same three fields, done two ways
Compared onScores wellScores badly
ChallengeA specific task that was failing, and for whomMarket context and company history
ApproachThe decision, the alternative, and whyA list of features shipped
OutcomesA measured change, with the method"Engagement increased significantly"
ResearchWhat you learned that changed the designHow many interviews you ran

Where a SaaS product should compete

At UXE Award, most product teams enter Product Experience — with SaaS, B2B or Enterprise as the subcategory — and then add one specialist category for the discipline that took the effort. If the year went on the design system, add Design Systems. If it went on rewriting every message in the product, add UX Writing & Content Design. If it went on making the thing usable without a mouse, add Inclusive & Ethical Design.

Three categories, one fee, and each one gives us something specific to assess, under a different set of weights. That is a far stronger entry than the same product filed three times as a general excellence claim.

What you get out of it, beyond the badge

A recognized profile carries the full score breakdown and the signed verdict, which makes it unusually useful in places a badge isn't: a procurement questionnaire, a security-and-accessibility review, a board update on design maturity, a hiring page. An independent assessment scoring your accessibility at 8.5, with its conditions printed, is a more persuasive artefact than your own statement that accessibility matters to you.

And if the score comes back lower than you hoped, you have a ranked list of what to fix, from people who used the product cold. That is worth more than the badge, and it's free. Enter a product.

The three artefacts that make a product entry legible

Product work is harder to present than a website, because the interesting parts are buried and stateful. Three artefacts solve most of it, and all three are cheap to produce.

What to prepare once, and reuse every year
  1. 01

    A seeded account

    Realistic data, realistic volume, realistic mess. Not three tidy rows.

  2. 02

    A 30-second recording

    The key task, at real speed, including one failure and its recovery.

  3. 03

    A state sheet

    Empty, loading, error, permission-denied, at-scale — one screen each.

Multi-surface products: what to submit when there are four of them

Plenty of B2B products are a web app, a mobile app, an admin console and an email programme. Entering all of it as one thing produces an entry with no centre.

Pick the surface where the design work actually happened and enter that as the project, then use the case study to explain how it relates to the others. If the achievement is genuinely the coherence across all four, that is Service Experience, and say so explicitly — it is a different claim, weighed differently.

What to do with the scorecard afterwards

A published profile carries all seven criterion scores and the conditions behind the measured ones. That artefact does work in places a badge doesn't reach, and most teams under-use it.

  • Procurement and vendor questionnaires. An independent accessibility score, with the assessors named, answers a question you would otherwise answer about yourself.
  • Board and roadmap conversations. A low score on one criterion is the cheapest business case a design team will ever get for fixing it.
  • Hiring. Designers read scorecards. A public record of how your product was assessed says more than a careers page.
  • Renewal conversations. For enterprise buyers, evidence that the product is independently assessed each year is a retention argument.

Questions we get asked

  • Our product is behind a login. Can we still enter?

    Yes — tick reviewer access on the form and we'll arrange credentials. Most B2B, health and enterprise entries need it, and editors are used to working in sandboxes.

  • Should we enter the marketing site or the product?

    The product, for a product award. If the marketing site is the achievement, that's Web Experience and a different entry — don't mix them, because we score whichever you sent.

  • Can an internal tool be entered?

    Only if an editor can reach it. A tool used by 400 staff is legitimate design work, but if we can't get in, we can't score it. A sandbox tenant solves this.

  • We shipped incrementally over two years. What do we submit?

    The product as it stands today, and a case study about the decision that mattered most. Award entries reward a clear claim, not a chronology.

  • Does entering a SaaS product cost more than entering a website?

    No. Entry is free for everything, and a recognized project costs the same regardless of what kind of product it is.

Assessed work in business software

Chosen by score from the work the editors have assessed, not by hand.

  • saas
  • product teams
  • entering

Written by

The UXE editors

The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.