How Architects Use Occupant Feedback to Improve Future Buildings

The best feedback shows up after people quit being polite about the house. I like to check in around the first month, then again after a full season, because that's when the real habits come out. A walkthrough before closing tells you the work looks good. A family riding out a February rainstorm in Union County tells you whether the mudroom actually works, whether the basement still feels damp, and whether somebody put the kitchen outlet in the wrong spot.

How do I get it? A few ways. I ask people straight, but I also listen for the little gripes they almost apologize for mentioning. Where do the shoes pile up? Which door do they never touch? Is there a bedroom that's always cold? Did they stick a trash can somewhere weird because the cabinets ignored how a person actually cooks? We also watch the callbacks from contractors and inspectors. A repair request that keeps coming back is feedback with a receipt stapled to it.

Then all of that goes into the next job. When three buyers in three different towns complain about the same laundry setup, that's not a taste thing anymore. That's a design miss. On the homes we buy and renovate around New Jersey, mostly older Cape Cods, split levels, and 1950s ranches, the floor plan ends up mattering more than the finishes. People fall for pretty tile on day one. By day thirty they care about storage, lighting, parking, and whether they can get the groceries inside without doing some sideways shuffle through a doorway.

The lesson that really moved me came off a small house in Essex County a few winters back. Renovation looked clean. On paper the kitchen had plenty of cabinets. But the buyer told us later the place had nowhere to put the ugly daily stuff. Backpacks, dog leashes, Amazon boxes, boots, the recycling. None of it ever makes the listing photos, and we hadn't given it a home.

That one stuck with me. Ever since, I push harder for real landing zones by the entry, deeper storage wherever I can steal the space, better lighting outside, and layouts built for somebody dragging themselves in the door at six at night. A house can photograph beautifully and still aggravate the person living in it every single day. The people who live in these places taught me that a design has to survive a Tuesday night, not just the open house.

In enterprise architecture post-occupancy feedback works as a crucial step of the PDCA (Plan-Do-Check-Act) cycle. It is that moment when the theoretical design of a system comes across practical use in daily occupation. My experience of managing enterprise implementation projects at production and distribution sites has shown me how to collect feedback - by recognizing the shadow systems, i.e manual spreadsheets and offline procedures created by users whenever the core digital solution seems too limited and unwieldy. We keep track of these adoptions in the first months of the system usage to find out where the architecture is unable to provide for the needs of operators in the real-life situation. When we use our observations in the Act stage, we can rethink the system to fit human behavior rather than ask a team to adjust to a stiff configuration of a system.

A valuable lesson I have learned during my experiences with users is that any friction a workflow brings will lead to a situation when users are bypassing it. This was a game-changing insight for my design practice: now, I realize that the system is never complete at the point of launch. Rather, the system becomes complete when it is adjusted after users move in and start using it on the daily basis.

At Matson Mourier, we like to revisit projects around six months and again a year after completion. By that point, the initial excitement of moving in has settled and clients have had time to understand how the building really works for them day to day.

Some of the most valuable feedback comes from seeing which seemingly small design decisions have the biggest impact. In one recent home, we introduced a small projecting window seat relatively late in the design process. It has since become a favourite place for the couple's young child to curl up with a book. It was a reminder that relatively modest design details can have a lasting influence on how people experience and enjoy their homes.

We also learn from the practical challenges clients encounter. On another project, a flat roof with a parapet has required more regular clearing of leaf litter because the site is surrounded by mature trees. The clients still prefer the appearance of the parapet, but their experience is something we now discuss with clients on similar projects so they understand the maintenance implications from the outset.

The biggest lesson is that good design is not just about how a building looks or performs on completion; it is about how people live with it over time. Post-occupancy feedback helps us understand which details genuinely improve everyday life, where practical considerations may have been underestimated, and what we can carry forward into future projects.

I'm Runbo Li, co-founder and CEO of Magic Hour. The best feedback loop isn't a survey six months after launch. It's watching people actually use what you built, in real time, and letting that behavior rewrite your assumptions. At Magic Hour, we treat every product release like a building that just got its first tenants. We instrument everything. We watch session recordings. We track where people hesitate, where they drop off, where they spend way more time than we expected. That behavioral data is more honest than any feedback form because people don't always know what they want, but their actions never lie. One lesson that fundamentally changed how we design: users don't read instructions. Early on, we built features with clear explainer text, tooltips, onboarding flows. Nobody read them. We had a video generation template that required a specific input format, and we wrote it out plainly on the page. Over 60% of users still got it wrong on the first try. That was humbling. So we stopped designing for the user who reads and started designing for the user who just clicks. Every template now has to be intuitive enough that someone who skips every word of guidance can still get a good result on their first attempt. We call it "zero-read design." If the interface needs a paragraph of explanation, the interface is broken. That principle applies to any built environment, digital or physical. A door that needs a "push" sign is a badly designed door. A building lobby that needs a directory to be navigable has a wayfinding problem. The best architecture, whether it's software or steel, teaches you how to use it just by existing. The other thing we do is close the loop fast. We don't wait for quarterly reviews. If we ship something on Monday and the data looks off by Wednesday, we're already redesigning. Speed of iteration is the real competitive advantage, not getting it right the first time. Build, watch, learn, rebuild. That's the cycle. And the single biggest lesson is this: your users will always find the version of your product you didn't intend to build. Your job is to pay attention when they do.