Hidden Structures

When the hotel closed for its six-month capital transformation, I had already decided to fire most of the kitchen team.

The chef would stay. He was the experienced one, the anchor, the logical choice. The cook and the kitchen assistant would go. They were hardworking but timid, and I did not believe they would survive what was coming.

On the morning I was going to tell them, something stopped me.

Not sentiment. An observation I had been collecting for months without letting it reach a conclusion. The chef had a pattern. Manipulative, slightly toxic, the kind that never appears in any review because it moves below the surface. The cook shrank when he entered the kitchen. The assistant worked faster, trying to disappear into efficiency.

They were good people working inside a structure that required them to be small.

I flipped the decision. The chef left. The cook and the assistant stayed.

One more detail, because the numbers matter in this series: the cook and the assistant together earned the same salary as the chef. I removed the structure suppressing two people without increasing payroll. I exchanged one assumed certainty for two developing capabilities.

Today, that cook is an executive chef, systems developer, and partner in my operating company. The assistant is now a cook, and the person who trains all new kitchen staff.

Their capacity had not changed overnight. The structure had. Once it did, they grew into what had been suppressed all along.

The misdiagnosis

Here is what I got wrong that morning, and what almost cost me two of my best people.

I had mistaken dominance for competence, and timidity for limited capacity.

The chef looked indispensable because the structure was organized around his power. The others looked weak because the same structure required weakness from them. I was reading the behavior and calling it the person. The behavior belonged to the structure.

This is the most common diagnostic error I see, in kitchens and in data rooms. The observable condition gets mistaken for the underlying capacity. A weak operator looks weak. A dependent organization looks loyal. A toxic leader looks indispensable. A channel dependency looks like revenue.

None of those readings are wrong about what is visible. All of them can be wrong about what is possible.

What a hidden structure is

A hidden structure is the thing installed so early or so deep that it stops looking like a structure and starts looking like fate.

I learned to see them in myself first. There is a thought pattern so familiar it stops looking like a choice and starts looking like who you are. Years ago, I learned to separate a repeated pattern from objective reality: to observe a belief without automatically obeying it. Once I could see my own structures, I could see them in other people too.

And then in every property I walked into.

Every founder-built property is a self-portrait. The owner’s fears become the pricing. The need for control becomes the org chart. The blind spots become the deferred decisions. The chef’s pattern was as much a part of that hotel as the roof, and it was carried on no inventory list.

A structure like this is invisible precisely because it is everywhere. Everyone inside it calls it normal.

Reading the asset

For a buyer, the hidden structures are where the actual risk and the actual upside live. A few worth underwriting, because none of them appear in a trailing twelve months:

Founder dependency. The property performs because one person holds the relationships, the pricing logic, and the memory. That person is not transferable with the asset.

Informal authority. The org chart names one decision maker. The building obeys another. Until you know who the building obeys, you do not know what you are buying.

Suppressed second-line talent. My cook had worked in that kitchen for years far below the level of his actual capability. Most underperforming properties are storing capability like this, priced at zero.

Fear-based reporting. Numbers that decorate reality instead of describing it because the structure punishes honesty. The books can be accurate and still tell the wrong story.

Habits fossilized into procedure. Pricing set years ago for a market that no longer exists. Channel arrangements nobody renegotiates. Decisions deferred so long they read as policy.

Each of these is invisible in a data room and legible in the building, if you know that what you are looking at is architecture and not character.

The acquisition implication

The opportunity is not simply to buy performance. It is to identify where performance is being suppressed, overstated, or held together by a person who cannot be transferred with the asset.

A property that runs on one man’s dominance carries a hidden dependency: remove him and it collapses. But the reverse is also true, and far more interesting to a buyer. A property suppressed by its own structure carries hidden capacity: change the structure and it rises, often with the people already standing in the building.

What looked like architecture was often only personality repeated at scale. And what looked like limited capacity was often only a structure requiring people to be small.

The strongest acquisitions happen when the buyer can read what the seller cannot see.

I learned to read it in a kitchen, on the morning I almost removed the very capacity the hotel would later depend on.

Part of the ongoing Field Notes series exploring how invisible structures shape the value of hospitality assets.

Tara Nicole Nowacki is an independent Hospitality Asset Architect advising investors, family offices and hotel owners on acquisition strategy, operational transformation and exit readiness across Central America. tara@taranowacki.com · taranowacki.com

Every Field Note is written from direct operational experience inside hospitality assets. Names, locations, or details may occasionally be adapted for clarity or confidentiality, but the underlying observations are real.