---
title: "What makes a screen look easy to use?"
code: JZ-004
series: Perception
published: 2026-10
updated: 2026-11-01
author: Joost van der Zwan
canonical: https://softwarebehavior.com/notes/jz-004
skill: studio-jz-looks-or-rules
license: CC BY 4.0
---

# What makes a screen look easy to use?

Field Note JZ-004 · Perception · Pretty feels easier

**252** people rated 26 ATM layouts

## The guess
Usability rules win: grouping, order, safe spacing.

## What the research found
252 people rated 26 ATM screen layouts that all used exactly the same keys. How easy a layout looked went together with how beautiful it looked (r = 0.59), and barely with most of the usability rules designers rely on. The one exception was a familiar, phone-style keypad.

## Why
Before use, looks are all people have. Beauty and familiarity stand in for ease until people actually try the screen.

## What to do
- Polish what people see first. A calm, well-composed layout earns the first try.
- Use patterns people already know (a phone-style keypad, standard form layouts): familiarity makes a screen look easier.
- Then test real use. Looking easy and being easy are separate questions.

## What not to do
- Mistake looking easy for being easy. A polished screen still needs a usability test.
- Swap a familiar pattern for a novel one just because it looks fresher.

## Limits
- People rated the layouts without using them, so this is about how easy a screen looks, not how well it works.
- ATM layouts in Japan; a later study in Israel found the same pattern.

## Example
- Before: A plain but functional payment form, rated hard to use by stakeholders at first sight.
- After: The same fields and order, with consistent alignment, spacing and a familiar card-number layout; then a five-person usability test to check real ease.

## Sources
- Kurosu, M. & Kashimura, K. (1995). Apparent usability vs. inherent usability: experimental analysis on the determinants of the apparent usability. CHI ’95 Conference Companion, 292–293. https://doi.org/10.1145/223355.223680
- Tractinsky, N. (1997). Aesthetics and apparent usability: empirically assessing cultural and methodological issues. Proceedings of CHI ’97, 115–122.

## Use with your AI
This note is also a skill: `studio-jz-looks-or-rules` (version 1.0.0). Download: https://softwarebehavior.com/skills/studio-jz-looks-or-rules.zip · All skills: https://softwarebehavior.com/field-kit

Software Behavior Field Notes by Joost van der Zwan · Studio JZ · CC BY 4.0 · softwarebehavior.com