The Problem
Next Door Photos offered 20–25+ services across 8 categories, all at once, in a single booking step. This presented too many paths for someone who is looking for 3 clear directions to choose from.
A top-producing real estate team left the platform. Not because the photos were poor. Not because the prices were wrong. Because the act of booking was too confusing. There were some key Laws of UX being violated and the results were real.
Hick's Law: more choices, longer decisions. Miller's Law: humans chunk—seven things, give or take two. Jakob's Law: users expect what they've already seen elsewhere. The booking flow violated all three simultaneously, creating a trifecta of friction.
Competitors have adopted curated Good / Better / Best package models which was the simpler and clearer experience to follow. Low friction experiences lead to higher retention.
What We Heard
We didn't conduct formal user interviews on this engagement—the timeline was four days, not four weeks. But the data spoke clearly enough.
The CEO directly stated to his team that a top-producing real estate team had just cited booking complexity as their explicit reason for leaving. That's not a usability complaint. That's a revenue event.
The competitive analysis confirmed what clients were experiencing everywhere else: simplicity wins. The industry had collectively decided that curation beats comprehensiveness. Every major competitor had drawn the same conclusion.
The Method
We began with an OOUX audit to map the problem domain, not the interface. We mapped the objects: Service, Package, Category, Booking, Client. We asked how they related and found the mismatch immediately. The interface was organized around Categories (internal logic) rather than Packages (client logic). Users were navigating the business's taxonomy, not their own intent. There was a disconnect between the represented conceptual modal and user’s expected mental model.
The object map became an X-ray into what was happening. It revealed not just what was broken, but why—a structural misalignment between how services were stored and how clients needed to encounter them. No amount of UI polish fixes a structural problem.
The Solution
We produced 3 main artifacts to provide an actionable path forward.
First, an Object Map of the problem domain—a diagram that made the invisible architecture visible. It gave Next Door Photos a shared language for discussing changes with developers and designers without the conversation collapsing into feature debates.
Second, an interactive mockup of an optimized booking flow. Not a redesign of the underlying system—that was scope we didn't have—but a proof of concept for a curated package experience. Good / Better / Best. Three paths, clearly marked. The kind of flow that respects the client's time.
Third, a report. Not a deck. A document with specific recommendations, quick wins, and a tiered implementation strategy—small scope, medium scope, large scope—so Next Door Photos could choose his level of ambition without choosing chaos.
What Changed
Delivery: we completed the engagement in 14 hours against a 20-hour estimate. The AI-assisted execution—Claude for reasoning, Claude Code for prototype scaffolding—shaved time without sacrificing quality.
Business outcomes: we set out to prevent further client loss and give Kurt a credible path forward. The top-producing real estate team was already gone. We can't recover that. But the report gave Next Door Photos a documented strategy and a working prototype they could show stakeholders.
What we didn't measure: whether Kurt implemented the recommendations. Whether the new booking flow—if built—changed conversion rates. Whether another top client left in the months after. Large engagements get KPIs. Four-day audits get artifacts. We're honest about that.
Lessons for Others
First: a lost client is a usability test you didn't schedule. When someone leaves and can articulate why, listen carefully. That complaint is a design brief.
Second: the interface is not the problem. The problem is always structural. Fix the object model first, then the screens will follow more naturally than you expect.
Third: think in objects before interfaces. Ask "what exists?" before "what should users do?" The nouns precede the verbs. Always.
Fourth: curation is a form of respect. Giving users 25 choices is not generous. It is a transfer of cognitive labor—from the business to the client. Good design absorbs that labor so clients don't have to.
Fifth: a four-day engagement can produce durable artifacts. An Object Map and a prototype are not deliverables that expire. They outlast the sprint.
Sixth: AI tools changed the math on small engagements. Work that used to require 20 hours took 14. That's not a minor efficiency gain—it's the difference between profitable and marginal.
Broader Implications
The photography services industry is not unique. Every service business with more than ten offerings faces this exact tension: comprehensiveness versus clarity. The instinct to show everything—to prove the full menu of capabilities—is understandable. It is also, consistently, wrong.
The Good / Better / Best model is not a trend. It is a convergence point. Every industry that has gone through this transition—insurance, software subscriptions, cable bundles—has landed in the same place: tiered, curated, opinionated.
OOUX offers a particular gift in these situations: it lets you see the structural problem before you spend money on surface solutions. Redesigning buttons and colors on a broken architecture produces prettier confusion. Fixing the object model first means the interface has somewhere true to go.
For small businesses especially, the risk of over-serving clients with options is existential. A real estate photographer who loses a top-producing team isn't just losing a client. They're losing a referral network, a portfolio anchor, a proof point.
The End
In the beginning, there was a booking form. It was comprehensive. It was complete. It contained multitudes—twenty-five services, eight categories, infinite combinations.
And then someone had to use it.
We came in with an object map and a four-day clock. We didn't save the client who left. But we gave the business a mirror, and a path, and a working prototype of something simpler.
Simplicity, it turns out, is not the absence of complexity. It is the decision to carry the complexity yourself, on behalf of the people you serve.
That's the work. That's always the work.
