Freelance work is supposed to be short. You arrive, you deliver a defined thing, you invoice, you move on. That is the shape of the trade, and most people I know live comfortably inside it. Mine keeps refusing to follow the script. A project that begins as a few screens for an early prototype stretches into the MVP, then survives into the investment round, then into the pitch itself, and somewhere along the way both sides quietly stop pretending it was ever a short engagement. I have been trying to understand why for a long time, partly out of gratitude and partly out of curiosity, and what follows is the closest I have come to an answer.

The founders I have worked with are not alike. Some understand their own product down to the smallest decision. Others, especially earlier in my career, could see what they wanted to build with complete clarity but had no way of judging the design or the development or the management underneath it, because those were never their languages. What they share is a position I did not properly appreciate for years, because I was too busy worrying about my own side of the table. Every one of them was spending serious money, often money that took years to gather, on people whose work they could not fully evaluate. I try sometimes to actually sit in that chair. You are sending a large sum to someone you barely know, for something you cannot inspect until it is too late to change your mind, and the person you are paying is the only one in the room who knows whether the plan is sound. We talk about founders and risk in an admiring, abstract way. Up close, a good part of the risk is simply the people they hire. People like me.

For most of my early career I assumed the answer to all of this was good work. Do the work well, and trust accumulates on its own, a small deposit with every solid deliverable. The longer I have sat with it, the less I believe that, and the reason took me a while to accept. Good work is the baseline. It is what everyone was hired for, and more to the point, it is what a purely self-interested person would also produce, because hitting the deadline and polishing the screens is exactly what keeps the money coming. When my interests and a client’s point in the same direction, my behaving well tells them almost nothing about me. They learn that I am competent. They cannot learn what I would do on the day our interests split, and that day is the only one they are actually afraid of.

So, trust, if I follow the thought honestly, can only be built in a narrow and strange set of moments: the ones where you could profit from someone and choose not to. Everything else is pleasant noise. There is a well-known idea in economics, from Michael Spence, that points at the same thing from another angle. He called it signaling, and the core of it fits in one line: a message is only believable when it costs the sender something. Words are cheap, which is why anyone can claim to be honest and why the claim carries no information at all. A signal that hurts to send is different. It cannot be faked cheaply, so it is the only kind that gets believed. Once the shape of that idea settles in, you start to recognize what the believable signals in this trade actually are. The feature you argue against, knowing you would have been the one paid to build it. The estimate you revise downward because the work turned out simpler than you priced. The mistake you raise before anyone would have found it. The month you tell someone not to hire you, because they are not ready to use you well. Each one is an invoice that never existed, and each one is expensive in the moment, which is precisely why it means something. None of them feel strategic when they happen. Mostly they feel like small acts of self-harm, and I suspect that feeling is the point. If it cost nothing, it would say nothing.

What does the founder actually receive in those moments? For a long time, I would have said better decisions, and sometimes that is true. But the deeper thing is quieter. A founder carries the company around in their head all day, and a real part of that weight is vigilance, the low, constant work of wondering whether the people they pay are telling them the whole truth. That worry appears in no budget and gets admitted to almost no one. The first time someone demonstrates, at their own expense, that they will volunteer the inconvenient truth unprompted, a founder gets to put that vigilance down, at least in one direction. They stop composing the checking-up email in their head. What they were buying was never really the screens. It was the ability to stop thinking about the screens. I keep returning to that as the most honest description of a long engagement I can manage, one person taking custody of a corner of another person’s worry. There is something almost tender in it, though I would phrase it more carefully in a meeting.

Follow that thought one step further and it opens onto something much larger, which I did not expect when I started pulling on it. All that vigilance has a cost, and the cost does not stop at one worried founder. Every relationship, every company, every country pays a hidden tax that is proportional to how little it’s people can trust each other. The tax is called checking. Contracts thick enough to survive a betrayal, approvals stacked on approvals, receipts for the receipts, the meeting held to confirm what the last meeting decided. None of that produces anything. All of it exists because somebody, somewhere, might not be straight, and so everyone must be treated as if they might not be. A team whose members never have to verify one another moves at a speed that looks, from the outside, like talent. Often it is nothing of the sort. It is simply that doubt has been removed, and with it the enormous invisible cost of re-checking everything twice. I have slowly come to believe that most of what we call efficiency is trust wearing work clothes, and that the most expensive thing in any system, a marriage, a startup, a state, is doubt. Which changes what a trustworthy person actually is. They are a subsidy. Every hour their colleagues do not spend double-checking them is an hour their honesty quietly paid for, and almost nobody sends them the bill they covered.

This also settled, for me, a question about portfolios I had carried for years without quite being able to phrase. A portfolio matters, and I tell every beginner to build one, because it is how a stranger checks that you can do the work at all. But it can only ever carry half of you. Competence leaves artifacts. Screens, systems, shipped things, all of it can be photographed and uploaded and browsed by someone who has never met you. Character produces no artifact. There is no file format for the feature you argued against, no case study for the fee you gave back. Character leaves only witnesses. Which explains something I had noticed but could not account for: somewhere in the middle of a career, the portfolio quietly stops being what brings the work in, and the stories people talk about you take over, told in rooms you are not in, by people describing a moment when you could have taken more from them and didn’t. So, the most important asset of a working life ends up stored outside you, scattered across other people’s memories, where you can neither audit it nor spend it directly. You cannot even see your own. You only ever make deposits, one expensive sentence at a time, and it circulates entirely without you.

I want to name the trap in all of this rather than pretend the thinking is tidy. The moment costly honesty becomes a tactic, a calculated deposit toward future contracts, something in it spoils. People detect performed virtue far better than we like to admit, and honesty-as-strategy has a smell that honesty-as-habit does not. Which leaves a slightly circular truth sitting in the middle of the whole subject, and I have not found a way around it: the signals only work when they are not sent in order to work. I should also say plainly that the world does not always cooperate. Costs get eaten that nobody notices. There are rooms that reward the confident liar over the careful truth-teller, and no amount of integrity fixes a room like that. Being worth trusting is not a machine you put coins into.

So, I do not end at a formula, and I have grown wary of anyone whose thoughts on trust arrive at one. What I am left with is smaller, and it has held up. The projects that would not end on schedule were never extended because a deliverable impressed someone. Somewhere inside each of them there must have been a moment, probably unannounced, probably invisible to me as well, when a founder stopped checking behind me, and everything that followed flowed out of that. The work I can point at afterwards is the visible part. The part that decided everything else has no artifact at all, and I have made my peace with that. No one will ever browse it. It exists for one person at a time; on the day they are deciding whether they can stop worrying about you.

Type of research: Secondary research synthesis

Primary research: Not conducted (freelance limitation)

References: 10 open-access peer-reviewed articles, 2018-2024

Project stage: Post-hypothesis ideation.

This will be an overview of UX research on a previous freelance assignment. Their private information such as the particular market, company names, and internal product decisions has been modified.

The central fact to interpret into this reading is that this was done on lean constraints: no money was available, and no time to carry out new user research, such as interviews, site visits, or usability tests. Then this outline was the initial in-depth examination of the product concepts. It had a pre-brainstorming step after which it was applied to check those ideas with already existing published information before any actual design choices were made.

I am posting it as an example of how a careful and solid way of conducting research is analyzing existing research when you lack a budget or have to work remotely.

Context and Methodology

This was written at the beginning of the analysis of freelance work on a software product related to independent hotel property management. At the time I wrote this synthesis, I had already formed some initial ideas and hypotheses. That was the step of making cautious guesses about who the users are, what the problems might be, and which product directions could be effective. These were the conjectures I made by consulting stakeholders, examining the market, and drawing on the experience of practitioners, but they had not yet been tested against external evidence.

