Guess what? You probably already have a UX research department. You just don’t call it that.
When people hear the phrase “user research,” they picture moderated interviews, analytics dashboards, heat maps, A/B testing, and consultants standing behind one-way glass. Those are useful tools, and I’ve used all of them. But some of the best usability research I’ve ever seen didn’t come from a lab or a software platform. It was hanging from a screened patio on Jekyll Island, Georgia.
Last week my family was driving to Disney, and somewhere south of Savannah we decided we’d all be happier if we stopped for the night instead of pushing through. We booked a hotel on Jekyll Island from the passenger seat and spent the evening there. The next morning, before getting back on the road, we wandered toward the beach through the hotel’s outdoor dining area. That’s where I noticed something I couldn’t quite explain. Clipped to the screen every twenty feet or so were white linen napkins hanging at eye level. They weren’t folded. They weren’t decorative, and they looked completely out of place.
My first assumption was that somebody’s kids had been entertaining themselves.
Then I watched a man carrying a cooler walk toward one of the screened panels. A few feet before he reached it, one of the napkins caught his attention as it moved in the breeze. Without thinking, he adjusted his path and walked through the opening instead of into the screen. In that instant the napkins made perfect sense. Someone had discovered that guests kept walking into nearly invisible screens and solved the problem with whatever happened to be nearby.
For me, the napkins aren’t the story. They’re evidence of something much more interesting. They reveal where useful innovation usually comes from and why so many organizations fail to capitalize on it.
We have a tendency to romanticize innovation as something that happens during strategy sessions or product planning meetings. We imagine breakthroughs beginning with vision and ending with execution. Reality is usually far less glamorous. Most innovation starts because somebody got tired of dealing with the same problem every day. They stopped waiting for permission, grabbed the closest available tool, and made life a little easier. The napkins weren’t an act of design as much as they were an act of necessity. Somebody probably got tired of repairing or replacing torn screens and realized that making the screen visible would prevent the damage altogether.
Don Norman’s work on affordances and signifiers gives us language for what happened. The screen already performed its intended function. It kept insects out. What it failed to do was communicate its own presence. The napkin became the signifier. It announced what had previously been invisible. Nothing about the screen changed. Only the user’s ability to perceive it did.
That’s where most people end the conversation. The lesson becomes “prototype early” or “test before you build.” They’re right, but only partially. Jakob Nielsen has argued for decades that inexpensive usability testing uncovers the majority of meaningful problems long before large budgets become necessary. Build something simple, put it in front of real people, learn what breaks, and improve it. Every experienced product designer already believes that.
The part that stayed with me happened after the experiment: Those napkins weren’t temporary anymore.
Some of them had clearly been hanging there for months. They were faded. A little weathered. The experiment had succeeded so completely that nobody ever came back to replace it with something permanent. A branded decal across the screen would have accomplished the same thing. A painted horizontal strip would have looked intentional while preserving the solution. Instead, the prototype quietly graduated into permanent infrastructure without anyone making that decision consciously. Once I noticed that, I started seeing the same pattern everywhere I walked.
Visit almost any busy restaurant and you’ll find handwritten instructions taped beside the POS because the system can’t process a certain order correctly. You’ll find laminated sheets explaining workarounds that were never supposed to become permanent procedures. You’ll find pickup shelves reorganized by individual managers because guests consistently reached for the wrong bags. You’ll find spreadsheets built by operators because the reporting software couldn’t answer the questions they actually needed answered. Every one of those solutions tells the same story. Somewhere, a system stopped serving the people using it, and the people adapted.
Those adaptations are rarely viewed as innovation. They’re viewed as clutter. And I think that’s totally backwards.
Every handwritten sign represents a problem that has already been identified. Every workaround represents an idea that has already survived contact with reality. Someone has already tested it under actual operating conditions with actual guests. The organization has already paid for the research through the daily work of its employees. What’s missing isn’t insight. It’s a process for recognizing that the insight exists.
This becomes especially important as organizations grow. A workaround in one restaurant is simply resourcefulness. The same workaround spreading quietly across hundreds of restaurants becomes an unofficial operating standard. Managers teach new managers what works. Field leaders share practical fixes from store to store. Before long, half the system is relying on procedures that exist nowhere in the official documentation. Nobody intended to create those standards. They simply emerged because reality kept rewarding them.
That’s how experiences start to fall apart.Not through dramatic failures. But through hundreds of tiny adjustments that no one ever circles back to evaluate.
This also changed the way I think about the relationship between usability and visual design. Designers often separate UX and UI as though one happens before the other. Solve the problem first, then make it beautiful. It’s a useful simplification, but I don’t think it’s an accurate description of how design actually evolves.
The napkin was already interface design. It was communicating visually. It was directing behavior. It was reducing friction. It simply wasn’t refined. The progression wasn’t UX followed by UI. It was rough solution followed by finished solution. Both stages belonged to the same design process.
That distinction matters because visual refinement isn’t cosmetic. In one of the foundational studies on what became known as the aesthetic-usability effect, researchers Masaaki Kurosu and Kaori Kashimura found that users consistently perceived better-looking interfaces as easier to use, even when the underlying functionality was identical. Subsequent research has reinforced the same principle. People extend more trust to experiences that appear intentional. They’re more patient when something feels thoughtfully designed. They assume competence before they’ve had evidence to confirm it.
Restaurant brands experience this every day. Two ordering flows can require exactly the same number of steps, but guests routinely prefer the one that feels clearer, calmer, and more deliberate. The interaction hasn’t changed. Their confidence has.
That brings me back to the napkins. The clever part wasn’t the napkins themselves. The clever part was the observation that produced them. Somebody noticed recurring friction, understood its cause, and solved it almost immediately. That’s the behavior every organization should be trying to encourage. Where they fall short is assuming the work is finished once the workaround succeeds.
It isn’t finished. The workaround is simply proof that the permanent solution deserves to exist.
The next time you visit your restaurants, don’t spend all your attention looking for problems. Look for adaptations. Photograph every handwritten instruction, every laminated reminder, every improvised shelf label, every spreadsheet living on someone’s desktop, every piece of tape covering a button that confuses guests or employees. Don’t dismiss them as operational clutter. They’re evidence. They’re your employees documenting, in real time, where your systems are asking too much of the people who depend on them.
Innovation isn’t hiding in your next brainstorming session. It’s probably already hanging on a screen door, waiting for someone to recognize that the prototype deserves to become the product.