A framework for assessing whether the systems around a place can carry the ambitions placed on them. Used as a diagnostic before capital is committed, and as an operating spine during pre-development, design and pre-opening.
Inside large organisations, we invest heavily in plans, structures and assets - and underestimate the lived reality required to make them work over time. Strategies are over-modelled at the top of the funnel and under-resourced at the bottom, where they actually have to be lived.
That gap is where risk accumulates. The plan does not fail. The lived reality fails to match the plan.
Experience is not soft. It is causal.
"Soft" sounds harmless. It is not. When the lived layer is treated as decoration, the failure does not show up in the brochure. It shows up first in the people the place is meant to serve - then, on a slower clock, in the model the capital was built on. Both bills always land. They land on different desks, which is why the human one is rarely traced back to its cause.
Sleep that does not come back. Focus that does not return after work. Recovery that gets postponed for years. Older neighbours who quietly stop coming downstairs. Families that never form because no one planned the social geometry. Children growing up without a corner of their own. A building can sit at full occupancy and still fail to be a place where a life can actually be lived over a decade.
This is the cost most easily called "soft" - and it is the one that is hardest to undo, because it compounds in bodies and biographies, not on a balance sheet.
Turnover above the underwriting. Lease-up that slows on the next phase because the first phase quietly broke its own promise. Common areas the operating budget cannot afford to keep alive. Amenities programmed once and then written down. Capex into a building the operator cannot run at the standard the capital was modelled on. Exit values pinned to a hold the lived reality never actually delivered.
This is the cost that eventually shows up in committee - usually two operators and a refinancing too late to fix at the source.
My work sits at the intersection of organisations, environments and capital. Add the lived reality of the people who use the place, and you have four interlocking systems. When something breaks in the visible layer, the cause is almost always one or two systems down.
Most under-performance in housing starts in the org chart, not the building. Decision rights are unclear, accountability is diffuse, and the people who hold the experience P&L are rarely the people authorised to change it.
I draw the actual decision map - not the one in the deck - and surface the calls that will not be made on time. The first deliverable is rarely a recommendation. It is a clear sentence about who owns what, signed by the people who do.
Plans are designed for opening day. Lived experience asks a different question: does the environment hold under daily, decade-long use? Building configuration, common spaces, programming, sequencing - every spatial decision compounds.
I work the spatial brief against operational reality. Not "what should this place feel like" but "what can this organisation actually deliver here every day for thirty years."
The home shapes behaviour, focus, recovery and wellbeing every single day. Behavioural systems are the lived reality the rest of the model has to serve. If the model cannot be lived, the model is the bug.
I look at how residents actually use the spaces, where the operating model creates friction, and which behaviours the development is implicitly asking of people that they will not do.
Capital structure decides what experience is allowed to cost - and across what time horizon. Hold periods that ignore lived experience destroy long-term value. Capital design and life design are the same problem in different languages.
I bring the experience question into the financial model early enough to change it. After committee, the cost of a course-correction multiplies.
The same framework deployed as a pre-investment diagnostic — read on a project before the model meets the resident.
See XDThe four systems are not a sequence to follow once. They are a debugging stack. When something breaks in the lived layer - service inconsistency, drift, vacancy, soft programming - the cause is almost always one or two layers down.
Most engagements I am brought into are sold as experience problems. They turn out to be organisational ones. I rewrite them as system problems and the visible layer takes care of itself.