This synthesis was intended to test my original hypotheses before beginning the design phase. The question was not whether the product could be built, but whether my assumptions about users were correct based on research. If a hypothesis was supported in the literature, I retained it. If something contradicted it, I modified the hypothesis. If I found a new factor that had not been captured in the initial stage, I included it in the analysis.

The study was structured as a secondary research synthesis. I used sources such as ResearchGate, MDPI, Sage Open, and other open-access publishing portals. I identified 10 peer-reviewed open-access articles published between 2018 and 2024. These papers were selected because they address three related issues: hospitality SMEs, technology adoption, and pricing model design and its influence on user behavior in SaaS products, as well as software design for distributed and mobile-first work. The references include links to each paper.

On lack of primary research

The main limitation of this report is that I did not conduct primary research. I did not interview users, observe hotel operators, or conduct contextual inquiries. The user insights are based on published studies rather than interviews or direct observations. The mental model descriptions therefore do not reflect the observed behavior of specific individuals but instead synthesize findings from existing research.

This limitation is acknowledged in the introduction of the synthesis as an analytical boundary rather than a disclaimer. When time or budget constraints prevent primary research, an in-depth secondary synthesis can still be a rigorous analytical process. It is more reliable than proceeding with untested assumptions and provides a documented evidence base that can guide and focus future primary research, making it more effective. This paper should therefore be considered not as definitive research but as a well-grounded starting point.

Research Questions

The synthesis was systematized into three research questions that were direct results of contemplating the hypothesis. These questions were not posed in the literature; I posed them initially. They helped to focus my attention on the most topical research and connect what we have studied with the design I have created.

RQ1 Why can independent hotel operators not embrace and continue to use property management software, even when it is obvious and apparent they need it?

RQ2 How does structural mismatch between subscription pricing model which is based on fixed cost and seasonal patterns of income influence the operator behavior and their perception of software value?

RQ3 What interface structure and interaction model would be good to the manner in which employees in a hotel actually work at different departments, mobile devices and with a poor network connection?

Who We Are Designing For

The UX synthesis is not based on solutions but users. In this project, no specific group of users exists, but a set of operationally different positions within the same property, with different structure of tasks, different device relations and a significantly different attitude towards the software product. The fact that these differences exist is not a peripheral concern to the design problem it is the design problem. An option that would be a good fit in one role may become a thorn in a different role.

The Owner-Operator

Most of the smaller hotels have the independent hotel owner-operator who is the primary consumer of this product, and does the reservations, housekeeping, the guest complaints, and the accounts reconciliation. The person who is carrying out a structural feature analysis using a procurement process is not a technology assessor. It is someone that already has a number of operating pressures and time limitations, and software will need to demonstrate itself in a positive way within a limited amount of time and offer or lose it.

The research which examined the adoption of digital transformation by 502 independent hoteliers has discovered that the financial resources constraint is the most important single predictor of digital transformation adoption intention among this segment as opposed to the digital awareness or peer influence (Nguyen et al., 2023). The implication is also important: the limitation to the adoption of technology does not lie in the resistance of this user to technology. It is a reasonable cost-risk estimation, and the approach of estimation is decided by the past experience. The operator who has paid full-rate subscription during the shoulder months when the system is not very occupied and when the system is hardly used carries the experience across all the future product consideration.

OBSERVATION: The owner-operators never quit PMS tools due to their reluctance towards technological advancement. They discount them because the fixed monthly fee is an apparent and non-proportional cost at the time when a small number of individuals are residing in it and the system is required to contribute lower operational value than what it is billing them.

MENTAL MODEL: The operator has come up with a mental notion about software as an overhead that is fixed in nature and structurally similar to rent. A reduced seasonal revenue is extractive of fixed costs. Comparative to rent, however, software does not, it appears like it should be growing with actual use. The flat subscription model contradicts this expectation and forms a kind of predetermined and permanent resentment.

DESIGN IMPLICATION: The operator should have an elastic pricing structure. Contract platform fee should also reduce in low occupancy months and increase in the peak months

The Front Desk Agent

The front office agent is the interface of the guests. Their work is hectic, time sensitive and interrupted. They check-in, receive requests, respond to room inquiries, and communicate with other departments, normally simultaneously. This can only be done under a condition that the information they get regarding the current state of the hotel is valid and prompt. A study of process innovation in hospitality established that the most significant technology deliverable to front-of-house employees in a survey of 631 hotel employees and managers was operational smoothness, or the reliability and speed of information flow between departments (Mohd Noor et al., 2023). The observation indicates that the most important relationship that the front desk agent has with software is not feature related, but trust: does this system provide me with what I need, when I need it, and I do not need to go after it?

OBSERVATION: Front desk agents are also usually forced to be dealing with check ins without knowing whether or not the rooms are ready. Their information receiving mode through housekeeping is not real-time and reliable either; it may be a phone call, a printed list of assignments, or a thread of messages in a group.

MENTAL MODEL: The front desk agents believe that rooms are not ready until they are confirmed. The PMS is a bookings and schedule record in their experience; it contains the past and future data but does not represent the real state of running of the building. It is not a coordination tool, but a reference tool.

DESIGN IMPLICATION: Room status should not be a periodically updated record, but a live operational feed. The front desk interface must consider the difference in time between a guest and room getting confirmed as a ready room as an equivalent to the design main failure state.

The Housekeeping Supervisor

The physical mobility user who is the most active in this system is the housekeeping supervisor. Their working regime presupposes that it is always on the move between the guest-trafficable floors, active control over the cleaning staff, and active reaction to the shift of priorities due to the early arrivals or delayed departures. They do not work in a stationary position. They can barely put a stop to their movement to navigate an interface that was not even designed to fit their situation. A SAGE Open (2024) study is an open-access article that has found mobile interface intuitiveness and usability to be among the most significant predictors of technology acceptance among hotel members that are operational and that tools with desktop interfaces had significantly lower levels of adoption rates among this category of mobile role (Fornells Herrera et al., 2024). The practical implication of this finding is simple; a tool is not on the equipment in the hand of the staff member is not in the hand of the staff member even though it may be operable in other places.

OBSERVATION: Housekeeping supervisors are given a list of rooms under their care in the form of print or informal messages and report back to front desk on the occupied rooms through the same way of using informal messages. Information flow between the housekeeping and front desk is not merely not seamless but also sluggish and based on personal follow ups and not constructions of systems.

MENTAL MODEL: The housekeeping supervisor has no mental perspective of the PMS as a tool that is a part of his work. The PMS represents a front desk system in their working experience. Their tools are the phone, the printed piece of paper and the group messaging application. Any new digital tool will be evaluated on these familiar substitutes on one practical ground: does this save time or spend time than I am currently doing?

DESIGN IMPLICATION: Housekeeping module is supposed to be provably quicker than a messaging application. It must function offline. It must be able to show one, clear screen with the room appointments of the day with one, single-tap action to show that a room is ready and one, single-tap action to show that something has gone wrong. The additional depth of interaction will cause the staff member to revert to his or her existing workaround

The Maintenance Technician

The maintenance technician operates in the least accessible areas of the building such as service corridors, plant rooms and basements. Through informal verbal or message feeds, they get fault reports. Due to the lack of a structured log system, there is no history of repeat issues to refer to, no history of a job being done, and the front desk has no means of determining whether the problem is resolved or not without calling the technician on the phone.

OBSERVATION : There is an informal approach to maintenance issues. These are communicated orally or by message and are set in place depending on the technician on the experience and memory, and are not written down. The front desk does not have an official method of making sure a problem is resolved without having to come in physical contact with the technician.

MENTAL MODEL: The absence of a structured system does not hurt the technician; they have learned to work with what they have. The impatience manifests itself in other ways: the employee at the front desk is not able to provide a definite response to the customers and the property owner is not able to observe patterns in the recurring issues. This problem does not primarily seem to victimize the technician, but rather makes him a bystander in the middle.

