Skip to content
Illustrative Case Study

Every submission disappeared into silence. Here’s the loop that closes it.

Three Lochs is a genuinely well-run estate with a resident experience that didn’t match it. Requests went in and nothing came back. Dues arrived like a bill instead of a membership. The sessions traced that gap precisely, and gave us a product built to close it, screen by screen.

The brief

The estate earns the trust. The admin was spending it.

847 homes, a genuinely premium setting, and a resident experience built on a generic property management portal that answered to nobody in particular. Residents weren’t hostile. They were resigned, carrying every unreturned call and silent submission into the next one. The brief was to find out exactly where that resignation formed, and what it would take to replace it with something closer to belonging.

01
Trust scored 1 out of 5. Anxiety scored 5. Almost all of it traced back to one pattern: residents submitted something and heard nothing back.
02
The gap wasn’t a values problem, it was a structural one. The physical estate delivers on its promise. The digital experience, described by residents as “a filing cabinet”, never has.
03
A closed loop only works if the operations behind it can actually deliver. The riskiest thing this product could do was promise a response time the team hadn’t committed to.
The process

Twelve sessions. The same finding, from every angle.

The First 60 Seconds, the Aspiration Gap and the Identity Shift were run independently and landed on the same three-stage arc: recognised, informed, then trusted enough to stop bracing. The Heartbreak Scale put numbers to what the team already sensed, trust at 1 out of 5, anxiety at 5, and named silence after submission as the single biggest trust-killer in the current experience.

Core PrinciplesThe Heartbreak Scale™75 min
DiscoveryThe First 60 Seconds™30 min
DiscoveryThe Aspiration Gap™60 min
DiscoveryThe Identity Shift™45 min
Brand PersonalityThe Dinner Party™15 min
Brand PersonalityThe Rejection Letter™30 min
Brand PersonalityThe Funeral Speech™60 min
Tone & CopyThe Voice Sort™40 min
Tone & CopyWrite It Wrong™30 min
Design PrinciplesDesign Principles Builder™60 min
Design PrinciplesThe Anti-Principles™40 min
Visual DirectionOpposite Ends™10 min
Fifteen years of running a small exceptional hotel was the register the sessions kept returning to: warm, specific, one step ahead. Not the owner, who can be too familiar. Not the front desk, who can be too scripted.
Output 01: Strategy & Brand

From a payer’s resignation to a member’s “we”.

The Feel Factor mapped the emotional arc across three layers, first impression, the journey, and identity transformation, and rated the current experience honestly: trust at 1/5, delight at 1/5, anxiety at 5/5. The Aspiration Gap traced the three moments where that arc holds or collapses. Design Principles turned both into six decision-making rules specific enough to test any screen against.

The Feel Factor®
The Feel Factor

The Feel Factor®

Three layers, first impression, the journey, identity transformation, mapping the emotional arc from account holder to member, and where the current experience breaks it at each stage.

Trust and delight both rated 1/5. Anxiety rated 5/5. The physical estate earns pride the administration hasn’t yet matched.
The arc runs in six stages: resignation, surprise, relief, trust, pride, belonging. Every design decision is tested against whether it advances that arc or stalls it.
The biggest named risk: warm design sitting on top of unchanged operations. The app cannot promise what the team behind it hasn’t committed to deliver.
Download document →
The Aspiration Gap™
Discovery & Strategy

The Aspiration Gap™

The distance between a resident bracing for silence and one who feels looked after, mapped across three critical moments where that distance closes or doesn’t.

Residents arrive asking “Will anyone actually respond if I engage with this?”, a reasonable conclusion from real experience, not cynicism.
Three thresholds govern the journey: the first screen, the first confirmation, and the loop that closes unprompted.
Four structural root causes identified, starting with the absence of any feedback loop between resident experience and what the organisation actually sees.
Download document →
Design Principles
Design

Design Principles

Six principles, each with a measurable signal, governing every judgement call between design and the day-to-day decisions of the build.

Principle one: every loop opened must be closed. A resolved maintenance request that closes silently is, in the words of the sessions, a missed handshake.
Principle five: tone is the product. “Transaction confirmed” and “All sorted for June” carry identical information and produce opposite feelings.
Principle six: the landscape isn’t decoration. A product built only an HOA serving these lochs, these trails, these four neighbourhoods, could have made is a product that can’t be replaced by a generic alternative.
Download document →
Output 02: The Design

Six screens, each one closing a loop the sessions found open.

From the personalised home screen through to the notification that confirms a request is resolved before anyone had to ask. Tap through the screens below.

Original
WAA
Output 03: Technology

A native stack, chosen for one reason: the notification has to arrive.

Every technology decision was tested against the same product requirement, real-time status updates, push notifications that deep-link reliably, and a personalised home screen that loads inside two seconds. The Developer Handoff carried the emotional intent of the design phase into acceptance criteria the build could actually be judged against.

Tech Stack Recommendations
Technical

Tech Stack Recommendations

Swift and Kotlin over React Native and Flutter, NestJS on Node, PostgreSQL, and a Redis caching strategy built specifically around what can and can’t tolerate staleness.

Native over cross-platform for one reason: push notification deep-linking. The maintenance loop is the most trust-sensitive notification in the product, and cross-platform bridges handle it imperfectly.
The home screen bundle is cached with a five-minute TTL, but invalidated immediately on a Stripe webhook. A resident who pays dues should never reopen the app to a stale “outstanding” balance.
Maintenance status is never cached. A resident who sees “received” an hour after it was assigned to a named person has been shown a lie, and no TTL is short enough to make that safe.
Download document →
Developer Handoff
Delivery

Developer Handoff

The layer between a design phase and a build phase: five non-negotiables, emotional and brand acceptance criteria, and a pre-launch review that a build can fail even after QA passes it.

Five load-bearing items, including closed-loop maintenance notifications and dues copy framed as membership rather than billing. Remove any one and the emotional architecture collapses at the moment a resident needs it most.
A prohibited language list is enforced before any component reaches QA: “outstanding balance”, “please be advised” and “reference number” are never permitted to ship.
The pre-launch emotional review requires sign-off from four roles, including a We Are Affective strategist, and a single dissenting voice on a blocking finding holds the release.
Download document →
The result

A product judged on whether a resident feels looked after, not just whether it ships.

Trust at 1/5 and anxiety at 5/5 explained almost everything about how the existing experience was built. The response wasn’t a redesign of the surface. It was a set of decision-making rules specific enough to hold under deadline pressure, and a build handoff that gave those rules teeth.

A definition of trust the team could build to
Closing every loop stopped being an aspiration and became a measurable signal: zero maintenance requests older than seven days without a visible status update.
A voice with a prohibited words list
“Please be advised” and “outstanding balance” are not style notes. They’re listed explicitly as strings that cannot ship, checked before any component enters QA.
A stack chosen for emotional stakes, not just the technical ones
Native mobile, proactive Redis invalidation, a notification service with its own module, each decision traced back to the same requirement: the resident hears back before they have to ask.
A review the build can still fail after QA passes
The pre-launch emotional review checks whether the product feels like Three Lochs, not just whether it functions. A single dissenting reviewer on a blocking finding holds the release.