Each new screen in a hotel system asks a busy person to remember where something lives. The second of our four principles treats that as a real cost: build for outcomes, not more tabs. In Guester it shapes the interface directly. Data reads first, every department shares one workspace, motion explains state and accessibility is pursued as a target.
Every new tab is a cost
Guester’s users are general managers and their department teams, who reach for it between guest interactions and during shift handovers. Every extra place to look takes attention away from the property itself.
For example, a manager looking into one guest’s stay might need the reservation, a recent review and an open ticket. Spread across separate tools, that is several logins and several ways of thinking for a single question.
A new tab adds a place to check and a place to forget. It is often the easiest thing for a product team to ship, because it does not have to fit with anything else. The line behind the principle comes from our About page:
People should run the business. Not spend their day running the software.
To us, building for outcomes means starting from what a manager needs to get done and shaping the interface around it, instead of giving every feature its own destination. The interface principles below are how that idea becomes design decisions.
Data reads first
The first interface principle is that data reads first. The idea is that when someone opens a view, the state of the property comes before navigation, settings or decoration. Controls exist to act on what the data shows, so we think they belong second.
For example, a list of open tickets should lead with the tickets and what each one needs, with filters close at hand but out of the way. The difference looks cosmetic. In practice it decides whether a person acts at a glance or spends their attention hunting for the right panel.
This is where outcomes and tabs part ways. A tab tells a person where something is stored. A view that reads data first tells them what is happening and what needs doing next.
One workspace for every department
Hotel work crosses departments all day. Housekeeping, the front desk, sales and F&B each own part of a guest’s stay. A separate tool for each team splits that stay into pieces that someone then has to reassemble by hand.
In Guester, management, the departments and the Morning Brief share one navigation and control language. A department team and a general manager may look at different work, but they move through it the same way. This matters most at handovers, where the incoming shift should not have to translate anything the outgoing shift left behind.
Continuity belongs to the same idea. Addresses, records and survey links are preserved, so the things a team relies on stay where they were as the interface changes.
Motion that explains state
Motion in Guester has a job: it conveys state. It is not there as decoration for a busy person to wait through. The rules it follows are specific:
- Feedback is brief.
- Updates are interruptible.
- Keyboard actions settle immediately.
- Reduced-motion preferences are respected.
- Offscreen effects pause.
- Native scrolling stays intact.
Each rule protects attention. An animation that cannot be interrupted makes a fast user wait. Custom scrolling that fights the device feels wrong almost at once. Effects that keep running offscreen spend resources on something nobody is looking at.
The test for any motion is simple. If it does not tell a person that something changed, it does not belong. Brief feedback confirming that an action registered passes the test. A flourish on every page load does not.
The same thinking applies when nothing moves. A section that is loading, empty or failing should say which. The designed states of the portal editor, covered in never overwrite someone’s work silently, apply the same rule.
Accessibility as a target, not a claim
We treat WCAG 2.1 AA as a target, not a claim of certification. We say so plainly because the difference matters to anyone who has to verify it.
Several commitments are concrete. Focus rings are visible, so keyboard users can see where they are. Status never relies on hue alone, so a person who cannot distinguish certain colors still reads it correctly. Labels come in Turkish, English, Spanish and Arabic, with right-to-left support.
Right-to-left support has to reach the whole layout, not only the words, for a team reading Arabic to work at full speed. Language support is part of the same promise: the interface should never be the slowest part of the shift.
Dark mode supports evening operations, for example a late shift working in a dim back office. In our view, none of this belongs on a separate accessibility track. It follows from the same principle: an interface built around outcomes has to work for everyone responsible for those outcomes.
Fewer tabs is the visible result. The real aim is a workspace where the people running a hotel spend their attention on the hotel. Every interface decision in Guester is held to one test: a new screen has to remove more work than it adds.