DESIGN IMPLICATION: The maintenance module has to generate operational value without incurring any cognitive overheads. An indication of a job queue, a completion toggle, and an optional photo record can be considered the right functional scope. This user does not have personal efficiency as his value proposition, but rather professional visibility. A successful and documented job offers some degree of responsibility that is more advantageous to the technician than it is to the operation.

Where the Current Experience Breaks

It is at this stage that the user group unity is formed, and the actual problems are revealed. The present experience is one of a combination of obsolete tools, unofficial communication and hack and slap solutions that cause friction, failure and leaving. These issues are not mere feature holes, they are the inappropriateness of what users need to the capabilities of what they are able to do in their workspace and what their tools are able to do.

Breakdown 1: It is Not a Cost that Match the Value Experienced

Most of the research studies have concluded that flat subscriptions are detrimental to businesses that are seasonal in demand. A hotel with few rooms selling only a few rooms during the slow months still incurs the same fee as during the times when it is full. The owner of the hotel makes payments in the form of percentage of bookings, percentage of revenue, and fee of the system even when the system is used less. This has a long-term impression of them overpaying.

Studies indicate that, when the consumers are employing pay-to-use pricing model, they will embrace more features and will remain on the platform. It is tough on the mind to pay unused capacity and therefore consumption model suits better to the operator.

This does not have to do with money, but rather how users feel. When the invoice includes a flat rate in the case of a slow hotel, the operator believes that the product is useless. The negative emotion transpires to the subsequent billing cycle and may result in churn. The user experience also includes the pricing model: it informs the operator about the importance of the product.

How Might We…

Develop a pricing experience that helps the operator feel that the platform is an actual partner when low months are on, not a set price that does not acknowledge what they are going through?

Breakdown 2: The Interface Had been Constructed to a different User

The independent hotel operators seek mainstream property management systems, yet the latter are aimed at large-hotels, having several rooms, permanent revenue teams, and IT personnel. Installing and operating such systems in a 20-room hotel is not as easy a task as it should be. Institutional theory study revealed that complexity and cost are the primary obstacles to independent operators who can give up the system when it becomes too difficult, particularly in comparison with chain hotels that do have IT support. (Abou-Shouk et al., 2021).

The outcome is expected: operators install the system, utilize a limited number of features they tend to use the reservation calendar and feel that they spent money on an extra functionality that they never used. The product was not a failure due to lack of features; it was a failure since it offered the wrong experience to the wrong user.

How Might We…

Create a system that does not make the operator feel like he/she is buying something he/she will not need and does not suit his/her operations?

Breakdown 3: The Tool Is Not Where the Work Is

Hotel work is distributed: guests on guest floors, service areas on maintenance, and desk on back-office. A tool that is based on a back-office desktop is not available to personnel who require it at their shifts. A research established that the option of accessing the system through mobile devices was accompanied by certain changes in operations that are measurable since the employees were able to use the system in the actual work place. (Amirulloh et al., 2024).

Breakdown 4: Information Cannot Cross Departmental Boundaries

The greatest breakdown of the present experience does not lie in a departmental unit but in the interdepartmental one. The guest arrives at the check-in desk, yet the agent is not sure whether the room is ready or not because the housekeeping has not updated status. There was some reported maintenance problem in the night, but the front desk does not know whether it is repaired or not. Dietary preference of the guest on which he/she made the booking is not displayed at the check-in point.

A systematic review hotel technology reported that the most service issues in independent hotels were related to cross-department coordination failure (Dirsehan & Yuksek, 2025). The review concluded that digital integrated tools are the difference between high and low performing hotels. The culprit is not the incompetence or the ill-intention of staff but information infrastructure. Employees are aware of what they are supposed to do but they lack the information necessary as the system does not give it.

How Might We…

Establish interdepartmental information exchange that is immediate and continuous, such as face to face talk without compelling employees to alter any of their fundamental communication habits within the identical day?

Design Directions

The entire outcome of this synthesis is a collection of design directions. All of them are the result of a particular user insight or research discovery that is formulated as a product goal rather than a feature list. Solutions are not them, but the concepts around which we have to construct solutions.

Direction 1: Pricing as User Experience Surface

This is a design pricing strategy but not only a business decision. It has an influence on the utilization of the tool by the operator. A user will trust the product in an event that he believes that the charge corresponds to the value the platform will give them in a certain period. Others cancel because they pay a fixed charge yet they are not exploiting the system.

The design should indicate the cost of the product not just on a bill. The operator that will also use their main dashboard should be able to view their present occupancy level, their monthly occupancy average, and what they will be charged at the end of the month without having to travel to a section that determines their bill (Kowalski et al., 2021). An analysis of tiered SaaS pricing discovered that apparent value congruency develops fairness and retains cost-sensitive SME clients. The pricing must be a daily experience and not a surprise on the invoice.

Realize the pricing logic on the dashboard of the operator

Why: The trust is achieved by making sure that you see fair costs on a regular basis. The invoice will not develop such a trust when there is some hidden pricing on the invoice, regardless of how just it is.

What: In the owner dashboard, the real-time occupancy tier, monthly average occupancy, and the forecasted monthly fee will be displayed. Plain language is used to describe the logic next to the figure. There is no necessity to go to a billing section.

Direction 2: One Role, One Interface

The article on the complexity of adoptions identifies that the use of a single interface by all individuals leads to issues. Rather than maintaining a monolithic design, we ought to provide purpose-specific interfaces to each role and present them with the information they require in their workflow.

Studies in the modular and micro-services architecture of hotel systems indicate that the presence of role-specific interfaces eliminates friction and is more welcoming to non-technical employees (Rahman & Hossain, 2024). As the example, a housekeeping supervisor does not require a front-desk interface. They require a housekeeping interface which is constructed on their job, equipment and surroundings.

Turn single operational modules into an experience of their own

Why: The tools that employees use are those they feel are designed to do their work. Even a basic interface is not associated with a generic interface which does not create trust and long-term use.

What: Front desk: live room, reservation activities, arrivals. Housekeeping: room assignment list, single-tap completion, issue flag. Maintenance: open job queue, completion toggle, photo log. Goal: occupancy, fees projection, cross-departmental health indicators.

Direction 3: Three Interactions as an Adoption Threshold

As they move around, operational staff have to complete their tasks within a short duration of time. The measuring of usability is not in features but rather in interactions and seconds. A housekeeping manager gets approximately fifteen seconds to finish a room and proceed. Assuming that the completion screen will require more than three interactions with the home screen, they will resort to using a messaging application, and the information will exit the system.

This ceiling is not an objective, it is the adoption limit. North of this level the product will be phased out by the existing workaround. The studies of technology acceptance in hospitality indicate that the pace of interactions is the primary criterion of mobile tool adoption (Fornells Herrera et al., 2024). The interaction model of any given module should not only resemble but also be as rapid as available workaround of the software.

The home screen of the module is supposed to allow a user to complete all tasks using three interactions.

Why: Employees will only match new tools to the speed. In case the tool is not fast enough compared to a messaging application, they will continue its old way.

What: Design the flow: open module then view task list then complete task. At most, two or three contacts. No confirmation boxes on regular status updates. The flow should be non-interruptible and available.

Direction 4: Trust Mechanism of Real-Time Synchronization

The key benefit of this platform is that one can share information generated in one department with another department without human assistance. When a housekeeper mentions a room as ready, the front desk has to view this change in a matter of several seconds, not the next time the list was updated or the next time a message was resent. This live match has to occur at the start, not the start up. It is in the way the platform fosters trust among the front desk agents who usually believe that no system can provide them with trustworthy live room status.

