Key Takeaways

  • Executives routinely kill design prototypes because static lorem ipsum feeds and mock accounts do not match their personal interests.
  • Reddit built Reddit Proto, an internal environment that authenticates engineers and designers with their real Reddit accounts.
  • Hooking live user data to an LLM for real-time ranking allows product teams to test novel discovery workflows in days instead of nine months.
  • Building custom Model Context Protocol (MCP) servers lets teams pull design tokens straight into Cursor to bridge visual design and live code.

Why Figma Mocks Fail Executive Reviews

Design reviews usually derail on content rather than interface mechanics. A designer creates a polished Figma board filled with generic posts, stock photography, and synthetic user profiles. When company leaders look at the screen, their immediate reaction focuses on the wrong thing.

Blair Metcalf, principal UX engineer at Reddit, watched this happen repeatedly. “The reason why that we do this is because Reddit has personalized data,” Metcalf noted. “If designers are mocking everything in Figma and then they show that to leadership, leadership's going to look at that and be like, 'What? This isn't relevant to me.'”

When a feed is personalized, mocked data breaks the illusion instantly. The reviewer cannot feel how the feature actually behaves because the data looks alien to them. They spend the meeting questioning the sample content rather than evaluating the interaction model. By running prototypes on authenticated user accounts, the reviewer sees their own communities, their own subscribed subreddits, and their own saved posts.

The Reddit Proto Method

Most software companies treat live production data as off-limits for early interface design. Host Claire Vo observed that allowing production authentication inside prototypes is rare across the industry: “I have not heard anybody say, 'Okay, go ahead and let you auth into your production data and render that,' which gives you a much more flexible set of data to work with when you're testing new features.”

Reddit bypassed this barrier with Reddit Proto, an internal environment that combines live user sessions with Cursor and custom Model Context Protocol (MCP) servers. The architecture removes Git friction for designers, injects live production tokens, and feeds live API responses into AI models.

“The nicest doodad here is that you can then use signed in data and so you'll know if your design works,” Metcalf said. “It's pulling that real data. It sends it to an LLM, ranks it, and then you can test out that design. And you don't have to take 9 months to get that into prod, see if that works. It saves so much time, and everybody can work on other things.”

Instead of writing full backend microservices to test an algorithmic discovery idea, the team pulls live search results, hands the payloads to an LLM prompt to rank or cluster, and displays the result directly in an authenticated UI.

Where This Breaks Down

This method requires clear boundaries around read and write access. Testing feed layouts and search ranking on read-only endpoints works safely. The moment a prototype allows write operations, like posting, upvoting, or sending direct messages, live authentication creates real operational risk. Accidental mutations on production accounts can pollute production databases or leak unfinished experiments to the public.

Personalized data can also hide universal edge cases. If an executive tests a prototype with an account that has thousands of interactions across ten years, the interface might look full and engaging. That same interface might look broken to a new user with zero friends, zero follows, and empty state screens.

What to Do With This

Take your company's core web application and create an isolated read-only staging route that accepts a developer session cookie. Instead of having your product team mock candidate cards, dashboard metrics, or customer activity in Figma for your next roadmap review, wire Cursor to render that single route using your founder account's real data. If the layout fails to make sense with your actual inbox or activity feed, scrap the design before engineering writes a single line of backend logic.