REAL ESTATE NZ DESIGN SYSTEM
DESIGN SYSTEMS
A case study about consistency, cognitive effort, and designing shared language across a real estate product ecosystem.
ROLE
Product Design, Systems
DELIVERABLES
Components, Patterns, Guidelines
TEAM
Solo
FOCUS
Consistency, Confidence
IMAGINE_
01
Every property page looks different.
02
Buttons move. Terminology changes. Forms behave differently.
03
Some pages feel trustworthy. Others don’t.
After hundreds of interactions, small inconsistencies become cognitive fatigue.
QUESTION TO PONDER
People rarely say
“Your component architecture is inconsistent.”
Instead they experience
The behaviour is visible. The underlying experience isn’t.
VISIBLE / HIDDEN SYSTEM
Visible Behaviour
“I can’t find it.”
“This feels different.”
“I don’t trust this.”
↓
Human Experience
Increased cognitive effort
Reduced familiarity
Loss of confidence
↓
System Causes
Multiple button styles
Different spacing rules
Inconsistent hierarchy
Fragmented component logic
Patterns I noticed
Every team solved similar problems differently.
What looked like creativity was actually fragmentation.
Pattern 02
Designers spent time recreating instead of designing.
The system wasn’t supporting thinking. It was increasing decision fatigue.
Pattern 03
Developers interpreted components differently.
The interface became inconsistent because the design language wasn’t shared.
Pattern 04
Users unknowingly paid the cost.
Every inconsistency required them to stop, reinterpret, and rebuild familiarity.
Interpretation gap
Designers thought
“We’re giving flexibility.”
Developers experienced
Users experienced
“Everything feels slightly different.”
One system. Three interpretations. The same flexibility created ambiguity at every handoff.
MY DESIGN PHILOSOPHY
A design system is often described as a library. I came to see it differently.
It is a shared language.
Languages create shared understanding. Design systems do the same. They reduce ambiguity, increase confidence, create familiarity, and help people move through experiences with less cognitive effort.
Design Principles
Principle 1
Reduce interpretation.
The interface should communicate clearly enough that people spend less time wondering what something means and more time achieving their goal.
Principle 2
Create familiarity.
Consistency isn’t about visual perfection. It’s about reducing unnecessary cognitive effort.
Principle 3
Design relationships.
Components should work together as a coherent ecosystem rather than isolated elements.
Principle 4
Support human confidence.
A predictable interface helps people feel capable, especially during important decisions like buying a home.
LIVE SITE CAPTURE / 02
component states / interaction rules / documentation
WHAT CHANGED MY THINKING?
I realised I wasn’t designing buttons. I was designing familiarity.
01
Initially, I believed a design system was about creating reusable components. This project changed that.
I wasn’t organising components. I was reducing uncertainty. I wasn’t documenting patterns. I was creating shared language.
03
That shift fundamentally changed how I think about design systems. Today I see every component as part of a larger human experience.
HM
Hans Melbert
SHARDS OF SHARED MEMORIES
Leave a note for the archive. Submitted memories become pixel shards visitors can open and read.
Click a shard to read what others left behind.
all rights reserved, hans melbert caoile ©2026