One of the studies conducted on cloud PMS discovered that the greatest benefit of properties which shifted to integrated systems was the ability to have real time data in different departments. This was missing on properties that remained with fragmented tools (Amirulloh et al., 2024). The platform should be able to synchronise in a way that it is perceived by the user that it is instant and any delay should be perceived as untrustworthy by those who already do not trust system information.

The room status and task completions must feel like it is in real time on all the relevant devices.

Why: Front desk agents do not believe that any system is able to offer reliable live data. Any delayed or wrong update will support that perception and destroy trust.

What: Status changes will be shown on all devices linked together in a few seconds. Status icons are all timed. Offline updates have been made automatic when the device is back online, and the user does not have to do anything.

Direction 5: Progressive Activation as Adoption Infrastructure

According to the research, the biggest obstacle to implementation of PMS to independent operators is the complexity of the implementation, second only to cost. The systems with a requirement to install lots of modules and to educate workers on lots of jobs and to start everything simultaneously will be discarded before they can demonstrate any positive outcome. The platform should be able to operate on the first night and also enhance itself without the aid of the operator.

This design suggests an activation model that is progressive. It will install the core reservation module on opening day and is capable of completing the setup in a single workday with assistant configuration. Follow-up modules will be enabled at the discretion of the operator and each will have a role-related onboarding experience. An experiment on the Technology Acceptance Model and institutional theory produced results showing that ease of initial configuration was the determining factor of sustained use when the help of an IT team was not received (Abou-Shouk et al., 2021).

This system must be capable of working at the first day and all the new modules must be enabled at the speed of the operator.

Why: The independent operators do not have the time, personnel or IT to execute staged implementation projects. Any additional vendor support requirement is a failure point.

What: Core reservation module: establish and check-in in a single session. All other modules: single-screen activation and a three-step guided set up and an in-app role-based walkthrough. No calls to vendors, no telephone calls, no implementation project needed.

Direction 6: Offline Capability as a Baseline Requirement

There is disproportionate connectivity with hotel properties. Devices usually lost connection in service corridors, plant rooms, basements, and high traffic times. Being offline is also typical of the staff who moves around the course of work. A system that becomes inactive when not online is not reliable and is not going to be adopted.

All operational modules should be functional without a network and automatic on recovery of network.

Why: In case of a room status or maintenance log lost when offline, the staff will perceive the system as unreliable. That is a failure of any job which works offline frequently.

What: Local-first data architecture: All information is stored in device storage and is only transferred to the cloud on an on-demand basis. The user is presented with the offline state but not prevented to work. Any outstanding updates are automatically updated upon regaining connectivity.

UX Principles

The above ideas about designs are transformed into a concise guide to be used in decisions about the products during development. All of the rules are based on actual user research. They must be used as a limiting element in the design, and not merely wishful thinking that can be sacrificed when time is of short supply or money is limited.

01. Elastic Pricing as UX

Why: Fixed prices can easily cause people to be angry when half the rooms are occupied. The product should demonstrate that the cost is not only fair, but clear as well not only stated in a contract.

What: Price bands varying according to occupancy are seen by the owner. There is real-time tier status, occupancy trend, and the estimated monthly fee shown on the dashboard.

02. One Role, One Interface

Why: Multipurpose interface that combines all the functions makes people deal with much of what they do not require.

What: Provide a distinct experience to each job. Only tasks, device settings, and environment are contained in it, based on that role.

03. Three-Interaction Maximum

Why: Field employees weigh in new tools against the pace of their informal shortcuts. A tool with over three steps is likely to be abandoned.

What: There are three module-home-screen interactions that should be done to complete all the operational tasks. There are no additional navigational layers or confirmation dialogs

04. The Trust Standard as Real-Time

Why: Front -desk agents depend on truthful information. Status information that becomes delayed is credibility killers that can hardly be restored.

What: Room status and task completions are displayed on all the associated devices within seconds. There is a timestamp on each indicator. Offline updates are stored and are automatically updated as soon as the connection is regained.

05. Progressive Activation

Why: The greatest implementation obstacle has been the perceived complexity of rollout. Making the scope of the initial deployment to seem less significant makes individuals more willing to give it a go.

What: The basic module is functional on the first day. Other modules are automatically activated by the operator and expand at their own speed and the role-oriented onboarding takes place within the app.

06. Offline by Default

Why: The mobile staff is prone to work in offline environment. A tool that fails to function once it loses connection is not reliable to individuals who require it most of all.

What: Local first architecture. The application is fully functional offline, and it will automatically update once the connection is recovered.

07. Privacy as Interface Embarkation

Why: In the European markets, regulatory compliance and data security are some of the major purchase drivers. Assuming that these features are normal and in the shadow, gaps of trust occur.

What: Data-management controls, storage facilities, and hosting facilities are easily accessible on the operator dashboard- transparent and not well hidden in legal documents.

Implications for MVP Scope

It is not a product roadmap synthesis and this document should not be used as such. What it provides are indications of priority: obvious indicators of what problems are the most serious obstacles to adoption, and which design decisions are most appropriate to address them. In that vein, we give the following scope indicators.

Must Be Present at Launch

These are needed to be adopted. They take away existing workaround which the user is accustomed to, and they occupy operators through the initial experience

• Occupancy-band pricing should indicate to every user how his or her price is in the product. In case an operator fails to visualize his tier and the fees portrayed to him immediately, he is not able to verify whether the promise given to him is valid.

• The fastest place where mistakes occur is live room status sync between the front desk view and housekeeping and demonstrating it is the most pressing evidence that the platform functions.

• The area where current workarounds are the most successful is mobile-first housekeeping that operates without the Internet connection, and users will select it by the speed at which it operates rather than by the number of functions it provides.

• The essential reservation module is expected to complete all the procedures during a single facilitated session and without external assistance. In the case that an operator fails to get the system working independently, the decision to adopt is not made.

Out of Scope for MVP

These product directions are not mandatory, though validated, and therefore delayed to later stages:

• Analytics and demand intelligence is based on the data configuration at the very beginning, yet it is primarily built to retain rather than attract new users.

• OTA and channel manager: the fundamental reservation can be manually keyed in the period of the MVP and can still be adopted.

• Accounting integration and financial export assist in retaining the users on a long term basis though it is not required at the moment and fits in later.

Limitations

With the same care with which we do the analysis of the results, we enumerate the deficiency of this synthesis. A research study that exceeds its scope is not a sound foundation in making design choices.

Absence of Primary Research

Every insight, mental, and behavior guess of the users of this document are secondary sources. None of them interviewed, observed or tested our target users. The theoretical mental models have not been proven. Any form of decision being arrived at out of this synthesis should presuppose that primary research will occur prior to final design determinations.

Research Context Variance

The ten included studies in this synthesis were performed in numerous locations, such as Southeast Asia, Middle East, North America, and Southern Europe. We rely on them as direction to an operator setting in Central Europe. The basic technology adoption, the perception of prices, and the usability of mobile may even remain the same, but the local regulations, culture, and the rules of the market may shift priorities or introduce new challenges. These assumptions should be subject to testing by regional primary research.

Pricing System Is Demonstrative

The model of occupancy-band pricing that is explained below belongs to UX frameworks of SaaS pricing research. It is not a complete financial model. The example thresholds, fees and levels must be verified by contrasting actual operator revenues, rivalry rates and platform economics prior to arriving at a commercial determination.

This Document Precedes Validation

The synthesis was developed in between the ideation phase of the hypothesis and before primary research. It demonstrates the best possible analysis within the frames of the project, still, it is not a complete piece of evidence. Take the design directions here as unproven hypotheses that must be tested in the future, and not conclusions. This secondary synthesis will be valuable in offering a critical hypothesis and an evidence base on more effective primary research in future.

References

All the mentioned articles are open-access or can be accessed freely on ResearchGate, MDPI, SAGE Open, or publisher open-access portals. When this synthesis was made, links were made to check them.

