Turning Guest Feedback Into a Better Capsule Home Specification

An operator puts four capsule homes on a site, runs them through a season, and ends up with something more valuable than the units: a long list of things guests noticed. Some of it is trivial. Some of it is the difference between a unit that works and one that generates support calls. The mistake is treating that list as a set of site fixes, when most of it is actually a specification brief for the next order.

The Short Answer

Collect feedback in a consistent form, separate recurring comments from one-off ones, and classify each item as behaviour, housekeeping, maintenance or hardware. Only the last category is a factory decision - and those items should be written into the next order as a defined revision, with the previous specification kept on file. Everything else is an operating change and costs nothing to fix.

The Situation

Consider a typical pattern. An operator places a small group of units on a scenic site. The first season goes reasonably well. The units are popular, occupancy is healthy, and the reviews are positive - but the same small complaints appear again and again in the free-text section: the shower takes a while to run hot, the kitchen lacks a surface to put things on, the unit gets warm in the afternoon, the door is awkward with luggage, and nobody can work out the heating controls on the first night.

None of these is a defect, and none of them alone justifies a change. Together, repeated across dozens of stays, they describe exactly what the next order should fix.

Step One: Put Feedback in One Place, in One Form

Feedback arrives scattered - in platform reviews, in messages, in notes left in the unit, in comments to cleaning staff. The first task is consolidation, and the second is consistency.

• One log, whatever form it takes, with unit identifier, date and source.
• A short category list so items can be counted: comfort, water, kitchen, bathroom, noise, controls, access, storage, cleanliness, other.
• Verbatim text preserved. The guest's own words are more useful than a summary.
• A severity marker: prevented use, caused discomfort, or minor irritation.
• A frequency count per category, which is what makes the pattern visible.

Separate the signal

• Recurring and specific - worth acting on.
• Recurring and vague - worth investigating before changing anything.
• One-off and severe - treat as a fault, not a trend.
• One-off and minor - acknowledge and move on.

Guests are good at noticing discomfort and less reliable at diagnosing causes. "The unit is damp" may be ventilation, may be a wet coat, and may be a seal. Investigate before spending money.

Step Two: Classify Every Item by Where the Fix Lives

This is the step that determines whether the feedback leads to a better order or to a wasted one.

Item	Where the fix lives	Action
Controls confusing on first night	Behaviour / housekeeping	A short card in the unit, and a one-line note in the arrival message
Unit warm in the afternoon	Operating or hardware	Check shading and ventilation first; if the cause is the glazing specification, it becomes a factory item
Not enough kitchen surface	Hardware	Factory item: revise the galley layout on the next order
Shower slow to run hot	Hardware or sizing	Check water heater sizing and pipe runs; specify accordingly next time
Door awkward with luggage	Hardware or site	Consider a shelf, a hook, or a threshold detail change
Dust on a shelf	Housekeeping	Change the cleaning checklist, not the unit
Noise from a neighbouring unit	Site planning	Arrive at spacing and orientation on the site plan

Roughly speaking, most recurring complaints resolve to an operating change, and a smaller but more valuable set resolve to a specification change. The discipline is not to convert the first group into spending.

Step Three: Write the Revision, Not a Rewrite

When something does need to change in the product, change that item and keep everything else. A wholesale redesign because of three complaints usually introduces new problems and destroys parts commonality with the units already on site.

• Keep the base specification document and issue a numbered revision.
• List every change and the reason for it, in one line each.
• Ask what the change does to spares. A new door lock is a second part line to stock.
• Check the change against the existing fleet. Prefer changes that can be retrofitted to units already delivered.
• Resist changing cosmetics in response to functional complaints.

Step Four: Close the Loop on Site

Some items are site fixes, and they are frequently the fastest wins.

• An arrival card covering controls, heating, ventilation and waste - the single most common source of first-night confusion.
• A hook, a shelf or a mat where guests demonstrably need one.
• Shading at the right elevation once the sun path is known from a season of use.
• A path or a step that reflects where people actually walk.
• A cleaning checklist revision for the areas that generate comments.

Do these immediately, and re-check the feedback categories afterwards. Items that persist after an operating fix are genuine candidates for the next specification.

What Not to Change

Restraint matters as much as responsiveness. Some recurring comments should never reach the specification.

• Requests that reflect one guest's taste. The test is recurrence across many stays, not the intensity of one opinion.
• Comments that are really about the site - a view, a path, a neighbouring unit. Changing the product will not fix them.
• Anything that breaks commonality with units already on site, unless the benefit is substantial and the spares consequence is accepted in writing.
• Cosmetic changes made in response to functional complaints. They treat the symptom and add a part line.
• Features that add maintenance without adding value to the stay. Every additional component is something that will eventually fail.
• Decisions made before the cause is understood. Guests report symptoms; the operator's job is diagnosis.

What the Factory Needs From You

A factory can only act on a clear description. The most useful brief is short and concrete.

• The model and trim, and the revision of the original specification.
• What guests or staff experienced, in their words.
• What you have already tried, and what changed as a result.
• The climate, occupancy pattern and turnover rate.
• Whether the change must also apply to units already delivered.

Haishu builds A Series units as turnkey dwellings finished in the factory, so layout, glazing, water heating, controls and storage are all decided on the drawing - which is exactly where this feedback belongs. A specification revision raised before the order is placed is a line item; the same change attempted after delivery is a retrofit.

The Takeaway

Consolidate feedback into one log with consistent categories, count it, and classify each recurring item by where the fix lives. Change operating things on site and immediately. Change product things as a numbered revision to a specification you keep on file, and check what each change does to spares. Then brief the factory in concrete terms. The second order should be measurably better than the first - and the reason should be written down.