← Back to context

Comment by rawoke083600

1 day ago

These are nice (and ofc not set in stone).

Me not being a "traditional or natural" designer, I like to have a set of best practises recipes or laws. These laws might be difficult to constantly hold in your head. I think this is a PERFECT starting point for AI to "bulk check" some screens.

Honestly I would map it to a short-cut, like I map "format source code" to a shortcut. If you building business software a set of laws or (shortcut mapped to them) can be really useful as a sanity check.

In fact I just did that:

- Downloaded the UX Laws as a screenshot

- Downloaded a screenshot of a dashboard (a userform might have worked better)

- Asked ChatGPT and Claude to do a review with those laws in mind and then to create a new mockup based on those recommendations

Project 1: CMMS Dashboard For Maintenance (fast food chain)

- Dashboard old: https://imgur.com/a/R3wrMpr

- Dashboard new (Claude): https://imgur.com/a/cYq4gE8

Project 2: https://swellslots.com (Surf Forecast App, arcade look and feel)

- Forecast old: https://imgur.com/a/W3daZrP

- Forecast new: https://imgur.com/a/kNi2Nvg

I feel like for Project 1 at least, the old dashboard is better than the new one.

The problem with a set of mutually conflicting laws like this is that good designers are able to intuitively understand which ones to ignore and which ones to use for a particular project.

In the first project, it seems that the old dashboard is intended for a manager doing reporting while the new dashboard is intended for a staff member actually handling the tickets. Did you have anything at all in the prompt with a specific purpose/role, or was it left open?