Abou-Shouk, M., Mannaa, M. T., & Elbaz, A. M. (2021). Technology adoption in hotels: Applying institutional theory to tourism. Tourism Management Perspectives. https://www.researchgate.net/publication/341297763_Technology_adoption_in_hotels_Applying_institutional_theory_to_tourism

Amirulloh, R., et al. (2024). Digital Transformation in the Hospitality Industry: Improving Efficiency and Guest Experience. International Journal of Management, Science and Information Technology, 4(2), 428–437. DOI: 10.35870/ijmsit.v4i2.3201. https://www.researchgate.net/publication/385653120_Digital_Transformation_in_the_Hospitality_Industry_Improving_Efficiency_and_Guest_Experience

Dirsehan, T., & Yüksel, M. (2025). Gaining Ground: How Technology Fuels Hotel Competitiveness — A Systematic Review of the Literature. Journal of Hospitality and Tourism Technology. https://www.tandfonline.com/doi/full/10.1080/21568316.2025.2534903

Fornells Herrera, A., Paradela Morgan, A., & Ficapal Mestres, J. (2024). Navigating the Technological Landscape in Hospitality: Added Values and Entry Barriers of Technologies 4.0. SAGE Open, 14(4). DOI: 10.1177/21582440241296237. https://journals.sagepub.com/doi/full/10.1177/21582440241296237

Mohd Noor, N., et al. (2023). A Study on the Impact of Innovative Technologies in the Hospitality Industry. ResearchGate / Journal of Hospitality and Tourism Research. https://www.researchgate.net/publication/374117091_A_Study_on_the_Impact_of_Innovative_Technologies_in_the_Hospitality_Industry

Nanu, L., et al. (2024). Digital transformation in the hospitality industry: A bibliometric review from 2000 to 2023. International Journal of Hospitality Management, 123, 103937. DOI: 10.1016/j.ijhm.2024.103937. https://www.sciencedirect.com/science/article/abs/pii/S0278431924000732

Nguyen, T. T., et al. (2023). Determinants of Digital Transformation in the Hospitality Industry: Technological, Organizational, and Environmental Drivers. Sustainability, 15(3), 2736. MDPI Open Access. DOI: 10.3390/su15032736. https://www.mdpi.com/2071-1050/15/3/2736

Okonkwo, C., et al. (2024). Dynamic SaaS Pricing: Implementing Usage-Based Models for Enhanced Customer Value. European Modern Studies Journal, 9(4). https://www.researchgate.net/publication/390498502_Dynamic_SAAS_Pricing_Implementing_Usage-Based_Models_for_Enhanced_Customer_Value

Rahman, M., & Hossain, R. (2024). The Performance of Hotel Management System Using Microservices and Containerization Technology. ResearchGate (peer-reviewed). https://www.researchgate.net/publication/377485627_The_Performance_of_Hotel_Management_System_Using_Microservices_and_Containerization_Technology

Weinert, S., Gräf, L., & Schulz, A. (2018). Adoption of Cloud Computing in Hotel Industry as Emerging Services. ResearchGate / Springer Proceedings. https://www.researchgate.net/publication/323753831_Adoption_of_Cloud_Computing_in_Hotel_Industry_as_Emerging_Services

The meeting room was full of men who had spent more years in insurance than I had spent being alive. It was April, and the higher-ups wanted the whole thing decided in April. On the table sat my laptop, and on the laptop sat a prototype, a clickable ghost of a product that existed nowhere else. Behind it there was nothing. No code, no database, no development team assigned. I was the most junior person in the building, by a margin nobody bothered to measure, and I was there to show a table of veterans whether something they quietly doubted could be done at all.

I had joined a software services company in 2022 as a junior designer, mostly because my portfolio was thin and I wanted one serious project in it. Within a few months I was carrying four at once, which is normal enough for a junior at an agency. Then the senior designer fell severely ill and had to travel abroad for treatment, and there was no second senior to absorb what he left behind. Three of my projects I could keep on their feet. The fourth was the one I quietly dreaded, the hardest of them by a long way, and it is the reason I am writing any of this down.

The client was a prominent, long-established insurance company, the kind of institution where decisions move slowly and paper moves slower. They wanted to modernise their website, and the centrepiece of that was a set of premium calculators. A premium calculator is a small, unglamorous tool. A customer enters a handful of facts about what they want to insure, and the tool returns what the policy would cost. Described like that, it sounds like an afternoon of work. In reality it was several completely different products wearing the same plain face, each with its own logic and its own exceptions, and all of that logic lived in one place, the company’s old paper documentation of its insurance rules, pages photocopied so many times the letters had gone soft at the edges. I doubt anyone in that building had read the whole thing in years. To design something that actually held together I would have to, so I spent the next several weeks doing exactly that, reading every page.

That reading is where the project stopped looking simple. Take motor insurance, the deepest of the calculators. Before a single price can appear, the logic splits on whether the customer wants comprehensive cover or only act liability, which in plain words is the difference between protecting the car itself and carrying the bare legal minimum. Then it splits again on whether this is a first policy or a renewal, then on what kind of vehicle it is, a private car, a commercial vehicle, a motorcycle, because each category reads from a different part of the rulebook. From there it wants the vehicle’s price, the number of passengers, the dates the policy will run, whether the person behind the wheel is the owner or a paid driver, whether the vehicle carries a tachometer or a tracking meter. And then comes the strangest part, a menu of risks the customer can choose to give up. Decline cover for riot and strike damage, for flood and cyclone, for earthquake, and each refusal shaves its own specific fraction off the rate, and several of them can be stacked together. What a customer would meet as a short form was really a decision tree with dozens of branches, and each branch traced back to a line somewhere in those soft photocopied pages.

The other calculators were different animals with the same temperament. Cash-in-safe insurance, the cover for money kept in a vault, cared who you were, a bank, a business, a private company, and where the building stood, and how much cash the vault could hold, and which category the location fell into for what the documents called Strike, Riot and Civil Commotion, the clause covering damage from unrest. Then it asked a question I have never forgotten, because it felt like the rulebook reaching out to touch the physical world. What is the building made of. Full concrete counted as one class, brick walls under a metal-sheet roof as another, full metal sheet as a third, and each pulled a different number out of the book, because a vault is only as safe as the walls around it.

This was the texture of the whole assignment, hundreds of small, stubborn rules written for clerks, now needing to be reshaped into something a stranger could walk through alone, with the machinery kept out of sight. And this, I slowly understood, was exactly what made the people above me hesitate. The officials I would eventually face were largely in their sixties. They had administered these rules across whole careers, and they knew better than anyone how tangled the thicket really was. Their hesitation was a form of expertise.

There is a name for what was happening in that hesitation. In 1961, Daniel Ellsberg described something odd and very human about how we handle the unknown, an effect now called ambiguity aversion. Offered a gamble with known odds and a gamble with unknowable odds, people reliably take the known one, even when the mystery might pay better. What truly unsettles us is the bet we cannot see, the one with odds nobody can name. The room I was preparing for was a live demonstration of it. Nobody could put odds on this project. The thing being asked to exist had never existed there before, the only person holding both the rulebook and the design in one head was a junior, and the cost of finding out was a real team for a real stretch of months. They had a harder question than whether they liked any particular design, and it was the one holding everything still. Could this much complexity become a usable tool at all.

Against that kind of fog, a description is worthless. You can stand in front of cautious people and talk about an unbuilt thing for an hour, and to a skeptic the words are just weather. So it had to be shown. I built a working, clickable prototype, end to end, every calculator, every branch I had pulled out of the paper. Then I sat in meetings with men who could have retired before I learned to write, and I walked them through it. Pick a vehicle. Choose comprehensive. Decline the flood cover and watch the rate move. Nobody had to take my word for anything. There was a thing on the table, and it either held together under their hands or it did not.

