There’s a deceptively simple scoring model at the heart of Scotland’s Home of the Year:
- Functionality
- Distinctiveness
- Style
👉 Watch it here:
https://www.bbc.co.uk/programmes/m00043v0
Three axes. That’s it.
And yet—watch a few episodes and you realise something important:
👉 The winners aren’t the most expensive homes
👉 They’re not the most technically complex
👉 They’re not even the most “architecturally impressive”
They’re the ones where everything works together.
That should sound very familiar.
The scoring system (and why it matters)
1. Functionality → Does it actually work?
In the show, judges constantly ask:
- Does the space flow?
- Is it practical for how people live?
- Does it solve real constraints?
Homes win when they are liveable, not just beautiful.
Software equivalent:
- Does the system do what users actually need?
- Is it reliable under real-world conditions?
- Can teams operate it at 2am during an incident?
This is your “boring and stable wins” layer.
A stunning system that falls over under load is the architectural equivalent of a glass house you can’t heat.
2. Distinctiveness → What makes it different?
Winning homes always have something unmistakable:
- A bold concept
- A strong point of view
- A clear sense of identity
Judges often say they can “tell who lives there” just by looking at the space.
Software equivalent:
- What is your product’s edge?
- Why does this exist vs competitors?
- What’s the opinion baked into the design?
This is where most systems fail.
They become:
- Generic
- Over-engineered
- Indistinguishable from everything else
If your system could be swapped with a competitor’s and no one notices, you’ve built a house with no personality.
3. Style → How it feels
This is the subtle one.
Style in the show isn’t about trends—it’s about coherence:
- Does everything belong?
- Is there a consistent language?
- Does it feel intentional?
The best homes feel effortless, even when they’re complex.
Software equivalent:
- Clean APIs
- Consistent patterns
- Thoughtful UX
- Clear developer experience
Style is what turns:
- “It works” → into “this is a pleasure to use”
The hidden fourth dimension: Cohesion
Here’s what the scoring model doesn’t explicitly say—but the show makes obvious:
👉 The winning home is the one where functionality, distinctiveness, and style reinforce each other
Not compete.
That balance is everything.
Where software teams go wrong (the anti-patterns)
❌ Over-index on “style” (architecture theatre)
- Kubernetes for a demo
- Microservices with no scale problem
- “Look, it’s event-driven”
Result: Beautiful house, no heating
❌ Over-index on “functionality”
- Works, but painful to use
- No product thinking
- No differentiation
Result: Perfectly functional… and completely forgettable
❌ Over-index on “distinctiveness”
- Reinventing everything
- “Clever” over “useful”
- No operational grounding
Result: A statement piece nobody wants to live in
The real lesson: design for how it’s lived in
The best insight from the show:
👉 Great homes are designed for the people who live in them—not the judges
That’s why personality matters.
That’s why constraints matter.
That’s why trade-offs matter.
Software parallel:
- Design for users, not demos
- Design for operators, not just builders
- Design for evolution, not perfection
TL;DR
- Functionality → It works, reliably
- Distinctiveness → It has a point of view
- Style → It’s coherent and usable
👉 Great systems win when all three align
Final thought
The best homes don’t feel engineered.
They feel right.
Same with software.
If people notice your architecture more than your product…
You’ve built something impressive.
But you haven’t built something great.