It held. And somewhere in those meetings the question changed. It stopped being whether this could work and became when they could have it, which is the entire distance between a stalled project and a funded one, crossed without a single line of production code being written. That is when I understood what I had actually been making all those weeks. The prototype’s real product was never the screens. It was certainty. The ideas were there, and engineers could be on it within a week. What no one had been able to buy, at any price, was confidence, and a prototype is a machine for producing exactly that. It turns an unknowable risk into a visible one, something you can poke at and put a number on, and that is what let’s careful people say yes.

I think about that spring often now, because the part of the work that produced the screens is exactly the part that has since become cheap. Code can be generated. Layouts can be generated. If the building had been the valuable part of what I did, that value would already be gone. But the building was the last and least of it. What could not have been handed to anyone, or anything, was the months of understanding underneath. Reading a rulebook nobody else would finish, holding all of its branches in one head, knowing which complexity the customer needed to see and which needed to disappear, and knowing the room well enough to turn all of that into a calm walk-through for people with every reason to doubt. The scarce work, then and now, is the understanding that turns a risky fog into something people will commit to. I say this with no anxiety about machines. It is simply where the difficulty lived.

The same machine has a darker setting. A prototype can manufacture confidence it has not earned. A slick demo for something that cannot actually be built is its own kind of lie, and a persuasive junior with a laptop is, in the wrong hands, a dangerous instrument. I was improvising at the edges, and I knew it. What made the confidence in that room legitimate was that every screen they clicked traced back to a clause I had actually read, and every branch of the logic was real before it was pretty. The certainty I sold them was certainty I had gone and gotten myself, first. Let those two things drift apart, and the same tool that earns trust quietly starts to steal it.

Once you see this pattern you find it everywhere people try to move cautious institutions. The founder pitching a company that is mostly conviction and slides. The architect who builds a scale model so a committee can lean over a future block of the city. Each of them is performing the same conversion I stumbled into that spring, turning somebody else’s ambiguity into a risk that can be looked at, and the future tends to go to whoever does that honestly, more often than to whoever merely had the best idea. Making an unbuilt thing feel real and safe enough to commit to is its own discipline, and I have come to think it is a steadier one than most of what we call skill.

The strangeness of that April has never quite worn off. The youngest person in the building, holding a thing that was not real, lending a room of veterans the confidence to make it real. The calculators got built, and like all software they have been changed since and will eventually be replaced. The understanding that let everyone begin is the part I still carry, and I suspect it was the part that mattered all along.

To do product work well, you have to understand a problem better than the people who handed it to you. That is the part of the job I love most, and now and then it rewards you in a way no one asked for. You go looking for the answer to one question and find a larger one sitting right next to it. That is what happened to me on Mallorca.

I am a freelance product designer. A while ago I took on a narrow, specific brief in Mallorca’s real estate market, the kind of thing you are hired to deliver, and I delivered it. But to do it properly I had to learn how property actually changes hands on the island, who buys it and through whom. The deeper I went, the more one pattern kept surfacing, something the brief never mentioned and that I could not unsee once I had noticed it. When the work was done, I went back and pulled on the thread. This is where it led, and I think it is worth your time whether you build products, invest in them, or have only ever tried to buy a home and wondered why the whole process felt as though it was working against you.

For anyone who has never been, Mallorca is a Mediterranean island off the eastern coast of Spain, all turquoise water and pale limestone hills, and for most of a century it has been one of the places wealthy northern Europeans most want to own a piece of. Hold that picture, because the island turns out to be an almost perfect specimen. Every flaw in the way we buy property is magnified here until it is impossible to miss.

The method is the part of this I most want to pass on. When the pattern first caught my eye, I did not trust it. A hunch from a single project is just a hunch. So, before I let myself get excited, I went to find out whether what I had seen was real or whether I had simply invented it, and I did that by reading, rather than by running interviews or surveys. There is decades of careful academic work on how housing markets behave, and a long public trail of transaction data from Spain and the Balearics. Real estate, it turns out, is one of the most stubbornly inefficient markets in the modern economy and has been studied as such for a long time. Primary research matters but run too early it mostly hands you back your own assumptions wearing a lab coat. The existing work is free to anyone willing to sit with it, and most people rush past it straight to users. I think that is backwards. You earn the right to ask good questions by first learning what is already known. The pattern I had spotted turned out to be one of the best-documented problems in the field.

The numbers alone are striking. The Balearics are the most international property market in Spain by a wide margin. Depending on whose figures you read, foreign buyers have accounted for somewhere between a third and 40% of every home sold there in recent years, against a national average closer to 12%. Spain’s notaries put the 2024 share at about 42%. Many of those buyers are wealthy, often paying entirely in cash, frequently buying from another country without ever moving there. The squeeze on locals is just as measurable: by the notaries’ own affordability index, a family in the Balearics has to stretch far harder to buy a home than the average Spanish household. If the process of buying a home is broken anywhere on earth, this is the place you would expect to notice it first.

The research is strikingly consistent about where it breaks, and it nearly always comes back to one thing. Real estate is the textbook case of what the economist George Akerlof called a market for lemons, a market where one side knows far more than the other. The seller knows what a property is really worth and what is quietly wrong with it. The buyer does not. Almost everything else grows out of that single imbalance. On Mallorca there is no clean public record of what homes have actually sold for, so the market price becomes, in practice, whatever an agent can say with a convincing face. The same villa shows up on five agencies’ sites at three different prices, photographed in three different years, and the buyer is left to untangle the noise by hand. People commit a million euros, often several, to a house they have never stood inside, in a country whose language and law they do not speak, on the word of a stranger whose income depends on the sale closing. To check what actually matters, whether the seller truly owns it and owes nothing hidden against it, whether it was ever built legally, they must navigate a foreign maze of notaries and lawyers from a thousand kilometres away, every step carrying its own fee and delay, the whole thing stretching across most of a year.

Here is the part that stopped me, and the reason I came to think this was worth far more than a note in my files. None of it is only a foreigner’s inconvenience. The same fog that lets a villa sell to a buyer from abroad at an inflated price is the fog that hides true values from a young local family trying to buy a first apartment. When no one can see what anything really costs, speculation thrives in the murk, and prices drift free of what ordinary people earn. On Mallorca this has stopped being abstract. Housing is now openly called the single greatest problem facing the people who live there, prices have badly outrun local wages, and the politics have turned raw, with proposals for steep taxes on foreign buyers and outright purchase bans that European law makes almost impossible to pass. An island is quietly changing hands. The outsider and the local are standing on opposite sides of the very same broken window, one overpaying through it and the other shut out by it, and the cause beneath both is the same: a market that profits from being impossible to see clearly. At bottom it is a question of who gets to belong to a place, and once you put it that way, it becomes very hard to find anyone who thinks the current arrangement is fine.

That was the moment the whole thing finally became a design problem I could hold in one hand. What is broken is not the houses, or even the prices. It is the journey. Buying a home is still assembled out of a dozen disconnected pieces, an agent, a lawyer, a bank, a notary, an endless thread of emails, a flight or two, and the buyer is left holding every loose seam while no one is accountable for the whole. So the question I could not put down was almost insultingly simple. What if the entire journey lived in one place, and was built around the buyer’s clarity instead of the agent’s commission?

The shape of the answer, and I would insist on calling it a hypothesis rather than a plan, is a single platform that carries a buyer from the first search all the way to the keys in their hand, with verification and honesty built into every step rather than bolted on at the end. One clean, de-duplicated source of real listings and real sold prices, so the question every buyer is secretly afraid of, am I overpaying, finally has an honest answer. Distance handled with verified video and on-demand viewings, so a thousand kilometres stops being a wall. Ownership and debts and permits and condition all checked inside the platform by independent professionals, not by the seller’s hand-picked ones. The money, the single most frightening part, moved through protected escrow instead of wired off into the dark. And the close, the final signing and the handover of the keys, finished without the buyer ever once losing the thread. None of the pieces are exotic. The whole, built for this particular buyer, is what does not yet exist.

Which raises the obvious and slightly deflating question. If the gap is this clear, why has no one filled it? So I went looking for whoever might already be building it. The honest answer is that the pieces exist almost everywhere and the whole exists almost nowhere. There is serious, well-funded property technology in this part of the world. Clikalia in Spain, and the Italian company Casavo, which also operates there, have raised enormous sums on the iBuyer model, in which the company itself buys your home, sometimes within days, fixes it up, and sells it on. It is impressive, and it solves a different problem for a different person, the seller who wants a fast, certain exit, and it works because it can put an algorithmic price on a standard city flat and flip it. You cannot price-and-flip a one-off villa with a sea view that way, and it does nothing for the remote buyer’s journey. The American story is even more telling. Opendoor still runs the iBuyer model, but the two giants who tried it alongside them, Zillow and Redfin, both shut their home-buying arms down, in 2021 and 2022, after losing a fortune. The model that was supposed to swallow the market quietly retreated from it. Around the edges, commission-free agencies trim the fees and the big portals own the search and then hand you off. Everyone owns a slice. No one has stitched the buyer’s whole journey, from the first search to the final handover, into one trusted flow built specifically for high-value, cross-border property. That corner, where the pain runs deepest and the buyer is most often a stranger from abroad, is the one almost everyone has left alone, because it is hard and bespoke, and refuses to fit a clean flippable model. The industry can feel the direction of travel, and analysts have started calling transactional transparency the defining shift of the coming decade. But sensing a direction and actually serving this buyer are two very different things.

It is worth taking seriously, because filling that gap would help far more than the wealthy outsider it first appears to flatter. A market you can see through is safer for the foreign buyer and fairer for the local family that can finally tell a real price from a flattering one. It is also far more hostile to the speculation that feeds on confusion. Legibility does not fix everything. Prices are partly a problem of supply, and no platform builds houses. But a market that is easy to see is one that is far easier to keep honest. Solve the journey and you do more than sell villas. You make the market legible, which is the thing fairness has to stand on.

So, would it work? I do not know yet, and that is the right place for an idea this young to sit. This is where the reading runs out and the real test begins. It has to face the people it claims to help, the buyer who flew in for a viewing that looked nothing like the photographs, the local family watching their hometown drift out of reach, and the people it might threaten, the agents who may not want any of it. Then I watch for where it holds and where it breaks.

If there is a lesson in any of this, it is plainer than I would like. The brief you are handed usually sits on top of a larger system that is creating the problem, and the work only gets interesting when you go looking for that system, even though no one hired you to. So go deep enough to understand a problem better than the people who handed it to you, and trust the pattern that keeps surfacing, as long as you test it against what is already known before you let yourself fall for it.

And there is a harder lesson sitting underneath the first one. Notice which problems tend to survive the longest. The ones that last are usually the ones that pay someone to keep them out of sight. Mallorca is an extreme case, beautiful enough that the damage is easy to look past, but the shape of it is everywhere. Any market or institution that profits from being hard to see is quietly moving something from the people who cannot see it to the people who can. The real work, more often than not, is the slow and unglamorous business of making one of those things visible. Mallorca handed me one. What stays with me is how rare it turns out to be, the plain act of looking clearly at something everyone has quietly agreed to stop seeing.

There is a small motion most of us make before we are fully awake. The hand reaches for the phone on the nightstand, the thumb finds the screen, and a feed is already moving before the day has formed a single thought. I do this. I suspect you do too. What interests me is how little it feels like a decision. It feels closer to gravity, a pull that was already there when we opened our eyes.

It has become fashionable to describe that pull as a trick, something engineered into our devices by people who want our time and have learned how to take it. There is truth in that, and I will come back to it. But the explanation that begins and ends with manipulation has always struck me as a little too easy, and a little vain. It assumes the pull is new. It assumes that before the glowing rectangle we were free, and that something was done to us. The longer I have worked in this field, designing the products people come back to, the more I have come to suspect the opposite is true. The pull is one of the oldest things about us, and the screen has only learned to find it.

It has become fashionable to describe that pull as a trick, something engineered into our devices by people who want our time and have learned how to take it. There is truth in that, and I will come back to it. But the explanation that begins and ends with manipulation has always struck me as a little too easy, and a little vain. It assumes the pull is new. It assumes that before the glowing rectangle we were free, and that something was done to us. The longer I have worked in this field, designing the products people come back to, the more I have come to suspect the opposite is true. The pull is one of the oldest things about us, and the screen has only learned to find it.

We form attachments to whatever rewards us, and we form them whether we approve or not. A path worn across a lawn where the pavement took too long to get somewhere. A chair that, over a few months, quietly becomes your chair. Most of how a life runs is habit, the patient machinery underneath the few choices we actually stop to weigh. Desire belongs to that same machinery, and it is the texture of being alive rather than a defect to be corrected. So when a product makes someone want to return to it, it is speaking the first language any of us ever learned. The wanting, on its own, is not the problem.

What that language runs on turned out to be stranger than I expected when I started reading the science behind it. For a long time people assumed that dopamine, the brain chemical everyone files under pleasure, was released when something good arrived. The reward shows up, the chemical floods in, we feel good, we go back for more. A neuroscientist named Wolfram Schultz spent years in the early 1990s recording from single cells in the brain to watch this happen, and he found something that did not fit. The cells fired hardest when the reward arrived as a surprise. Deliver the same reward on a predictable schedule and the signal faded. Dopamine was tracking the gap between what was expected and what actually occurred.

That small fact rearranges a great deal. The chemistry of wanting is tuned to uncertainty. A reward you can perfectly predict barely moves it. A reward that might come, one you cannot quite forecast, lights it up. This is why a feed you checked five minutes ago can pull you straight back. There might be something new. The wanting lives in the not knowing, in the unanswered question of what you will find, and it is strongest exactly where the outcome is least certain.

Then there is a second finding, and this is the one I keep returning to, because it changes how you see your own behavior. Two researchers, Kent Berridge and Terry Robinson, spent decades pulling apart what we lazily fold together as enjoyment. Most of us assume that wanting something and liking it are the same event, two words for a single feeling. Their work suggests they run on separate systems in the brain, and that those systems can come apart.

You can want something intensely and barely like it once you have it.

The wanting can outlive the liking entirely.

Everyone has felt this without having the words for it. The app you open out of a reflex you cannot quite explain and close a moment later feeling slightly worse. The scroll that was never really enjoyable and was somehow hard to stop. That hollow quality is the visible seam where wanting has been pried apart from liking, and the person feeling it has done nothing wrong to deserve it. Once you know the seam is there, you cannot stop seeing it, because it points straight at the question every maker of these products has to answer, honestly or not. Does the thing you are building deepen the wanting and the liking at once, or has it learned to manufacture the wanting while quietly letting the liking drain away?

The methods are not secret and they are not complicated. Most habit-forming products run on a loop that is simple to describe. Something prompts you to act, a notification, or just the flicker of boredom in an empty minute. The action is made as effortless as the designer can make it. What comes back in return is variable, a little more some times and a little less others, never quite the same, which keeps the whole thing balanced on the uncertainty that wanting is tuned to. Then you put something of your own in, a post or a saved preference, and that gives the product a reason to reach for you again.

None of this is sinister by itself. It is the same loop that sits underneath a tool you would genuinely hate to lose. The loop has no conscience. It points wherever the person building it decides to point it.

So the real question was never whether to use these mechanisms. Anyone serious about making something people love is already using them, by craft or by instinct, because a product that no one returns to is a dead one, whatever else you might want to call it. The real question is where the line runs, and it runs right along that seam. A product earns its place when the wanting it creates stays roughly honest to the liking it delivers, when the person who keeps coming back would, in a clear and unhurried moment, be glad they had. It becomes something colder when it works to widen the gap, when it gets very good at pulling people toward an experience that leaves them a little emptier each time, and pulls anyway.

It would be easy to turn this into a sermon, and the truth is more demanding than a sermon. Almost anyone can make something compelling. The levers are well known, and a capable team can ship a product that is hard to put down within a few months. That part does not impress me. What separates a designer who is merely effective from one who is genuinely good is the ability to feel where compelling tips into corrosive, and to stop there on purpose, even when pushing past it would move the numbers in the right direction for a quarter. That sense is hard won, and it tends to come from one particular kind of experience: paying close attention to what your product actually does to the people who live with it.

I learned to see the seam on a product I worked on, a database for searching property listings, the kind of thing people open when they are trying to find somewhere to live. We had built a solid search, and then we built the part that brought people back, an alert that fired whenever a new listing appeared that matched a search someone had saved. It worked. Every number we had agreed to care about moved the way we wanted. People opened the alerts. They came back several times a day, and their visits got longer. By every measure on the dashboard the feature was a success, and for a while I was proud of it.

What I noticed later was simpler than the dashboard made it look. The product was very good at bringing people back, and not nearly as good at helping them find a place to live. The same people came back week after week, opening the alert and scrolling the new listings, and a home never seemed to arrive at the end of it. The alert had learned to produce the wanting. It was doing almost nothing for the liking.

There was a proposal to push the alerts harder and to loosen the matching so there was always something new to show, along with a small line telling you how many other people were looking at the same place right now. The numbers said all of it would lift engagement again. I argued against most of it, because by then I could see what the people on the other side of the screen could not. They felt a pull and took it for their own desire. I could see it sitting on a chart, the distance between how often they came back and how little it was helping them. Once you have seen that distance with your own eyes, you stop being able to call the choice the user’s.

And it is not only me, or only that one product. If you want a sign of how real and how widely felt this line is, look at the people who build these things and how they behave at home. Not long after the first iPad came out, the reporter Nick Bilton asked Steve Jobs whether his children loved it. Jobs said they had not used it, and that the family kept firm limits on how much technology the kids used at home. The detail spread quickly because of the irony, and the irony is the point. A striking number of the engineers and executives who design for everyone else’s endless attention are quietly strict about the same products inside their own homes. The most generous reading, and I think the right one, is that these are people who can see the seam from the inside, and that seeing it changes what they are willing to do.

None of this is only about software. The gap between wanting and liking is older than any product, and it runs through far more of a life than the hours we spend on our phones. People give years to a promotion, or to a number in a bank account, sure that arriving will feel like something, and then arrive to a quiet that surprises them. A good deal of our private unhappiness may come from mistaking the pull of a thing for proof that it will be good to have. We seem to be built to chase the horizon, and the chase can feel more alive than the having ever does. That does not excuse anyone who profits from the chase. If anything it raises the stakes, because the gap was already in all of us long before any product arrived, and what the maker decides is whether to widen it or to handle it with some care.

Which brings me back to the morning, and the hand reaching for the phone before the mind has caught up to it. I do not think the answer is guilt, or pretending desire is an enemy. I love making things people are drawn to, and I have spent my career doing it. The question I have learned to carry is just narrower, and far less comfortable. It is not whether I can get someone to come back. It is whether, looking back from somewhere further along in their life, they would be glad this thing had taken the hours it took from them.

Winning a person’s attention turns out to be the easy part.

The harder test, and the one I think actually matters, is the quieter verdict they would reach much later, once the pull has worn off and only the honest residue of the time is left. Build toward that, and a surprising number of the hard decisions stop feeling hard.

Back in 2023 I used AI the way most designers did, just to ideate. It helped me get unstuck, draft a line of UX copy, throw ideas at the wall and see what stuck. Useful, but nothing I would have called important.

A few years later it sits inside almost everything I do as a freelancer. Research synthesis, data analysis, the rough first pass of my wireframes. GPT and Claude took the parts of the job that used to eat whole weeks and made them quick, and I don’t think I’m overstating it when I say they changed what one person can ship.

Two changes stand out. The first is research. I can read across what feels like a thousand papers, pull out the patterns, and put together a few different versions of a user journey before I have drawn anything at all. I understand the product earlier, and more honestly, than I ever could back when research meant five interviews and a lot of hoping.

The second is the wireframe. If I build an interaction-first version before I open the visual file, I can settle the flows and the components while they’re still cheap to change. The bones are set before anyone argues about color.

All of that gave me a kind of confidence I didn’t have before. The honest version is that I ship work now that feels twenty or thirty times better than what I made on my own a few years ago. So no, I’m not here to tell you AI is killing design. It made me better. That’s where I have to start.

And yet. Open any design group right now and you can feel the panic. The loudest posts say the same thing in different fonts: AI makes gorgeous interfaces in minutes, the job is finished, go home. In my own country I’ve watched senior designers tell people who haven’t even started yet to quit. To pick something safer. To give up before the first real attempt.

Some of that is fair. A founder who once needed a small tech team to get an MVP out the door can now do a good chunk of it with AI. That’s genuinely happening and pretending otherwise would be silly.

But most of the doom isn’t analysis. It’s reach. The post does well precisely because it scares people, and the cost of that lands on someone none of us ever meet: the beginner who quietly shuts the laptop and decides the door is closed. We are talking people out of a future to win a little attention, and the argument was never that clean to begin with.

Yes, you can make something beautiful in minutes now. I won’t argue with that. But a beautiful screen and a working product are not the same thing, and anyone who has actually shipped one knows the size of the gap between them. Products get good slowly. Someone notices a small friction, the team argues about it, gets it wrong, tries again. Do that a few hundred times over a few months and you end up with something more than a layout. You end up with judgment sitting inside the interface.

That’s the part I kept calling soul, though I think I had the wrong word for it for a long time. It was never that AI work looks bad. A lot of it looks great. Clean, fast, polished. What it skips is the why. Why this tradeoff and not the other one. Why this flow makes sense for the specific, distracted person who is going to use it on the worst day of their week. AI will hand you a thousand reasonable answers in an afternoon. It still can’t tell you which one is true for these people, in this place. That call comes from someone who has sat with the problem long enough to have an opinion worth trusting.

For years you needed a trained eye to feel the difference between work made with care and work made without it. What I notice now is stranger. People want the human signal back. I keep seeing teams quietly drop “AI-powered” from the way they describe themselves, because the phrase started to read as the opposite of considered. The market is asking for fingerprints again, and to me that’s the clearest sign yet that the human part of this work is going up in value, not down.

So here is what I think AI actually did. It didn’t take the work away from us. It raised the floor under it. It took the slow, expensive parts and made them nearly free, which means you now have almost endless ways to fix a person’s experience, and you can reach most of them fast. But the soul of a design never lived in those parts. It lives in the conversation, the slow back-and-forth between people who see the problem from different sides and argue their way toward something deliberate. A design that looks like it was made with attention usually was. There is no shortcut into that room, and AI hasn’t found one yet.

Which is why the panic is pointed the wrong way. AI got better at everything around the human core, so the human core matters more now, not less. The beginners being told to leave are being pushed out at exactly the moment their taste and their willingness to actually care became the rare thing in the room.

UX is better than I ever imagined it could be when I started messing with these tools in 2023. And the soul of design hasn’t gone anywhere. It just turned into the part worth protecting. If someone tells you there’s no room left for you, listen to what they’re really saying. The easy half got automated. The half that was always the point is wide open, and it’s waiting for you.